Event Data
Issue 1 June 2005 165
Troubleshooting
● Check Communication Manager administration (network generated the Cause Value).
- Communication Manager sent the transit network identification in the NSF IE when the
network expected it to be in the TNS IE. The protocol version on the DS1 form does not
match the near-end ISDN network that is terminating the D-channel. Contact the ISDN
network service provider and try to line up the protocols being used. NI-2 only supports
the TNS IE, while custom protocol supports use of the NSF IE for this purpose.
Cause Value 95
[0x5F/0xDF] -
Invalid message, unspecified
This Cause Value indicates an invalid message event only when no other cause in the invalid
message class applies.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Troubleshooting
The diagnostic information (DIAG) of the Cause Value should contain, if implemented, the
message type identifier of the invalid message. See Cause Values and their meanings/
interpretations on page 128.
Protocol Error Class Cause Values
Cause Value 96
[0x60/0xE0] -
Mandatory information element is missing
The equipment that sent this Cause Value Call Reference Value (CRV) received a message that
did not contain a required Information Element for the message to be parsed and processed.
Depending on which message in the call establishment sequence is missing information, a
message returned with this Cause Value might or might not indicate a problem establishing a
call.
When the public network is screening for Calling Party Number (CPN), the fact that CPN is
missing causes the network to return this Cause Value, but depending on optioning in the CO
the call might still go through.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
● Send no cause indication through the network
● Send a more generic Cause Value through the network