- Cisco Unified Border Element Enterprise Protocol-Independent Features and Setup
- SIP-to-SIP Extended Feature Functionality for Session Border Controllers
- Bandwidth-based Call Admission Control
- Interworking Between RSVP Capable and RSVP Incapable Networks
- Cisco Resource Reservation Protocol Agent
- SIP INFO Method for DTMF Tone Generation
- DTMF Events through SIP Signaling
- Negotiation of an Audio Codec from a List of Codecs
- Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- iLBC Support for SIP and H.323
- DSP-Based Functionality on the Cisco UBE Enterprise Including Transcoding and Transrating
- Acoustic Shock Protection
- Noise Reduction
- 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
- Cisco UBE Support for SRTP-RTP Internetworking
- SIP SRTP Fallback to Nonsecure RTP
- VoIP for IPv6
- Support for Software Media Termination Point
- Cisco Unified Communication Trusted Firewall Control
- Cisco Unified Communication Trusted Firewall Control-Version II
- Cisco Unified Communications Trusted Firewall Control - Version III
- Additional References
- Glossary
- Finding Feature Information
- Symmetric and Asymmetric Calls
- Prerequisites for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- Restrictions for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- How to Configure Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- Feature Information for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
The Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature provides dynamic payload type interworking for dual tone multifrequency (DTMF) and codec packets for Session Initiation Protocol (SIP) to SIP calls.
Based on this feature, the Cisco Unified Border Element (Cisco UBE) interworks between different dynamic payload type values across the call legs for the same codec. Also, Cisco UBE supports any payload type value for audio, video, named signaling events (NSEs), and named telephone events (NTEs) in the dynamic payload type range 96 to 127.
- Finding Feature Information
- Symmetric and Asymmetric Calls
- Prerequisites for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- Restrictions for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- How to Configure Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- Feature Information for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
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.
Symmetric and Asymmetric Calls
Cisco UBE supports dynamic payload type negotiation and interworking for all symmetric and asymmetric payload type combinations. A call leg on Cisco UBE is considered as symmetric or asymmetric based on the payload type value exchanged during the offer and answer with the endpoint:
- A symmetric endpoint accepts and sends the same payload type.
- An asymmetric endpoint can accept and send different payload types.
The Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature is enabled by default for a symmetric call. An offer is sent with a payload type based on the dial-peer configuration. The answer is sent with the same payload type as was received in the incoming offer. When the payload type values negotiated during the signaling are different, the Cisco UBE changes the Real-Time Transport Protocol (RTP) payload value in the VoIP to RTP media path.
To support asymmetric call legs, you must enable The Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature. The dynamic payload type value is passed across the call legs, and the RTP payload type interworking is not required. The RTP payload type handling is dependent on the endpoint receiving them.
Prerequisites for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
Cisco Unified Border Element
- Cisco IOS Release 15.0(1)XA 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.
Restrictions for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
The Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature is not supported for the following:
- H323-to-H323 and H323-to-SIP calls.
- All transcoded calls.
- Secure Real-Time Protocol (SRTP) pass-through calls.
- Flow-around calls.
- Asymmetric payload types are not supported on early-offer (EO) call legs in a delayed-offer to early-offer (DO-EO) scenario.
- Multiple m lines with the same dynamic payload types, where m is:
m = audio <media-port1> RTP/AVP XXX m = video <media-port2> RTP/AVP XXX
How to Configure Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- Configuring Dynamic Payload Support at the Global Level
- Configuring Dynamic Payload Support for a Dial Peer
- Verifying Dynamic Payload Interworking for DTMF and Codec Packets Support
- Troubleshooting Tips
Configuring Dynamic Payload Support at the Global Level
Perform this task to configure the Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature at the global level.
1. enable
2. configure terminal
3. voice service voip
4. sip
5. asymmetric payload {dtmf | dynamic-codecs | full | system}
6. end
DETAILED STEPS
Configuring Dynamic Payload Support for a Dial Peer
Perform this task to configure Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature for a dial peer.
1. enable
2. configure terminal
3. dial-peer voice tag voip
4. voice-class sip asymmetric payload {dtmf | dynamic-codecs | full | system}
5. end
DETAILED STEPS
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | enable Example: Device> enable |
Enables privileged EXEC mode. |
||
| Step 2 | configure terminal Example: Device# configure terminal |
Enters global configuration mode. |
||
| Step 3 | dial-peer voice tag voip Example: Device(config)# dial-peer voice 77 voip |
Enters dial peer voice configuration mode. |
||
| Step 4 | voice-class sip asymmetric payload {dtmf | dynamic-codecs | full | system} Example: Device(config-dial-peer)# voice-class sip asymmetric payload full |
Configures the dynamic SIP asymmetric payload support.
|
||
| Step 5 | end Example: Device(config-dial-peer)# end |
(Optional) Exits dial peer voice configuration mode and enters privileged EXEC mode. |
Verifying Dynamic Payload Interworking for DTMF and Codec Packets Support
This task shows how to display information to verify Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls configuration feature. These show commands need not be entered in any specific order.
1. enable
2. show call active voice compact
3. show call active voice
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable Example: Device> enable |
Enables privileged EXEC mode. |
| Step 2 | show call active voice compact Example: Device# show call active voice compact |
(Optional) Displays a compact version of call information. |
| Step 3 | show call active voice Example: Device# show call active voice |
(Optional) Displays call information for voice calls in progress. |
Troubleshooting Tips
Use the following commands to debug any errors that you may encounter when you configure the Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature:
- debug ccsip all
- debug voip ccapi inout
- debug voip rtp
Feature Information for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
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 Name |
Releases |
Feature Information |
|---|---|---|
| Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls |
15.0(1)XA 15.1(1)T |
The Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature provides dynamic payload type interworking for DTMF and codec packets for SIP-to-SIP calls. The following commands were introduced or modified: asymmetric payload and voice-class sip asymmetric payload. |
| Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls |
Cisco IOS Release XE 3.1S |
The Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls feature provides dynamic payload type interworking for DTMF and codec packets for SIP-to-SIP calls. The following commands were introduced or modified: asymmetric payload and voice-class sip asymmetric payload. |
Feedback