Scott wrote: ... > > The superadmin will have some extra work, but it'll make life > > considerably easier than no solution at all. > > This sounds suspiciously like: > > Let's make life a little easier for a few developers who have > deep knowledge and a little more complicated for a > lot of system > admins who don't. > > Doesn't sound like a recipe for customer satisfaction to me.
The unfortunate fact is that Polycom 3.1.4 will not deploy on sipXecs as expected. With no fix, the admin would need to extract the firmware file from the ZIP, rename it to "sip.ld", and deploy it as an "Unmanaged (T)FTP file". But you still can only have one version of Polycom firmware active, since they all use "sip.ld". Actually sipXconfig would unfortunately not prevent you from activating both, and then quietly tromp the existing "sip.ld" file with the latest. So the situation with 3.1.4 is worse than I hypothesized here: http://list.sipfoundry.org/archive/sipx-users/msg17596.html That being said, here's an improvement on my original proposal: Instead of deploying the 3.1.X and 2.1.X "sip.ld" files as unmanaged, we could make room for them in the Polycom firmware device file type. i.e. Like we currently do for the "license.cfg" License File. An Upload.deployFile() change would be required to rename the uploaded file to the name that would be expected by the phones ("sip_31X.ld" or "sip_21X.ld".) But that change should be fairly simple, and a worthy improvement on its own anyway. So the superadmin would still need to extract the "sip_314.ld" file from the 3.1.4 ZIP package, but no renaming would be required. The file would then be uploaded as the "Legacy 3.1.X sip.ld" file in the Polycom device file entry. Upon activation, it would be renamed such that it's only picked up by Polycom 301, 501, 600, 601, and 4000 models. The same would be done with "Legacy 2.1.X sip.ld" for Polycom 300 and 500 models. Thoughts? -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/
