History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XCF-860
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Alex Zolotar
Votes: 0
Watchers: 0
Available Workflow Actions

Resolve
Request Information
Operations

If you were logged in you would be able to see more operations.
sipXconfig

SIPx doesn't easily support an environment with various Polycom phone models that require different version of firmware

Created: 2006-01-09 11:07   Updated: 2006-02-01 16:07
Component/s: polycom
Affects Version/s: 3.0
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
Configserver needs ability to maintain different version of firmware for different Polycom phones. Different phone models now come with various bootrom and sip loads. Currently, if we use TFTP server on the SIPx for upgrades all the phones will try to load whatever is on the TFTP server. This doesn't always work. For example SoundPoint 4000 now ships with bootrom 3.1, while SoundPoint 500 can only run bootrom 2.6.

Each Polycom configuration file contains APPLICATION APP_FILE_PATH="sip.ld" variable that can be set to a certain sip image. I don't know if there is a similar structure for bootrom as well. This setting has to be manageable from the SIPx GUI, based on the group and phone model.


 All   Comments   Work Log   Change History      Sort Order:
Douglas Hubler - 2006-01-09 12:29
If we need it, we can add it, I want to make sure we need it though. Did you read somewhere that SoundPoint 500 cannot load bootrom 3.1 or did it reject it w/error? If so what error did you get?

Alex Zolotar - 2006-01-09 13:00
No, I didn't try loading bootrom 3.1 on SoundPoint 500. I don't want my 500 model phones to have that version, I want them to have 2.6 - the latest certified version. However 4000 comes with bootrom 3.1 and can not be downgraded to 2.6. If I try to downgrade to 2.6 it comes up with "BootRom has changed....Error 0x0". This is a real production example. I'm forced to use DHCP with a MAC address reservations to force a different value of TFTP server for some phones. For these phone I use a different TFTP server that contains firmware for these phones only. I'm lucky to have two TFTP servers in this environment, or I'd be configuring my 4000 phones manually through its web UI.

Here is another possible scenario: I want to upgrade my Polycom phones to newer version of bootrom/sip. I want to try with a small pilot group first, to see if works before I upgrade all the phones.

Douglas Hubler - 2006-02-01 16:07
r6011 | lazyboy | 2006-02-01 11:50:32 -0500 (Wed, 01 Feb 2006) | 1 line

FYI: With the fix of XCF-898, you can now define multiple firmware entries, however this doesn't address your issue of having 2 active at the same time. You must toggle from one firmware version to another, so I'm not marking this issue resolved.

See wiki for more info
 http://sipx-wiki.calivia.com/index.php/Managing_Device_Firmware