VoIP profile configuration task list
512
SmartWare Software Configuration Guide
40 • VoIP profile configuration
Figure 79. DTMF Relay
This procedure describes how to configure DTMF relay
Mode: Profile VoIP
Configuring RTP payload types
If you are using DTMF relay with SIP, the DTMF digits are transported in RTP packets with a special payload
type. The default value for this payload type can be configured in the profile VoIP.
Procedure: Configure RTP NTE payload type
Mode: Profile VoIP
Configuring RTP payload type for Cisco NSE
Configure the RTP payload-type when transmitting the NSE events. This payload-type is negotiated during
call-setup when using SIP.
Named Service Events (NSE) are the Cisco-proprietary version of Named Telephony Events (NTEs). NTEs
are defined in RFC 2833. Various telephony signaling events use tones, for example, DTMF. NSEs and NTEs
communicate these tones (for representing signaling events), not by the presence of tones, but by sending a
binary code representing the tone that is recreated at the destination. Cisco’s proprietary NSEs use different
values to represent tones and events than the NTEs use.
Step Command
Purpose
1
node(pf-voip)[
pf-name
]#dtmf-relay
{default|rtp|signaling}
Define how DTMF digits shall be transmitted.
You can configure the SIP gateway to send
DTMF digits either by using the SIP INFO
method or in the RTP stream (RFC 2833). The
gateway will always receive both types of
DTMF digits. The command has currently no
effect for H.323 calls.
Step
Command
Purpose
1
node(pf-voip)[
name
]#rtp payload-
type nte
payload-type
Specifies the RTP payload-type for named tone
events NTE (RFC2833). Default: 101.
encoder
decoder
payload
Signalling of dtmf tones
Generates dtmf tones
Detects dtmf tones
