Examine the Router's CME Configuration
On your router, examine your running config to see the telephony changes added. They are located in the telephony-service section. It is important that you familiarize yourself with the command line configuration as CME lives half in the GUI and the other half in the command line.
The IP phone configuration starts in the telephony-service section of the running configuration. The actual telephony commands are scattered through-out the running configuration and are not limited to the telephony-service section. The following configuration is a bare bones example of the telephony-service section:
telephony-service load 7960-7940 P00308000500 max-ephones 2 max-dn 2 ip source-address 192.168.30.1 port 2000 auto assign 1 to 2
load 7960-7940 P00308000500
This command identifies the firmware to load for specific phone models. In this case, its for the 7960 and 7940 series of phones. It works for 7961 and 7941 phones also. This way you can specify specific firmware for different models if needed.
This command sets the maximum number of physical phones that are allowed to connect to CME. During the initial setup, only 2 were indicated. If more phones were required, you could manually issue the command with however many phones you need.
This command sets the maximum number of dialing numbers (extensions) that CME will allow. In this case, only 2 extensions. If you want to add another phone then you will need to increase the number of dialing numbers too.
ip source-address 192.168.30.1 port 2000
This command specifies which IP address that CME will use for voice communications - it should be on the Voice VLAN. All phones will register to this IP address. The port indicates the UDP port that is used by the SCCP protocol which is port 2000.
auto assign 1 to 2
This command allows CME to auto configure the phones as they are physically connected. The ephone and ephone-dn commands will be auto populated with information. If there were more phones, you could change it to "auto assign 1 to 10".
I have mixed feelings about this command as I've had instances where I've had to take the whole system down and then when CME and the phones rebooted, all of the phone's dialing numbers changed! So it was like all of the extensions were randomly assigned depending on which phone booted first. After the initial setup, I prefer to assign any new extensions through the CME GUI and remove this command.
The command ephone-dn stands for "electronic phone dialing number" or as it is commonly known as the "extension" number. The first extension is "ephone-dn 1", the next "ephone-dn 2", etc.. Here's an example of the first extension configuration:
ephone-dn 1 dual-line ; this indicates the first (1) extension number 2201 ; assigns the extension or dialing number call-forward busy 2200 ; when busy forward to the voicemail pilot number call-forward noan 2200 timeout 10 ; on no answer go to voicemail pilot number
Examine the physical phone configuration under the command "ephone x". The first physical phone is "ephone 1", the next is "ephone 2", etc.. This is an example of a bare bones ephone configuration:
ephone 1 ; indicates the first phone to configure multicast-moh ; allow music on hold mac-address 001B.535C.FC66 ; mac address of phone type 7960 ; model of phone for firmware loading button 1:1 ; Line 1 uses dialing number 1
Cisco Unified IP Phones have two default ring types: Chirp1 and Chirp2. Unique rings can be configured and the user can configure their phone with a distinctive ring through the phone's Settings - Ring Type. This is a very nice feature for users who work in a cubicle style or an area where there are a lot of phones. The users recognize when it is their phone ringing and not their neighbour's. It gives immediate positive feedback and users really appreciate this feature.
Note: files on the router are case sensitive! You will have to share each ring tone and the XML files that list the ring tones: DistinctiveRingList.xml and RingList.xml. The format fo the two files is quite simple and you will have to format the files to list the ring tones that you have shared via tftp on your system.
I've found that Cisco does not have a standard case convection for the RingList.xml file that the phones look for. The default file name is RingList.xml, but I've found that some 7960 phones require a file called RINGLIST.XML. Solution is to copy RingList.xml as RINGLIST.XML on the router. Then the phones are happy. You can check the phone's Status Messages to see if it is failing to download the files from the tftpserver.
Enable distinctive ring tones by adding the following files to the router's tftp-server list. In my system, I shared each of the following files:
Router(config)# tftp-server flash:DistinctiveRingList.xml
When the phone boots up, it requests from the tftp server the RingList.xml file and the DistinctiveRingList.xml file. This gives the phone a list of ring tones that will appear in the phone's Settings - Ring Type menu. When you select a ring tone, the phone makes a request to the tftp server to download the file exactly as indicated by the xml files. The file names have to match case and must be shared by the tftp server for this to work.
If this page has helped you, please consider donating $1.00 to support the cost of hosting this site, thanks.