Configuring Cisco CallManager ExpressCisco Public
IP Telephony
Cisco Networking Academy Program
Cisco Public
IP Telephony
Overview of Cisco CME
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Call processing for small to medium sized deployments
VoIP integrated solution
IOS based solution
Cisco Public
IP Telephony
Select IOS based platform
Cisco Public
IP Telephony
Connection(s) to PSTN
Cisco Public
IP Telephony
WAN
H.323
H.323
H.323
SIP
PSTN
PSTN
PSTN
WAN
Cisco Public
IP Telephony
Differences between Traditional Telephony and VoIP
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
*
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Cisco Public
IP Telephony
*
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Quantize the sample
Compress the samples to reduce bandwidth (multiplexing), optional step
*
Cisco Public
IP Telephony
Nyquist Theorem
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Quantization Techniques
Two methods
*
Cisco Public
IP Telephony
Voice-Compression Techniques
Waveform algorithms
Cisco Public
IP Telephony
ITU standards:
*
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
Works with queuing to prioritize voice traffic over other traffic
Services include:
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
RTP Header Compression
*
Cisco Public
IP Telephony
Narrowband links
Need to conserve bandwidth on a WAN interface
*
Cisco Public
IP Telephony
Challenges and Solutions in VoIP
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Data networks must consider reliability and availability requirements when incorporating voice
Methods to improve reliability and availability include:
Redundant hardware
Redundant links
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Cisco Public
IP Telephony
*
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Cisco CME Features and Functionality
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Analog Phones
Cisco Public
IP Telephony
Cisco proprietary
Cisco Public
IP Telephony
Supported Protocols and Integration Options (Cont.)
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
Skinny Protocol Caveats
Cisco Public
IP Telephony
Cisco CME does not support remotely registered phones
Remote Phones
Local Phones
Cisco Public
IP Telephony
Supports Voice, Video, and Data
Industry Standard
Complex protocol
CAC functionality is part of the protocol
Authentication is part of the protocol
H.323 Protocol
Cisco Public
IP Telephony
H.323 Connections
Cisco Public
IP Telephony
Gatekeeper
WAN
Register
H.323
1000 2095551000
2000 3095552000
Register
*
Cisco Public
IP Telephony
Emerging standard
Authentication is part of the protocol
Based on other well known protocols
SIP Protocol
Cisco Public
IP Telephony
SIP Connections
Cisco Public
IP Telephony
IP Voice
GUI files
Cisco Public
IP Telephony
G.729 conferences
Cisco Public
IP Telephony
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
Direct media- and voice-handling
Cisco Public
IP Telephony
Cisco CME Network Parameters
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Auxiliary VLANs
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
*
Cisco Public
IP Telephony
Public IP addresses
10.1.1.1
171.68.249.100
IP Phone + PC on same switch ports
IP Phone uses private network
IP Phone + PC on separate switch ports
10.1.1.1
171.68.249.100
Recommended
Cisco Public
IP Telephony
Native VLAN (PVID) and Auxiliary VLAN (VVID)
Hardware set to dot1q trunk
Tagged 802.1q (Voice VLAN)
Untagged 802.3 (Native VLAN)
Cisco Public
IP Telephony
Address learning
Forward/filter decision
Loop avoidance
Cisco Public
IP Telephony
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
Console(config)#interface FastEthernet0/1
Console(config-if)#switchport trunk native vlan 1
Console)config-if)#switchport access vlan 12
Console(config-if)#switchport mode trunk
Console(config-if)#spanning-tree portfast
*
Cisco Public
IP Telephony
Name: Fa0/17
Switchport: Enabled
Trunking Native Mode VLAN: 12 (VLAN0012)
Trunking VLANs Enabled: ALL
Trunking VLANs Active: 1-3,5,10,12
Pruning VLANs Enabled: 2-1001
Voice VLAN: 112
Appliance trust: none
Cisco Public
IP Telephony
802.1q trunk
Cisco Public
IP Telephony
DHCP Service Setup
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
Dynamic Host Configuration Protocol
Cisco Public
IP Telephony
Separate DHCP IP Address Pool for Each Cisco IP Phone
DHCP Relay Server
DHCP Service Options
Cisco Public
IP Telephony
Range of available IP addresses
The subnet mask
A default gateway
DNS server(s)
On the Cisco CME router a DHCP Scope can be configured. The scope should define the following:
The IP phone powers on
The phone performs a Power on Self Test (POST)
Through CDP the IP phone learns what the auxiliary VLAN is
The phone initializes the IP stack
The phone boots up
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
CMERouter(config)#
Sets a range of addresses to be excluded from the configured scopes
ip dhcp pool pool-name
network subnet subnet-mask
CMERouter(dhcp-config)#
*
Cisco Public
IP Telephony
CMERouter(dhcp-config)#
Sets the default gateway that will handed out to the DCHP clients
dns-server primary-IP [secondary IP]
CMERouter(dhcp-config)#
Sets the DNS server(s) that will assigned to the DHCP clients
option option-number ip IP-address
*
Cisco Public
IP Telephony
Option 150 sets the TFTP server on the IP phone
The TFTP server contains the configuration files and firmware for the IP phone
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)#default-router 10.90.0.1
Cisco Public
IP Telephony
IP Phone Registration
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
TFTP Server
Cisco Public
IP Telephony
Files (Cont.): Firmware
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
…
…
7905
Firmware
7940
Firmware
7960
Firmware
Cisco Public
IP Telephony
<device>
<devicePool>
<callManagerGroup>
<members>
  <loadInformation>P00303020214</loadInformation>
