[cisco-voip] tftp server 255.255.255.255

[Neil Robst]

Alternatively have you tried configuring ip helper on your routers:

http://routergod.com/trinity/

to forward the TFTP broadcast to your TFTP server?

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: 14 February 2011 13:27
To: Andy Carse
Cc: cisco-voip
Subject: Re: [cisco-voip] tftp server 255.255.255.255

You probably know those already, but some phones can have their TFTP server set manually. If you browse to the phones configuration page, you can look at the Alternate TFTP setting and see if it says Yes. 

With a remote control software or the clients help you can easily set this back to no. 

Sent from my iPhone

On Feb 14, 2011, at 8:21 AM, Andy Carse <andy at carse.demon.co.uk> wrote:

> yes the tftp options are correct its just certain handsets don't over write tftp info
> 
> On 02/14/2011 12:42 PM, Neil Robst wrote:
>> I assume you have the "option 150" settings configured in the DHCP scopes for these phones pointing at the correct TFTP servers?
>> 
>> That's what we use here and it works a treat...
>> 
>> Regards,
>> Neil
>> 
>> -----Original Message-----
>> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
>> Sent: 14 February 2011 12:36
>> To: Andy Carse
>> Cc: cisco-voip
>> Subject: Re: [cisco-voip] tftp server 255.255.255.255
>> 
>> There are some remote control software solutions out there that might be useful. You still have to perform the steps but it's a little better than having to visit each site.
>> 
>> Sent from my iPhone
>> 
>> On Feb 14, 2011, at 6:31 AM, Andy Carse<andy at carse.demon.co.uk>  wrote:
>> 
>>> I guess I already know the answer, but I'll ask any way.
>>> 
>>> I have possibly several handsets that have been deployed that out of the box had their tftp server as 255.255.255.255.
>>> 
>>> They are setup for DHCP but the tftp server info doesn't seem to get updated, I have seen this before but we found it whilst actually deploying handsets so we checked them as they were rolled out.
>>> 
>>> As such they would have booted up ok and worked assuming they didn't have extension mobilty setup.
>>> 
>>> No we are in the process of upgrading the firmware for an upgrade due in a couple of weeks.
>>> 
>>> These handsets won't be able to upgrade is there an "easy" way of finding these devices?
>>> 
>>> They won't show up in the Device Firmware Load info as they don't talk to the cluster in the normal way.
>>> 
>>> The only way we have found to recify this is to visit a handset and erase its config.
>>> 
>>> we have 10 sites and 4000 handsets, so it could take awhile.
>>> 
>>> Currently running 5.1.2 going to 7.1.5su3
>>> 
>>> -- 
>>> Rgds Andy
>>> 
>>> _______________________________________________
>>> 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
>> 
> 
> -- 
> Rgds Andy
> 
> _______________________________________________
> 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