Re: CME and tftp-server flash command

ciscoforum · ‎11-19-2004

I found without tftp-server flash command the ip phone also will register with CME router. Initially i defined tftp-server flash:P00403020214.bin for 7960 and 7940. They working fine. later on I put 7910 on the network,it also register without configure tftp flash for 7910 image. Was this command not necessary. CME 3.1 and 3745 ios c3745-ipvoice-mz.123-8.T3.bin. thanks . btw,also non load command under telephony sevice.

Aaron Harrison · ‎11-20-2004

Basically the tftp-server command allows the TFTP service on your CME router to server that particular file.

The load command specifies the particular load that the phones should run - if they don't have the same version they will try to download it.

So if you configure both commands phones will all go to the same load version. If you don't configure the load command, they will just register and will work if they have a compatible load on there.

If you configure the load command but not the tftp-server command for that file, then you may find that your phone just reboots continuously if it has the wrong load...

You should configure them to all run the same version to avoid any interoperability issues that may come up....

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

ciscoforum · ‎11-20-2004

Thanks very much for your answer.

What I am not clear is the process of the phone registration. Usually phone reboots get IP from DHCP and then send TFTP request to TFTP server to download image and phone config. So which one of the command tftp-server or load command will help phone to download the image? i think it should the tftp command , right?

In my case I have no tftp and load configured. there must be a default behavior. I think CME allows the phone to look for a image file in the flash and load it to the phone because when phone boots up the CME knows which model it is. Is assumption right? thanks

rajeshkh · ‎12-01-2004

The phone boot process is as follows:

1.Sends out CDP (Cisco Discovery Protocol) messages to discover the voice VLAN information from the switch.

2.If the LAN switch is configured with voice VLAN information the phone receives its voice VLAN information from the switch.

3.The IP phone broadcasts a DHCP request to the LAN.

4.The DHCP server responds to the DHCP request with IP address, default gateway, and TFTP server information.

5.The IP Phone requests a file named SEPxxxxyyyyzzzz.cnf.xml, where xxxxyyyyzzzz denotes the MAC address of the IP phone, from the TFTP server.

6.The TFTP server sends the requested file to the IP phone. The file also contains the IP address of the Cisco CME router.

7.The IP phone sends a registration request to the Cisco CME router.

8.The Cisco CME router sends the phone configuration to the IP phone.

Now when you configure the "create-cnf-file" command the SEPxxxxyyyyzzzz.cnf.xml files are automatically created put on the tftp-server. You can see these files by issuing the command "show telephony-service tftp-bindings". If the current load on the phone is different from the phone load on the router then the phone will try to download this load from the tftp-server. If you have the load on the flash and if you haven't configured the tftp-server command for this new load, then the phone will not be able to download this load. If you running phone loads from CME v2.0 (P003H302.bin) loads, your phone will never get registered. If the current load of the phone is (P00303030214.bin or something similar) then the phone will register after a few attempts with an error. The phone will get registered but not all of the functions may work properly.

Rajesh