Information Technology Reference
In-Depth Information
■
The
session transport
{
tcp
|
udp
} and
bind
{
all
|
control
|
media
}
source-interface
interface
command configures the
gateway to use either TCP or UDP for SIP session transport and to source control traffic/media traffic from a particular
interface.
A SIP UA configuration is shown here:
sip-ua
registrar ipv4:10.1.1.1 tcp
authentication username mark password cisco123
■
You can enter the SIP UA configuration mode by using the
sip-ua
command.
■
The
registrar ipv4:
ip-address
tcp
command configures the gateway to register E.164 numbers with a SIP registrar on behalf
of (E)FXS ports and SCCP phones.
■
authentication username
username
password
password
is used to specify a username and password used for authentication.
■
You can configure a SIP trunk on a CUCM by navigating to
Device, Trunk
and clicking
Add a New Trunk
.
Before finishing this section, it's worth looking at the transport of DTMF between SIP endpoints. Many methods can be categorized
as being either in-band or out-of-band:
■
Unsolicited Notify (UN):
Nonstandard, out-of-band method of carrying DTMF in SIP NOTIFY messages that is only
supported on Cisco IOS gateways in IOS 12.2 and later releases.
■
INFO:
This involves the out-of-band transport of DTMF tones in SIP INFO messages and is not supported in CUCM.
■
Key Press Markup Language (KPML):
This out-of-band method of carrying DTMF tones is defined in RFC 4370 and is
supported in CUCM, Cisco IOS gateways running IOS 12.4 and later, and some Cisco IP phones. KPML takes advantage of
the SIP SUBSCRIBE and NOTIFY message types. SIP NOTIFY messages signal the DTMF, with the event specified in the
NOTIFY as KPML and the actual DTMF tones carried in XML-formatted messages in the NOTIFY.
■
RFC 2833:
RFC 2833 Named Telephony Events (NTE) are an in-band method of transporting DTMF tones. Payload types
can be dynamically assigned, but the Cisco default is 101.
