Phone reboots if the Susbcriber goes down

[tarun.pahuja]

Folks,

I have a cluster comprimising of a Publisher and a Suscriber. I have followed cisco's best practices and registered the phones to the suscriber. I see that the suscriber and the publisher do syncronize with each other. Also when i look at the phone network settings it shows me that the suscriber is the active call manager and the publisher is the backup. But, when i reboot the suscriber the phone can not register and reboots and then keeps trying to register.

I have autoregistration turned of on the publisher, but the phone already was registered.

Any ideas, i thought the servers in the cluster were redundant.

Thanks

[munatara]

Cisco CallManager service is responsible for the devices to register. Is that service is up and running fine in the publisher? If it is CallManager 3.3, it needs to be activated first.

[tarun.pahuja]

All services are running on both call managers.

Thanks

[lyanes]

Verifying TFTP Server Settings

The Cisco IP Phone uses the TFTP server setting (settings > Network Configuration > TFTP Server 1) to identify the Cisco CallManager server. If this setting is incorrect, the Cisco IP Phone might continually cycle while attempting to contact the identified TFTP Server. Make sure the TFTP service is running on both PUB and SUB servers.

If you have assigned a static IP address to the phone, you must manually enter this setting. Refer to the "Configuring IP Settings" section.

If you are using DHCP, the phone obtains the address for the TFTP server from the DHCP server. Check the IP address configured in Option 150. See Configuring Windows 2000 DHCP Server for Cisco Call Manager on Cisco.com: http://www.cisco.com/warp/customer/788/AVVID/win2000_dhcp.html

You can also enable the phone to use an alternate TFTP server (settings > Network Configuration > Alternate TFTP Server). This is particularly useful if this phone was recently moved from a different location, such as a test lab to a production network.

You must unlock the network settings before you can assign an alternate TFTP server.

Luis.

[jamie.moss]

One simple thing I would check is that you have both Call Manager servers is the Call Manager Group and that the CM group is assigned to the Device Pool.

What should happen is that if the phone is already running and you shut the primary server down (in your case the subscriber) then it shouldn't cause the phones to go down - all you should see is the screen flicker as it switches to the other Call Manager.

You can verify that by looking at the phone's network configuration (On a 7940/7960 phone press settings, network configuration and look at lines 21 and 22 (Call Manager 1 and Call Manager 2).

Hope this helps.

[jamie.moss]

From reading your problem I have a couple of questions:-

Are all the devices (including CM servers) on the same network segment or are there spread across multiple VLAN's? (if so do the phones have a default gateway and can they ping both Call Manager servers from that segment).

if the above works then the only thing it really can be is configuration of your services (sorry).

I would double check under seviceability and look at the service activation and make sure that all your services are activated and running (just because they are activated doesn't mean they are running) - you can check this in Serviceability / Control center.