AT commands supported by SAGEM myX-5 mobile phones

Depending on the model of your mobile phone, a few of the following commands may not be implemented. You can check which AT commands are available on your mobile phone using the AT+CLAC command.
For more detailed informations about specific parameter or command, you should refer to the above-noticed recommendations.
--------------------------------------------------------------------------------
1.2. Implementation of indexes
SMS and phonebook entries can be stored in either SIM card or mobile phone memory. For each type of memory, a valid range of indexes are defined. These ranges may vary according to SIM / mobile phone type. For instance, + for SMS:
When the preferred memory storage is set to SM, the indexes begin from 1 to 10 (if the SIM card supports up to 10 SMS).
When the preferred memory storage is set to ME, the indexes begin from 900 to 919 (if the Mobile equipment supports up to 20 SMS).
When the preferred memory storage is set to MT, the indexes begin from 1 to 10 (if the SIM card supports up to 10 SMS) and jump to 900 to 919 (if the Mobile equipment supports up to 20 SMS).
The reason of this implementation is to have the same numbering from a mobile point of view and a TE point of view for the user.
+ for phonebook management:
When the preferred memory storage is set to SM, the indexes begin from 1 to 80 (if the SIM card supports up to 80 phonebook entries).
When the preferred memory storage is set to ME, the indexes begin from 750 to 999 (if the Mobile equipment supports up to 250 phonebook entries).
When the preferred memory storage is set to MT, the indexes begin from 1 to 80 (if the SIM card supports up to 80 phonebook entries) and jump to 750 to 999 (if the Mobile equipment supports up to 250 phonebook entries). The reason of this implementation is to have the same numbering from a mobile point of view and a TE point of view for the user.
--------------------------------------------------------------------------------
1.3. Modification of this document
The commands described in this document are subject to change without notice, and shall only be used as
a support for usual AT commands use.
--------------------------------------------------------------------------------
2. SMS SPECIFIC COMMANDS
2.1. Text Mode
2.1.1. Set Text Mode Parameters +CSMP
Command Parameters / Possible response(s)
+CSMP=[[,[,
[,]]]] Parameters
Only SMS-SUBMIT (default 17) is supported
GSM 03.40 TP-Validity-Period, in integer format
71 6 hours
167 24 hours (default)
173 7 days
255 63 weeks
GSM 03.40 TP-Protocol-Identifier in integer format
(default 0)
GSM 03.38 SMS Data Coding Scheme (default 0)
Response
OK or ERROR
+CSMP? +CSMP: ,,,
+CSMP=? +CSMP:(list of supported s),(list of supported
s),(list of supported s),(list of supported s)
--------------------------------------------------------------------------------
2.1.2. Preferred Message Storage +CPMS
Command Parameters / Possible response(s)
+CPMS= Parameters
memory from which messages are read and deleted, also
memory to which writing and sending operations are made
number of messages currently in
total number of message locations in
Response
+CPMS: ,
+CPMS? +CPMS: ,,
+CPMS=? +CPMS: (list of supported s)
--------------------------------------------------------------------------------
2.1.3. Message Format +CMGF
Command Parameters / Possible response(s)
+CMGF=[] Parameters

