Mike wrote: > If that's true, how will we deal with a mixed environment of phones?
Legacy phones will simply not download 3.2.X firmware. This is Polycom BootROM behaviour. On the sipXecs side, the config files generated for these models are compliant with Polycom 3.1.3RevC. (The latest 3.1.X.) The issue is that sipXecs can only have a single active Polycom device file at a time. Suppose Polycom releases 3.1.4. You will want to upgrade your legacy phones (from 3.1.3), but not downgrade your non-legacy phones (from 3.2.2.) It's a little tricky: - Deactivate Polycom 3.2.2. - Activate Polycom 3.1.4. - Cross your fingers and hope that no non-legacy Polycoms get rebooted. - Reboot all your legacy Polycoms. - Deactivate Polycom 3.1.4. - (Un-cross your fingers.) - Activate Polycom 3.2.2. It would be nice if sipXecs allowed multiple Polycom device file variations: "2.1.X", "3.1.X", and "current". You should be able to have all three active at once, and sipXecs would then refer each Polycom model to the appropriate one. -Paul [email protected] _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
