A3LA-R-MIL-MOD User Guide Version B
Document Number: 451-93156-001A
98 of 159
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
DTEs requiring SBD Ring Alert functionality should use the extended +SBDIX
command.
Exec Command: +SBDI
This command initiates an SBD session between the A3LA-R 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
A3LA-R and placed into the mobile terminated buffer.
The message, if any, in the mobile originated buffer will be sent from the A3LA-
R to the GSS
If there is a message queued at the GSS it will be transferred to the A3LA-R 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 A3LA-R
1
SBD message successfully sent from the A3LA-R to the GSS
2
An error occurred while attempting to send SBD message from A3LA-R to
GSS
<MOMSN>: The Mobile Originated Message Sequence Number (MOMSN) is a value
assigned by the A3LA-R when sending a mobile-originated message to the GSS. This
value is incremented each time an SBD session is successfully completed between the
A3LA-R to the GSS. This wraparound counter can range from 0 to 65535.