0 PDU mode
1 text mode
Response
OK or ERROR
+CMGF? +CMGF:
+CMGF=? +CMGF: (list of supported s)
--------------------------------------------------------------------------------
2.1.4. Message Service Failure Result Code +CMS ERROR:
0...127 GSM 04.11 Annex E-2 values
128...255 GSM 03.40 subclause 9.2.3.22 values
300 ME failure
301 SMS service of ME reserved
302 operation not allowed
303 operation not supported
304 invalid PDU mode parameter
305 invalid text mode parameter
310 SIM not inserted
311 SIM PIN required
312 PH-SIM PIN required
313 SIM failure
314 SIM busy
315 SIM wrong
316 SIM PUK required
317 SIM PIN2 required
318 SIM PUK2 required
320 memory failure
321 invalid memory index
322 memory full
330 SMSC address unknown
331 no network service
332 network timeout
340 no +CNMA acknowledgement expected
500 unknown error
511 other values in range 256...511 are reserved
512... manufacturer specific
--------------------------------------------------------------------------------
2.1.5. Service Centre Address +CSCA
Command Parameters / Possible response(s)
+CSCA=[,] Parameters
GSM 04.11 RP SC address Address-Value (SMS Service
Center)
GSM 04.11 RP SC address Type-of-Address octet
Response
OK or ERROR
+CSCA? +CSCA? +CSCA: ,
+CSCA=? +CSCA=? +CSCA: list of supported s,(list of supported s)
--------------------------------------------------------------------------------
2.1.6. List Messages +CMGL
Command Command Parameters / Possible response(s)
+CMGL[=] Parameters Parameters
integer type; value in the range of location
numbers supported by the associated memory
integer type (default 0: "REC UNREAD"); indicates the
status of message in memory; defined values:
0 "REC UNREAD" received unread message (i.e. new message)
1 "REC READ" received read message
2 "STO UNSENT" stored unsent message (only applicable to SMS)
3 "STO SENT" stored sent message (only applicable to SMS)
4 "ALL" all messages (only applicable to +CMGL command)
GSM 03.40 TP-Originating-Address / TP-Destination-Address Address-Value field in string format GSM 03.40 TP-Service-Centre-Time-Stamp in time-string
format integer type value indicating the length in
characters of the message body
GSM 03.40 TP-User-Data in text mode responses
Response
If command successful and SMS-SUBMITs and/or SMS-DELIVERs:
If = "REC READ" or "REC UNREAD"
+CMGL: ,,,,

[+CMGL: ,,,,
[...]]
If = "STO UNSENT" or "STO SENT"
+CMGL: ,,,

[+CMGL: ,,,
[...]]
Otherwise:
+CMS ERROR:
+CMGL? +CMS ERROR:
+CMGL=? +CMGL: (list of supported s)
--------------------------------------------------------------------------------
2.1.7. Read Message +CMGR
Command Parameters / Possible response(s)
+CMGR= Parameters
See command above.
Response
If command successful and SMS-DELIVER:
+CMGR: ,,,

If command successful and SMS-SUBMIT:
+CMGR: ,,

Otherwise:
+CMS ERROR:
+CMGR? +CMS ERROR:
+CMGR=? +CMS ERROR:
--------------------------------------------------------------------------------
2.1.8. Write Message to Memory +CMGW
Command Parameters / Possible response(s)
+CMGW=
text is entered
Parameters
See command above.
Response
+CMGW:
+CMS ERROR: if selected memory full
+CMGW? +CMS ERROR:
+CMGW=? OK
--------------------------------------------------------------------------------
2.1.9. Delete Message +CMGD
Command Parameters / Possible response(s)
+CMGD= Parameters
See command above.
Response
OK or +CMS ERROR:
+CMGD? +CMS ERROR:
+CMGD=? +CMS ERROR:
--------------------------------------------------------------------------------
2.1.10. Send Message +CMGS
Command Parameters / Possible response(s)
+CMGS=
text is entered
Parameters
See command above.
Response
If sending successful: +CMGS: 0
If sending fails: +CMS ERROR:
+CMGS? +CMS ERROR:
+CMGS=? OK
--------------------------------------------------------------------------------
2.1.11. Send Message from Storage +CMSS
Command Parameters / Possible response(s)
+CMSS=[,] Parameters
See command above.
Response
If sending successful: +CMSS: 0
If sending fails: +CMS ERROR:
--------------------------------------------------------------------------------
2.1.12. New Message Indications to TE +CNMI
Command Parameters / Possible response(s)
+CNMI=,,
,, Parameters
buffering mode
0 Buffer unsolicited result codes in the TA. If TA result
code buffer is full, the oldest indications may be discarded
and replaced with the new received indications.
1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the TE.
2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush them to the TE after reservation. Otherwise forward them directly to the TE.
rules for storing received SMs
0 No SMS-DELIVER indications are routed to the TE.
1 If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code +CMTI: ,
rules for storing received CBMs
0 No CBM indications are routed to the TE.
SMS-STATUS-REPORTs routing mode
0 No SMS-STATUS-REPORTs are routed to the TE.
TA buffer of unsolicited result codes behaviour
0 TA buffer of unsolicited result codes defined within this
command is flushed to the TE when 1...3 is entered (OK
response shall be given before flushing the codes).
1 TA buffer of unsolicited result codes defined within this
command is cleared when 1...3 is entered.
Response
ERROR
+CNMI? +CNMI: ,,,,
+CNMI=? +CNMI=? +CNMI: ?