> 13.24 | AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow

> The write command sets the overflow presentation mode.
> The read command returns the overflow presentation mode and the SMS overflow status.
> Syntax

> Test Command AT^SMGO=?
> Response(s)
> ^SMGO: (list of supported<n>s)
> OK

> Read Command AT^SMGO?
> Response(s)
> ^SMGO: <n>, <mode>
> OK
> ERROR
> +CMS ERROR

> Write Command AT^SMGO=<n>
> Response(s)
> OK
> ERROR
> CME ERROR

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

> Unsolicited Result Code
> SMS buffer change:
> ^SMGO: <mode>
> Status of SMS buffer has changed.
> Parameter Description

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

> SMS overflow presentation mode
> [0](&F)
> Disable
> 1
> Enable

> <mode>(num)(&V)

> SMS overflow status
> 0
> Space available
> 1
> SMS buffer full (The buffer for received short messages is <mem3>. See AT+CPMS.)
> 2
> Buffer full and new message waiting in SC for delivery to phone
> Notes

> • | Incoming short messages with message class 1 (ME specific short messages) or class 2 (SIM specific short messages), see <dcs> in GSM 03.38, will be stored either in ''ME'' or in ''SM'' storage. Therefore the "^SMGO: 2" indication could occur, without issuing the indication "^SMGO: 1" before. The indication "^SMGO: 1" means that both buffers (''ME'' and ''SM'') are full.

> • | For more information regarding SIM and ME specific message classes refer to <dcs> and the following specifications: GSM 03.38 and 3GPP TS 23.038 .