
|
Available Workflow Actions
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
Created: 2008-08-21 09:32
Updated: 2008-11-06 09:59
|
|
| Component/s: |
polycom
|
| Affects Version/s: |
3.11.4
|
| Fix Version/s: |
4.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Sub-Tasks:
|
All
|
Open
|
|
| Sub-Task Progress: |
|
|
|
Currently, sipXconfig is hardcoding the default values for some parameters that are not settable from UI. However, Polycom cannot guarantee that some parameters might change between releases that can cause subtle problems - the most obvious real issues from the past were some audio settings which caused poor audio quality if they were not updated between releases. We'd like to clean this up, but where we are now with the number of models of phones and different releases out in the field we can only test and guarantee proper performance if the software and configuration files are matched.
sip.cfg and phone1.cfg provided with each Polycom software release contain all the default values corresponding to the particular release. In order to make sure Polycom pickup the correct default values and avoid problems mentioned earlier, Preserving the sip.cfg and phone1.cfg files in config files is STRONGLY RECOMMNEDED practice. So this request is to create mechanism that will pickup default values from sip.cfg and phone1.cfg for parameters that are not settable from UI.
|
|
Description
|
Currently, sipXconfig is hardcoding the default values for some parameters that are not settable from UI. However, Polycom cannot guarantee that some parameters might change between releases that can cause subtle problems - the most obvious real issues from the past were some audio settings which caused poor audio quality if they were not updated between releases. We'd like to clean this up, but where we are now with the number of models of phones and different releases out in the field we can only test and guarantee proper performance if the software and configuration files are matched.
sip.cfg and phone1.cfg provided with each Polycom software release contain all the default values corresponding to the particular release. In order to make sure Polycom pickup the correct default values and avoid problems mentioned earlier, Preserving the sip.cfg and phone1.cfg files in config files is STRONGLY RECOMMNEDED practice. So this request is to create mechanism that will pickup default values from sip.cfg and phone1.cfg for parameters that are not settable from UI.
|
Show » |
|
The only piece left is how to distribute the default configuration files to tftproot for both developement and production deployment environment.
In order to de-risk the 3.10.3, the submission of this is on hold.