[cisco-voip] Registering Phones

[Ryan Ratliff]

Most likely the firmware on the phone from manufacturing doesn't support peer firmware sharing.

That said, if it did then it would be enabled by the TFTP config file the phone downloads from CUCM and that happens before the phone tries to upgrade firmware.

-Ryan

On Apr 1, 2010, at 4:01 PM, Jason Aarons (US) wrote:

Does the default load out of the box from manufacturing having peer firmware sharing enabled by default?  O
 
r do new phone deployments require a TFTP/cnf download that turns on peer firmware sharing?
 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Thursday, April 01, 2010 2:03 PM
To: H, Tim
Cc: cisco-voip at puck-nether.net
Subject: Re: [cisco-voip] Registering Phones
 
You can specify a load server in CCMAdmin for the phone(s).  They will use DHCP option 150 for TFTP but when pulling firmware files will try to get it from that server.  
 
That and peer-firmware sharing should help out a lot.
 
-Ryan
 
On Apr 1, 2010, at 1:34 PM, H, Tim wrote:


Is there a way to tell the status of a phone from a remote site?  I have phones setup to DHCP and auto-register to the CUCM.  The problem is, they’ll be downloading different firmware and probably take quite a while to load up.  I need to know if the phones actually are downloading the firmware or not.  Any idea on how to tell this?
 
Is there a way to put the firmware config on the local VGW to pull from it?
 
Thanks,
 
Tim
 
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
 


Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100401/541040c8/attachment.html>