Configuring Cisco Callmanager Express (Cme) : Cisco Networking Academy Program

Configuring Cisco CallManager
Express (CME)
Cisco Networking Academy Program
IP Telephony © 2005 Cisco Systems, Inc. All rights reserved. Cisco Public 1
Overview of Cisco CME
What is Cisco CallManager Express?
Cisco CME
Trunks
PSTN
WAN
• Call processing for small to medium sized

deployments
• VoIP integrated solution
• Up to 120 IP phones
• IOS based solution
What is Cisco CallManager Express?
(Cont.)
• Select IOS based platform

• Multiservice access routers
2600XM
3700 1700
How Does Cisco CallManager Express
Work?
Connection(s) to PSTN
• Analog
• Digital
PSTN
How Does Cisco CallManager
Express/Cisco Unity Express Work? (Cont.)
PSTN H.323 between Cisco

CME systems
H.323
H.323 WAN
WAN
H.323 SIP
PSTN Gateway
and IP to IP
Gateway
functionality
PSTN
PSTN
Differences between Traditional
Telephony and VoIP
Basic Components of a Telephony
Network
Central Office Switches
What Is a PBX?
What Is a Key System?
Basic Call Setup
Digitizing Analog Signals
1. Sample the analog signal regularly

2. Quantize the sample
3. Encode the value into a binary expression
4. Compress the samples to reduce bandwidth
(multiplexing), optional step
Nyquist Theorem
Quantization
Quantization Techniques
• Linear
Uniform quantization
• Logarithmic quantization
Compands the signal
Provides a more uniform signal-to-noise ratio
• Two methods
α-law (most countries)
μ-law (Canada, U.S., and Japan)
Voice-Compression Techniques
• Waveform algorithms
PCM
ADPCM
• Source algorithms
LDCELP
CS-ACELP
Example: Waveform Compression
• PCM
Waveform coding scheme
• ADPCM
Waveform coding scheme
Adaptive: automatic companding
Differential: encode changes between samples only
• ITU standards:
G.711 rate: 64 kbps = (2 x 4 kHz) x 8 bits/sample
Example: Source Compression
• CELP
Hybrid coding scheme
• High-quality voice at low bit rates, processor

intensive
• G.728: LDCELP—16 kbps
• G.729: CS-ACELP—8 kbps
G.729A variant—8 kbps, less processor intensive, allows
more voice channels encoded per DSP
Annex-B variant –VAD and CNG
G.729 and G.729A Comparison
• Both are ITU standards

• Both are 8 kbps CS-ACELP
• G.729 more complex and processor intensive
• G.729 slightly higher quality than G.729A
• Compression delay the same (10 to 20 ms)
• Annex-B variant may be applied to either
Real-Time Transport Protocol
• Provides end-to-end network functions and delivery

services for delay-sensitive, real-time data, such as
voice and video
• Works with queuing to prioritize voice traffic over
other traffic
• Services include:
Payload type identification
Sequence numbering
Timestamping
Delivery monitoring
Real-Time Transport Control Protocol
• Monitors the quality of the data distribution and

provides control information
• Provides feedback on current network conditions
• Allows hosts involved in an RTP session to
exchange information about monitoring and
controlling the session
• Provides a separate flow from RTP for UDP
transport use
RTP Header Compression
• RTP header compression saves bandwidth by

compressing packet headers across WAN links
When to Use RTP Header Compression
• Narrowband links
• Slow links (less than 2 Mbps)
• Need to conserve bandwidth on a WAN interface
Challenges and Solutions in VoIP
Reliability and Availability
• Traditional telephony networks claim 99.999%

uptime
• Data networks must consider reliability and
availability requirements when incorporating voice
• Methods to improve reliability and availability
include:
Redundant hardware
Redundant links
UPS
Proactive network management
Bandwidth Implications of Codec
Impact of Voice Samples
Data Link Overhead
• Ethernet: 18 bytes overhead

• MLP: 6 bytes overhead
• Frame Relay: 6 bytes overhead
Total Bandwidth Required
Effect of VAD
Cisco CME Features and Functionality
Supported Protocols and Integration
Options (Cont.)
FAX ATA
H.323
ATA Skinny
Analog
V
Skinny
Analog Phones
Options
Skinny Client Control Protocol (SCCP)

• Cisco proprietary
• Call Control protocol
• Lightweight protocol
• Low memory requirements
• Low complexity
• Low CPU requirements
Options (Cont.)
Skinny Protocol Caveats

• QoS, bandwidth and CAC support are not built into
the Skinny protocol
• Complex connection paths can cause QoS
problems
• Remote registration of IP phones and ATAs is not
supported
Options (Cont.)
• Cisco CME does not support remotely registered

phones
CME PSTN
WAN X X
Remote Phones
Local Phones
Options (Cont.)
H.323 Protocol
• Supports Voice, Video, and Data
• Industry Standard
• Complex protocol
• Higher complexity than Skinny protocol
• CAC functionality is part of the protocol
• Authentication is part of the protocol
Options (Cont.)
CallManager
H.323 Connections Cluster
Vmail
PSTN
CME
H.323
H.323
H.323
WAN
V H.323 CME
Recommended
Options (Cont.)
Cisco CME can register to a H.323 gatekeeper thereby

ensuring the WAN is not oversubscribed
H.323
WAN
Register Register
1000 2000
2095551000 3095552000
Gatekeeper
Register Extension number Register Extension number
and/or E.164 number and/or E.164 number
Options (Cont.)
SIP Protocol
• Emerging standard
• Vendor specific in most cases
• Higher complexity than Skinny protocol
• Authentication is part of the protocol
• Based on other well known protocols
Options (Cont.)
CallManager
SIP Connections Cluster
Vmail
PSTN
CME
H.323
SIP
SIP
WAN
V SIP CME
H.323 is recommended today

Cisco CallManager Express Requirements
• Feature license
• Seat license
• IOS platform
12.3(7)T or greater is recommended
IP Voice
• Cisco CME software and files

GUI files
Firmware
Cisco CallManager Express Restrictions
Cisco CME 3.1 caveats

• TAPI v2.1
• Cisco JTAPI
• Cisco IP Softphone
• Remote SCCP phones across a WAN
• G.729 conferences
• MGCP
Cisco CallManager Express Restrictions
(Cont.)
• TAPI Lite Functionality

• Supported:
Operation of multiple independent clients (e.g. one client per
phone line)
Windows phone dialer
Outlook contact dialer
Third party applications
• Not Supported:
TAPI based softphone
Multiple-user or multiple-call handling (Required for ACD)
Direct media- and voice-handling
JTAPI
Cisco CME Network Parameters
Auxiliary VLANs
• Prevent unnecessary IP address renumbering

