- Cisco Unified Border Element Protocol-Independent Features and Setup
- Interworking Between RSVP Capable and RSVP Incapable Networks
- SIP INFO Method for DTMF Tone Generation
- WebEx Telepresence Media Support Over Single SIP Session
- DTMF Events through SIP Signaling
- Call Progress Analysis Over IP-to-IP Media Session
- Codec Preference Lists
- AAC-LD MP4A-LATM Codec Support on Cisco UBE
- Multicast Music-on-Hold Support on Cisco UBE
- Network-Based Recording
- Video Recording - Additional Configurations
- TDoS Attack Mitigation
- Cisco Unified Communications Gateway Services--Extended Media Forking
- Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
- Acoustic Shock Protection
- Noise Reduction
- iLBC Support for SIP and H.323
- Configuring RTP Media Loopback for SIP Calls
- SIP Ability to Send a SIP Registration Message on a Border Element
- Session Refresh with Reinvites
- SIP Stack Portability
- Interworking of Secure RTP calls for SIP and H.323
- Cisco UBE Support for SRTP-RTP Internetworking
- Support for SRTP Termination
- Configuring RTCP Report Generation
- SIP SRTP Fallback to Nonsecure RTP
- Configuring Support for Interworking Between RSVP Capable and RSVP Incapable Networks
- VoIP for IPv6
- Mid-call Signaling Consumption
- 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
- URI-Based Dialing Enhancements
- Fax Detection for SIP Call and Transfer
- Feature Information 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
- Symmetric and Asymmetric Calls
- High Availability Checkpointing Support for Asymmetric Payload
- How to Configure Dynamic Payload Type Passthrough for DTMF and Codec Packets for SIP-to-SIP Calls
- Configuration Examples for Assymetric Payload Interworking
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.
- Feature Information 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
- Symmetric and Asymmetric Calls
- High Availability Checkpointing Support for Asymmetric Payload
- How to Configure Dynamic Payload Type Passthrough for DTMF and Codec Packets for SIP-to-SIP Calls
- Configuration Examples for Assymetric Payload Interworking
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 . 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. |
High Availability Checkpointing Support for Asymmetric Payload |
15.4(2)T |
High availability support for asymmetric payload type interworking was added. |
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.
-
Cisco fax relay.
-
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
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.
High Availability Checkpointing Support for Asymmetric Payload
How to Configure Dynamic Payload Type Passthrough for DTMF and Codec Packets for SIP-to-SIP Calls
- Configuring Dynamic Payload Type Passthrough at the Global Level
- Configuring Dynamic Payload Type Passthrough for a Dial Peer
- Verifying Dynamic Payload Interworking for DTMF and Codec Packets Support
- Troubleshooting Tips
Configuring Dynamic Payload Type Passthrough at the Global Level
Perform this task to configure the pass through of DTMF or codec payload to the other call leg (instead of performing dynamic payload type interworking) 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 Type Passthrough for a Dial Peer
Perform this task to configure the pass through of DTMF or codec payload to the other call leg (instead of performing dynamic payload type interworking) feature at the dial-peer level.
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:
Use the following debug commands to troubleshoot HA Checkpointing for Asymmetric Payload:
- debug voip ccapi all
- debug voice high-availability all
- debug voip rtp error
- debug voip rtp inout
- debug voip rtp packet
- debug voip rtp high-availability
- debug voip rtp function
- debug ccsip all
Use the following show commands to troubleshoot HA Checkpointing for Asymmetric Payload:
- show redundancy state
- show redundancy inter-device
- show standby brief
- show voice high-availability summary
- show voip rtp stats
- show voip rtp high-availability stats
- show voip rtp connection detail
- show call active voice brief
- show call active voice [summary]
- show call active video brief
- show call active video [summary]
- show align
- show memory debug leak
Configuration Examples for Assymetric Payload Interworking
Example: Asymmetric Payload Interworking—Passthrough Configuration
! voice service voip allow-connections sip to sip sip rel1xx disable asymmetric payload full midcall-signaling passthru ! dial-peer voice 1 voip voice-class sip asymmetric payload full session protocol sipv2 rtp payload-type cisco-codec-fax-ind 110 rtp payload-type cisco-codec-video-h264 112 session target ipv4:9.13.8.23 !
Example: Asymmetric Payload Interworking—Interworking Configuration
! voice service voip allow-connections sip to sip ! dial-peer voice 1 voip session protocol sipv2 rtp payload-type cisco-codec-fax-ind 110 rtp payload-type cisco-codec-video-h264 112 session target ipv4:9.13.8.23 !