On Wed, Feb 15, 2012 at 10:01 PM, Todd Hodgen <[email protected]> wrote: > New models of phones from Polycom come with version 4.0.1 now, so in order > to support this, changes are necessary within sipXecs. Even some of the > phones supported in the past, such as the Polycom 335 are now released as > the Polycom 335C and require the new firmware. It is just a matter of time > before someone runs into this issue.
agreed > The Polycom’s look for a file called [mac].cfg in the TRFT root first. If > it doesn’t find a cfg file, then it looks to a default of 000000000000.cfg. > Within this file currently, there are some parameters defined for loading > some of the old firmware files into older models of Polycom. This method > essentially allows for running several versions of firmware on the system. > > > > I believe that file can be further modified to create model specific files > for configuration of phones running the new firmware. For example, adding > code to cause the phones to look into a directory with their model name, and > then their [mac].cfg file. This accomplishes a few things. First, it puts > the configuration files for all of the same model into one directory, along > with its current firmware and organizes things a bit. Secondly, it allows > these phones to pull their specific firmware, while older legacy phones can > continue to pull their firmware from the TFTP root, or another directory all > together. > > > > I’m currently doing this manually, and it works rather well. Manually in > that I move the files to the correct directory manually, but the phones find > them automatically via the modified 000000000000.cfg file. > > > > This could actually allow for using one firmware with one particular model, > while using a different version with another model phone. > > > > I believe this is manageable, and is actually a smaller task that originally > thought. > > > > Question for the list – is there wisdom in breaking things out into > different folders like this, or is it just added complexity? Is this > beneficial for large installations? > > > > I believe we need to get started on this sooner rather than later. I will > create the Jira’s necessary to get things tracked. I would like to hear > opinions regarding the method for managing the transition from current > firmware files, and management of phones running on the new firmware. If it's working for you, then it seems like a good plan. It would require digging into project to give more helpful advice unfort. -- Join me to talk about sipXecs and the upcoming version 4.6 at CoLab @ CSU March (5th & 6th). http://www.sipfoundry.org/sipx-colab Hack with me on at the CoLab Hackfest. http://wiki.sipfoundry.org/display/sipXecs/2012+sipX-CoLab+Hackfest _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
