Configuring Isdn-To-Isdn Release Cause Mapping - AudioCodes Mediant 1000B User Manual

User's Manual
ISDN Release
Reason
87 User not member of CUG
88 Incompatible destination
90 Non-Existent CUG
91 Invalid transit network selection
95 Invalid message
Mandatory information element is
96
missing
Message type non-existent or not
97
implemented
Message not compatible with call state
98 or message type non-existent or not
implemented
Information element non-existent or not
99
implemented
100 Invalid information elements contents
101 Message not compatible with call state
102 Recovery of timer expiry
Parameter Non-Existent Or Not
103
Implemented - Passed On
111 Protocol error
112 Uknown Error
127 Interworking unspecified
* Messages and responses were created because the 'ISUP to SIP Mapping' draft doesn't
specify their cause code mapping.

25.8.3 Configuring ISDN-to-ISDN Release Cause Mapping

The Release Cause ISDN to ISDN table lets you configure up to 10 ISDN ITU-T Q.850
release cause code (call failure) to ISDN ITU-T Q.850 release cause code mapping rules.
In other words, it lets you change the originally received ISDN cause code to a different
ISDN cause code. For example, the PSTN may indicate disconnected calls (hang up) by
sending cause code 127. However, you can change the cause code to 16, which is a more
typical cause code for such call scenarios. When the device receives an ISDN cause code
from the PSTN side, it searches the table for a matching ISDN cause code. If found, the
device changes the cause code to the corresponding ISDN cause code. If the ISDN cause
code is not configured in the table, the originally received ISDN cause code is used. If the
new ISDN cause code also appears in the Release Cause Mapping ISDN to SIP table (see
''Configuring ISDN-to-SIP Release Cause Mapping'' on page 562), the device maps it to
the corresponding SIP response code, which it sends to the IP side.
Version 7.2
Description
565
SIP
Description
Response
503 Service unavailable
503 Service unavailable
503 Service unavailable
502* Bad gateway
503 Service unavailable
409* Conflict
480* Temporarily not available
409* Conflict
480* Not found
501* Not implemented
503* Service unavailable
408 Request timeout
400 Bad Request
500 Server internal error
400 Bad Request
500 Server internal error
Mediant 1000B Gateway & E-SBC
25. Manipulation