- Cisco Unified Border Element SIP Support
- SIP Core SIP Technology Enhancements
- Reporting End-of-Call Statistics in SIP BYE Message
- Configurable Hostname in Locally Generated SIP Headers
- SIP Parameter Modification
- SIP Session Timer Support
- SIP-to-SIP Basic Functionality for Session Border Controller
- SIP-to-SIP Supplementary Services for Session Border Controller
- Session Refresh with Reinvites
- Configuring Cisco UBE Out-of-dialog OPTIONS Ping for Specified SIP Servers or Endpoints
- Configuring an Error Response Code upon an Out-of-Dialog OPTIONS Ping Failure
- SIP INFO Method for DTMF Tone Generation
- SIP Enhanced 180 Provisional Response Handling
- Configuring SIP 181 Call is Being Forwarded Message
- Expires Timer Reset on Receiving or Sending SIP 183 Message
- SIP UPDATE Message per RFC 3311
- Support for PAID PPID Privacy PCPID and PAURI Headers on the Cisco Unified Border Element
- Configurable Pass-through of SIP INVITE Parameters
- Conditional Header Manipulation of SIP Headers
- Transparent Tunneling of QSIG and Q.931
- SIP Diversion Header Enhancements
- SIP History INFO
- SIP Ability to Send a SIP Registration Message on a Border Element
- Configurable SIP Parameters via DHCP
- Multiple Registrars on SIP Trunks
- Additional References
- Glossary
SIP Parameter Modification
The SIP Parameter modification feature allow customers to add, remove, or modify the SIP parameters in the SIP messages going out of a border element. The SIP message is generated from the standard signaling stack, but runs the message through a parser which can add, delete or modify specific parameters. This allows interoperability with additional third party devices that require specific SIP message formats. All SIP methods and responses are supported, profiles can be added either in dial-peer level or global level. Basic Regular Expression support would be provided for modification of header values. SDP parameters can also be added, removed or modified.
This feature is applicable only for outgoing SIP messages. Changes to the messages are applied just before they are sent out, and the SIP SPI code does not remember the changes. Because there are no restrictions on the changes that can be applied, users must be careful when configuring this feature - for example, the call might fail if a regular expression to change the To tag value is configured.
In releases prior to Cisco IOS Release 15.1(3)S1, outgoing SIP messages used to have non-token characters in server and user-agent SIP headers. In Cisco IOS Release 15.1(3)S1 and later releases, server and user-agent SIP headers have only token characters. Token characters can be a alphanumeric character, hyphen (-), dot (.), exclamation mark (!), percent (%), asterisk (*), underscore (_), plus sign (+), grave (`), apostrophe ('), or a tilde (~).
The all keyword is used to apply rules on all requests and responses.
Cisco Unified Border Element
- Cisco IOS Release 12.4(15)XZ or a later release must be installed and running on your Cisco Unified Border Element.
Cisco Unified Border Element (Enterprise)
- Cisco IOS XE Release 2.5 or a later release must be installed and running on your Cisco ASR 1000 Series Router.
DETAILED STEPS
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see 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 document.
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.
Example
! ! ! voice service voip allow-connections sip to sip redirect ip2ip sip early-offer forced midcall-signaling passthru sip-profiles 1 ! ! ! voice class sip-profiles 1 request INVITE sip-header Supported remove request INVITE sip-header Min-SE remove request INVITE sip-header Session-Expires remove request INVITE sip-header Unsupported modify "Unsupported:" "timer" ! ! !
Feature Information for Configuring SIP Parameter Modification
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.
Feature History Table entry for the Cisco Unified Border Element.
| Table 1 | Feature Information for Configuring SIP Parameter Modification |
| Feature Name |
Releases |
Feature Information |
|---|---|---|
| SIP Parameter Modification |
12.4(15)XZ 12.4(20)T |
Allows users to change the standard SIP messages sent from the Cisco SIP stack for better interworking with different SIP entities. This feature introduces or modifies the following commands: voice class sip-profiles, voice-class sip profiles |
Feature History Table entry for the Cisco Unified Border Element (Enterprise) .
| Table 2 | Feature Information for Configuring SIP Parameter Modification |
| Feature Name |
Releases |
Feature Information |
|---|---|---|
| SIP Parameter Modification |
Cisco IOS XE Release 2.5 |
Allows users to change the standard SIP messages sent from the Cisco SIP stack for better interworking with different SIP entities. This feature introduces or modifies the following commands: voice class sip-profiles, voice-class sip profiles |
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.
Feedback