Based on the current table structures, why won't you add a field to the Device Files page that allows you to select the phone model. The upload table which contains the device files already has a link into the table setting_value for storing values related to the row. To make it simple, you could use the phone model as the subdirectory for loading the firmware.
When generating the mac-address.cfg, since the phone_model is a column in the phone table, it would be easy to know what subdirectory to use for the firmware when building the file. Sincerely, Dave Deutschman Managing Partner Innovational IP Solutions, LLC PO Box 983 Bothell, WA 98041 206.965.9586 x 301 (o) 425.478.9642 (m) [email protected] (s) www.innovational.net "The information transmitted is intended only for the person or entity to which it is addressed and may contain proprietary, confidential and/or legally privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers." -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hodgen Sent: Monday, April 30, 2012 9:51 AM To: 'sipXecs developer discussions' Subject: Re: [sipx-dev] Support for 4.0.2+ and beyond firmware for Polycom 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/ ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4969 - Release Date: 04/30/12 _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
