[cisco-voip] CM 8 ITL and TFTP problems

[Jason Burns]

Justin,

Option 150 is usually an array of IPv4 addresses. This is how I have it
setup with my CUCM 8 cluster and my phones are downloading their
configuration files successfully. Your config as you've described it should
be fine.

I'd be curious to see if the phone is downloading the config file and then
rejecting it, or if the phone isn't able to contact the TFTP server.

One great way to check is to go to the webserver on the IP Phone (if it's in
a state where the web server is active) and download the console log files.

The phone is going to try downloading the config file, and then compare the
signature in the file with the ITL file contents. Post back the contents of
the console logs, or let us know if you see any errors there. A good first
troubleshooting step is to restart the TFTP service on CUCM and then delete
the ITL from the phone. This will make sure the phone and the server have
the same copy of the ITL file. (The phone will download the new ITL as soon
as you delete it.)

-Jason

On Thu, Dec 9, 2010 at 10:34 PM, Justin Steinberg <jsteinberg at gmail.com>wrote:

> New cm 8 install and I'm having issues with the 7945 phones not being
> able to download files (ringlist, phone config file, etc) from TFTP.
>
> I think it is related to ITL and the security by default.
>
> My CM is setup User system>server as IP address.   My voice vlan dhcp
> scopes are setup with IP addresses for the option 150 values.
>
> When I look at the phone, under the security section and ITL section I
> see the TFTP server is referred there as the FQDN.
>
> I think my prob is the dhcp scope is IP and do it's not matching the ITL
> value.
>
> Has anyone dealt with this or understand what is going on?
>
> Justin
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101212/383354a0/attachment.html>