[cisco-voip] IP Phone Keep Looking old CCM

[Ryan Ratliff]

The security profile only comes into play when your cluster is in  
mixed mode.  If this is true then even though your security profile  
is set to unsecured the phone will still have downloaded the CTL.tlv  
file and thus will only use a TFTP server that is specified in the  
CTL file.  Unless you ran the CTL client and added your new cluster's  
TFTP server as authorized then the phones would never have picked up  
a config file from the new cluster.  If you gave the new servers the  
same IP address as servers in the old cluster then the phone's "old"  
config file would have been sufficient once you changed system- 
 >server to reference IP address rather than hostname.

-Ryan

On May 14, 2009, at 3:11 PM, Anthony Kouloglou wrote:

Hi Ryan,
you are correct. That was (is) a dark spot for me: the hostname of  
the ccm at these two settings.
I will do some more reading on this.
Maybe they got registered because the hostname was the same as the  
old integration?
Also, the security profile on the device has nothing to do with the  
problem i had?

Ryan Ratliff wrote:
>
> Sounds like you are talking about the OS Admin hostname of the  
> server versus the CCMAdmin System->Server settings.   The OS admin  
> pages are all specific to the OS of the server.  The CCMAdmin  
> settings are all the CallManager application settings.   They are  
> entirely separate and only related in that the CUCM application  
> relies on the underlying OS.
>
> IIRC  you mentioned before that you do not have DNS configured in  
> the network.  If that is the case and your System->Server entries  
> were by hostname then you are lucky your phones registered in the  
> first place.   I encourage you to go check the documentation for  
> more information on the role the System->Server entries play in  
> phone registration.
>
> -Ryan
>
> On May 14, 2009, at 11:42 AM, Anthony Kouloglou wrote:
>
> I have just changed the name from system->server to IP and kept the  
> hostname in the field of the hostname of the settingd->ethernet-  
> and the phones overcame the problem and work fine!
> If someone could explain this?
> If you have an ip configured in system->server what is the meaning  
> of host field in the settings->ip-?ethernet field?
>
> Thanks and Kind Regards
> Anthony
>
> Anthony Kouloglou wrote:
>>
>> Hi Wes,
>> yes security is enabled (in serviceability you mean).
>> Also, the devices got generated by the DMA from 4.1 so they have  
>> been inserted with a security profile!! (i have never used this  
>> thing)
>> I I changed it back to standard no secure 79XX profile but again,  
>> they keep searching first for the old tftp.
>> But, when i navigated through the phone menu to network config and  
>> then to option 29 (something about resetting the settings) the  
>> phone never looked for the old CCM :-)
>> How can i do this remotely though?
>>
>> Thanks
>> Anthony
>>
>> Wes Sisk wrote:
>>>
>>> Do you have secruity enabled?  If so, you have to updated CTL  
>>> files to make the 6.1 TFTP address a 'valid' TFTP provider.
>>>
>>> /Wes
>>>
>>> On May 13, 2009, at 5:20 PM, Anthony Kouloglou wrote:
>>>
>>> Hi, i had my 4.1 CCM replaced by a 6.1 CUCM.
>>> the old one is still running since it has co resident a CRS with  
>>> an AA.
>>> I use a trunk to send calls to new 6.1. That works fine
>>> In my DHCP pool, i have the tftp option changed to point at 6.1  
>>> IP but, the phones even though they have the new option for the  
>>> TFTP (CUCM 6.1) They keep register at old CCM 4.1!!
>>> Only if i shutdown CCM service at 4.1, the phone after a timeout,  
>>> it registers to 6.1.
>>> If then i turn again on the CCM service at 4.1, the phone does  
>>> not register back to the 4.1.
>>> But, if i reset the phone, it goes and registers back to the 4.1!!
>>> I do not use DNS but both CCM have the same name.
>>> Could this be a problem even though i do not use DNS?
>>> how about a factory reset to all phones?
>>>
>>> Because when i plugged in a brand new device, it got registered  
>>> directly to the 6.1.
>>> So it has something to do with the "memory" of the old devices.
>>>
>>> Thanks
>>> Anthony
>>> _______________________________________________
>>> 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
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>