CH 5 Managing Endpoints and End Users with CME REVIEW Flashcards
The following list outlines the Cisco IP Phone boot process:
- The 802.3af PoE switch send a small DC voltage on the Ethernet cable, detects an unpowered 802.3af device, and supplies power to the line.
- The switch delivers Voice VLAN info to the Cisco IP Phone using CDP.
- The IP Phone sends a DHCP request on its voice VLAN. The DHCP server replies with IP addressing info, including DHCP Option 150, which directs the IP phone to the TFTP server.
- The IP phone contacts the TFTP server and downloads its configuration file and firmware.
- Based on the IP address listed in the configuration file, the IP phone contacts the call processing server (up to 3 CME routers) which supports VoIP functions
Voice VLAN
To separate the voice and data traffic, you must configure each port connecting to a Cisco IP Phone for a voice VLAN
Switch#conf t
Switch(config)#int f0/1
Switch(config-if)#switchport mode access
Switch(config-if)#switchport voice vlan 100
Switch(config-if)#switchport access vlan 200
Switch(config-if)#spanning-tree portfast
DHCP Services
After the IP phone receives its voice CLAN info, it begins sending DHCP requests. The example enables a Cisco router as a DHCP server. See DATA for your PCs has one pool and VOICE for your ip phones has another pool.
ROUTER(config)#ip dhcp pool VOICE_SCOPE
ROUTER(dhcp-config)#network 172.16.1.0 255.255.255.0
ROUTER(dhcp-config)#default-router 172.16.1.1
ROUTER(dhcp-config)#option 150 172.16.1.1
ROUTER(dhcp-config)#dns-server 4.2.2.2
Note: Option 150, which gives the IP phone the IP address of the TFTP server.
TFTP Services
During the IP phone boot process, the IP phone contacts the TFTP server to download its configuration files.
The TFTP server is what it has always been: a simple file store that serves files to unauthenticated clients on demand.
The TFTP server plays the role of “file server” in the IP telephony network.
Although you can install and configure a TFTP server on virtually any device, typically the Cisco router (in the case of CME) or the CUCM Publisher server handles the role of the TFTP server.
CME router generates these configuration files
The CME router generates these configuration files as you work through the initial configuration. For example, if you specify a new firmware load for a Cisco IP Phone to use, the CME router would modify a configuration file in flash (or an external TFTP server, if that’s what you chose to use) to list the new firmware image. The next time the phone reboots, it receives the new configuration file, realizes its firmware is out of date, and contacts the TFTP server to download and apply the new firmware image.
XMLDefault.cnf.xml file
If you have not entered any individual phone configurations, the only configuration file sent to the Cisco IP Phones is the XMLDefault.cnf.xml file. This file contains the IP address and port number used to connect to the call processing server (the CME router, in our case) and the names of the firmware file the IP phone should use. After the IP phone has this configuration file, it downloads the necessary firmware and contacts the CME router
stored on an external TFTP server
In CME 4.0 and later, configuration and firmware files can be stored on an external TFTP server using the command cnf-file location tftp:// from telephony service configuration mode. This can save some valuable flash space on your router.
Configure Router as TFTP for IP phone firmware files
Verify the files are on the flash
CME_Voice# dir flash:
Directory of flash:
98 -rw- 129824 May 12 2008 21:33:56 -07:00 P00308000500.bin
99 -rw- 458 May 12 2008 21:33:56 -07:00 P00308000500.loads
100 -rw- 705536 May 12 2008 21:34:00 -07:00 P00308000500.sb2
101 -rw- 130228 May 12 2008 21:34:00 -07:00 P00308000500.sbn
Make files available on TFTP-server
CME_Voice# configure terminal
CME_Voice(config)# tftp-server flash:P00308000500.bin
CME_Voice(config)# tftp-server flash:P00308000500.loads
CME_Voice(config)# tftp-server flash:P00308000500.sb2
CME_Voice(config)# tftp-server flash:P00308000500.sbn
Load each model
CMERouter(config-telephony)# load 7960-7940 P0003080500
CMERouter(config-telephony)# load 7942 P0003080500
Basic CME configuration
- max-ephones: The max-ephones parameter configures the maximum number of IP phones the router will support.
- max-dn: The max-dn parameter specifies the maximum number of directory numbers
- ip source address: The ip source-address command enables the router to know which IP address will receive registration requests from the IP phones.
Understanding and Configuring Ephone-DNs
- An ephone-dn in its simplest form is just a directory number that can be assigned to one or more buttons on one or more Cisco IP Phones.
- You can configure each ephone-dn you create as either a single- or dual-line mode ephone-dn.
Single-line ephone-dn
In single-line mode, the ephone-dn is able to make or receive only one call at a time. If a call arrives on an ephone-dn where there is already an active call, the caller receives a busy signal.
Dual-line ephone-dn
In dual-line mode, the ephone-dn is able to handle two simultaneous calls. This is useful for supporting features like call waiting, conference calling, and consultative transfers.
Configuring ephone-dn
CME_Voice# config t
CME_Voice(config)# ephone-dn 1
CME_Voice(config-ephone-dn)# number 1000
CME_Voice(config-ephone-dn)# exit
CME_Voice(config)# ephone-dn 2
CME_Voice(config)# ephone-dn 2 dual-line
CME_Voice(config-ephone-dn)# number 1001