User Manual

Iridium Communications, Inc. Information Contained in this Guide
Iridium 9523 Product Developers’ Guide is Subject to Change Without Notice
Revision 2.6
Iridium Communications, Inc. Distribution of Guide Restricted
Proprietary & Confidential Information Page 78 of 115 to Product Developers
Only
0 Detach successfully performed
1..4 Reserved, but indicate success if used
5..14 Reserved, but indicate failure if used
15 Access is denied
Iridium 9523-reported values:
16 Modem has been locked and may not make SBD calls (see +CULK command)
17 Gateway not responding (local session timeout)
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 Iridium 9523 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 Iridium 9523. Successful
completion of the detach command implies that the GSS has performed the requested detach action and
the Iridium 9523 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.
5.7.105 +SBDI - Short Burst Data: Initiate an SBD Session
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 Iridium 9523 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 Iridium 9523 and placed into the mobile
terminated buffer.
The message, if any, in the mobile originated buffer will be sent from the Iridium 9523 to the GSS
If there is a message queued at the GSS it will be transferred to the Iridium 9523 and placed into
the mobile terminated buffer
Command Response:
+SBDI:<MO status>,<MOMSN>,<MT status>,<MTMSN>,<MT length>,<MT queued>
where: