Hi everyone!  I have two phone groups defined:/

"normal_phone",/ which defines my basic settings for all phones, and

/"snom320_admin_mode"/, which simply turns the admin mode on in a phone.

The default setting in SipX is for admin mode to be ON, but I turn it OFF in /"normal_phone"/. I should therefore be able to apply /"snom320_admin_mode"/ after /"normal_phone"/ to configure a phone with my basic settings + admin mode ON. But it doesn't appear to work. When I turn the admin mode OFF in a phone group, the web ui indicates that the setting has been changed away from the SipX defaults. But when I turn it on again, the web ui indictes that the setting is the same as the SipX defaults and will therefore have no affect. Here is the chain of events that I *_/expect/_* to happen:

  1. SipX default: admin mode ON
  2. Apply phone group /"normal_phone"/ (with admin mode OFF).
  3. Result: admin mode OFF
  4. Apply phone group /"//snom320_admin_mode//"/ (with admin mode ON).
  5. Result: admin modeON

Here is the chain of events that _/*actually*/_ happens:

  1. SipX default: admin mode ON
  2. Apply phone group /"normal_phone"/ (with admin mode OFF).
  3. Result: admin mode OFF
  4. Apply phone group /"//snom320_admin_mode//"/ (admin mode same as
     SipX default, so ignored).
  5. Result: admin mode OFF

It seems to me that this is a fundamental problem with the way that groups are implemented in SipX. Here are two possible alternatives that I would suggest:

  1. Provide a boolean for each setting that defines if the value in
     the setting should take affect or not (don't calculate it based on
     the SIpX default), or
  2. Allow the selection of another group on which the current group
     settings are based (like styles in word processors).




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

Reply via email to