• Simplifies Quality of Service (QoS) configurations
• Separates Voice and Data traffic
• Requires two Virtual Local Area Networks (VLANs)
one for Data and one for Voice
• Requires only one drop down Ethernet for the
CallManager Express IP phone and the PC plugged
into the phone
Auxiliary VLANs (Cont.)
IP Addressing Deployment Options
IP Phone + PC on same IP Phone + PC on same switch
switch ports Recommended ports
171.68.249.100 171.68.249.100
171.68.249.101 10.1.1.1
Public IP addresses IP Phone uses private Network
IP Phone + PC on separate switch ports IP Phone + PC on separate switch ports

171.68.249.101 171.68.249.100 10.1.1.1 171.68.249.100
Public IP addresses IP Phone uses private network
Configuring Auxiliary VLANs
• An access port able to handle 2 VLANs

• Native VLAN (PVID) and Auxiliary VLAN (VVID)
• Hardware set to dot1q trunk
Tagged 802.1q (Voice VLAN)
Untagged 802.3 (Native VLAN)
Configuring Auxiliary VLANs - Switching
Review
• Address learning
• Forward/filter decision
• Loop avoidance
Configuring Auxiliary VLANs (Cont.)
Example 3550 switch or EtherSwitch Network Module

Console(config)#interface FastEthernet0/1
Console(config-if)#switchport trunk encapsulation dot1q
Console(config-if)#switchport trunk native vlan 1
Console)config-if)#switchport access vlan 12
Console(config-if)#switchport mode trunk
Console(config-if)#switchport voice vlan 112
Console(config-if)#spanning-tree portfast
• 802.1q trunking is enabled on the port

• The access VLAN is used for the PC plugged into the IP
phone
• The voice VLAN is used for voice and signaling that
originates and terminates on the IP phone
• Spanning tree portfast enables the port to initialize quickly
Configuring Auxiliary VLANs (Cont.)
Switch# show interface fa0/17 switchport
Name: Fa0/17
Switchport: Enabled
Administrative mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Disabled

Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 12 (VLAN0012)
Trunking VLANs Enabled: ALL
Trunking VLANs Active: 1-3,5,10,12
Pruning VLANs Enabled: 2-1001
Priority for untagged frames: 0

Override vlan tag priority: FALSE
Voice VLAN: 112
Appliance trust: none
Configuring Auxiliary VLANs - Router
Configuration
802.1q trunk
Trunk on a router
interface fastethernet 1/0.1
encapsulation dot1q 10
ip address 10.10.0.1 255.255.255.0
VLAN 10
interface fastethernet 1/0.2
encapsulation dot1q 20
ip address 10.20.0.1 255.255.255.0
VLAN 20 ...
DHCP Service Setup
Dynamic Host Configuration Protocol

• Assigns an IP addresses and subnet masks for one
or more subnets
• Optionally can assign a default gateway
• Optionally can assign DNS servers
• Optionally can assign other commonly used
servers
• The DHCP scope can be customized to assign a
TFTP server to IP phones
• Best practice is to configure a DHCP scope for the
IP phones
DHCP Service Setup (Cont.)
DHCP Service Options

• Single DHCP IP Address Pool
• Separate DHCP IP Address Pool for Each Cisco IP
Phone
• DHCP Relay Server
DHCP Service Setup (Cont.): Phone Bootup
On the Cisco CME router a DHCP

The IP phone powers on Scope can be configured. The
scope should define the following:
The phone performs a • Range of available IP addresses
Power on Self Test (POST)
• The subnet mask
The phone boots up • A default gateway
Through CDP the IP phone learns • The address of the TFTP server
what the auxiliary VLAN is • DNS server(s)
The phone initializes the IP stack
Continued next slide…
DHCP Service Setup (Cont.): Phone Bootup
(Cont.)
IP phone send DHCP Discover

broadcast requesting an IP address
DHCP server selects a free IP

address from the pool and sends
along with the other scope
parameters as a DHCP Offer
The IP phone initializes applies the

IP configuration to the IP stack
The IP phone requests it

configuration file from
the TFTP server
CMERouter(config)#
ip dhcp excluded-address start-IP end-IP
• Sets a range of addresses to be excluded from the

configured scopes
CMERouter(config)#
ip dhcp pool pool-name
• Creates and enters a the DHCP scope mode

CMERouter(dhcp-config)#
network subnet subnet-mask
• Defines the range of addresses that will be used to

assign to DHCP clients
option option-number ip IP-address
• Defines a custom option and its value
default-router IP-address
• Sets the default gateway that will handed out to the

DCHP clients
dns-server primary-IP [secondary IP]
• Sets the DNS server(s) that will assigned to the DHCP

clients
Configuring DHCP on an IOS router

CMERouter(config)#ip dhcp exluded-address 10.90.0.1 10.90.0.10
CMERouter(config)#ip dhcp pool mypool
CMERouter(dhcp-config)#network 10.90.0.0 255.255.255.0
CMERouter(dhcp-config)#option 150 ip 10.90.0.1
CMERouter(dhcp-config)#default-router 10.90.0.1
CMERouter(dhcp-config)#dns-server 10.100.0.1 10.100.0.2
CMERouter(dhcp-config)#exit
• Option 150 sets the TFTP server on the IP phone

• The TFTP server contains the configuration files
and firmware for the IP phone
IP Phone Registration
Files
7960
Firmware
7940
Files critical to the IP phone SEP
SEP
Firmware
7920
Firmware
7912
Firmware
7905
• Firmware XML SEP
XML SEP
Firmware
7902
Firmware
7910
XML SEP Firmware
XML
• SEPAAAABBBBCCCC.cnf.xml XML
• XmlDefault.cnf.xml TFTP Server

• SCCP-dictionary.xml
• Phonemodel-dictionary.xml
• Phonemodel-tones.xml
Files (Cont.): Firmware
CMERouter1#show flash
7905 -#- --length-- -----date/time------ path
1 399514 Mar 1 2002 12:56:28 P00305000301.sbn
Firmware 2 22649180 Mar 1 2002 12:38:00 c3725-ipvoice-mz.123-7.T.bin
3 321939 Mar 1 2002 12:55:58 CP7902010200SCCP031023A.sbin
4 317171 Mar 1 2002 12:56:06 CP7905010200SCCP031023A.sbin
7940 5 317968 Mar 1 2002 12:56:10 CP7912010200SCCP031023A.sbin
6 700651 Mar 1 2002 12:56:18 CiscoIOSTSP.zip
Firmware 7 369950 Mar 1 2002 12:56:22 P00303020214.bin
8 333822 Mar 1 2002 12:56:30 P00403020214.bin
9 47904 Mar 1 2002 12:56:54 S00103020002.bin
7960 10 301298 Mar 1 2002 12:56:56 ata18x-v2-16-ms-030327b.zup
Firmware 11 496521 Mar 1 2002 12:57:22 music-on-hold.au
12 1908762 Mar 1 2002 12:56:54 P00503010100.bin
13 21 Mar 1 2002 12:56:18 OS7920.txt
14 839984 Mar 1 2002 12:57:18 cmterm_7920.3.3-01-06.bin
…
…
33 307067 Mar 1 2002 12:56:02 CP79050101SCCP030530B31.zup
34 710144 Mar 1 2002 12:57:06 cme-gui-3.1.1.tar
• Firmware is installed in flash RAM with the Cisco CME

