
| Key: |
XCF-860
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Alex Zolotar
|
| Votes: |
0
|
| Watchers: |
0
|
|
Available Workflow Actions
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
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
|
|
|
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.
|
|
Description
|
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.
|
Show » |
|