I don't have any objections. What objections there are should "lessen" over time, given that they are no longer available. Perhaps a script can be run from the CLI or sipxconfig where the "legacy' zip file can be uploaded and the files renamed and given the proper owner/permissions?
On Thu, Jan 7, 2010 at 12:59 PM, Paul Mossman <[email protected]> wrote: > Hi all, > > 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. > > Basically, Polycom configuration files can specify which firmware files > should be loaded on a per-model basis. All models are currently > directed to use "sip.ld", which is the default filename used in the > "current" Polycom firmware ZIPs. The sip.ld will simply not load on a > Polycom that does not support it. > > The legacy models will be told to pick up say filenames "sip_31X.ld" or > "sip_21X.ld". That is the easy part. > > Unfortunately the "legacy" Polycom firmware ZIPs don't use consistent > names for the sip.ld file. So, it would be challenging to handle them > gracefully like we do for the "current" ZIPs. I think the best option > is simply to have the superadmin extract the file from the ZIP, rename > it ("sip_31X.ld" or "sip_21X.ld"), and then upload it as an "Unmanaged > (T)FTP file". > > The superadmin will have some extra work, but it'll make life > considerably easier than no solution at all. > > > Objections? > > > -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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ 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/