software or individually as needed
• Served up by the TFTP server on the Cisco CME router
• The command tftp-server flash:firmware-file-name
Files (Cont.): Device Configuration XML File
<device>
<devicePool>
SEPXXXXXXXXXXXX.cnf.xml <callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
</ports>
<processNodeName>10.15.0.1</processNodeName>
</callManager>
</member>
SEP </members>
</callManagerGroup>
</devicePool>
<versionStamp>{Jan 01 2002 00:00:00}</versionStamp>
<loadInformation>P00303020214</loadInformation>
XML
- <userLocale>
<name>English_United_States</name>
<langCode>en</langCode>
</userLocale>
<networkLocale>United_States</networkLocale>
<idleTimeout>0</idleTimeout>
<authenticationURL />
<directoryURL>http://10.15.0.1/localdirectory</directoryURL>
<idleURL />
<informationURL />
<messagesURL />
* XXXXXXXXXXX = to the <proxyServerURL />
MAC address <servicesURL />
</device>
Files (Cont.): Default XML File
XMLDefault.cnf.xml
<Default>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
</ports>
Default <processNodeName>10.15.0.1</processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
XML
<loadInformation6 model="IP Phone 7910">P00403020214</loadInformation6>
<loadInformation124 model="Addon 7914"></loadInformation124>
<loadInformation9 model="IP Phone 7935"></loadInformation9>
</Default>
* Notice there is
no ATA or 7914
Files (Cont.): Language Specific XML Files
<?xml version="1.0" encoding="ISO-8859-1" ?>
7960-dictionary.xml <phrases>
<phrase i="173" t="Login"/>
SCCP-dictionary.xml <phrase i="172" t="Flash"/>
<phrase i="171" t="Acct"/>
<phrase i="170" t="Incompatible device type"/>
<phrase i="169" t="Another Barge exists"/>
<phrase i="168" t="Failed to setup Barge"/>
<phrase i="167" t="Barge" />
<phrase i="166" t="Network congestion,rerouting" />
Language <phrase i="165" t="CallBack" />
<phrase i="164" t="SAC" />
<phrase i="163" t="DND" />
<phrase i="162" t="TrnsfVM" />
<phrase i="161" t="SetWtch" />
<phrase i="160" t="Intrcpt" />
XML <phrase i="159" t="ImmDiv" />

<phrase i="158" t="Voicemail"/>
<phrase i="157" t="RmLstC"/>
<phrase i="156" t="Unknown Number"/>
<phrase i="155" t="Not Enough Bandwidth"/>
<phrase i="154" t="Private"/>
<phrase i="153" t="Park Number"/>
<phrase i="152" t="Conference"/>
<phrase i="151" t="Error Mismatch"/>
Contents will vary based <phrase i="150" t="Error Unknown"/>
upon language selected with <phrase i="149" t="Error Pass Limit"/>
the user-locale command …
Files (Cont.): Call Progress XML File
<tones>
<tone c1="30831" i1="-2032" c2="30467" i2="-1104" d="2"
7960-tones.xml t="ringing">
<part m="on" t="2000"/>
<part m="off" t="4000"/>
<repeat c="65535"/>
</tone>
<tone c1="30467" i1="-1104" c2="28959" i2="-1404" d="2"
Call t="reorder">
<part m="on" t="250"/>
<part m="off" t="250"/>
Progress <repeat c="65535"/>
</tone>
<tone c1="30467" i1="-1104" c2="28959" i2="-1404" d="2"
t="busy">
XML
<part m="on" t="500"/>
<part m="off" t="500"/>
<repeat c="65535"/>
</tone>
<tone c1="30743" i1="-1384" c2="29780" i2="-1252" d="2"
t="odial">
<part m="on" t="65535"/>
<repeat c="65535"/>
</tone>
Contents will vary based <tone c1="30831" i1="-2032" c2="31538" i2="-814" d="2"
t="idial">
upon call progress tones <part m="on" t="65535"/>
selected with the network- <repeat c="65535"/>
</tone>
locale command </tones>
IP Phone Information
No 7914 in the
XMLDefault.cnf.xml <loadInformation6 model="IP Phone 7910">P00403020214</loadInformation6>
<loadInformation124 model="Addon 7914"></loadInformation124>
Default <loadInformation20000 model="IP Phone 7905"></loadInformation20000>
XML <loadInformation30019 model="IP Phone 7936"></loadInformation30019>
• The 7914 expansion module cannot auto register

• Require the use of the “type” command entered by
the administrator
• All other valid devices can be recognized
automatically by the Cisco CME system
Download and Registration
Power over Ethernet
Step 1 - Switch sends a Fast Link Pulse (FLP)

FLP
Step 2 - The phone returns the FLP to the

switch due to a completed circuit
FLP
Step 3 - Power is applied
Step 4 - Link is detected on

switchport
Step 5 - The IP phone boots up
Step 6 - The amount of power really needed is passed

through CDP from the IP phone to the switch
CDP
Power needed
Download and Registration (Cont.)
DHCP
DHCP Server
or
DHCP Relay
Step 7 - CDP is used to
send the auxiliary VLAN
information from the
switch to the IP phone
CDP
Voice VLAN
Step 8 - The IP phone initializes the

IP stack and sends a DHCPDiscover
broadcast message
DHCPDiscover
Broadcast
Step 9 - The DHCP server hears the

DHCPDiscover message and
selects an IP address from the
scope and sends a DHCPOffer
DHCPOffer
IP address, Subnet Mask, Default
Gateway, and TFTP server (option 150)
Existing IP Phone
MAC 000F.2470.AA32
Cisco CME is
the TFTP
Server
Step 10 - Phone applies
addressing information
obtained through DHCP to
the IP stack
Step 11 - Using the address of the TFTP server learned from the option 150
in the DHCPOffer the phone looks for and downloads the file named
SEPAAAABBBBCCCC.cnf.xml (where AAAABBBBCCCC is the MAC
address), if the file is found the phone will register
SEP TFTP request for the SEP000F2470AA32.cnf.xml file
XML
SEP000F2470AA32.cnf.xml file
If no SEP XML file is found go to Step 14

Unknown IP Address
MAC 000F.2470.AA32
Cisco CME is
the TFTP
Server
Step 12 - If the firmware version currently on the phone is different

than the version specified in the SEPAAAABBBBCCCC.cnf.xml file
then the firmware is downloaded from the TFTP server
7960
Firmware TFTP request for firmware if needed
Firmware file
Step 13 - IP phone will reboot if the

firmware was updated
Unknown IP Phone
Unknown IP address with
MAC 000F.2470.AA32
CallManager
Express is the
TFTP Server
Step 14 - If no SEP XML file was found then download
from the TFTP server the XMLDefault.cnf.xml file
Default TFTP request for the XMLDefault.cnf.xml file
XML
XMLDefault.cnf.xml file
Step 15 - The phone will register to CallManager Express but without

