> 13.11 | AT+CNMI New short Message Indication

> The write command selects the procedure how the receipt of new short messages from the network is indicated to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving should be done as specified in GSM 03.38. If the DTR signal is not available or the state of the signal is ignored (V.250 command AT&D0, reliable message transfer can be assured by using AT+CNMA acknowledgment procedure. The rules <mt>=2 and <mt>=3 for storing received messages are possible only if phase 2+ compatibility is activated with AT+CSMS=1. The parameter <ds>=1 is only available in phase 2+
> Syntax

> Test Command AT+CNMI=?
> Response(s)
> +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

> Read Command AT+CNMI?
> Response(s)
> +CNMI: <mode>, <mt>, <bm>, <ds>, <bfr>
> OK

> Write Command AT+CNMI=[<mode>][, <mt>][, <bm>][, <ds>][, <bfr>]
> Response(s)
> OK
> ERROR
> +CMS ERROR

> Reference(s) |  | PIN |  | ASC0 | ASC1 | USB | MUX1 | MUX2 | MUX3 |  |  | Charge | Q | Last
> GSM 07.05 |  | + |  | + | + | + | + | + | + |  |  | - | + | -

> Unsolicited Result Codes
> URC 1
> <mt>=1:
> +CMTI: <mem3>, <index>
> Indicates that new message has been received
> URC 2
> <mt>=2 (PDU mode enabled):
> +CMT: <length><CR><LF><pdu>
> Indicates that new message has been received
> URC 3
> <mt>=2 (text mode enabled):
> +CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<CR><LF><data>
> Indicates that new message has been received
> URC 4
> <bm>=2 (PDU mode enabled):
> +CBM: <length><CR><LF><pdu>
> Indicates that new cell broadcast message has been received
> URC 5
> <bm>=2 (text mode enabled):
> +CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data>
> Indicates that new cell broadcast message has been received
> URC 6
> <ds>=1 (PDU mode enabled):
> +CDS: <length><CR><LF><pdu>
> Indicates that new SMS status report has been received
> URC 7
> <ds>=1 (text mode enabled):
> +CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st>
> Indicates that new SMS status report has been received
> URC 8
> <ds>=2:
> +CDSI: <mem3>, <index>
> Indicates that new SMS status report has been received
> Parameter Description

> <mode>(num)(&W)

> [0](&F)
> Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or 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 online data mode) and flush them to the TE after reservation. Otherwise forward them directly to the TE.
> 3
> Forward unsolicited result codes directly to the TE. When TA-TE link is reserved (e.g. in online data mode) the URCs are signaled according to the AT^SCFG parameters <uri>, <udri> and <urat>

> <mt>(num)(&W)(&V)

> Rules for storing received short messages depend on the relevant data coding method (refer to GSM 03.38), preferred memory storage (AT+CPMS) setting and this value.
> Note: If AT command interface is acting as the only display device, the ME must support storage of class 0 messages and messages in the message waiting indication group (discard message)
> [0](&F)
> No SMS-DELIVER indications are routed to the TE.
> 1
> If SMS-DELIVER is stored in ME/TA, indication of the memory location is routed tothe TE using unsolicited result code:
> 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:
> 3
> Class 3 SMS-DELIVERs are routed directly to the TE using unsolicited result codes defined in <mt>=2. Messages of other data coding schemes result in indication as defined in <mt>=1.

> <bm>(num)(&W)(&V)

> Rules for storing received CBMs depend on the relevant data coding method (refer to GSM 03.38), the setting of Select CBM Types (AT+CSCB) and this value:
> [0](&F)
> No CBM indications are routed to the TE.
> 2
> New CBMs are routed directly to the TE using unsolicited result code:
> 3
> Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2.

> <ds>(num)(&W)(&V)

> [0](&F)
> No SMS-STATUS-REPORTs are routed to the TE.
> 1
> SMS-STATUS-REPORTs are routed to the TE using unsolicited result code:
> 2
> If SMS-STATUS-REPORT is routed into ME/TA, indication of the memory location is routed to the TE using unsolicited result code:

> <bfr>(num)(&V)

> [1](&F)
> TA buffer of unsolicited result codes defined within this command is cleared when <mode> changes from 0 to 1...3.

> <index>(num)

> Integer type; value in the range of location numbers supported by the associated memory
> Notes

> • | Parameters <mt>=2,3 and <ds>=1 are only available with GSM phase 2+ (see AT+CSMS=1). Incoming SMs or Status Reports have to be acknowledged with AT+CNMA=0 when using these phase 2+ parameters.

> • | Requirements specific to Multiplex mode: In multiplex mode (AT+CMUX=0) only one channel can use a phase 2+ parameter. The parameter for <mt> and <ds> on the other channels have to be set to zero. If either a SM or a Status Report is not acknowledged, all AT+CNMI parameter in all channels will be set to zero.

> • | If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for routing and indicating short messages. For example, if messages shall be routed directly to one instance of the TE (set with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMER or AT+CNMI on another instance. Any attempt to activate settings that conflict with existing settings on another interface, will result in CME ERROR, or accordingly CMS ERROR.

> • | Handling of Class 0 short messages: If the host application is provided with a display and AT^SSDA=1 has been set Class 0 short messages can be displayed immediately. If the host application does not include a display, ME handles Class 0 short messages as though there was no message class, i.e. it will ignore bits 0 and 1 in the <dcs> and normal rules for exceeded memory capacity shall apply. This approach is compliant with GSM 03.38 .

> • | The parameters <ra> and <tora> will only be displayed if <ra> of the AT^SSCONF command is set to 1.

> • | If either a SM or a Status Report is not acknowledged, all AT+CNMI parameter in all channels will be set to zero.