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

[Candace Holman]

Sorry - I think you're out of luck if the phone record exists on both 
publishers and you only have access to one of them.  What you are trying 
to do is evade a built-in failover between clusters, and the only sure 
way to do that within the same subnet  is to make sure the phone is only 
registered on one publisher.

(Seems strange to me that anyone would set up failover clusters on the 
same subnet.  It would be a better idea to put them on different subnets 
- if that were the case you could set up a different DHCP scope for your 
Option 150 record too, and be done with this.)

You never mentioned your CM versions are the same between clusters.  
7905 and 7912 require 3.3.3 and above, so if your second publisher is 
not 3.3.3, you won't be able to register.

Candace

Paul Yago wrote:

>Thanks Candace, the problem is that I'd like to switch back and forth
>between CCMs. And I don't have access to the first one. And when I
>attempt to register a phone with CCM2 which has never been registered on
>CCM1, then I still see this problem. Perhaps there is still a phone
>record on the CCM1 though. I was checking for phone records and I'm not
>quite sure where they are? In TFTPPath?
>
>-----Original Message-----
>From: Candace Holman [mailto:candace_holman at harvard.edu] 
>Sent: Wednesday, August 10, 2005 1:12 PM
>To: Paul Yago
>Cc: Ryan Ratliff; cisco-voip at puck.nether.net
>Subject: Re: [cisco-voip] Registering a hardphone to a different CCM
>cluster
>
>Do you have the phone record on both clusters?  It may be worth a try to
>
>just delete the phone record from the first cluster, or even more 
>simply, zero out the MAC address, save and reset the phone. 
>
>Candace
>
>Paul Yago wrote:
>
>  
>
>>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
>> 
>>
>>    
>>