any assigned extension. No calls will be able to be placed or received
and a SEP file will be created on the CallManager Express router
or
Step 16 - If auto assign is enabled or the phone has been configured then the new
IP phone will register to the CallManager Express and given an extension number
Ephone-dn and Ephone
Ephone-dn
A DN and Extension number
are equivalent Primary extension number
Line and voice port are

on a single line ephone-dn
that can make or receive
DN1
one call at a time
equivalent
Has a unique tag or ephone-dn
sequence number assigned
when the ephone-dn is Primary/Secondary
created extensions configured on a
single line ephone-dn where DN1 and
Can have one or more
telephone numbers
the primary is an internal
extension number and the
secondary is an E.164
DN2
associated with it number
Can have one voice channel ephone-dn

or two voice channels
Creates one or more
One phone extension on a
dual line ephone-dn for DN1
telephony system pots dial ephone-dns that need call
peers when the ephone-dn
waiting, consultative
transfer and conferencing DN1
is initially configured
ephone-dn
Ephone-dn (Cont.)
router(config)#
ephone-dn dn-tag [dual-line]
• This command is used to create an extension

(ephone-dn) for a Cisco IP phone line, an intercom
line, a paging line, a voice-mail port, or a message-
waiting indicator (MWI).
router(config-ephone-dn)#
number dn-number secondary dn-number [no-reg [both |
primary]]
• This command is used to associate a DN number with

the ephone-dn instance
Ephone
• Software configuration of a 7960

Button 1 DN Button 4 DN
physical phone
Button 2 DN Button 5 DN
• Has a unique tag or sequence
number assigned when the Button 3 DN Button 6 DN
ephone is created
MAC 000F.2470.F92A
• Can be an IP phone, analog phone
attached to an ATA 7912
• The MAC of the IP phone or ATA is
used to tie the software Button 1 DN
configuration to the hardware
• The hardware is auto detected for
MAC 000F.2470.F92B
all supported models except the
ATA and 7914 expansion module ATA 188
Analog 1 DN
• Can have one or more ephone-
dn(s) associated with the ephone MAC 000F.2470.F92D
• Number of line buttons will vary Analog 2 DN

based on the hardware
MAC 000F.2470.F92E
Ephone (Cont.)
router(config)#
ephone phone-tag
• Creates an ephone instance and enters ephone

configuration mode
router(config-ephone)#
mac-address mac-address
• Assigns the physical IP phone by MAC address with

this instance of an ephone
Ephone (Cont.)
button button-number {separator} dn-tag [[button-number
{separator} dn-tag]…]
• Associates the ephone-dn(s) with a specific button(s)

on the IP phone
type {7940 | 7960} addon 1 7914 [2 7914]
• Defines the device as a 7914 module(s)
Ephone (Cont.): Basic Example
MAC 000F.2470.F8F8
ephone 1
1001 ephone-dn 7:
one virtual port
Button 1
000F.2470.F8F8
CMERouter(Config)#ephone-dn 7
CMERouter(Config-ephone-dn)#number 1001
CMERouter(config)#ephone 1
CMERouter(config-ephone)#mac-address 000F.2470.F8F8
CMERouter(config-ephone)#button 1:7
Ephone (Cont.): Example Multiple Ephones
1004
1004 1004
1005
1005 1005
1006
1006 1006
V • Four physical phones

1007
1007 ATA-186/188 • Four ephones defined 1007
• Four ephone-dns defined
Ephone (Cont.): Example Multiple Ephones
Configuration
Configuration example
CMERouter(config)#ephone-dn 10 dual-line
CMERouter(config-ephone-dn)#number 1004
CMERouter(config)#ephone-dn 12dual-line
CMERouter(config-ephone)#mac-address 000F.2470.F8F1
CMERouter(config-ephone)#mac-address 000F.2470.A302
CMERouter(config-ephone)#mac-address 000F.2470.66F6
CMERouter(config-ephone)#mac-address 000F.2470.7B54
CMERouter(config-ephone)#type ata
Ephone (Cont.): Multiple Ephone-dns
1008
Button 1
1008 on line 1 1008
1009 on line 2
1009
Button 2
1009
1010 on line 1
1010
1011 on line 6 Button 1
1010
• Two physical phones Button 6

1011
1011
• Four dual line ephone-dns defined

• Two ephones defined
Ephone (Cont.): Multiple Ephone-dns
Configuration Example
Multiple line ephone configuration example

CMERouter(config-ephone)#mac-address 000F.2470.FAA1
CMERouter(config-ephone)#button 1:14 2:15
CMERouter(config-ephone)#mac-address 000F.2470.A7E2
Type of Ephone-dns: Overview
Single line 1001

Six types of ephone-dns
• Single-line ephone-dn 1002
Dual line 1002
• Dual-line ephone-dn
Primary and
• Primary and secondary secondary extension 1004 and
on a single or dual 1005
extension on ephone-dn line ephone-dn
• Shared ephone-dn
Shared single or 1006 1006
• Multiple ephone-dns dual line ephone-dn
• Overlay ephone-dn Multiple single or

dual line ephone-
1003 1003
dns on one or more 1003 1003
ephones
Overlay ephone-
dns on an ephone 1007
Single Line Ephone-dn
One virtual
voice port
One channels 1001
• The ephone-dn creates one virtual voice port

• One call to or from this ephone-dn at any one time
Dual Line Ephone-dn
One virtual
voice port
1002
Two channels
1002
CMERouter(Config)#ephone-dn 2 dual-line

• The “dual-line” keyword indicates two voice channels for calls to terminate on
an ephone-dn extension
• Use on ephone-dns that need call waiting, consultative transfer, or
conferencing on one button
• Cannot be used on ephone-dns used for intercoms, paging, MWI or MoH
feeds
Primary and Secondary Extension Number
on Ephone-dn
One virtual
voice port
1005 and
One channels 2065559005
CMERouter(Config-ephone-dn)#number 1005 secondary 2065559005 no-reg primary

• Two different directory numbers can be dialed to reach this ephone-dn
• One call connection allowed if configured as a single-line ephone-dn
• Two call connections allowed if configured as a dual-line ephone-dn
• Allows two numbers to be configured without using an extra ephone-dn
• The secondary number will be registered to the H.323 gatekeeper
Shared Ephone-dn
1006
1006 on line 1 Button 1
1006
1100 on line 2
Button 2 1100
1007 on line 1
1100 on line 2 1007
Button 1
1007
• One ephone-dn applied on two different ephones
• Only one phone can use the ephone-dn at a time
Button 2 1100
• Both phones ring when a call arrives at the ephone-
dn
• Only one ephone can pick up the call ensuring
privacy
• If a call is placed on hold either ephone can retrieve
the call
Shared Ephone-dn Configuration Example
Shared line appearance configuration example

