Douglas, maybe I'm misunderstanding something when you say use phone groups. You are referring to the Groups within sipXecs device configuration, is that correct? Or a different concept?
If the suggestion is to attach the firmware and bootrom to the Group within sipXecs, I see your point on that. However, if there are different models of phones in the same group, then there could be issues. I guess the simple answer is to have multiple groups then, defined by the model of phone. Input from someone with a large installation as to how manageable that would be would be helpful. And it does seem to get back full circle to it being defined by the model of phone. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Hubler Sent: Monday, April 30, 2012 2:41 AM To: sipXecs developer discussions Subject: Re: [sipx-dev] Support for 4.0.2+ and beyond firmware for Polycom On Sun, Apr 29, 2012 at 11:55 PM, Todd Hodgen <[email protected]> wrote: > The phone group should be able to become the master "container" of the > "firmware" used. It could certainly be an option. > > Yes, it could be an option. I guess it sounds like you are wanting to > have a rewrite of what is there today. Im looking for options to > modify what is there. I dont have an interest personally in rewriting what works today. Using phone groups shouldn't be a rewrite. In general, if anyone submits a patch that : * is an improvement over what we have today * doesn't prohibit us from improving on it later (i.e. take us down the wrong path) seems reasonable it would be accepted. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