XML
SEP
Cisco Public
IP Telephony
<Default>
<callManagerGroup>
<members>
<loadInformation124 model="Addon 7914"></loadInformation124>
<loadInformation8 model="IP Phone 7940">P00303020214</loadInformation8>
<loadInformation7 model="IP Phone 7960">P00303020214</loadInformation7>
<loadInformation20000 model="IP Phone 7905"></loadInformation20000>
<loadInformation30008 model="IP Phone 7902"></loadInformation30008>
<loadInformation30002 model="IP Phone 7920"></loadInformation30002>
<loadInformation30019 model="IP Phone 7936"></loadInformation30019>
<loadInformation30007 model="IP Phone 7912"></loadInformation30007>
</Default>
XMLDefault.cnf.xml
XML
Default
Cisco Public
IP Telephony
<?xml version="1.0" encoding="ISO-8859-1" ?>
<phrases>
<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" />
<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" />
<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"/>
<phrase i="150" t="Error Unknown"/>
<phrase i="149" t="Error Pass Limit"/>
…
7960-dictionary.xml
SCCP-dictionary.xml
Contents will vary based upon language selected with the user-locale command
XML
Language
Cisco Public
IP Telephony
<tones>
<tone c1="30831" i1="-2032" c2="30467" i2="-1104" d="2" 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" t="reorder">
<part m="on" t="250"/>
<part m="off" t="250"/>
<repeat c="65535"/>
</tone>
<tone c1="30467" i1="-1104" c2="28959" i2="-1404" d="2" t="busy">
<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>
<tone c1="30831" i1="-2032" c2="31538" i2="-814" d="2" t="idial">
<part m="on" t="65535"/>
<repeat c="65535"/>
</tone>
</tones>
7960-tones.xml
Contents will vary based upon call progress tones selected with the network-locale command
XML
Call
Progress
Cisco Public
IP Telephony
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
<loadInformation6 model="IP Phone 7910">P00403020214</loadInformation6>
<loadInformation124 model="Addon 7914"></loadInformation124>
<loadInformation8 model="IP Phone 7940">P00303020214</loadInformation8>
<loadInformation7 model="IP Phone 7960">P00303020214</loadInformation7>
<loadInformation20000 model="IP Phone 7905"></loadInformation20000>
<loadInformation30008 model="IP Phone 7902"></loadInformation30008>
<loadInformation30002 model="IP Phone 7920"></loadInformation30002>
<loadInformation30019 model="IP Phone 7936"></loadInformation30019>
<loadInformation30007 model="IP Phone 7912"></loadInformation30007>
No 7914 in the XMLDefault.cnf.xml
XML
Default
Cisco Public
IP Telephony
Step 3 - Power is applied
FLP
FLP
Step 4 - Link is detected on switchport
Step 6 - The amount of power really needed is passed through CDP from the IP phone to the switch
CDP
Power needed
*
Cisco Public
IP Telephony
DHCP
Step 7 - CDP is used to send the auxiliary VLAN information from the switch to the IP phone
Step 8 - The IP phone initializes the IP stack and sends a DHCPDiscover broadcast message
Step 9 - The DHCP server hears the DHCPDiscover message and selects an IP address from the scope and sends a DHCPOffer
CDP
DHCPDiscover
DHCPOffer
IP address, Subnet Mask, Default Gateway, and TFTP server (option 150)
Broadcast
Cisco Public
IP Telephony
Existing IP Phone
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
Cisco CME is the TFTP Server
SEP000F2470AA32.cnf.xml file
MAC 000F.2470.AA32
If no SEP XML file is found go to Step 14
XML
SEP
Cisco Public
IP Telephony
Unknown IP Address
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
Cisco CME is the TFTP Server
TFTP request for firmware if needed
Step 13 - IP phone will reboot if the firmware was updated
MAC 000F.2470.AA32
Firmware file
Cisco Public
IP Telephony
Unknown IP Phone
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
Step 14 - If no SEP XML file was found then download from the TFTP server the XMLDefault.cnf.xml file
CallManager Express is the TFTP Server
XMLDefault.cnf.xml file
TFTP request for the XMLDefault.cnf.xml file
Unknown IP address with MAC 000F.2470.AA32
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
or
XML
Default
Cisco Public
IP Telephony
Ephone-dn and Ephone
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Line and voice port are equivalent
Has a unique tag or sequence number assigned when the ephone-dn is created
Can have one or more telephone numbers associated with it
Can have one voice channel or two voice channels
Creates one or more telephony system pots dial peers when the ephone-dn is initially configured
DN1
DN1
Primary/Secondary extensions configured on a single line ephone-dn where the primary is an internal extension number and the secondary is an E.164 number
One phone extension on a dual line ephone-dn for ephone-dns that need call waiting, consultative transfer and conferencing
DN1
Primary extension number on a single line ephone-dn that can make or receive one call at a time
ephone-dn
ephone-dn
ephone-dn
Cisco Public
IP Telephony
Ephone-dn (Cont.)
router(config)#
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).
number dn-number secondary dn-number [no-reg [both | primary]]
router(config-ephone-dn)#
*
Cisco Public
IP Telephony
Software configuration of a physical phone
Has a unique tag or sequence number assigned when the ephone is created
Can be an IP phone, analog phone attached to an ATA
The MAC of the IP phone or ATA is used to tie the software configuration to the hardware
The hardware is auto detected for all supported models except the ATA and 7914 expansion module
Can have one or more ephone-dn(s) associated with the ephone
Number of line buttons will vary based on the hardware
MAC 000F.2470.F92A
MAC 000F.2470.F92E
MAC 000F.2470.F92B
Cisco Public
IP Telephony
Ephone (Cont.)
ephone phone-tag
mac-address mac-address
router(config-ephone)#
*
Cisco Public
IP Telephony
Ephone (Cont.)
router(config-ephone)#
Associates the ephone-dn(s) with a specific button(s) on the IP phone
type {7940 | 7960} addon 1 7914 [2 7914]
router(config-ephone)#
*
Cisco Public
IP Telephony
000F.2470.F8F8
Cisco Public
IP Telephony
Four physical phones
Four ephones defined
Four ephone-dns defined
Cisco Public
IP Telephony
CMERouter(config)#ephone-dn 10 dual-line
Cisco Public
IP Telephony
Two ephones defined
Cisco Public
IP Telephony
CMERouter(config)#ephone-dn 14 dual-line
*
Cisco Public
IP Telephony
Shared ephone-dn
Multiple ephone-dns
Overlay ephone-dn
Single line
Dual line
Primary and secondary extension on a single or dual line ephone-dn
Shared single or dual line ephone-dn
Overlay ephone-dns on an ephone
1003
1003
Multiple single or dual line ephone-dns on one or more ephones
1003
1003
Cisco Public
IP Telephony
The ephone-dn creates one virtual voice port
One call to or from this ephone-dn at any one time
CMERouter(Config)#ephone-dn 1 CMERouter(Config-ephone-dn)#number 1001
1001
Cisco Public
IP Telephony
The ephone-dn creates one virtual voice port
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
CMERouter(Config)#ephone-dn 2 dual-line
Cisco Public
IP Telephony
Primary and Secondary Extension Number on Ephone-dn
The ephone-dn creates one virtual voice port
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
CMERouter(Config)#ephone-dn 6
1005 and 2065559005
Cisco Public
IP Telephony
Shared Ephone-dn
Only one phone can use the ephone-dn at a time
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
1006 on line 1
1100 on line 2
Cisco Public
IP Telephony
*
Cisco Public
IP Telephony
On the same ephone
Used when more than two calls to the same extension are needed
On different ephones
Not a shared line
Only one ephone will ring at a time
A call on hold can be retrieved only by the ephone that put the call on hold
1003
1003
Cisco Public
IP Telephony
huntstop [channel]
router(config-ephone-dn)#
*
Cisco Public
IP Telephony
X
Busy
Busy
Busy
Busy
Busy
Preference 0
Preference 1
Preference 2
Preference 3
1020 DN
1020 DN
1020 DN
1020 DN
*
Cisco Public
IP Telephony
Huntstop Channel
Ephone-dn 10
Channel 1
Channel 2
Ephone-dn 11
Channel 1
Channel 2
Ephone-dn 12
Channel 1
Channel 2
no huntstop
no huntstop
Ephone-dn 13
Channel 1
Channel 2
X
Busy
Busy
Busy
Preference 0
Preference 1
Preference 2
Preference 3
1020 DN
1020 DN
1020 DN
1020 DN
Cisco Public
IP Telephony
Two Ephone-dns/One Number/Same Ephone
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
1003 on line button 1
1003 on line button 2
1003
1003
Cisco Public
IP Telephony
CMERouter(config-ephone)#button 1:3 2:4
*
Cisco Public
IP Telephony
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
1004 on line button 2
1004
1004
Cisco Public
IP Telephony
Two ephone-dns with one number on different ephones configuration example
CMERouter(config)#ephone-dn 5 dual line
CMERouter(config-ephone-dn)#number 1004
CMERouter(config-ephone-dn)#preference 0
CMERouter(config-ephone-dn)#no huntstop
CMERouter(config-ephone-dn)#number 1004
CMERouter(config-ephone-dn)#preference 1
Cisco Public
IP Telephony
Overlay Ephone-dn
Two or more ephone-dns applied to the same ephone line button
Up to ten ephone-dns per line button on the phone
1101 on line 4
1101 on line 4
huntstop
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
*
Cisco Public
IP Telephony
Cisco Public
IP Telephony
Number of Ephone-dns max-dn Command
The maximum number of ephone-dns supported is a function of the license and hardware platform
The default is zero
router(config-telephone)#
*
Cisco Public
IP Telephony
*
Cisco Public
IP Telephony
1001
Cisco Public
IP Telephony
Cisco CME Files
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Used to upgrade Cisco CME
Load music on hold files
FLASH
Cisco Public
IP Telephony
Bundled Files
Cisco Public
IP Telephony
Bundled Files
GUI Files
*
Cisco Public
IP Telephony
Individual Files
Cisco Public
IP Telephony
GUI Files
GUI Files
Cisco Public
IP Telephony
GUI Files
Cisco Public
IP Telephony
TAPI Integration
Cisco Public
IP Telephony
TAPI Integration
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
Initial Phone Setup
Thanks for joining us today to attend the Cisco Brand and Corporate Identity Workshop.
In the first half of the workshop I am going to cover Brand Matters and talk in detail about the Cisco brand, and in the second half my colleague Gary McCavvit is going to take you through our updated visual identity system.
*
Cisco Public
IP Telephony
Three ways to setup phones:
Manual
Requires knowledge of Cisco CME commands
Phones entered manually
Requires knowledge of Cisco CME commands
Simplifies deployment of many IP phones
Automated
Requires little knowledge of Cisco CME commands
Simplifies deployments
Cisco Public
IP Telephony
Deployment and configuration are automated
Must be no existing telephony service configuration
*
Cisco Public
IP Telephony
Configure NTP prior to running the setup utility
Load the firmware files into flash RAM prior to running the setup utility
Enter the automated setup mode by entering the command “telephony-service setup”
A question and answer session will start asking for basic parameters
CTRL + c keystroke can be used at any time to break out of the setup mode
No changes are committed until the end
CMERouter1(config)#telephony-service setup
--- Cisco IOS Telephony Services Setup ---
Do you want to setup DHCP service for your IP Phones? [yes/no]: y
Configuring DHCP Pool for Cisco IOS Telephony Services :
IP network for telephony-service DHCP Pool:10.90.0.0
Subnet mask for DHCP network :255.255.255.0
TFTP Server IP address (Option 150) :10.90.0.1
Default Router for DHCP Pool :10.90.0.1
Do you want to start telephony-service setup? [yes/no]: y
Configuring Cisco IOS Telephony Services :
Enter the IP source address for Cisco IOS Telephony Services :10.90.0.1
Enter the Skinny Port for Cisco IOS Telephony Services : [2000]:2000
How many IP phones do you want to configure : [0]: 10
Do you want dual-line extensions assigned to phones? [yes/no]: y
What Language do you want on IP phones :
0 English 6 Dutch
1 French 7 Norwegian
2 German 8 Portuguese
3 Russian 9 Danish
4 Spanish 10 Swedish
Cisco Public
IP Telephony
Automated Setup (Cont.)
When configuration is committed the settings show up in the running-config
Which Call Progress tone set do you want on IP phones :
0 United States
1 France
2 Germany
3 Russia
4 Spain
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 ---
Cisco Public
IP Telephony
Firmware available to TFTP server
Flash is searched and if firmware is found it will be loaded
Telephony-service configuration results
DID configuration
Firmware is searched and if MoH is found this entry is made
The selected number of ephone-dns are configured
Creates SEP XML files at boot up and load to RAM
ip dhcp pool ITS
voicemail 9999
dialplan-pattern 1 2095559... extension-length 4 extension- pattern 1...
moh music-on-hold.au
*
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
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
auto assign start-dn to stop-dn [type model] [cfw number timeout seconds]
CMERouter(config-telephony-service)#
*
Cisco Public
IP Telephony
Phones Setup in Cisco CallManager Express System
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
New phone plugs in
auto assign 41 to 50
...
...
When an new IP phone registers with the Cisco CME system, this creates a new ephone with the MAC address of the IP phone
*
Cisco Public
IP Telephony
Good for experienced administrators
Full functionality through IOS commands
*
Cisco Public
IP Telephony
tftp-server flash:filename
create cnf-files
keepalive seconds
Commands needed to configure a basic telephony service
*
Cisco Public
IP Telephony
tftp-server flash:filename
Allows a file in flash to be downloadable with TFTP
tftp-server flash:P00303020214.bin
tftp-server flash:cmterm_7920.3.3-01-06.bin
tftp-server flash:P00403020214.bin
Cisco Public
IP Telephony
telephony-service
CMERouter(config)#
CMERouter(config-telephony-service)#
Sets the maximum number of ephones that may be defined in the system (default is 0)
max-dn maximum-directory-numbers
CMERouter(config-telephony-service)#
*
Cisco Public
IP Telephony
load model firmware-file
Associates a firmware file with the model of IP phone
7940/7960
7920
7910
telephony-service
Cisco Public
IP Telephony
ip source-address ip-address [port port]
CMERouter(config-telephony-service)#
Identifies the address and port through which IP phones communicate with Cisco CME
telephony-service
10.90.0.1
XML
Default
Cisco Public
IP Telephony
create cnf-files
Builds the specific XML files necessary for the IP phones
telephony-service
Cisco Public
IP Telephony
Default is 30 seconds, range is 10 – 65535 seconds
If 3 keepalives are missed in a row, the device will have to register again
keepalive seconds
CMERouter(config-telephony-service)#
Sets the length of the time interval between keepalive message from the IP phones to Cisco CME
telephony-service
Cisco Public
IP Telephony
dialplan-pattern tag pattern extension-length length extension-pattern pattern [no-reg]
CMERouter(config-telephony-service)#
Sets a dial plan pattern which can expand extension numbers to E.164 numbers that can be used for DIDs
PSTN
*
Cisco Public
IP Telephony
dialplan-pattern 1 2095559... extension-length 4 extension-pattern 1...
ephone-dn 1 dual-line
ephone 1
mac-address 000F.2745.2AD8
button 1:1
Manually configured see module 3 lesson 3
*
Cisco Public
IP Telephony
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
*
Cisco Public
IP Telephony
Show flash
...
*
Cisco Public
IP Telephony
Danish
Dutch
French
German
Swedish
Spanish
Portuguese
Norwegian
Italian
Cisco Public
IP Telephony
network-locale language-code
CMERouter(config-telephony-service)#
*
Cisco Public
IP Telephony
CMERouter(config-telephony-service)#
time-format {12 | 24}
CMERouter(config-telephony-service)#
*
Cisco Public
IP Telephony
Reset Command
Hard reboot
System message changes
Cisco Public
IP Telephony
reset {all [time-interval] | cancel | mac-address | sequence-all}
CMERouter(config-telephony-service)#
reset
CMERouter(config-ephone)#
Cisco Public
IP Telephony
restart {all [time-interval] | mac-address}
restart
CMERouter(config-ephone)#
Cisco Public
IP Telephony
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
Cisco Public
IP Telephony
Verify ephone-dn Configurations
create cnf-files dialplan-pattern 1 2015559... extension-length 4 extension-pattern 1...
voicemail 9999
max-conferences 8
Cisco Public
IP Telephony
Debug tftp events command
CMERouter#debug tftp events
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
*
Cisco Public
IP Telephony
Verify Phone Firmware Installation
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: ephone-1[1]:Date Format M/D/Y
*
Cisco Public
IP Telephony
Verify Locale-Specific Files
Cisco Public
IP Telephony
Verify Cisco IP Phone Setup
CMERouter1#show ephone
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
*
Cisco Public
IP Telephony