CMERouter(config)#ephone-dn 9
Two Ephone-dns with one extension
number
Multiple ephone-dns Ephone 3
• On the same ephone 1003
preference 0
Button 1 no huntstop
1003
Used when more than two
calls to the same extension
1003
are needed preference 1
Button 2 huntstop
1003
• On different ephones
Used when two different
ephones need the same Ephone 4
number
1004
preference 0
Not a shared line Button 2 no huntstop
1004
Only one ephone will ring at a

Ephone 5
time
1004
A call on hold can be Button 2
preference 1
1004 huntstop
retrieved only by the ephone
that put the call on hold
Preference and Huntstop Commands
preference {0-10}
• Sets the dial-peer preference order
huntstop [channel]
• Discontinues the call hunting behavior for an

extension (ephone-dn) or an extension line (dual-line)
Huntstop
Call arrives at first
1020 DN no huntstop Ephone-dn 10 ephone-dn
Preference 0 no huntstop channel Channel 1

Busy
Channel 2
1020 DN no huntstop Ephone-dn 11 Busy

Busy
Channel 2
1020 DN huntstop Ephone-dn 12 Busy

Busy
Channel 2
1020 DN
Preference 3
Ephone-dn 13
Channel 1
X
* Ring no answer timeout
* Same DN on the ephone-dns Channel 2 of 10 seconds set globally
Huntstop Channel
Call arrives at first
1020 DN no huntstop Ephone-dn 10 ephone-dn
Preference 0 huntstop channel Channel 1

Channel 2
Busy
1020 DN no huntstop Ephone-dn 11

Preference 1 huntstop channel Channel 1
Channel 2
Busy
huntstop Ephone-dn 12
1020 DN
Busy
Channel 2
1020 DN
Preference 3
Ephone-dn 13
Channel 1
X
* Ring no answer timeout
Channel 2 of 10 seconds set globally
Two Ephone-dns/One Number/Same
Ephone
Ephone 3
1003 on line button 1
1003
1003 on line button 2 preference 0
Button 1 no huntstop
1003
1003
preference 1
Button 2 huntstop
1003
• If either of the two voice channels are available, the ephone-dn assigned to
line button 1 will be used when an incoming call is setup
• When the two voice channels on the ephone-dn are being used on line button
1, an incoming call will roll to the ephone-dn assigned to line button 2
• A fifth call will receive busy treatment when both voice channels on both
ephone-dns are being used on line button 1 and 2
• The preference of 0 is more preferred than a preference of 1. The default is 0
• The “no huntstop” on the line button 1 ephone-dn allows the call to hunt to
the second ephone-dn when the first ephone-dn is busy
• The “huntstop” on the line button 2 ephone-dn stops the hunting behavior
and applies the busy treatment
Two Ephone-dns/One Number/Same Ephone
Two ephone-dns with one number on the same

ephone configuration example
CMERouter(config-ephone-dn)#preference 0
CMERouter(config-ephone-dn)#no huntstop
CMERouter(config-ephone-dn)#huntstop
Two Ephone-dns/One Number/Diff Ephones
preference 0
Ephone 4 Button 2 1004
no huntstop
preference 1
Ephone 5 Button 2 1004
huntstop
• Ephone 4 will be used first if available

• When the first ephone-dn is being used on ephone 4, an incoming call will use
the ephone-dn assigned to ephone 5
• A third call will receive busy treatment when both ephone-dns are being used
on line ephone 4 and 5
• The preference of 0 is more preferred than a preference of 1; the default is 0
• The “no huntstop” on the ephone-dn on ephone 4 allows the call to hunt to the
second ephone-dn on ephone 5 when the first ephone-dn is busy
• The “huntstop” on the ephone-dn on ephone 5 stops the hunting behavior and
applies the busy treatment for the third call
• Unlike a share line appearance, if a call is placed on hold, only the original
phone will be able to retrieve the call
Two Ephone-dns/One Number/Diff Ephones
Two ephone-dns with one number on different

ephones configuration example
CMERouter(config)#ephone-dn 5 dual line
CMERouter(config)#ephone-dn 6 dual line
CMERouter(config-ephone-dn)#huntstop
CMERouter(config-ephone)#mac-address 000F.2470.F131
CMERouter(config-ephone)#mac-address 000F.2470.FA5B
Overlay Ephone-dn
1101
Button 4 Preference 0
no huntstop
1101 on line 4
1101
1101 on line 4 Button 4 Preference 1
huntstop
1101
1101 on line 4 Button 4 Preference 0
1101 on line 4 no huntstop
• Two or more ephone-dns applied to the same ephone line 1101

button Button 4 Preference 1
huntstop
• Up to ten ephone-dns per line button on the phone
• All ephone-dns in the overlay set must be either single-line or all must be dual-line
• The ephone-dns are usually applied on more than one phone
• Allows up to ten calls (depending on the number of ephone-dns) to the same phone
number that resides on multiple ephones
• Call waiting and call pickup not supported
• A call placed on hold can be retrieved by only the phone that placed the call on hold
Type of Ephone-dns (Cont.)
Overlay Configuration Example
Overlay configuration example

CMERouter(config-ephone)#mac-address 000F.2470.FA31
CMERouter(config-ephone)#button 4o10,11
CMERouter(config-ephone)#button 4o10,11
Number of Ephone-dns max-dn Command
router(config-telephone)#
max-dn max-dn
• Sets the maximum definable number of ephone-dns

that may be configured in the system
• The maximum number of ephone-dns supported is

a function of the license and hardware platform
• The default is zero
Number of Ephone-dns (Cont.)
DN DN
DN DN
DN DN
CMERouter(config-telephony)#max-dn 10
DN DN
Attempting to create an 11th

ephone-dn will fail DN DN
Ephone-dn (Cont.): Basic Configuration
One virtual
voice port
One Line 1001

or channel
• Assigns a primary extension number to an ephone-dn
Cisco CME Files
Cisco CallManager Express Files
TFTP or FLASH
FTP server
GUI files
firmware
Music on Hold
IOS copy tftp flash
or
copy ftp flash
• Load firmware for IP phones and devices

• Used to upgrade Cisco CME
• Load music on hold files
Cisco CallManager Express Files (Cont.)
Bundled Files
Bundled Cisco CME File
Bundled Files
• GUI Files
cme-gui-3.1.1.zip
• Cisco TAPI file
CiscoIOSTSP.zip
• Firmware files
ATA
7902
cme-3.1.1.tar or 7905
7912
cme-3.1.1.zip 7914
extracted yields 7914 Expansion Module
7920
7935
7936
7940
7960
• Music on Hold
music-on-hold.au
Individual Files
Individual Cisco CME Files
• Firmware files
• Basic Cisco CME tar
• GUI tar
GUI Files
GUI Files
GUI Files
• XMLTemplate
xml.template
• GUI files
admin_user.html
admin_user.js
CiscoLogo.gif
Delete.gif
dom.js
cme-gui-3.1.1.tar downarrow.gif
extracted yields ephone_admin.html
logohome.gif
normal_user.html
normal_user.js
Plus.gif
sxiconad.gif
Tab.gif
telephony_service.html
uparrow.gif
xml-test.html
TAPI Integration
Cisco CME - TAPI Integration
TAPI Integration
CiscoIOSTSP1.2.zip
Additional Files
music-on-hold.au
• Use the music-on-hold.au audio file to provide
music for external callers on hold when you are not
using a live feed
xml.template
• Use the xml.template file to allow or restrict the GUI
functions that are available to an optional customer
administrator
Initial Phone Setup
Phones Setup in Cisco CallManager
Express System
Three ways to setup phones:

