On Thu, Jun 3, 2010 at 9:30 AM, Mossman, Paul (Paul) <[email protected]> wrote: > My hope is that most of the commonly used phone configuration could be > generalized. This would make Phone Groups much more usable. It would also > give us a cohesive UI for phone configuration, a valuable improvement even on > its own. > > > Does that clarify?
yes it does, thank you. Line management is an example of a generalized UI that affects each phone in a very specific way. I think this is a good model to follow going forward, and I would suggest building more sipXconfig pages that walks admins thru generalized concepts like QoS and each phone provides support for by providing concrete implementations to various interfaces. Other generalized options at the group level include Phonebooks, Paging, Intercom, Music on Hold, even voicemail extension. It could be made more clear what phones these generalized concepts apply to then a note in the Quick Help. In these pages, you set the phone groups each one applies to. When you want to actually deal with specific group settings and not generalized UI, I do think a general polycom phone group would be a good thing, but I see this has a separate issue. This can be achieved by simply allowing a phone implementation to supply a settings model that is available in the group settings list, but not as a physical phone one could select in the add phone page. The rest takes care of itself. Having to define VLAN setting for each phone makes sense because each phone may have a specific VLAN setting. I'm not a fan of the XSLT processing for the final settings file because it seems to add a serious level of complexity. If you have a XSLT that helped new phone vendors get started or helped bulk edit phone settings, that seems less intrusive. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
