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. 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. 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. -----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: > Id 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. Id 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/
