Feedback
Contents
- Configuring SIP Error Message Pass Through
- Finding Feature Information
- Restrictions for Configuring SIP Error Message Pass Through
- Information About Configuring SIP Error Message Pass Through
- How to Configure SIP Error Message Pass Through
- Configuring SIP Error Message Pass Through
- Additional References
- Feature Information for Configuring SIP Error Message Pass Through
Configuring SIP Error Message Pass Through
The Configuring SIP Error Message Pass Through feature allows an error response that is received from one SIP leg to pass transparently over to another SIP leg. This functionality will pass SIP error responses that are not yet supported on the Cisco Unified Border Element (Cisco UBE) or will preserve the Q.850 cause code across two sip call-legs.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About Configuring SIP Error Message Pass Through
SIP error responses that are not supported on the Cisco UBE include: 300--Multiple choices, 301--Moved permanently, and 485--Ambiguous.
Pre-leg SIP error responses that are not transparently passed though include:
| Error Code Received | Corresponding Error Reported on the Peer Leg |
|---|---|
| 400--Bad request | 500--Internal Server Error |
| 401--Unauthorized | 503--Service Unavailable |
| 406--Not acceptable | 500--Internal Server Error |
| 407--Authentication required | 503--Service Unavailable |
| 413--Request message body too large | 500--Internal Server Error |
| 414--Request URI too large | 500--Internal Server Error |
| 416--Unsupported URI scheme | 500--Internal Server Error |
| 423--Interval too brief | 500--Internal Server Error |
| 482--Loop detected | 500--Internal Server Error |
| 483--Too many hops | 500--Internal Server Error |
| 488-- Not acceptable media (applicable only when the call is transcoded) | 500--Internal Server Error |
How to Configure SIP Error Message Pass Through
Configuring SIP Error Message Pass Through
DETAILED STEPS
Additional References
Technical Assistance
| Description | Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Configuring SIP Error Message Pass Through
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.