I found that even though I was using bootROM 4.2.2 in both entries, I
had to fully delete the bootROM from the upload page. Essentially
leaving 3.1.3revC "Device Files" entry as an empty shell (no zip files,
references for SIP and bootROM at <browse>). Then I could activate the
other (i.e. 3.2.3) for the IP335s.

So basically to toggle back to say 3.1.3revC I would first have to
deactivate the now active 3.2.3 entry, and delete both the SIP and
bootROM files. Then click on the 3.1.3 entry, browse and load the
3.1.3revC SIP zip and the same bootrom zip I was using before. Apply
etc. and that will activate.



-----Original Message-----
From: Tony Graziano [mailto:tgrazi...@myitdepartment.net] 
Sent: Thursday, July 15, 2010 3:07 PM
To: McIlvin, Don; sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] "Internal Error" trying to activate in Device
files 3.1.3revC for Polycom phones

I would suggest deleting the entry for the one that gives you a problem
via
sipxconfig first. Then I'd suggest making sure those zip files are gone
from
the tftp directory. Then I'd try to upload the files again and check
their
ownership/permissions and try to activate it again.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

----- Original Message -----
From: sipx-users-boun...@list.sipfoundry.org
<sipx-users-boun...@list.sipfoundry.org>
To: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org>
Sent: Thu Jul 15 14:55:23 2010
Subject: Re: [sipx-users] "Internal Error" trying to activate in
Devicefiles3.1.3revC for Polycom phones

Tony,

Thanks for the XX tracker..



Just to Clarify, I was dealing strictly at the .zip file level using the
sipXconfig. At the linux level just (ls -al) etc. on the .../tfptroot to
see what was there, and a (cat xx) to view ReadMe.txt).



I wanted to have in Device Files one Polycom entry for the phones using
SIP 3.1.3revC, and a second entry for SIP 3.2.3 to use with the IP335s
(not supported in 3.1.3revC), both would use Bootrom 4.2.2. I had hoped
to simply activate and deactivate which ever version I needed in
.../tfptroot.



The error log indicated a problem with opening a ZIP file. The
.../tfptroot would contain the correct SIP files (which ever version I
was trying to activate), but no corresponding Bootrom files. While it
didn't indicate the file name, it apparently erred trying to open the
associated bootrom zip file. Each time there was a second logging event
related to an "illegal state" that corresponded to when I clicked on
(here) within the "Internal error" message.





Regards,

Don McIlvin



Telecom Department

Realogy/NRT/Coldwell Banker

52 Second Ave. (3rd Floor)

Waltham, MA 02451

Office 781-684-5669









From: Tony Graziano [mailto:tgrazi...@myitdepartment.net]
Sent: Wednesday, July 14, 2010 4:48 PM
To: McIlvin, Don
Cc: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] "Internal Error" trying to activate in Device
files 3.1.3revC for Polycom phones



You should only be uploading the polycom ZIP file. If not, perhaps you
hit this.



http://track.sipfoundry.org/browse/XX-6856





On Wed, Jul 14, 2010 at 4:43 PM, McIlvin, Don
<don.mcil...@nrtnortheast.com> wrote:

The error occurred on both the "device file" page and "upload" page
after clicking <activate>.. "An internal error has occurred. Click
(here) to continue". The (here) brought me to the SipXecs config 4.2
login page. All the other device file sets where deactivated at the
time. Only by deleting list entries so only one Polycom remained, would
it successfully activate.

Is there an XX-nnnn entry to fix this? I sure would like very much to
vote for it :).

Making it easier to manage and apply different versions or combinations
of boot and SIP sw for varied phone models would be rather helpful.

I have some IP335s that are not supported in SIP 3.1.3revC. But also
have IP4xx, IP5xx, and IP6xx which evidently work best with that SIP
rev.


Regards,
Don McIlvin

Telecom Department
Realogy/NRT/Coldwell Banker
52 Second Ave. (3rd Floor)
Waltham, MA 02451
Office 781-684-5669






"The information in this electronic mail message is the sender's
confidential business and may be legally privileged. It is intended
solely for the addressee(s). Access to this internet electronic mail
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken or
omitted to be taken in reliance on it is prohibited and may be
unlawful."

"The sender believes that this E-mail and any attachments were free of
any virus, worm, Trojan horse, and/or malicious code when sent. This
message and its attachments could have been infected during
transmission. By reading the message and opening any attachments, the
recipient accepts full responsibility for taking protective and remedial
action about viruses and other defects. The sender's employer is not
liable for any loss or damage arising in any way from this message or
its attachments." [v1.0.07.109]
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/




-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to