Configuring Isdn-To-Isdn Release Cause Mapping - AudioCodes Mediant 800B User Manual
Media gateway & enterprise session border controller (e-sbc)
Hide thumbs
Also See for Mediant 800B:
- User manual (1338 pages) ,
- Installation and maintenance manual (104 pages) ,
- Hardware installation manual (56 pages)
Table of Contents
Advertisement
User's Manual
ISDN Release
Reason
85
No call suspended
Call having the requested call identity
86
has been cleared
87
User not member of CUG
88
Incompatible destination
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
111
Protocol error
127
Interworking unspecified
* Messages and responses were created because the 'ISUP to SIP Mapping' draft doesn't
specify their cause code mapping.
23.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 488), the device maps it to
the corresponding SIP response code, which it sends to the IP side.
Version 7.0
Description
491
SIP
Description
Response
503*
Service unavailable
408*
Request timeout
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
500
Server internal error
500
Server internal error
Mediant 800B Gateway and E- SBC
23. Manipulation
Advertisement
Table of Contents
