Hello,

Background: http://track.sipfoundry.org/browse/XCF-3622

I think we need to take more caution on change of device settings
through sipXconfig GUI, as most of device settings, such as network
settings are not done through sipXconfig GUI. 
To simply expose some of them but without any level of control sometime
can lead to confusion in the field.

For device settings, device.xxx.yyy.set  is used to  determine whether
or not the existing setting of device.xxx.yyy on the phone should be
changed or not. 
For example,  in profile, if device.net.cdpEnabled.set =1, it will
overwrite the existing device setting with the value configured; if
device.net.cdpEnabled.set =0, the existing configuration for
device.net.cdpEnabled will not be changed, or in other words, the
configuration for the setting will be ignored.

Details on device settings can be seen on page A-124 of:
http://www.polycom.com/global/documents/support/setup_maintenance/produc
ts/voice/spip_ssip_Admin_Guide_SIP_3_1.pdf 


If we set device.xxx.yyy.set  to 1 for all the device settings exposed
to sipXconfig, it will always overwrite the existing device settings. In
some cases, may lead to unintended result. A good example from Paul
Mossman, if user enables CDP by hand on TUI, and the default on
sipXconfig GUI is "disabled", when user simply adding a new polycom
phone unaware of the default congiruation on sipXconfig GUI and send
profile, the CDP setting will be overwritten to "disabled", which is
probably not the result of what customer intends to have.  

To avoid this kind of unfriendly user experience,  after a discussion
with Paul Mossman, we think it is better to introduce a layer of control
for overwriting device settings. We propose to add a flag, called
something like "Overwrite Device Settings" for all the device settings
exposed to sipXconfig for Polycom phones, and by default, it is
disabled. 
- Disabled: means device.xxx.yyy.set will be set to 0, and the device
settings from profile generated by sipXconfig will be ignored. 
- Enabled: means device.xxx.yyy.set will be set to 1, and device
settings from profile generated by sipXconfig will overwrite the
existing settings on the device. 

This way, when customer explicitly enable the flag, that means he/she
understand the effect and causes no confusion.

Comments?

Thanks,
Huijun
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to