• Manual
Numerous commands from the CLI
Requires knowledge of Cisco CME commands
Phones entered manually
• Partially automated
Numerous commands from the CLI
Requires knowledge of Cisco CME commands
Simplifies deployment of many IP phones
• Automated
Few commands needed from the CLI
Requires little knowledge of Cisco CME commands
Simplifies deployments
Automated Setup: Overview
Automated Setup
• Simple to configure
• Question and answer interface
• Good for inexperienced administrators
• Created IOS commands in the background
• Deployment and configuration are automated
• Must be no existing telephony service configuration
Automated Setup (Cont.)
• Configure NTP prior to CMERouter1(config)#telephony-service setup

running the setup utility --- Cisco IOS Telephony Services Setup ---
• Load the firmware files Do you want to setup DHCP service for your IP Phones? [yes/no]: y
Configuring DHCP Pool for Cisco IOS Telephony Services :
into flash RAM prior to IP network for telephony-service DHCP Pool:10.90.0.0
running the setup utility Subnet mask for DHCP network :255.255.255.0
TFTP Server IP address (Option 150) :10.90.0.1
• Enter the automated Default Router for DHCP Pool :10.90.0.1
setup mode by entering Do you want to start telephony-service setup? [yes/no]: y
the command Configuring Cisco IOS Telephony Services :
“telephony-service Enter the IP source address for Cisco IOS Telephony Services :10.90.0.1
setup” Enter the Skinny Port for Cisco IOS Telephony Services : [2000]:2000
How many IP phones do you want to configure : [0]: 10
• A question and answer Do you want dual-line extensions assigned to phones? [yes/no]: y
session will start asking What Language do you want on IP phones :
for basic parameters 0 English 6 Dutch
1 French 7 Norwegian
• CTRL + c keystroke can 2 German 8 Portuguese
be used at any time to 3 Russian 9 Danish
4 Spanish 10 Swedish
break out of the setup 5 Italian
mode [0]: 0
• No changes are
committed until the end
Automated Setup (Cont.)
Which Call Progress tone set do you want on IP phones :
• When configuration 0 United States
1 France
is committed the 2 Germany
settings show up in 3 Russia
4 Spain
the running-config 5 Italy
6 Netherlands
7 Norway
8 Portugal
9 UK
10 Denmark
11 Switzerland
12 Sweden
13 Austria
14 Canada
[0]: 0
What is the first extension number you want to configure : [0]: 9000
Do you have Direct-Inward-Dial service for all your phones? [yes/no]: y
Enter the full E.164 number for the first phone :2095559000
Do you want to forward calls to a voice message service? [yes/no]: y
Enter extension or pilot number of the voice message service:9999
Call forward No Answer Timeout : [18]: 10
Do you wish to change any of the above information? [yes/no]: n
---- Setup completed config ---
Automated Setup (Cont.): Results
ip dhcp pool ITS
DHCP pool created network 10.90.0.0 255.255.255.0

default-router 10.90.0.1
Firmware available option 150 ip 10.90.0.1
to TFTP server tftp-server flash:P00303020214.bin
Flash is searched tftp-server flash:P00403020214.bin

and if firmware is telephony-service
found it will be
load 7910 P00403020214
loaded
load 7960-7940 P00303020214
Creates SEP XML create cnf-files
files at boot up and
load to RAM max-ephones 10
max-dn 10
Telephony-service ip source-address 10.10.0.1 port 2000
configuration
results voicemail 9999
auto assign 1 to 10
DID configuration
dialplan-pattern 1 2095559... extension-length 4 extension-
pattern 1...
Firmware is
moh music-on-hold.au
searched and if
MoH is found this ephone-dn 1 dual-line
entry is made number 401
The selected call-forward busy 9999
number of ephone- call-forward noans 9999 timeout 10
dns are configured
Partially Automated Setup: Overview
• Partially Automated Setup

• Is the same as a manual setup except for deploying
phones
• Deployment of IP phones is automated
• Uses the “auto assign” command
• All ephone-dns must be the same type (single-line
or dual-line)
Partially Automated Setup (Cont.)
Auto Assign Command
CMERouter(config-telephony-service)#
auto assign start-dn to stop-dn [type model] [cfw number
timeout seconds]
• Automatically assigns the ephone-dns configured to
new ephones
Auto assign usage guidelines

• Can take up to 5 minutes for phones to register
• Wait for all phones to register before saving the
configuration
• cfw setting defines the call forward busy number
and timeout value for phones that register
Phones Setup in Cisco CallManager
Express System
New phone plugs in telephony-service

auto assign 1 to 10 type 7920
auto assign 11 to 20 type 7940
• When an new IP phone registers with the auto assign 21 to 40 type 7960
Cisco CME system, this creates a new
ephone with the MAC address of the IP auto assign 41 to 50
phone ...
ephone-dn 1 dual-line
• A pre-existing ephone-dn is assigned to the
new ephone; this is selected from the range number 1000
defined for the type of phone ...
• The lowest unassigned ephone-dn in matching statement range will

be used
• If all ephone-dns in a range have been assigned, some phones may
not receive an ephone-dn or may overflow to the general auto assign
without a type
• If the new IP phone does not match any auto assign with a type, then
the auto assign without a type will be used
Manual Setup: Overview
• All commands can be entered from the CLI

• Good for experienced administrators
• Leverages IOS knowledge
• Full functionality through IOS commands
• Deployment of IP phones can be batched or
scripted through a text file
Manual Setup (Cont.): Commands Overview
Commands needed to configure a basic
telephony service
• tftp-server flash:filename
• telephony-service
• max-ephones max-ephones
• max-dn max-directory-numbers
• load phone-type firmware-file
• ip source-address ip-address [port port]
• create cnf-files
• keepalive seconds
• dialplan-pattern tag pattern extension-length length
extension-pattern pattern
Manual Setup (Cont.): tftp-server Command
CMERouter(config)#
tftp-server flash:filename
• Allows a file in flash to be downloadable with TFTP

7940/60
Firmware
7920
Available through TFTP
Firmware
7910
Firmware
tftp-server flash:P00303020214.bin
tftp-server flash:cmterm_7920.3.3-01-06.bin
Manual Setup (Cont.): Telephony Service
Commands
CMERouter(config)#
telephony-service
• Enters telephony service mode
max-ephone maximum-ephones
• Sets the maximum number of ephones that may be

