-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Mossman Sent: Thursday, January 07, 2010 6:27 PM To: Eric Varsanyi; [email protected] Subject: Re: [sipX-dev] Handling firmware for Polycoms in a mixed legacy/non-legacy environment
Eric wrote: > I got the impression from the polycom release notes that the > base config files that come with each firmware release have > to be used with that firmware release, I looked around in the > template stuff but I couldn't find any obvious way to use > different templates for different instances of a polycom phone. > > How does one do that in 4.2? It looked to me like someone > just checked in the updated templates (based on the files in > the 3.2.2 release zip) in 4.2 and now 4.2 supports phones > with firmware 3.2.2 and 4.0.4 supports phones with firmware > 3.1.3c (based on the config file templates alone). > > Or does it really not matter if 3.2.2 config parameters end > up in a 3.1.3c phone? Each sipXecs release is "locked" to a given "current" (non-legacy) Polycom release. For 4.2, this will likely by 3.2.2. It is probably OK to run Polycom firmware that is newer than the version supported by the sipXecs release. But there could be problems, so we don't recommend it. -Paul [email protected] Sorry, just rest this message from paul, so my past message, although well intentioned, is a waste it seems. It is problematic to tell people that 501 telephones, as an example, are no longer supported. _______________________________________________ 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/
