I wrote: > Polycom 301, 501, 600, 601, and 4000 were deemed "legacy" as > of 3.2.0. This means they will only be supported in 3.1.X. > Previously this was 3.1.3, but 3.1.4 has recently been released. > > (Polycom 300 and 500 are only supported in 2.1.X.) > > This presents a challenge when sipXecs is deployed with a mix > of legacy and non-legacy Polycoms. > > The configuration file generation is actually handled very well now. > > > Firmware deployment on the other hand, is not. See: > http://list.sipfoundry.org/archive/sipx-users/msg17596.html > > Scott and I once talked about a graceful solution, but it is > certainly will not go into 4.2. > > > I'd like to propose a solution that is nearly as good, but > easy to implement.
Upon further discussion we've decided to pursue the graceful solution only, without any hacks in the meantime. I've raised a JIRA to cover the enhancement request: http://track.sipfoundry.org/browse/XX-7401 : Activate multiple Polycom firmware version, select which version to run from phone "Firmware" config setting -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