defined in the system (default is 0)
max-dn maximum-directory-numbers
• Sets the maximum number of ephone-dn that may be

defined in the system (default is 0)
Manual Setup (Cont.): Firmware
Association
load model firmware-file
• Associates a firmware file with the model of IP phone
7940/60 7940/7960
telephony-service Firmware
load 7960-7940 P00303020214
load 7920 cmterm_7920.3.3-01-06.bin
load 7910 P00403020214
7920
7920
Firmware
Filenames are case-sensitive 7910

Firmware 7910
Manual Setup (Cont.): Source IP and Port
ip source-address ip-address [port port]
• Identifies the address and port through which IP

phones communicate with Cisco CME
Default
XML
10.90.0.1
telephony-service
ip source-address 10.90.0.1 port 2000
Manual Setup (Cont.): Create XML Files
create cnf-files
• Builds the specific XML files necessary for the IP

phones
SEP SEP000F2473AB14.cnf.xml
XML
000F.2473.AB14
10.90.0.1
telephony-service
create cnf-files
Manual Setup (Cont.): Keepalive
keepalive seconds
• Sets the length of the time interval between keepalive

message from the IP phones to Cisco CME
telephony-service
keepalive 10
Keepalive
Keepalive
• Default is 30 seconds, range is 10 – 65535 seconds

• If 3 keepalives are missed in a row, the device will
have to register again
Manual Setup (Cont.): DID Configuration
Commands
dialplan-pattern tag pattern extension-length length
extension-pattern pattern [no-reg]
• Sets a dial plan pattern which can expand extension
numbers to E.164 numbers that can be used for DIDs
DN 1000
PSTN ISDN PRI

… DN 10XX
DIDs assigned
2015559000
DN 1099
thru
2015559099
telephony-service
dialplay-pattern 1 20155590.. extension-length 4 extension pattern 10..
Manual Setup (Cont.): Example
Manual Setup of the Cisco CME

telephony-service
load 7910 P00403020214
load 7960-7940 P00303020214
create cnf-files
max-ephones 10
max-dn 10
dialplan-pattern 1 2095559... extension-length 4 extension-pattern 1...
Manually number 401
configured call-forward busy 1999

call-forward noans 1999 timeout 10
see module
ephone 1
3 lesson 3
mac-address 000F.2745.2AD8
button 1:1
Setup Troubleshooting: Verify IP
Addressing
Verify the IP addressing on the IP phone

• Use the Settings button and select “Network
Configuration”
• Verify IP and subnet mask are correct
• Verify the TFTP server is the Cisco CME router
• Verify the default gateway is correct
Setup Tips (Cont.): Verify the Correct Files
in Flash
Show flash
CMERouter#show flash
-#- --length-- -----date/time------ path
1 399514 Mar 1 2002 12:56:28 P00305000301.sbn
2 22649180 Mar 1 2002 12:38:00 c3725-ipvoice-mz.123-7.T.bin
3 321939 Mar 1 2002 12:55:58 CP7902010200SCCP031023A.sbin
4 317171 Mar 1 2002 12:56:06 CP7905010200SCCP031023A.sbin
5 317968 Mar 1 2002 12:56:10 CP7912010200SCCP031023A.sbin
6 369950 Mar 1 2002 12:56:22 P00303020214.bin
7 333822 Mar 1 2002 12:56:30 P00403020214.bin
8 47904 Mar 1 2002 12:56:54 S00103020002.bin
9 301298 Mar 1 2002 12:56:56 ata18x-v2-16-ms-030327b.zup
10 496521 Mar 1 2002 12:57:22 music-on-hold.au
11 1908762 Mar 1 2002 12:56:54 P00503010100.bin
12 21 Mar 1 2002 12:56:18 OS7920.txt
13 839984 Mar 1 2002 12:57:18 cmterm_7920.3.3-01-06.bin
14 307067 Mar 1 2002 12:56:02 CP79050101SCCP030530B31.zup
...
Optional Parameters: Locale Parameters
Allow changes to:

• Language of phone display Danish Italian
• Locale for call progress Spanish

tones and cadences
Dutch Norwegian
Swedish
French Portuguese
English
German Russian
Federation
Optional Parameters: Locale Parameters
user-locale language-code
• Specifies the language for display on an IP phone
network-locale language-code
• Specifies the set of call progress tones and cadence

on the IP phone
Optional Parameters: Date and Time
date-format {mm-dd-yy | dd-mm-yy | yy-dd-mm | yy-mm-dd}
• Sets the date format for IP phone displays
time-format {12 | 24}
• Specifies the set of call progress tones and cadence

on the IP phone
Rebooting Cisco CallManager Express
Phones
Reset Command Restart Command

• Hard reboot • Soft reboot
• Phone firmware changes • Phone buttons changes
• User locales changes • Phone lines changes
• Network locales changes • Speed-dial number changes
• URL parameters changes • No DHCP or TFTP invoked
• DHCP and TFTP invoked • System message changes
• Takes longer than restart
Router Configuration: Two Commands
(Cont.)
reset {all [time-interval] | cancel | mac-address |
sequence-all}

CMERouter(config-ephone)#
reset
• Resets a specific ephone
Router Configuration: Two Commands
(Cont.)
restart {all [time-interval] | mac-address}

CMERouter(config-ephone)#
restart
• Restarts the ephone
Setup Troubleshooting
Troubleshooting setup overview

• Verify that a correct IP address and scope options
are received on the IP phone
• Verify the correct files are in flash
• Debug the tftp server
• Verify phone firmware install
• Verify locale is correct
• Verify phone setup
• Review configuration
Verifying Cisco CallManager Express
Phone Configuration
Verify ephone-dn Configurations

show running-config
telephony-service
load 7910 P00403020214
load 7960-7940 P00303020214
max-ephones 10
max-dn 10
auto assign 1 to 10
create cnf-files dialplan-pattern 1 2015559... extension-length 4 extension-pattern 1...
voicemail 9999
max-conferences 8
!
number 9000
!
ephone 1
mac-address 000F.2470.F8F8
button 1:1
Setup Tips (Cont.): Debug tftp events
command
Debug tftp events command

CMERouter#debug tftp events
Mar 2 19:32:59.333: TFTP: Looking for OS79XX.TXT
Mar 2 19:32:59.337: TFTP: Looking for SEP000F2470F8F8.cnf.xml
Mar 2 19:32:59.681: TFTP: Opened system:/its/XMLDefault7960.cnf.xml, fd 0, size 784 for
process 131
Mar 2 19:32:59.685: TFTP: Finished system:/its/XMLDefault7960.cnf.xml, time 00:00:00 for
process 131
Mar 2 19:33:02.713: TFTP: Looking for SEP000F2470F8F8.cnf.xml
Mar 2 19:33:02.713: TFTP: Opened system:/its/XMLDefault7960.cnf.xml, fd 0, size 784 for
process 131
Mar 2 19:33:02.745: TFTP: Finished system:/its/XMLDefault7960.cnf.xml, time 00:00:00 for
process 131
• Can verify if the SEP file for the phone is found

