Configuring CME router

davenull · December 2014

make sure you have option 150 set in the dhcp pool for the Data vlan as well

sacredboy · December 2014

davenull wrote: »

make sure you have option 150 set in the dhcp pool for the Data vlan as well

It was an issue of permissions. I launched CIPC using "Run As" and the Network tab became available.

sacredboy · July 2015

Hello guys.

For now I have my all 7960G IP phones working via SCCP. Is it possible to configure CME so that some phones to use SIP and other phones to use SCCP?

davenull · July 2015

Yes, voice register global and telephony-service can coexist but with some caveats, for example this one: https://supportforums.cisco.com/discussion/11585026/telephony-service-voice-register-global-interoperability

sacredboy · July 2015

I mean, is it possible to have, for instance, ephone 1 and ephone 3 to use SIP and ephone 2 and ephone 4 to use SCCP. How to define explicitly which exactly phone should use either SIP or SCCP?

BTW: One question regarding TFTP server. I'd like to use an external TFTP server rather than internal one on CME. For firmware that were hosted on CME router I'm using the following lines:

tftp-server flash:FMW/7940-7960/P0030801SR02.bin alias P0030801SR02.bin
tftp-server flash:FMW/7940-7960/P0030801SR02.loads alias P0030801SR02.loads
tftp-server flash:FMW/7940-7960/P0030801SR02.sb2 alias P0030801SR02.sb2
tftp-server flash:FMW/7940-7960/P0030801SR02.sbn alias P0030801SR02.sbn

How to specify (which command I should use) the way to external TFTP server?

davenull · July 2015

To use an external TFTP server you'll first need to specify that server's IP address in the option 150 under the dhcp scope configuration. You'll also need to tell CME to save config files to that tftp server by using cnf-file location tftp:// command under telephony-service for SCCP phones or tftp-path tftp:// command under voice register global for SIP phones.

I haven't tried running both SCCP and SIP phones on the same router but you should be able to. To make CME support SIP phones you'll have to do a totally separate configuration which somewhat mirrors SCCP configuration. Here's a sample config from an 1861 router:

voice service voip
 allow-connections h323 to h323
 allow-connections sip to sip
 allow-connections h323 to sip
 allow-connections sip to h323
 h323
 sip
  bind control source-interface Vlan10
  bind media source-interface Vlan10
  registrar server
!
!
voice register global
 mode cme
 source-address 10.0.10.1 port 5060
 max-dn 15
 max-pool 8
 load 7961 SIP41.9-4-2SR1-1S
 create profile sync 0201375098428007
!
voice register dn  1
 number 4001
!
voice register pool  1
 id mac 0017.95F5.4F1D
 type 7961
 number 1 dn 1

as you can see:

voice register global = telephony-service
voice register dn = ephone-dn
voice register pool = ephone

To make sure specific phones use SCCP or SIP you'll need to configure your ephones and voice register pools with the correct mac addresses before you boot the phones. Run create cnf-files and create profile under telephony-service and voice register global, respectively, after you added the phones mac addresses too.

sacredboy · July 2015

OK, for now the TFTP server is installed and configured; firmwares are moved; option 150 tftp_ip_address is configured with external TFTP address, cnf-files location TFTP tftp://ip_address/directory is configured. But how to specify which firmware a phone (a model of phone) should load and the way to a firmware? When firmwares are stored in CME flash, it is specified in the following way:

tftp-server flash:FMW/7940-7960/P0030801SR02.bin alias P0030801SR02.bin
tftp-server flash:FMW/7940-7960/P0030801SR02.loads alias P0030801SR02.loads
tftp-server flash:FMW/7940-7960/P0030801SR02.sb2 alias P0030801SR02.sb2
tftp-server flash:FMW/7940-7960/P0030801SR02.sbn alias P0030801SR02.sbn

But how it works with an external TFTP server?

davenull · July 2015

Here's how it works I think:

