Patton electronic SmartNode 4110 Series ユーザーズマニュアル
VoIP profile configuration task list
580
SmartWare Software Configuration Guide
47 • VoIP profile configuration
Configuring RTP payload type for transparent-clearmode
The following command configures the RTP payload type used for the transparent-clearmode codec.
Mode: configure/profile voip
Configuring RTP payload types for the g726-32k and g726-32k-cisco coders
The following command specifies the RTP payload types for the g726-32k and the g726-32k-cisco coders to
be used. It allows changing the payload types to a value in the range of 96 to 127 whereas the default value is 2
for both. Once a payload type has been changed, the ‘no’ form of the command must be used to go back to the
default value.
be used. It allows changing the payload types to a value in the range of 96 to 127 whereas the default value is 2
for both. Once a payload type has been changed, the ‘no’ form of the command must be used to go back to the
default value.
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.
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.
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.
NSEs are normally sent with RTP payload type 100. The RTP packets have the same source and destination
IP addresses and UDP ports as the other packets in the media stream, but differ in the RTP payload types so
they can be distinguished from the stream’s audio packets.
IP addresses and UDP ports as the other packets in the media stream, but differ in the RTP payload types so
they can be distinguished from the stream’s audio packets.
Mode: Profile VoIP
Configuring Cisco NSE for Fax
This command specifies the method to be used for signaling the remote device the RTP Stream has switched to
a voice-band Modem transmission. This feature is only available on the SIP protocol. If the command option
a voice-band Modem transmission. This feature is only available on the SIP protocol. If the command option
Step Command
Purpose
1
[name](pf-voip)[profile]#[no] crtp payload-
type transparent-clearmode <payload-
type>
type transparent-clearmode <payload-
type>
Specifies the rtp payload type used for
transparent clearmode. Value must be
between 97 and 127. Default value is
97.
transparent clearmode. Value must be
between 97 and 127. Default value is
97.
Step
Command
Purpose
1
[name](pv-voip)[name]#[no] rtp
payload-type [g726-32k | g726-
32k-cisco] <value 96..127>
payload-type [g726-32k | g726-
32k-cisco] <value 96..127>
Defines the RTP payload types for the g726-32k
and the g726-32k-cisco coders.
Default: 2
and the g726-32k-cisco coders.
Default: 2
Step Command
Purpose
1
node(pf-voip)[ name]#rtp payload-type nse
payload-type
payload-type
Specifies the RTP payload-type for Named Sig-
naling Events (NSE).
Default: 100
naling Events (NSE).
Default: 100