![background image](http://html1.mh-extra.com/html/3com/vcx-v7122/vcx-v7122_user-manual_440856454.webp)
454
V7122 GatewayUser Guide
A
PPENDIX
H:
R
ELEASE
R
EASON
M
APPING
This appendix describes the available mapping mechanisms of SIP Responses to Q.850
Release Causes and vice versa.
Table 97
and
Table 98
describe the existing mapping of ISDN Release Causes to SIP
Responses. To override this hard-coded mapping and flexibly map SIP Responses to ISDN
Release Causes use the parameters CauseMapISDN2SIP and CauseMapSIP2ISDN
(described in
ISDN and CAS Interworking-Related Parameters
), or using the Embedded
Web Server (see
Release Cause Mapping
).
It is also possible to map the less commonly-used SIP Responses to a single default ISDN
Release Cause. Use the parameter DefaultCauseMapISDN2IP (described in
ISDN and CAS
Interworking-Related Parameters
) to define a default ISDN Cause 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). This mechanism is only available for
Tel to IP calls.
Reason Header
The gateway supports the Reason header according to RFC 3326. The Reason header is
used to convey information describing the disconnection cause of a call:
Sending Reason header:
If a call is disconnected from the Tel side (ISDN), the Reason
header is set to the received Q.850 cause in the appropriate message (BYE / CANCEL /
final failure response) and sent to the SIP side. If the call is disconnected because of a
SIP reason, the Reason header is set to the appropriate SIP response.
Receiving Reason header:
If a call is disconnected from the IP side and the SIP
message includes the Reason header, it is sent to the Tel side according to the following
logic:
If the Reason header includes a Q.850 cause, it is sent as is.
If the Reason header includes a SIP response: (1) If the message is a final response,
the response status code is translated to Q.850 format and passed to ISDN. (2) If the
message isn’t a final response, it is translated to a Q.850 cause.
When the Reason header is received twice (that is, SIP Reason and Q.850), the
Q.850 takes precedence over the SIP reason and is sent to the Tel side.
Summary of Contents for VCX V7122
Page 28: ...28 V7122 GatewayUser Guide ...
Page 39: ...V7122 Gateway User Guide 39 Reader s Notes ...
Page 40: ...40 V7122 GatewayUser Guide ...
Page 58: ...58 V7122 GatewayUser Guide Reader s Notes ...
Page 66: ...66 V7122 GatewayUser Guide Reader s Notes ...
Page 144: ...144 V7122 GatewayUser Guide Reader s Notes ...
Page 239: ...V7122 Gateway User Guide 239 Reader s Notes ...
Page 240: ...240 V7122 GatewayUser Guide ...
Page 246: ...246 V7122 GatewayUser Guide Reader s Notes ...
Page 270: ...270 V7122 GatewayUser Guide Reader s Notes ...
Page 287: ...V7122 Gateway User Guide 287 Reader s Notes ...
Page 288: ...288 V7122 GatewayUser Guide ...
Page 294: ...294 V7122 GatewayUser Guide Reader s Notes ...
Page 300: ...300 V7122 GatewayUser Guide Figure 88 Gateway s Startup Process ...
Page 315: ...V7122 Gateway User Guide 315 Reader s Notes ...
Page 316: ...316 V7122 GatewayUser Guide ...
Page 332: ...332 V7122 GatewayUser Guide Reader s Notes ...
Page 358: ...358 V7122 GatewayUser Guide Reader s Notes ...
Page 362: ...362 V7122 GatewayUser Guide Reader s Notes ...
Page 389: ...V7122 Gateway User Guide 389 Reader s Notes ...
Page 390: ...390 V7122 GatewayUser Guide ...
Page 398: ...398 V7122 GatewayUser Guide Reader s Notes ...
Page 406: ...406 V7122 GatewayUser Guide Reader s Notes ...
Page 408: ...408 V7122 GatewayUser Guide Reader s Notes ...
Page 409: ...V7122 Gateway User Guide 409 ...
Page 419: ...V7122 Gateway User Guide 419 Reader s Notes ...
Page 437: ...V7122 Gateway User Guide 437 Reader s Notes ...
Page 452: ...452 V7122 GatewayUser Guide Figure 137 UDP2File Utility ...
Page 453: ...V7122 Gateway User Guide 453 Reader s Notes ...
Page 459: ...V7122 Gateway User Guide 459 Reader s Notes ...
Page 475: ...V7122 Gateway User Guide 475 ...