AT^SICS causes "+CME ERROR: .. temporary not allowed" on some modules | Telit Cinterion IoT Developer Community
November 26, 2018 - 11:39am, 3071 views
My BGS2-E init code causes +CME error on some modem but not on other modems.
Log right after boot, same everytime:
RX:+CME ERROR: operation of service temporary not allowed
This init code failed on this modem version:
HW model: JD
But the same init code works on:
HW model: J4
it still works when GSM jammer is on, so it doesnt have to do anything with the GSM provider
Why does the same modem firmware behave differently?
I didn't use up all the TCP serices, only the first one.
The AT^SICI reply shows that the connection profile 0 is being used. This is probably the reason of an error on modifying connection profile 0 with AT^SICS command. Are you using only one interface on which you execute the commands showed in the log or is there any other logic executed on the other interface at the same time?
Please try to detach from GPRS with AT+CGATT=0 or use other connection profile for test.
I only use one channel. So this could happen when the HW restart failed, and previous connection is retained?
Is there a SW based restart command, which would bring the modem to a clear start, if HW reset fails?
Or deletion of existing connections.
After reboot, hardware or software, any previous connection should not be retained.
You can store the connection and IP service configuration with AT^SIPS command and it can be loaded automatically on reboot. But the defined connection should not be open automatically.
You may try to reset all AT^SIPS configuration and save.
The problem was that the HW modem reset failed.
Is there a SW modem reset AT command, which sets every parameters to the default?
There is AT&F command which restores factory defaults for some but not all commands. You can see the detailed list in AT commands specification.
There is also AT&W command which can restore user settings on each start but it also has it's command list.