AL3A-RM User Guide Version B
Document Number: 451-93156-002B
103 of 172
<MO status>: MO session status provides an indication of the disposition of the
mobile originated transaction. The field can take on the following values:
Gateway-reported values:
0
MO message, if any, transferred successfully
1
MO message, if any, transferred successfully, but the MT message in the
queue was too big to be transferred
2
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
10
GSS reported that the call did not complete in the allowed time
11
MO message queue at the GSS is full
12
MO message has too many segments
13
GSS reported that the session did not complete
14
Invalid segment size
15
Access is denied
A3LA-RM-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
A3LA-RM is busy, unable to initiate call
36..
Reserved, but indicate failure if used
<MOMSN>: The Mobile Originated Message Sequence Number (MOMSN) is a value
assigned by A3LA-RM when sending a mobile-originated message to the GSS. This
