Specifications

ISU AT Command Reference Phase VI AT Commands
Iridium Proprietary Version 2.45
20 June 2011 82
18 Connection lost (RF drop).
19 Link failure (A protocol error caused termination of the call).
20..31 Reserved, but indicate failure if used.
32 No network service, unable to initiate call.
33..34 Reserved, but indicate failure if used.
35 ISU is busy, unable to initiate call.
36.. Reserved, but indicate failure if used.
This instructs the GSS to disable (detach) SBD ring alerts for the calling ISU. Successful completion of the
detach command implies that the GSS has performed the requested detach action and the ISU is no longer
registered for SBD ring alerts. This session does not transfer any MO or MT messages.
Note: A user can send an MO-SBD message and request a detach at the same time by using the +SBDI
command. The +SBDI command always requests a detach.
10.13 +SBDI - Short Burst Data: Initiate an SBD Session (Revised)
Note: The +SBDI command is provided for backwards compatibility with existing FAs which do not use
SBD Ring Alert functionality. For SBD calls invoked with this command:
 The SBD session type is fixed at type 0 – MO call.
 The SBD Delivery Short Code will be the value specified by the +SBDDSC command.
 An SBD Detach is performed as part of the call.
 No SBD location update is performed.
FAs requiring SBD Ring Alert functionality should use the extended +SBDIX command.
Exec Command: +SBDI
This command initiates an SBD session between the ISU and the GSS. If there is a message in the mobile
originated buffer it will be transferred to the GSS. Similarly if there is one or more messages queued at the
GSS the oldest will be transferred to the ISU and placed into the mobile terminated buffer.
 The message, if any, in the mobile originated buffer will be sent from the ISU to the GSS.
 If there is a message queued at the GSS it will be transferred to the ISU and placed into the
mobile terminated buffer.
Command Response:
+SBDI:<MO status>,<MOMSN>,<MT status>,<MTMSN>,<MT length>,<MT
queued>
where:
<MO status>:
MO session status provides an indication of the disposition of the mobile originated transaction. The field
can take on the following values:
0 No SBD message to send from the ISU.
1 SBD message successfully sent from the ISU to the GSS.
2 An error occurred while attempting to send SBD message from ISU to GSS.
<MOMSN>:
The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by the ISU when
sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is
successfully completed between the ISU to the GSS. This wrap around counter can range from 0 to 65535.