[cisco-voip] Registering a hardphone to a different CCM cluster

Paul Yago pyago at adomo.com
Wed Aug 10 18:04:07 EDT 2005


Wes, I don't have any fwd/rev DNS lookup service running on the second stand-alone cluster. How would this affect the phone registry?



-----Original Message-----
From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Wednesday, August 10, 2005 12:59 PM
To: Paul Yago; Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Registering a hardphone to a different CCM cluster

originally even the 40's and 60's had a concept of 'verified' server where
it attempted a forward and reverse DNS lookup of the server and stored
whichever lookup was successful as the last known good server.

do both of your clusters have fwd/reverse DNS lookup?

/Wes

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Paul Yago
Sent: Wednesday, August 10, 2005 3:25 PM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Registering a hardphone to a different CCM
cluster


These suggestions (Alternate TFTP, DHCP enabled, TFTP setting) work fine on
the 7940s and IPCommunicators. However the 7905s and the 7912s are still
staying with the original CCM.

Unfortunately, we also have 7902s which are useless because we can't even
change the TFTP settings, and register with the right CCM.

-Paul




-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, August 10, 2005 10:59 AM
To: Paul Yago
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Registering a hardphone to a different CCM cluster

Since the TFTP server tells the phone what CM to register with the only
way to force your phone to register to another CM cluster would be to
change the TFTP settings.

That said you do not need to disable DHCP to achieve this.  Simply set
"Alternate TFTP" to True, then manually enter in the TFTP server IP
address.

-Ryan
On Aug 10, 2005, at 1:49 PM, Paul Yago wrote:

Hello,
 
Does anyone know the secret to forcing a phone to register to another
CCM cluster on the same subnet?
 
We have one CCM cluster, running TFTP on both CCMs, to which our DHCP
server points new phones (via the 150 option). Sometimes I would like
to switch a hardphone (i.e. 7905) from this cluster to another separate
cluster.
 
To do so, on the phone I disable DHCP and change the TFTP Server 1
value to the other CCM. And when I validate, it restarts the phone and
50% of the time, the phone registers with the other CCM. 50% of the
time it stays with the original CCM, regardless of the new settings. In
such a case, the network settings on the phone still have the correct
TFTP and DHCP settings, but the Call Manager settings are still set to
the original CCM.
 
I would like to find a way to force my phone to register with the new
CCM. Is there a way other than changing the TFTP settings? By the way,
I've tried turning off the TFTP service of the original CCM, which
works. However I don't always have access to that CCM.
 
 
Thanks,
Paul
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



More information about the cisco-voip mailing list