• Can verify the downloading of the correct firmware
Phone Configuration (Cont.)
Verify Phone Firmware Installation
debug ephone register
Mar 2 15:16:57.582: New Skinny socket accepted [1] (2 active)
Mar 2 15:16:57.582: sin_family 2, sin_port 49692, in_addr 10.90.0.11
Mar 2 15:16:57.582: skinny_add_socket 1 10.90.0.11 49692
Mar 2 15:16:57.766: %IPPHONE-6-REG_ALARM: 20: Name=SEP000F2470F8F8 Load=3.2(2.14) Last=Phone-Keypad
Mar 2 15:16:57.766: Skinny StationAlarmMessage on socket [1] 10.90.0.11 SEP000F2470F8F8
Mar 2 15:16:57.766: severityInformational p1=2368 [0x940] p2=184551946 [0xB000A0A]
Mar 2 15:16:57.766: 20: Name=SEP000F2470F8F8 Load=3.2(2.14) Last=Phone-Keypad
Mar 2 15:16:57.766: ephone-(1)[1] StationRegisterMessage (1/2/2) from 10.90.0.11
Mar 2 15:16:57.766: ephone-(1)[1] Register StationIdentifier DeviceName SEP000F2470F8F8
Mar 2 15:16:57.766: ephone-(1)[1] StationIdentifier Instance 1 deviceType 7
Mar 2 15:16:57.766: ephone-1[-1]:stationIpAddr 10.90.0.11
Mar 2 15:16:57.766: ephone-1[1]:phone SEP000F2470F8F8 re-associate OK on socket [1]
Mar 2 15:16:57.766: %IPPHONE-6-REGISTER: ephone-1:SEP000F2470F8F8 IP:10.90.0.11 has registered.
Mar 2 15:16:57.766: Phone 0 socket 1
Mar 2 15:16:57.766: Skinny Local IP address = 10.95.0.1 on port 2000
...
Mar 2 15:16:57.766: Skinny Phone IP address = 10.90.0.11 49692
Mar 2 15:16:57.766: ephone-1[1]:Date Format M/D/Y
Mar 2 15:16:57.766: ephone-1[1][SEP000F2470F8F8]:RegisterAck sent to ephone 1: keepalive period 30
Verify Locale-Specific Files

CMERouter1#show telephony-service tftp-bindings
tftp-server system:/its/SEPDEFAULT.cnf
tftp-server system:/its/SEPDEFAULT.cnf alias SEPDefault.cnf
tftp-server system:/its/XMLDefault.cnf.xml alias XMLDefault.cnf.xml
tftp-server system:/its/ATADefault.cnf.xml
tftp-server system:/its/united_states/7960-tones.xml alias United_States/7960-tones.xml
tftp-server system:/its/united_states/7960-font.xml alias English_United_States/7960-font.xml
tftp-server system:/its/united_states/7960-dictionary.xml alias English_United_States/7960-
dictionary.xml
tftp-server system:/its/united_states/7960-kate.xml alias English_United_States/7960-kate.xml
tftp-server system:/its/united_states/SCCP-dictionary.xml alias English_United_States/SCCP-
dictionary.xml
tftp-server system:/its/XMLDefault7960.cnf.xml alias SEP000F2470F8F8.cnf.xml
tftp-server system:/its/XMLDefault7960.cnf.xml alias SEP000F23FC9CF0.cnf.xml
Verify Cisco IP Phone Setup

CMERouter1#show ephone
ephone-1 Mac:000F.2470.F8F8 TCP socket:[1] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:1
IP:10.10.0.11 49692 Telecaster 7960 keepalive 29 max_line 6
button 1: dn 1 number 1000 CH1 IDLE CH2 IDLE
ephone-2 Mac:000F.23FC.9CF0 TCP socket:[2] activeLine:0 REGISTERED

mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:1
IP:10.10.0.13 52633 Telecaster 7960 keepalive 135 max_line 6
button 1: dn 2 number 1001 CH1 IDLE CH2 IDLE

Configuring Cisco Callmanager Express (Cme) : Cisco Networking Academy Program

Uploaded by

Copyright:

Available Formats

Configuring Cisco Callmanager Express (Cme) : Cisco Networking Academy Program

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Cisco Callmanager Express (Cme) : Cisco Networking Academy Program

Uploaded by

Copyright:

Available Formats

Configuring Cisco CallManager

Cisco Networking Academy Program

• Call processing for small to medium sized

• Select IOS based platform

PSTN H.323 between Cisco

1. Sample the analog signal regularly

• High-quality voice at low bit rates, processor

• Both are ITU standards

• Provides end-to-end network functions and delivery

• Monitors the quality of the data distribution and

• RTP header compression saves bandwidth by

• Traditional telephony networks claim 99.999%

• Ethernet: 18 bytes overhead

Skinny Client Control Protocol (SCCP)

Skinny Protocol Caveats

• Cisco CME does not support remotely registered

Cisco CME can register to a H.323 gatekeeper thereby

H.323 is recommended today

• Cisco CME software and files

Cisco CME 3.1 caveats

• TAPI Lite Functionality

• Prevent unnecessary IP address renumbering

Public IP addresses IP Phone uses private Network

IP Phone + PC on separate switch ports IP Phone + PC on separate switch ports

Public IP addresses IP Phone uses private network

• An access port able to handle 2 VLANs

Tagged 802.1q (Voice VLAN)

Untagged 802.3 (Native VLAN)

Example 3550 switch or EtherSwitch Network Module

• 802.1q trunking is enabled on the port

Negotiation of Trunking: Disabled

Priority for untagged frames: 0

Dynamic Host Configuration Protocol

DHCP Service Options

On the Cisco CME router a DHCP

The phone initializes the IP stack

Continued next slide…

IP phone send DHCP Discover

DHCP server selects a free IP

The IP phone initializes applies the

The IP phone requests it

• Sets a range of addresses to be excluded from the

• Creates and enters a the DHCP scope mode

• Defines the range of addresses that will be used to

• Defines a custom option and its value

• Sets the default gateway that will handed out to the

• Sets the DNS server(s) that will assigned to the DHCP

Configuring DHCP on an IOS router

• Option 150 sets the TFTP server on the IP phone

• XmlDefault.cnf.xml TFTP Server

• Firmware is installed in flash RAM with the Cisco CME

XML <phrase i="159" t="ImmDiv" />

the user-locale command …

• The 7914 expansion module cannot auto register

Step 1 - Switch sends a Fast Link Pulse (FLP)

Step 2 - The phone returns the FLP to the

Step 3 - Power is applied

Step 4 - Link is detected on

Step 5 - The IP phone boots up