1. You specify load 7960 P00308010200 under telephony-service for SCCP phones or load 7960 P0S3-8-12-00 under voice register global for SIP phones.
2. You configure your phones under ephones (SCCP) or voice register pools (SIP) with their mac addresses and type.
3. You run create cnf-files or create profile. When you run this command CME is going to create a config file for every configured phone and it's going to store that config on the external tftp-server (in our case). That file will also include the version of firmware the phone is supposed to run. The config file is of the format SEP<mac_address>.cnf.xml for a SCCP phone and SIP<mac_address>.cnf for a SIP phone.

The phone knows the tftp server's address and it's programmed to look for a config file with its own mac-address. However, phones are not aware of paths to the file; all they know is the ip address and what the file should look like. That's why you configure aliases on the CME router. You'd have to make all files available under the root directory of the external tftp server, or configure something like aliases on it as well, if possible.

When the phone downloads its config file, it compares the firmware that it's running against the firmware that is specified in the file. It then downloads new firmware from the tftp server if needed.

Here's some more information from Cisco:

After a phone is reset or restarted, the phone automatically selects protocol depending on which matching configuration file is found first. To ensure that Cisco Unified IP phones download the appropriate configuration for the desired protocol, SCCP or SIP, you must properly configure the IP phones before connecting or rebooting the phones. The hunt algorithm searches for files in the following order:
1. CTLSEP file for a SCCP phone—For example, CTLSEP003094C25D2E.tlv
2. SEP file for a SCCP phone—For example, SEP003094C25D2E.cnf.xml
3. SIP file for a SIP phone—For example, SIP003094C25D2E.cnf or gk003069C25D2E
4. XML default file for SCCP phones—For example, SEPDefault.cnf.xmls
5. XML default file for SIP phones—For example, SIPDefault.cnf.

More info at:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm/cmefiles.pdf

sacredboy · July 2015

davenull, thank you for your reply.

davenull wrote: »

1. You specify load 7960 P00308010200 under telephony-service for SCCP phones or load 7960 P0S3-8-12-00 under voice register global for SIP phones.

Actually, I even didn't specify this line in my configuration on the CME and phones successfully found the firmware.

davenull wrote: »

The phone knows the tftp server's address and it's programmed to look for a config file with its own mac-address. However, phones are not aware of paths to the file; all they know is the ip address and what the file should look like. That's why you configure aliases on the CME router. You'd have to make all files available under the root directory of the external tftp server, or configure something like aliases on it as well, if possible.

When the phone downloads its config file, it compares the firmware that it's running against the firmware that is specified in the file. It then downloads new firmware from the tftp server if needed.

You know, if I store the firmwares in TFTP root directory then everything works fine. But I want to create own directory for every IP phone model. For example, /7960 directory for 7960 firmware and /7970. Which command or commands I should use in order to crate aliases on CME router?

davenull · July 2015

The reason the phones found their firmware is because CME comes with some firmware. You can see it in show telephony-service tftp-bindings.

Use the same commands mentioned earlier, for example:

tftp-server flash:7960/P00308010200.loads alias P00308010200.loads

They are applicable only when the CME itself acts as a tftp server though.

In case of an external tftp server I'm not aware of any command that would make a phone look in a specific directory on that server. It's the external tftp server's job to know aliases (if possible) for when a phone comes to look for a file. I looked around in tftpd64 but didn't see anything.

sacredboy · July 2015

I faced with the problem with my Cisco 7970G IP phone which I'm trying to configure to work via SIP. Below is the part of my config:

