On Sun, Apr 29, 2012 at 11:16 PM, Todd Hodgen <[email protected]> wrote:
> ** ** > > ** ** > > On Sun, Apr 29, 2012 at 8:39 PM, Todd Hodgen <[email protected]> wrote: > **** > > I don't necessarily agree with that position. We did discuss this at > Colab, > and I agree with you that there is a concern for the Group configuration > process. Because of that, I am recommending only the Firmware be in the > separate directories, while the configuration files remain in the TFTP root > directory. There are mechanisms included in the Polycom phones to support > this, and in fact it is being used today for the support of the older > legacy > phones. > > Phone model is a designation made by Polycom, where phone group is a > sipXecs > feature. The problem I see with only planning by group today is there are > some phones that will operate on one version, while other models of phones > will only operate on different versions. Over time this could continue to > happen based on changes in the Polycom product line, and changes to > firmware > for individual phone models. > > I can envision a group of phones that is made up of several models of > phones > - for example a medical staff. Some may have 550's, while others have > VVX500 phones, still others 335. Today, within sipXecs, these would > require > at least two different versions to be supported.**** > > ** ** > > I fail to see the point. If one group is designated to have 3.x firmware > and another group 4.x firmware, this would suffice and would be part of the > device template most likely. **** > > ** ** > > This is exactly the confusion Tony. Groups don’t have different firmware, > Polycom Phone models do. The device template doesn’t have anything to do > with the Firmware version the phone is picking up, it is all related to the > phone and its model number only. There isn’t a method in configuration > today to tell the phone what Firmware to use, and I don’t see a reason to > build that into the system with the way Polycom works today. > The phone group should be able to become the master "container" of the "firmware" used. It could certainly be an option. > **** > > > The Polycom firmware today has changed to where it has either one combined > SIP.ld file that contains all of the firmware for all of the phones and the > phone downloads it and pulls out its specific firmware file, or you can > download the split version which has a discrete file for each model of > phone > and only that file is downloaded to the phone. It's a simple designation > within the naming of the file. The phones will find the correct file based > on its model number, and the directory that it is pointed to for searching > and download only that file, regardless of the sipXecs group that it is > configured into. > > The configuration files do get downloaded, and contain Group specific > configuration parameters. However, keeping this all in the root directory > makes it easy to make group changes, as you have suggested, while having > the > Firmware in separate directories does make it easy to have multiple > versions > of the firmware running on the system. Oh course, you could have multiple > versions of firmware placed in the TFTP root, but I suspect it would become > cumbersome to deal with.**** > > ** ** > > I think over time the 2.x and 3.x stuff would make a lot less difference. > **** > > Agreed, and once it is gone, then that section of the GUI can be > completely removed – a trivial task, or potentially used for the next > iteration from Polycom.**** > > If someone has a need to support them long term, then they can manually > configure the 000000000000.cfg file.**** > > > BTW, there is a mechanism for having just a specific phone have one > version, > while an identical model could run a different version of the firmware. > > All of this said, there needs to be serious discussion about an overall > Polycom architecture for the long term benefit of the project.**** > > ** ** > > I think I have some volunteers lined up for this effort (4.x) and that > will proceed without the need for architecture discussion, because really > it is a two part discussion anyway (three in my view).**** > > Explain?**** > > ** > 1. Re-writing the sipxconfig field name/values for configuration 2. Containerizing (is that a word) the firmware b phone group to allocate the proper firmware. 3. Adding new feature to new fimrware and sending profiles based on "profile name" instead of mac address (i.e. login/logout of phone via xhtml to get the profile to load, hot reloading of phones without reboot, new features like pin-locking, etc.). > ** > > ** ** > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Douglas Hubler > Sent: Sunday, April 29, 2012 5:22 PM > To: sipXecs developer discussions > Subject: Re: [sipx-dev] Support for 4.0.2+ and beyond firmware for Polycom > > On Sat, Apr 28, 2012 at 3:46 AM, Todd Hodgen <[email protected]> wrote: > > I’d like to suggest that a new section be added to the Device file > > section of the GUI for the Polycom phones. Today, there exists a > > section for uploading Firmware (current) and for adding Firmware for > > legacy phones. I’d like to propose a temporary section for adding the > > 3.3.x versions of Firmware also. > > I would think controlling firmware version by phone group would be more > useful then by phone model. > _______________________________________________ > 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/**** > > > > **** > > ** ** > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~**** > > LAN/Telephony/Security and Control Systems Helpdesk:**** > > Telephone: 434.984.8426**** > > sip: [email protected]**** > > ** ** > > Helpdesk Customers: http://myhelp.myitdepartment.net**** > > Blog: http://blog.myitdepartment.net**** > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
