Version 7.2 573 Mediant 800B Gateway & E-SBC
User's Manual 25. Manipulation
Parameter Description
[1] International-Level2 Regional
[2] National-Level1 Regional
[3] Network-PSTN Specific
[4] Subscriber-Level0 Regional
If you select E.164 Public as NPI, you can select one of the
following:
[0] Unknown
[1] International-Level2 Regional
[2] National-Level1 Regional
[3] Network-PSTN Specific
[4] Subscriber-Level0 Regional
SIP Phone-Context
context
[PhoneContext_Context]
Defines the SIP 'phone-context' URI parameter.
25.8 Configuring Release Cause Mapping
When a call is disconnected, the reason for the disconnection (or call failure) is sent by the
side (IP or Tel) on which the call disconnection occurred. From the IP side, a SIP response
is sent (e.g., 406); from the Tel side, an ISDN cause code is sent (e.g., 6). You can
configure ISDN-SIP release cause mapping rules, as discussed in this section.
Note: The feature is applicable only to digital interfaces.
25.8.1 SIP-to-ISDN Release Cause Mapping
25.8.1.1 Configuring SIP-to-ISDN Release Cause Mapping
The Release Cause Mapping from SIP to ISDN table lets you configure up to 12 SIP
response code to ISDN ITU-T Q.850 release cause code (call failure) mapping rules. The
table lets you override the default SIP-to-ISDN release cause mappings, listed in 'Fixed
Mapping of SIP Response to ISDN Release Reason' on page 574. When the device
receives a SIP response from the IP side, it searches the table for a matching SIP
response. If found, the device sends the corresponding Q.850 Release Cause to the
PSTN. If the SIP response is not configured in the table, the default, fixed SIP-to-ISDN
release reason mapping is used.
Note: For Tel-to-IP calls, you can also map less commonly used SIP responses to a
single, default ISDN release cause code, using the DefaultCauseMapISDN2IP
parameter. The parameter defines a default ISDN cause code that is always used,
except when the following Release Causes are received: Normal Call Clearing (16),
User Busy (17), No User Responding (18) or No Answer from User (19).