Loading Softkey Template on 7960 and CCM 4.01

[h.mahmoud]

Did anyone face the below problem? any work arrounds?

1- I had a working 7960 with the latest firmware.

2- I have CCM 4.01 sra

3- everything was ok.

4- i moved the set across the WAN to a new site to work on the same call manager in a central deployment model.

4- i changed the confiuration of the set to reflect the new network (IP, gateway, TFTP....etc).

5- The set loads and checks the firmware with the call manager. then it got registared BUT IT Never loads the softkey template?? it keeps requesting the softkey then it fails. So it starts regestering once more. Once the regestiration is successul it requests the softkey template and it fails.....etc...

I did't find any documents on the web and i had never seen such thing before....

i have no ACLs or firewalls in the middle. I have no special softkey templates. i work with the default one!!!

Any idea?? Thanks

[kthorngr]

Hi,

You noted that you changed the network config of the phone including the TFTP server. What is the new TFTP server? What happens if you point the phone back to the previous TFTP server?

Tha best way to find out what is happening during phone registration is to capture the packets to/from the phone. normally you can do this from the PC connected to the PC Port of the phone.

Kevin

[mo.ragheb]

Hello Kevin,

I'm also working with h.mahmoud on this project. I want to add a minor correction. We deployed only 1 callmanager mcs server, thus the TFTP server stays the same. When we deploy ip phones over the local LAN where the callmanager server is located, all the ip phones work fine. However when we take them to the remote location, they keep hanging up on "requesting softkey template". Another correction, we are using CallManager 4.0.2a along with the sr1a multifix patch. I noticed that it added a newer firmware version for the 7960/7940 ip phones. Version 7.1(1) to be exact. Could the new firmware be the problem, or perhaps a bug with CCM 4.0.2? Thanks

[tvanblon]

I had the same problem caused by a bad CM subscriber in the cluster. Pointed the phone to a good CM via device pool->CMG to fix it, then rebuilt the bad subscriber.