It is important to ensure synchronization between software versions and configuration files. Hence 'Legacy' releases need to support both a 'Legacy' naming for the .ld files and the sip.cfg and phone1.cfg files.
See technical bulletin TB35311 available from http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical_Bulletins_pub.html for details. Polycom is starting to release 'Legacy' versions of the older software which have the release files already named for the convention - e.g. see the SIP 3.1.4 Legacy release posted on http://downloads.polycom.com/voice/voip/sip_sw_releases_matrix.html Regards Marek From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hodgen Sent: Thursday, January 07, 2010 8:09 PM To: 'Tony Graziano'; 'Eric Varsanyi' Cc: [email protected]; 'sipX-dev' Subject: Re: [sipX-dev] [sipx-users] Handling firmware for Polycoms in a mixed legacy/non-legacy environment From: [email protected] [mailto:[email protected]] On Behalf Of Tony Graziano Sent: Thursday, January 07, 2010 11:10 AM To: Eric Varsanyi Cc: [email protected] Subject: Re: [sipx-users] [sipX-dev] Handling firmware for Polycoms in a mixed legacy/non-legacy environment FWIW, this really should be a sipx-dev discussion (IMO). The polycom phones will "discard" any parameter they are given that they do no know how to handle (like EFK). That being said, I think there was a workaround being suggested by Paul to allow sipx to "know" the model of a phone and hence, push (or allow the phone) a legacy version of firmware for just this instance. On Thu, Jan 7, 2010 at 2:06 PM, Eric Varsanyi <[email protected]<mailto:[email protected]>> 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? -Eric On Jan 7, 2010, at 11:59 AM, Paul Mossman wrote: > > 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. I'd like to make a suggestion here. Would it not make sense to have three zip files created for sipXecs that each contain the necessary files required to support the three sets of Polycom Phones. Rather than having someone download the files from Polycom, install them and have issues that creates confusion on the lists here, wouldn't it be nice to have three sets of files that people can download if they desire to upload into their system to have the support for the phones they desire? Taking the files that are desireable for sipXecs, Zipping them into a file with the file naming convention desired by the sipXecs schema, and having them in a repository somewhere seems like a simple way to limit confusion. And, if necessary a script file to run to ensue things are installed correctly. Alternatively, could this be handled via a "yum polycom-sipxecs update" or some similar method that doesn't get to complicated? The user community could help with this process by creating the files and making them available for download. I think kicking this idea around could come up with a simple method of ensuring the correct files are available for everyone, and in a manner that lessons the issue for sipXecs admin, and helps ensure the integrity of this product called sipXecs we love so much.
_______________________________________________ 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/
