George wrote: > <[email protected]> wrote: > > > > And the phone-group.xml could show up as the "General" > > model under the Phone Groups setting, right? > > I suspect this is possible (though I'll be 100% sure after > some more investigations / simple POC). Correct me if I'm > wrong - in your scenario, specific phone config panels will > show general settings inherited from Phone Group as well?
Correct. I see this being analogous to the current behaviour. You change a Polycom-common setting under the "Polycom SoundStation IP 6000" model, and can see the same value under the "Polycom SoundPoint IP 450" model. > > And the values you set under "General" would be carried into the > > corresponding settings of all phone models whose plug-ins use > > general.xml? > > We could programmaticaly propagate general settings to all > configured phones in group. Could you propagate up as well down? For example, I'm looking at a Polycom model, some settings are general and some are not. I change one of the general settings. I should be able see the same change in both the "General" and the "Avaya 1220 IP Deskphone" models. > > > > Could acme-model.xml use some but not all of the settings in > > general.xml? i.e. Apply "hidden" to some settings, so they don't > > appear? The example I'm thinking about is a soft client, > which has a > > lot of common SIP phone functionality, but wouldn't have Network > > Settings such as VLAD ID. > > Yes, settings could be ignored when merging via XSLT, based > on some predefined attributes. Is there any JIRA issue raised > for this improvement? http://track.sipfoundry.org/browse/XX-8532 Generalized phone plug-in model settings improvement -Paul [email protected] _______________________________________________ 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/
