- Interworking Between RSVP Capable and RSVP Incapable Networks
- SIP INFO Method for DTMF Tone Generation
- DTMF Events through SIP Signaling
- Negotiation of an Audio Codec from a List of Codecs
- Multicast Music-on-Hold Support on Cisco UBE
- Network-Based Recording Using Cisco UBE
- Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- iLBC Support for SIP and H.323
- Configuring RTP Media Loopback for SIP Calls
- Support for Media Flow- Around with SIP Signaling control on CUBE
- Configuring Media Antitrombone
- SIP Ability to Send a SIP Registration Message on a Border Element
- SIP Parameter Modification
- Session Refresh with Reinvites
- SIP Stack Portability
- Interworking of Secure RTP calls for SIP and H.323
- CUBE Support for SRTP-RTP Internetworking
- Configuring RTCP Report Generation
- SIP SRTP Fallback to Nonsecure RTP
- Configuring Support for Interworking Between RSVP Capable and RSVP Incapable Networks
- VoIP for IPv6
- Cisco UBE Mid-call Re-INVITE Consumption
- Interworking Between RSVP Capable and RSVP Incapable Networks
- Support for Software Media Termination Point
- Cisco Unified Communication Trusted Firewall Control
- Cisco Unified Communication Trusted Firewall Control-Version II
- Domain-Based Routing Support on the Cisco UBE
SIP SRTP Fallback to Nonsecure RTP
The SIP SRTP Fallback to Nonsecure RTP feature enables a Cisco IOS Session Initiation Protocol (SIP) gateway to fall back from Secure Real-time Transport Protocol (SRTP) to Real-time Transport Protocol (RTP) by accepting or sending an RTP/Audio-Video Profile(AVP) (RTP) profile in response to an RTP/SAVP (SRTP) profile. This feature also allows inbound and outbound SRTP calls with nonsecure SIP signaling schemes (such as SIP URL) and provides the administrator the flexibility to configure Transport Layer Security (TLS), IPsec, or any other security mechanism used in the lower layers for secure signaling of crypto attributes.
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.
Prerequisites for SIP SRTP Fallback to Nonsecure RTP
Cisco Unified Border Element
- Cisco IOS Release 12.4(22)T or a later release must be installed and running on your Cisco Unified Border Element.
Cisco Unified Border Element (Enterprise)
- Cisco IOS XE Release 3.1S or a later release must be installed and running on your Cisco ASR 1000 Series Router.
Configuring SIP SRTP Fallback to Nonsecure RTP
To enable this feature, see the "Configuring SIP Support for SRTP" section of the Cisco IOS SIP Configuration Guide, Release 15.1 at the following URL: http://www.cisco.com/en/US/docs/ios/voice/sip/configuration/guide/sip_cg-srtp_ps10592_TSD_Products_Configuration_Guide_Chapter.html
Detailed command information for the srtp, srtp negotiate, and voice-class sip srtp negotiatecommands is located in the Cisco IOS Voice Command Reference http://www.cisco.com/en/US/docs/ios/voice/command/reference/vr_book.html
Feature Information for SIP SRTP Fallback to Nonsecure RTP
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 SIP SRTP Fallback to Nonsecure RTP |
| Feature Name |
Releases |
Feature Information |
|---|---|---|
| SIP SRTP Fallback to Nonsecure RTP |
12.4(22)T |
The SIP SRTP Fallback to Nonsecure RTP feature enables a Cisco IOS Session Initiation Protocol (SIP) gateway to fall back from SRTP to RTP by accepting or sending an RTP/AVP(RTP) profile in response to an RTP/SAVP(SRTP) profile. This feature also allows inbound and outbound SRTP calls with nonsecure SIP signaling schemes (such as SIP URL) and provides the administrator the flexibility to configure TLS, IPsec, or any other security mechanism used in the lower layers for secure signaling of crypto attributes. The following commands were introduced or modified: srtp (voice), srtp negotiate, and voice-class sip srtp negotiate |
Feature History Table entry for the Cisco Unified Border Element (Enterprise).
| Table 2 | Feature Information for SIP SRTP Fallback to Nonsecure RTP |
| Feature Name |
Releases |
Feature Information |
|---|---|---|
| SIP SRTP Fallback to Nonsecure RTP |
Cisco IOS XE Release 3.1S |
The SIP SRTP Fallback to Nonsecure RTP feature enables a Cisco IOS Session Initiation Protocol (SIP) gateway to fall back from SRTP to RTP by accepting or sending an RTP/AVP(RTP) profile in response to an RTP/SAVP(SRTP) profile. This feature also allows inbound and outbound SRTP calls with nonsecure SIP signaling schemes (such as SIP URL) and provides the administrator the flexibility to configure TLS, IPsec, or any other security mechanism used in the lower layers for secure signaling of crypto attributes. The following commands were introduced or modified: srtp (voice), srtp negotiate, and voice-class sip srtp negotiate |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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