Due to the nature of wireless communications, transmission and reception of data can never be
guaranteed. Data may be delayed, corrupted (i.e., have errors) or be totally lost. Although significant
delays or losses of data are rare when wireless devices such as the Sierra Wireless modem are used
in a normal manner with a well-constructed network, the Sierra Wireless modem should not be used
in situations where failure to transmit or receive data could result in damage of any kind to the user or
any other party, including but not limited to personal injury, death, or loss of property. Sierra Wireless
accepts no responsibility for damages of any kind resulting from delays or errors in data transmitted or
received using the Sierra Wireless modem, or for failure of the Sierra Wireless modem to transmit or
receive such data.
Safety and Hazards
Do not operate the Sierra Wireless modem in areas where blasting is in progress, where explosive
atmospheres may be present, near medical equipment, near life support equipment, or any equipment
which may be susceptible to any form of radio interference. In such areas, the Sierra Wireless modem
MUST BE POWERED OFF. The Sierra Wireless modem can transmit signals that could interfere with
this equipment. Do not operate the Sierra Wireless modem in any aircraft, whether the aircraft is on
the ground or in flight. In aircraft, the Sierra Wireless modem MUST BE POWERED OFF. When
operating, the Sierra Wireless modem can transmit signals that could interfere with various onboard
systems.
Note: Some airlines may permit the use of cellular phones while the aircraft is on the ground and the door is
open. Sierra Wireless modems may be used at this time.
The driver or operator of any vehicle should not operate the Sierra Wireless modem while in control of
a vehicle. Doing so will detract from the dri
some states and provinces, operating such communications devices while in control of a vehicle is an
offence.
Limitations of Liability
implied, including any implied warranties of merchantability, fitness for a particular purpose, or
noninfringement. The recipient of the manual shall endorse all risks arising from its use.
The information in this manual is subject to change without notice and does not represent a
commitment on the part of Sierra Wireless. SIERRA WIRELESS AND ITS AFFILIATES
SPECIFICALLY DISCLAIM LIABILITY FOR ANY AND ALL DIRECT, INDIRECT, SPECIAL,
GENERAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES INCLUDING,
BUT NOT LIMITED TO, LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS OR
REVENUE ARISING OUT OF THE USE OR INABILITY TO USE ANY SIERRA WIRELESS
PRODUCT, EVEN IF SIERRA WIRELESS AND/OR ITS AFFILIATES HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES OR THEY ARE FORESEEABLE OR FOR CLAIMS BY ANY
THIRD PARTY.
Notwithstanding the foregoing, in no event shall Sierra Wireless and/or its affiliates aggregate liability
arising under or in connection with the Sierra Wireless product, regardless of the number of events,
occurrences, or claims giving rise to liability, be in excess of the price paid by the purchaser for the
Sierra Wireless product.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 2
AT Command Manual for Firmware L23
AT Commands Description
Sales Desk:
Phone:
1-604-232-1488
Hours:
8:00 AM to 5:00 PM Pacific Time
E-mail:
sales@sierrawireless.com
Post:
Sierra Wireless
13811 Wireless Way
Richmond, BC
Canada V6V 3A4
Fax:
1-604-231-1109
Web:
www.sierrawireless.com
Patents
This product may contain technology developed by or for Sierra Wireless Inc.
This product includes technology licensed from QUALCOMM® 3G.
This product is manufactured or sold by Sierra Wireless Inc. or its affiliates under one or more patents
AirCard® is a registered trademarks of Sierra Wireless. Sierra Wireless™, AirPrime™, AirLink™,
AirVantage™, Watcher™ and the Sierra Wireless logo are trademarks of Sierra Wireless.
, , ®, inSIM®, WAVECOM®, WISMO®, Wireless Microprocessor®,
Wireless CPU®, Open AT® are filed or registered trademarks of Sierra Wireless S.A. in France and/or
in other countries.
Windows® and Windows Vista® are registered trademarks of Microsoft Corporation.
Macintosh and Mac OS are registered trademarks of Apple Inc., registered in the U.S. and other
countries.
QUALCOMM® is a registered trademark of QUALCOMM Incorporated. Used under license.
Other trademarks are the property of the respective owners.
Contact Information
Consult our website for up-to-date product descriptions, documentation, application notes, firmware
upgrades, troubleshooting tips, and press releases: www.sierrawireless.com
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 3
AT Command Manual for Firmware L23
AT Commands Description
Revision
Date
Update(s)
001
May 12, 2010
Merged Revision 003 of AirPrime WISMO228 and WISMO218 AT Command
Manuals and the TCP/IP AT Command Manual for this new entity for all
commands for Firmware L20.
Added additional parameters and clarification for *PSSTKI SIM Toolkit
interface configuration.
Added command +CSNS as section 3.2.10 on page 41, and command
+WMADC as section 8.6.21 on page 156.
Removed mode=3 option of command WIPCFG in section 9.3.1 on page 169
as it does not apply to Firmware L20.
Updated section 4.3.12 on page 114to indicate “Hardware flow control is
supported as of Firmware L20 and later versions.” Same for section 8.2.
002
August 19, 2010
Updated section 3.1.7<N1> range to 1-1540.
Updated +WSVN IMEI Software Version Number command.
Updated the *PSENGI Network informationcommand‟s Neighbor cells
information mode response and added the <BSIC> parameter.
Corrected the <stat> parameter values for the +COPS Operator Selection
command.
Updated default value of the<TA_by_TE> parameter and note regarding
Hardware flow control for the +IFC TE-TA local flow control command.
Indicated that option 2 of the <mode> parameter of the *PSSTKI SIM Toolkit
interface configuration command is the default.
Added new +WLCK Network operator lock command as section 3.4.5.
Added new +PACSP Customer Service Profile query by ME command as
section 8.5.6.
Updated default for parameter <TA_by_TE> to 0x02 for sections 4.2.3 and
4.2.4 .
003
January 14, 2011
Updated the description of +WIPCFG command <opt num> 12 to indicate the
entered value represents a number of seconds, and <opt num> 13 to indicate
that the default is 0.
Added clarification that +VGR Receive Gain setting takes effect during voice
call.
Updated the +SIDET command information; in previous releases changes to
the setting were applied after reset, and now +SIDET Sidetone level settings
immediately take effect during voice calls.
Updated the clarifications for the +CGACT command.
Added the new proprietary +WGPRS command.
Added a new <mode> 3 for command +CNMI New Messages Indication to TE.
Removed the inaccurate AT+WIPDATA option from the Leaving
Continuous/Continuous Transparent Mode information, and removed
inaccurate <mode> 0.
Added a new Clarification to the +CGCLASS section and two new
Clarifications to the +CMUX Multiplexing mode section.
Updated the possible response to the *PSCCDN=? command.
Updated UDP Sockets in Continuous Mode footnote to reflect that the
maximum size of a UDP datagram has been fixed to 5904 Bytes
Document History
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 4
AT Command Manual for Firmware L23
AT Commands Description
Revision
Date
Update(s)
004
November 3, 2011
Updated the Clarification section contents for the +WLCK Network operator
lock command.
Updated the < RxLevel > and < RxLevelFull > parameter definitions, and the
<mode> 2 description, in the *PSENGI section.
Updated the <fac> table of the +CLCK command by adding the PS parameter
and updating the PN parameter.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 5
Contents
1. AT COMMANDS DESCRIPTION ....................................................................... 13
This manual presents detailed information about the AT command set used with the AirPrime WS
Series of Intelligent Embedded Modules including WISMO218 and WISMO228.
Note: There is no SIM card auto-detect mechanism for the AirPrime WS Series of embedded modules. After
the SIM card has been changed, the embedded module has to be restarted in order to detect the new
SIM card. If the SIM card is not detected by the embedded module, most of the AT Commands will
return ERROR.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 13
2. 3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Select messages service
+CSMS=<service>
+CSMS: <mt>,<mo>,<bm>
OK
+CMS ERROR: <err>
Get current service and
settings
+CSMS?
+CSMS: <service>,<mt>,<mo>,<bm>
OK
+CMS ERROR: <err>
Get supported services
+CSMS=?
+CSMS: (list of supported <service>s)
OK
+CMS ERROR: <err>
<service>
Description
0 (default)
3GPP TS 23.040 and 3GPP TS 23.041
1
3GPP TS 23.040 and 3GPP TS 23.041
(the requirement of <service> setting 1 is mentioned under corresponding command
descriptions)
<mt>, <mo>, <bm>
Description
0
Type not supported
1 (default)
Type supported
Description
Command
Possible Response(s)
Select memory
storage
+CPMS=<mem1>[,
<mem2>[,<mem3>]]
+CPMS: <used1>,<total1>,<used2>,<total2>,<used3>,<total3>
OK
+CMS ERROR: <err>
2.1. General Configuration Commands
2.1.1. +CSMS Select Messages Service
Parameters
Clarification
<service> = 1 shall be used only on dual OS platforms i.e when TE is the only SMS client (SMS are
only routed to TA in this case)
<service> = 0 shall be used by default.
The <service> parameter is automatically saved in non-volatile memory and restored to the default
value by AT&F command.
2.1.2. +CPMS Preferred Messages Storage
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 14
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Get current
storage status
+CPMS?
+CPMS: <mem1>,<used1>,<total1>,<mem2>,<used2>,<total2>,
<mem3>,<used3>,<total3>
OK
+CMS ERROR: <err>
Get supported
storages
+CPMS=?
+CPMS: (list of supported <mem1>s),(list of supported
<mem2>s),(list of supported <mem3>s)
OK
+CMS ERROR: <err>
<memx>
Description
“SM”
Only “SM” storage is supported
“BM”, “ME”, “MT”, “TA”, “SR” memory locations are not supported
<usedx>, <totalx>
Description
Integer type
Computed value
Description
Command
Possible Response(s)
Select message format
+CMGF=[<mode>]
OK
+CMS ERROR: <err>
Get current format
+CMGF?
+CMGF: <mode>
OK
Get supported formats
+CMGF=?
+CMGF: (list of supported <mode>s)
OK
<mode>
Description
0 (default)
PDU mode
1
Text mode
Omitted
Use previous value
Parameters
2.1.3. +CMGF Messages Format
Parameters
Clarification
+CMGF parameter is automatically saved into non-volatile memory.
The <mode> parameter is restored to default value by AT&F command.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 15
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Update SMSC address
+CSCA=<sca>[,<tosca>]
OK
+CMS ERROR: <err>
Get current format
+CSCA?
+CSCA: <sca>,<tosca>
OK
+CMS ERROR: <err>
Get supported formats
+CSCA=?
OK
+CMS ERROR: <err>
<sca>
Description
String type
SC address Address-Value
<tosca>
Description
Integer type
SC address Type-of-Address
Description
Command
Possible Response(s)
Select CBM types
+CSCB=[<mode>[,<mids>[,<dcss>]]]
OK
+CMS ERROR: <err>
Get current values
+CSCB?
+CSCB: <mode>,<mids>,<dcss>
OK
+CMS ERROR: <err>
Get supported
modes
+CSCB=?
+CSCB: (list of supported <mode>s)
OK
+CMS ERROR: <err>
2.2. Message Configuration Commands
2.2.1. +CSCA Service Center Address
Parameters
Clarification
This command reads and writes the service center address in EF-SMSP (U)SIM file.
If the SCA is not readable or empty, read command returns an empty string.
At switch on, the SCA is read on (U)SIM to have a default SCA for send and write command in text
mode. (In PDU mode, SCA can be provided in PDU).
Service Center Address is reset on switch on and is read on SIM on first PC connection after switch
on.
See data stored by +CSAS for default values.
2.2.2. +CSCB Select Cell Broadcast Messages Types
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 16
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
<mode>
Description
0
Message types specified in <mids> and <dcss> are accepted
1
Message types specified in <mids> and <dcss> are not accepted
<mids>
Description
String type
all different possible combinations of CBM message identifiers (refer <mid> in 27.005)
<dcss>
Description
String type
all different possible combinations of CBM data coding schemes (refer <dcs> in
27.005)
Default value: no DCS accepted
Description
Command
Possible Response(s)
Select SM
parameters
+CSMP=[<fo>[,<vp>[,<pid>[,<dcs>]]]]
OK
+CMS ERROR: <err>
Get current values
+CSMP?
+CSMP: <fo>,<vp>,<pid>,<dcs>
OK
+CMS ERROR: <err>
Test if command is
supported
+CSMP=?
OK
+CMS ERROR: <err>
Parameters
Clarification
All the <dcss> values can be accepted or up to 5 different <dcss> values can be accepted.
Ranges are not supported for <mids> and <dcss>, i.e notation "0,1,5,320-478,922" is not allowed for
<mids> and notation "0-3,5" is not allowed for <dcss> .
Up to 15 different <mids> values can be accepted.
AT+CSCB=1 means all <dcss> are accepted but this command has no effect on the list of the <mids>
accepted. To modify those lists: use before the AT+CSCB=0 command to select no mid and no dcs,
and after this operation, add some dcs or mid to the current lists.
AT+CSCB=0,<mids> adds the <mids> values in the <mids> current list handled by the mobile.
AT+CSCB=0,,<dcss> adds the <dcss> values in the <dcss> current list handled by the mobile.
not added.
AT+CSCB=1,<mids> removes the <mids> values in the <mids> current list handled by the mobile.
AT+CSCB=1,,<dcss> removes the <dcss> values in the <dcss> current list handled by the mobile.
AT+CSCB? can only display an enabled list, so <mode> = 0 is returned.
2.2.3. +CSMP Set Text Mode Parameters
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 17
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
<fo>, <vp>, <pid>,
<dcs>
Description
Integer type
Refer to 27.005 for description
Description
Command
Possible Response(s)
Select header presentation
+CSDH=[<show>]
OK
+CMS ERROR: <err>
Get current status
+CSDH?
+CSDH: <show>
OK
+CMS ERROR: <err>
Get supported values
+CSDH=?
+CSDH: (list of supported <show>s)
OK
+CMS ERROR: <err>
<show>
Description
0
Do not show header values
1
Show the values in result codes
Omitted
Use previous value
Description
Command
Possible Response(s)
Save SM service settings
+CSAS=[<profile>]
OK
+CMS ERROR: <err>
Get the list of available profiles
+CSAS=?
+CSAS: (list of supported <profile>s)
OK
+CMS ERROR: <err>
<profile>
Description
0
Save SM service settings in profile 0
Parameters
Clarification
The enhanced validity period format ($(EVPF)$, see [23.040]) is not supported.
<fo> is only for SMS-DELIVER, SMS-SUBMIT or SMS-STATUS-REPORT.
See data stored by +CSAS for default values.
+CSMP parameters are automatically saved in non-volatile memory and restored to default values by
AT&F command.
2.2.4. +CSDH Show Text Mode Parameters
Parameters
2.2.5. +CSAS Save Settings
Parameters
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 18
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
<profile>
Description
1
Save SM service settings in profile 1
Omitted
Use previous value
Command
Parameter name
+CSCA
<sca>
+CSCA
<tosca>
+CSMP
<fo>
+CSMP
<vp>
+CSMP
<pid>
+CSMP
<dcs>
Description
Command
Possible Response(s)
Restore SM service settings
+CRES=[<profile>]
OK
+CMS ERROR: <err>
Get the list of available profiles
+CRES=?
+CRES: (list of supported <profile>s)
OK
+CMS ERROR: <err>
<profile>
Description
0
Restore SM service settings from profile 0
1
Restore SM service settings from profile 1
Description
Command
Possible Response(s)
Select procedure for
received messages
+CNMI=[<mode>[,<mt>[,<bm>[,<ds>[,<bfr>]]]]]
OK
+CMS ERROR: <err>
Get current values
+CNMI?
+CNMI:
<mode>,<mt>,<bm>,<ds>,<bfr>
OK
+CMS ERROR: <err>
Clarification
Parameter stored by +CSAS
2.2.6. +CRES Restore Settings
Parameters
2.3. Message Receiving and Reading Commands
2.3.1. +CNMI New Messages Indication to TE
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 19
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Get supported
values
+CNMI=?
+CNMI: (list of supported
<mode>s),(list of supported
<mt>s),(list of supported <bm>s),(list
of supported <ds>s),(list of supported
<bfr>s)
OK
+CMS ERROR: <err>
<mode>
Description
0 (default)
Buffer unsolicited result codes in the TA.
When TA result code buffer is full:
The oldest indication is discarded and replaced with the new one when +CSMS=0
All indications are buffered when +CSMS=1
1
Discard indication and reject new received message unsolicited result codes when TATE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the
TE. Not supported for CBM messages.
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.
3
Forward unsolicited result codes to the TE by using the following specific inband
method:
While TA-TE link is reserved (meaning the TE is in online data mode by CSD or GPRS
call), unsolicited result codes are replaced by a break (100ms) and stored in a buffer.
The unsolicited result codes buffer is flushed to the TE after reservation (after +++ is
entered). If however the TE is not in online data mode, it forwards them directly to the
TE.
<mt>
Description
0 (default)
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
2
SMS-DELIVERs (except class 2 messages and messages in the message waiting
indication group (store message)) are routed directly to the TE using unsolicited result
code: +CMT
3
Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes
defined in <mt>=2. Messages of other data coding schemes result in indication as
defined in <mt>=1
<bm>
Description
0 (default)
No CBM indications are routed to the TE
2
New CBMs are routed directly to the TE using unsolicited result code: +CBM
<ds>
Description
0 (default)
No SMS-STATUS-REPORTs are routed to the TE
1
SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: +CDS
Parameters
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 20
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
<bfr>
Description
0 (default)
TA buffer of unsolicited result codes defined within this command is flushed to the TE
when <mode> 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
<mode> 1...3 is entered
Description
Command
Possible Response(s)
Acknowledge indication
if text mode (+CMGF=1):
+CNMA
if PDU mode (+CMGF=0):
+CNMA[=<n>[,<length>[<CR>PDU is
given<ctrl-Z/ESC>]]]
OK
+CME ERROR: <err>
Get supported values
+CNMA=?
if PDU mode (+CMGF=0):
+CNMA: (list of supported <n>s)
OK
if text mode (+CMGF=1):
OK
+CME ERROR: <err>
<n>
Description
0
Command operates similarly as defined for the text mode
1
Send RP-ACK (or buffered result code received correctly)
2
Send RP-ERROR
Acknowledgement TPDU not supported
Clarification
TA result code buffer is in volatile memory. Messages may get lost if the power of ME/TA is switched
off before codes are sent to TE. Thus, it is not recommended to use direct message routing (<mt>=2
or 3, <bm>=2 or 3, or <ds>=1) with <mode> value 0 or 2.
When +CSMS <service> is set to 0, all received SMS are automatically stored in SIM before +CMT or
+CMTI URC is sent to TE whatever <mt> value.
When +CSMS <service> is set to 1, depending of it class, SMS has to be acknowledged to network
thanks to +CNMA commands. Depending of <mode>, <mt> and channel status (available or
reserved) URC cannot or should not be sent to TE. In these cases SMS can be automatically
acknowledged or rejected without waiting +CNMA command.
+CNMI parameters are automatically saved in non-volatile memory.
2.3.2. +CNMA New Message Acknowledgement to ME/TA
Parameters
Clarification
This command is allowed only if +CSMS <service> is set to 1 and is used to acknowledge SMS
received from network.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 21
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
+CNMI <mt>
+CSMS <service>=0
+CSMS <service>=1
0
SMS DELIVER mode = 0
SMS DELIVER mode = 0
1
SMS DELIVER mode = 0
SMS DELIVER mode = 0
2
SMS DELIVER mode = 0
SMS DELIVER mode = 1
3
SMS DELIVER mode = 0
SMS DELIVER mode = 2
+CNMI <ds>
+CSMS <service>=0
+CSMS <service>=1
0
STATUS REPORT mode = 0
STATUS REPORT mode = 0
1
STATUS REPORT mode = 0
STATUS REPORT mode = 1
Description
Command
Possible Response(s)
List messages
with status
+CMGL[=<stat>]
if text mode (+CMGF=1), command successful:
+CMGL: <index>,<stat>,<oa/da>,[<alpha>],[<scts>]
if PDU mode (+CMGF=0) and command successful:
+CMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu>
[<CR><LF>+CMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu>[...]]
OK
otherwise:
+CMS ERROR: <err>
Routing of SMS-DELIVER and SMS-STATUS-REPORT to ME/TA depends on both +CSMS
configuration as well as <mt> and <ds> values of +CNMI.
In PDU, acknowledgement TPDU is not supported.
The following table summarizes the SMS-DELIVER notification modes according to these parameters:
When SMS Mode = 0: SMS acknowledgement and storage are managed internally by MS whatever
their class (if needed they will be stored in SIM).
When SMS-DELIVER Mode = 1: SMS with no message class, class 0, class 1, class 3 are sent to
ME/TA for acknowledgement
them. SMS class 2 & message waiting indication group (Store or Discard) are managed internally by
MS (if needed they will be stored in SIM, no +CNMA expected).
When SMS-DELIVER Mode = 2: SMS class 3 are sent to ME/TA for acknowledgement (+CNMA
class 0, class 1, class 2 & message in waiting group are managed internally by MS (if needed they will
be stored in SIM, no +CNMA expected).
Following table summarizes the STATUS-REPORT (SR) notification modes according to +CSMS and
<ds> parameters:
When STATUS-REPORT Mode = 0: MS manages SR internally.
When STATUS-REPORT Mode = 1: SR are sent to ME/TA for acknowledgement and storage.
Refer also to +CMT URC description for waiting message indication treatment.
2.3.3. +CMGL List Messages
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 22
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Get supported
values
+CMGL=?
+CMGL: (list of supported <stat>s)
OK
+CMS ERROR: <err>
<stat>
Description
0
"REC UNREAD"
Received unread message (i.e. new message)
1
"REC READ"
Received read message
2
"STO UNSENT"
Stored unsent message
3
"STO SENT"
Stored sent message
4
“ALL”
All messages
Description
Command
Possible Response(s)
Read a
message
+CMGR=<index>
if text mode (+CMGF=1), command successful and SMS-DELIVER:
+CMGR: <stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,
<sca>,<tosca>,<length>]<CR><LF><data>
OK
if text mode (+CMGF=1), command successful and SMS-SUBMIT:
+CMGR: <stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],
<sca>,<tosca>,<length>]<CR><LF><data>
OK
if PDU mode (+CMGF=0) and command successful:
+CMGR: <stat>,[<alpha>],<length><CR><LF><pdu>
OK
otherwise:
+CMS ERROR: <err>
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
Other parameters are extracted from memory storage.
Clarification
Only SMS-SUBMIT and/or SMS-DELIVER can be read.
SMS-COMMAND are not supported.
CBM are not stored in ME/TA memory. CBM are not saved in SIM.
Using the <alpha> parameter will return an empty string as this parameter is not supported.
2.3.4. +CMGR Read Message
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 23
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Test if
command is
supported
+CMGR=?
OK
+CMS ERROR: <err>
<index>
Description
1..255
Message location in “SM” memory.
<stat>
Description
0
"REC UNREAD"
Received unread message (i.e. new message)
1
"REC READ"
Received read message
2
"STO UNSENT"
Stored unsent message
3
"STO SENT"
Stored sent message
4
“ALL”
All messages
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
Other parameters are extracted from memory storage.
Clarification
Only SMS-SUBMIT and/or SMS-DELIVER can be read.
SMS-COMMAND are not supported.
CBM are not stored in ME/TA memory. CBM are not saved in SIM.
Using the <alpha> parameter will return an empty string as this parameter is not supported.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 24
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Send a message
if text mode (+CMGF=1):
+CMGS=<da>[,<toda>]<CR>
text is entered<ctrl-Z/ESC>
if PDU mode (+CMGF=0)
+CMGS=<length><CR>PDU is
given<ctrl-Z/ESC>
if text mode (+CMGF=1) and sending
successful:
+CMGS: <mr>[,<scts>]
OK
if PDU mode (+CMGF=0) and sending
successful:
+CMGS: <mr>[,<ackpdu>]
OK
if sending fails:
+CMS ERROR: <err>
Test if command is
supported
+CMGS=?
OK
+CMS ERROR: <err>
2.4. Message Sending and Writing Commands
2.4.1. +CMGS Send Message
Parameters
For all other parameters, refer to +CMT URC description.
In text mode <scts> is not supported, in PDU mode <ackpdu> is not supported.
Clarification
In text mode: entered text is sent to address <da> and all current settings (refer to sections 2.2.3
+CSMP Set Text Mode Parameters and 2.2.1 +CSCA Service Center Address) are used to construct
the actual PDU in ME/TA.
In PDU mode: <length> must indicate the number of octets coded in the TP layer data unit to be given
(i.e. SMSC address octets are excluded).
The TA sends a four character sequence <CR><LF><greater_than><space> (IRA 13, 10, 62, 32)
after command line is terminated with <CR>; after that text can be entered or PDU can be given from
TE to ME/TA.
The DCD signal shall be in ON state while text or PDU is entered.
The echoing of entered characters back from the TA is controlled by V.25ter echo command E.
In text mode, the entered text should be formatted as follows:
if <dcs> (set with +CSMP) indicates that GSM 7 bit default alphabet is used and <fo>
indicates that TP-User-Data-Header-Indication is not set: ME/TA converts the entered text
into the GSM 7 bit default alphabet according to rules of Annex A; backspace can be used to
delete last character and carriage returns can be used (previously mentioned four character
sequence shall be sent to the TE after every carriage return entered by the user);
if <dcs> indicates that 8-bit or UCS2 data coding scheme is used or <fo> indicates that TP-
User-Data-Header-Indication is set: the entered text should consist of two IRA character long
In PDU mode:
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 25
hexadecimal numbers which ME/TA converts into 8-bit octet (e.g. two characters 2A (IRA 50
and 65) will be converted to an octet with integer value 42).
The PDU shall be hexadecimal format (similarly as specified for <pdu>) and given in one line;
ME/TA converts this coding into the actual octets of PDU. When the length octet of the SMSC
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible Response(s)
Send a message
from storage
+CMSS=<index>[,<da>[,<toda>]]
if text mode (+CMGF=1) and sending
successful:
+CMSS: <mr>[,<scst>]
OK
if PDU mode (+CMGF=0) and sending
successful:
+CMSS: <mr>[,<ackpdu>]
OK
if sending fails:
+CMS ERROR: <err>
Test if command is
supported
+CMSS=?
OK
+CMS ERROR: <err>
<index>
Description
1..255
Message location in “SM” memory.
Description
Command
Possible
Response(s)
Write a message
if text mode (+CMGF=1):
+CMGW[=<oa/da>[,<tooa/toda>[,<stat>]]]<CR>
text is entered<ctrl-Z/ESC>
if PDU mode (+CMGF=0):
+CMGW=<length>[,<stat>]<CR>PDU is given<ctrl-Z/ESC>
+CMGW: <index>
OK
+CMS ERROR: <err>
address (given in the PDU) equals zero, the SMSC address set with command Service
Centre Address +CSCA is used; in this case the SMSC Type-of-Address octet shall not be
present in the PDU, i.e. TPDU starts right after SMSC length octet.
Sending can be cancelled by giving <ESC> character (IRA 27).
<ctrl-Z> (IRA 26) must be used to indicate the ending of the message body or PDU.
Text length is limited to PDU max length (164).
2.4.2. +CMSS Send Message from Storage
Parameters
In text mode <scts> is not supported, in PDU mode <ackpdu> is not supported.
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
Clarification
Since SMS-STATUS-REPORTs, SMS-COMMANDs and CBM are not stored in ME/TA memory, only
<index>s of SMS-SUBMITs and/or SMS-DELIVERs can be used in +CMSS.
2.4.3. +CMGW Write Message to Memory
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 26
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Command
Possible
Response(s)
Test if command
is supported
+CMGW=?
OK
+CMS ERROR: <err>
<index>
Description
1..255
Message location in “SM” memory.
Description
Command
Possible Response(s)
Delete a message
+CMGD=<index>[,<delflag>]
OK
+CMS ERROR: <err>
Get supported values
+CMGD=?
+CMGD: (list of supported <index>s)[,(list of
supported <delflag>s)]
OK
+CMS ERROR: <err>
<delflag>
Description
0 (default value)
Delete the message specified in <index>
1
Delete all read messages from preferred message storage, leaving unread messages
and stored mobile originated messages (whether sent or not) untouched
2
Delete all read messages from preferred message storage and sent mobile originated
messages, leaving unread messages and unsent mobile originated messages
untouched
3
Delete all read messages from preferred message storage, sent and unsent mobile
originated messages leaving unread messages untouched
4
Delete all messages from preferred message storage including unread messages
<index>
Description
1..255
Message location in “SM” memory.
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
Clarification
Text length is limited to PDU max length (164).
2.4.4. +CMGD Delete Message
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 27
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Result code
Receive a SMS
already stored
+CMTI: <mem>,<index>
<index>
Description
1..255
Message location in “SM” memory.
<mem>
Description
“SM”
Only “SM” storage possible for SMS
Descriptio
n
Result code
Receive a
SMS
if text mode (+CMGF=1):
+CMT:<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<CR><LF><dat
a>
if PDU mode (+CMGF=0):
+CMT: [<alpha>],<length><CR><LF><pdu>
2.5. SMS and CBM Unsolicited Result Codes
2.5.1. +CMTI Received SMS indication
Parameters
2.5.2. +CMT Received SMS indication
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
Clarification
When +CSMS <service> is set to 0, all received SMS are automatically stored in SIM before +CMT is
sent to TE.
When +CSMS <service> is set to 1, depending of it class, SMS has to be acknowledged to network
thanks to +CNMA commands. Depending of <mode>, <mt> of CNMI or channel status (available or
reserved) URC cannot or should not be sent to TE. In these cases SMS can be automatically
acknowledged or rejected without waiting +CNMA command.
When a +CMT URC is sent to TE for a SMS that has NOT been acknowledged by TA, a timer is
started. If timer expires (15sec) before +CNMA command is received, SMS is rejected.
When a +CMT URC is sent to TE for a SMS that has already been acknowledged by TA a timer is
started. If timer expires (15sec) before +CNMA command is received, SMS is automatically saved in
SIM (this is to not to lost an already acknowledged SMS for which +CNMA has not been received in
case of switch off). If CNMA is received before timer expiration OK is returned, else ERROR is
returned (TE knows that SMS has been stored in SIM).
Message waiting indication:
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 28
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Description
Result code
Receive a CBM
if text mode (+CMGF=1):
+CBM: <sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data>
if PDU mode (+CMGF=0):
+CBM: <length><CR><LF><pdu>
Description
Result code
Receive a CDS
if text mode (+CMGF=1):
+CDS: <fo>,<mr>,<ra>,<tora>,<scts>,<dt>,<st>
if PDU mode (+CMGF=0):
+CDS: <length><CR><LF><pdu>
There are 3 possible cases to receive voice mail notification:
TP-DCS method (STORE/DISCARD message coding groups in DCS) TP-UDH (Special SMS indication IEI in UDH of the SM) CPHS method (originating address decoding)
In all cases, the ME manages messages notifications internally (update of EF VMWI CPHS file,
In case of TP-DCS method, for message waiting indication group (store message), +CMTI is sent.
For message waiting indication group (discard message) +CMT URC is sent but no +CNMA
command is expected.
Voice mail waiting indication status are managed by *PSVMWN command.
Using the <alpha> parameter will return an empty string as this parameter is not supported.
2.5.3. +CBM Received CBM indication
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
2.5.4. +CDS Received status report (SR) indication
Parameters
For all other parameters, refer to 27.005 §3.1 Parameter Definitions.
Clarification
When +CSMS <service> is set to 0, all received SR are automatically acknowledged before +CDS is
sent to TE.
When +CSMS <service> is set to 1, SR has to be acknowledged to network thanks to +CNMA
commands. Depending of <mode>, <mt> and channel status (available or reserved) URC cannot or
should not be sent to TE. In these cases SR can be automatically acknowledged or rejected without
waiting +CNMA command.
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 29
AT Command Manual for Firmware L23
3GPP TS 27.005 Commands
Value
Description
0...127
3GPP TS 24.011 [6] clause E.2 values
128...255
3GPP TS 23.040 [3] clause 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
(U)SIM not inserted
311
(U)SIM PIN required
312
PH-(U)SIM PIN required
313
(U)SIM failure
314
(U)SIM busy
315
(U)SIM wrong
316
(U)SIM PUK required
317
(U)SIM PIN2 required
318
(U)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
2.6. +CMS ERROR Message Service Failure Result
Codes
WA_DEV_WISMO_UGD_012 Rev 004 November 3, 2011 30
Loading...
+ 185 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.