[asterisk-users] problems with Polycom 500 boot up

[Forum]

It looks like the problem is solved. The existing bootROM on the phone was
2.0.2 so I updated it with the earliest bootROM I could find - 2.3. Now the
challenge updating to the latest bootROM.

 

  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jessee J
Holmes
Sent: Wednesday, September 20, 2006 12:07 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] problems with Polycom 500 boot up

 

Dear Steve,

 

This is very puzzling, it should take.

 

bootrom.ld is the file on your FTP server right? Does your FTP server show
the phone pinging it in the FTP application logs?

 

Which bootrom are you trying to load. The latest should be 3.2.2 I
believe.....

 

Let me know and I'll see what I can find you. You shouldn't have a corrupted
bootrom chip, but I won't rule it out just yet.

 

 

Jessee Holmes

Atacomm / Ataractic Corporation

www.atacomm.com

V: 1-877-700-VOIP

jholmes at atacomm.com

 

Looking for voice over IP products?  Visit our VoIP store at
http://voipstore.atacomm.com/





 

On Sep 20, 2006, at 12:18 PM, Forum wrote:





Thanks for your response.

 

Unfortunately I still receive the same error - 'Error updating bootrom' - no
matter what version of sip and the bootROM I upload to the ftp site. I have
even used the latest release of the fimware - could I have somehow broke the
phone with a corrupted flash. How do I do a full format when it can not
update the bootROM?

 

Steve

 

  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jessee J
Holmes
Sent: Friday, September 15, 2006 7:17 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] problems with Polycom 500 boot up

 

Dear Steve,

 

The phone may be looking for it's specific configuration files (not
phone1.cfg, but instead 0004F........cfg {or [mac].cfg}). In our past
experience, if the phone was ever formatted (fully formatted), the phone
will request this from the FTP server specified. Of course confirm your
phone's login to your FTP server is correct, confirm the phone is logging in
and grabbing the files (should be able to be done through your FTP program's
interface).

 

Also, as odd as this sounds, check your firewall on your network. In the
past, we've ran into some weird things happening where the firewall will let
some Polycom phones through, but not all. So confirm your Polycom phone is
talking to your FTP client (again your log files can tell you this).

 

For further information, I suggest looking at one of our knowledgeable
articles on this topic:
http://voipstore.atacomm.com/Support/KB/ViewArticle.aspx/27934028032-1-24.ht
m

 

 

 

Jessee Holmes

Atacomm / Ataractic Corporation

www.atacomm.com

V: 1-877-700-VOIP

jholmes at atacomm.com

 

Looking for voice over IP products?  Visit our VoIP store at
http://voipstore.atacomm.com/






 

On Sep 14, 2006, at 4:03 PM, Forum wrote:






I have a Polycom 500 that I am having issues with provisioning via an ftp
server. I have a bunch of 301's that find the server and configure without
an issue. For some reason the 500 gives me an error that it 'could not
contact boot server' and will reboot continuously.  I also get the error
'Error updating Bootrom'. I am using Bootrom 3.2.1. What files do I need on
the ftp server ? - I have sip.Id, bootrom.Id, sip.ver, phone1.cfg and
sip.cfg. 

 

Any help would be appreciated!

 

Steve

 

 

_______________________________________________

--Bandwidth and Colocation provided by Easynews.com --

 

asterisk-users mailing list

To UNSUBSCRIBE or update options visit:

   http://lists.digium.com/mailman/listinfo/asterisk-users

 

_______________________________________________

--Bandwidth and Colocation provided by Easynews.com --

 

asterisk-users mailing list

To UNSUBSCRIBE or update options visit:

   http://lists.digium.com/mailman/listinfo/asterisk-users

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060920/a185e297/attachment.htm