FALCOM A2
A2MAN.DOC
08 MARCH 1999
This confidential document is the property of Funkanlagen Leipoldt OHG and may not be copied or circulated without permission.
Page 43
Cause no 29: "Facility rejected"
This cause indicates that the facility requested by the Mobile Station is
not supported by the PLMN.
Cause no 30: "Unknown subscriber"
This cause indicates that the subscriber is not registered in the HLR
(i.e. IMSI or directory number is not allocated to a subscriber).
Cause no 38: "Network out of order"
This cause indicates that the network is not functioning correctly and
that the condition is likely to last a relatively long period of time; e.g.,
immediately re-attempting the short message transfer is not likely to
be successful.
Cause no 41: "Temporary failure"
This cause indicates that the network is not functioning correctly and
that the condition is not likely to last a long period of time; e.g., the
Mobile Station may wish to try another short message transfer attempt
almost immediately.
Cause no 42: "Congestion"
This cause indicates that the short message service cannot be serviced
because of high traffic.
Cause no 47: "Resources unavailable, unspecified"
This cause is used to report a resource unavailable event only when no
other cause applies.
Cause no 69: "Requested facility not implemented"
This cause indicates that the network is unable to provide the
requested short message service.
Cause no 81: "Invalid short message transfer reference value"
This cause indicates that the equipment sending this cause has
received a message with a short message reference which is not
currently in use on the MS-network interface.
Cause no 95: "Invalid message, unspecified"
This cause is used to report an invalid message event only when no
other cause in the invalid message class applies.
Cause no 96: "Invalid mandatory information"
This cause indicates that the equipment sending this cause has
received a message where a mandatory information element is missing
and/or has a content error (the two cases are indistinguishable).
Cause no 97: "Message type non-existent or not implemented"
This cause indicates that the equipment sending this cause has
received a message with a message type it does not recognise either
because this is a message not defined or defined but not implemented
by the equipment sending this cause.