tftp-server flash:/7970/SIP/apps70.9-4-2ES9.sbn alias apps70.9-4-2ES9.sbn 
tftp-server flash:/7970/SIP/cnu70.9-4-2ES9.sbn alias cnu70.9-4-2ES9.sbn 
tftp-server flash:/7970/SIP/cvm70sip.9-4-2ES9.sbn alias cvm70sip.9-4-2ES9.sbn 
tftp-server flash:/7970/SIP/dsp70.9-4-2ES9.sbn alias dsp70.9-4-2ES9.sbn 
tftp-server flash:/7970/SIP/jar70sip.9-4-2ES9.sbn alias jar70sip.9-4-2ES9.sbn 
tftp-server flash:/7970/SIP/SIP70.9-4-2SR1-1S.loads alias SIP70.9-4-2SR1-1S.loads 
tftp-server flash:/7970/SIP/term70.default.loads alias term70.default.loads 
tftp-server flash:/7970/SIP/term71.default.loads alias term71.default.loads
!
voice service voip 
 allow-connections sip to sip 
 fax protocol cisco 
 sip 
  registrar server 
! 
voice register global 
 mode cme 
 source-address 177.3.11.1 port 5060 
 max-dn 10 
 max-pool 5 
 load 7970 SIP70.9-4-2SR1-1s 
 tftp-path flash: 
 create profile sync 0078327219347302 
! 
voice register dn  1 
 number 3002 
! 
voice register pool  1 
 id mac 001F.9E26.4B8B 
 number 1 dn 1 
 codec g711ulaw

The 1st problem is that phone is stuck with UNPROVISIONED error.
The 2nd problem is that after erasing config section for SIP and entering lines for SCCP aliases I get the error (on screenshots).

Could you please help me to solve this problem.

cisco_nerd · July 2015

I noticed that you have this:

voice register global
load 7970 SIP70.9-4-2SR1-1s

but your TFTP alias is SIP70.9-4-2SR1-1S

sacredboy · July 2015

It seems that the reason of the problem was the firmware and CME version incompatibility.

sacredboy · June 2016

Hi guys,

I'm in the process of installing Cisco Unified CME but stucked in the very beginning. Below are the steps I have already taken:
1. Checked CME compatibility matrix. As I have C2800NM-ADVENTERPRISEK9-M version 15.1(4)M10 IOS on my router then CME 8.6 version is compatible.
2. Downloaded cme-151-4Mv1.zip
3. Copied cme-151-4Mv1.zip to TFTP
4. Run archive tar /xtract tftp://192.168.10.2/cme-151-4mv.zip flash:/CME

However, I got:
%Tar checksum error in tftp://192.168.10.2/cme-151-4mv.zip

This is I suppose because I use tar command attribute but my cme file is in zip format. But on Cisco website there is no .tar file for CME 8.6. Also it's not clear what does "CME tar bundle for version 8.6 - cme-151-4Mv1.zip" mean.

Could you please help me with is issue.

davenull · June 2016

You don't really need to install CME. You've got an image that has VoIP, so you just need to type 'telephony-service' or 'voice register global' and CME activates. That zip contains firmwares, music-on-hold.au, and the archaic CME GUI that nobody uses.

Legacy User · July 2016

sacredboy wrote: »

Hi guys,

I'm in the process of installing Cisco Unified CME but stucked in the very beginning. Below are the steps I have already taken:
1. Checked CME compatibility matrix. As I have C2800NM-ADVENTERPRISEK9-M version 15.1(4)M10 IOS on my router then CME 8.6 version is compatible.
2. Downloaded cme-151-4Mv1.zip
3. Copied cme-151-4Mv1.zip to TFTP
4. Run archive tar /xtract tftp://192.168.10.2/cme-151-4mv.zip flash:/CME

However, I got:
%Tar checksum error in tftp://192.168.10.2/cme-151-4mv.zip

This is I suppose because I use tar command attribute but my cme file is in zip format. But on Cisco website there is no .tar file for CME 8.6. Also it's not clear what does "CME tar bundle for version 8.6 - cme-151-4Mv1.zip" mean.

Could you please help me with is issue.

You could extract that zip on your pc and convert it to a tar file then retry that command again. But there is no need to extract every file in that zip to your machine. Just upload the firmware for the phones you have in your lab and files related to the cme gui, ringtones, background.

Configuring CME router

Comments