+SBDIXcommand must be used in place of the +SBDI command for applications wishing to make use of SBD Ring Alert functionality
This command initiates an SBD session between the ISU and the GSS, setting the SBD Session Type according to the type of command +SBDIX or +SBDIXA, Delivery Short Code according to the value specified by the +SBDDSC command, and the type of location according to whether the optional location value is provided. 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.
- This command will always attempt an SBD registration, consisting of attach and location update, during the SBD session in order to support SBD Ring Alert. If this is not desired, the +SBDI command should be used.
- The FA should append an ‘A’ to the command, i.e. +SBDIXA, when the SBD session is in response to an SBD ring alert.
<location> has format:
Degrees latitude (00-89)
Minutes latitude (00-59)
Thousandths of minutes latitude (000-999)
Degrees longitude (000-179)
Minutes longitude (00-59)
Thousandths of minutes longitude (000-999)
The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +.
corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.
+SBDIX:<MO status>,<MOMSN>,<MT status>,<MTMSN>,<MT length>,<MT queued>
MO session status provides an indication of the disposition of the mobile originated transaction. The field can take on the following values:
MO message, if any, transferred successfully.
MO message, if any, transferred successfully, but the MT message in the queue was too big to be transferred.
MO message, if any, transferred successfully, but the requested Location Update was not accepted.
3 .. 4
Reserved, but indicate MO session success if used.
5 .. 8
Reserved, but indicate MO session failure if used.
GSS reported that the call did not complete in the allowed time.
MO message queue at the GSS is full.
MO message has too many segments.
GSS reported that the session did not complete.
Invalid segment size.
Access is denied.
ISU has been locked and may not make SBD calls (see +CULK command).
Gateway not responding (local session timeout).
Connection lost (RF drop).
Link failure (A protocol error caused termination of the call).
20 .. 31
Reserved, but indicate failure if used.
No network service, unable to initiate call.
Antenna fault, unable to initiate call.
Radio is disabled, unable to initiate call (see *Rn command).
ISU is busy, unable to initiate call.
Try later, must wait 3 minutes since last registration.
SBD service is temporarily disabled.
Try later, traffic management period (see +SBDLOE command)
39 .. 63
Reserved, but indicate failure if used.
Band violation (attempt to transmit outside permitted frequency band).
PLL lock failure; hardware error during attempted transmit.
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.
<MT status> :
The MT status provides an indication of the disposition of the mobile terminated transaction. The field can take on the following values:
No SBD message to receive from the GSS.
SBD message successfully received from the GSS.
An error occurred while attempting to perform a mailbox check or receive a message from the GSS.
The Mobile Terminated Message Sequence Number (MTMSN) is assigned by the GSS when forwarding a message to the ISU. This value is indeterminate if the field
<MT status> is zero. This wrap around counter can range from 0 to 65535.
<MT length> :
The MT length is the length in bytes of the mobile terminated SBD message received from the GSS. If no message was received, this field will be zero.
<MT queued> :
MT queued is a count of mobile terminated SBD messages waiting at the GSS to be transferred to the ISU.