Hello, There had been some discussions on this topic before, but I like to bring this up again, and hopefully we can get closure on this.
Some background information regarding this topic: With current Polycom plug&play, sipXconfig generates a configuration file that contains all the configuration parameters for Polycom, and some of the parameters are not settable from web UI, instead they are hard-coded in sip.cfg.vm and phone.cfg.vm, and sipXconfig does NOT use configurations files provided as part of the firmware package, named sip.cfg and phone1.cfg, which contain default values for many paramerters. There have been various problems reported because we are not using Polycom default configuration files: 1) One type of the problem is that since the default values for some parameters might get changed in new firmware release, but they are not updated in sip.cfg.vm and phone.cfg.vm. With invalid default values might result in unexpected result. 2) Another type of problem is that some paramertes are in Polycom default configuration file, but are missing from sip.cfg.vm and phone.cfg.vm, and that had been identified as the root cause for conferencing audio quality issue. 3) Also, currently, we are not differentiate Polycom firmware versions ( 2.0 or newer) . In cases of deployment with multiple Polycom firmware versions(2.0 or newer), the configuration files generated by sipXconfig are similar. There might be a case that some parameters default values need to be different between releases. Given there are hundreds of configuration paramerters, and trying to maually keep a partial clone of what Polycom has in the default configuration files in sip.cfg.vm and phone.cfg.vm is just error prone, not to mention that Polycom may change, add/remove parameters in future releases. Instead of trying to address these problems at one shot, we would like to make the improvement and move to the middle ground by solving issues 1 and 2 for sipXecs 4.0 release. I would propose that we include Polycom latest default configuration files, and for those parameters that are not settable from the UI and are currently hard-coded in sip.cfg.vm and phone.cfg.vm, we will remove those and have them picked up from Polycom default configuration files. In this way, we are assured that the default values for those parameters are correct and expected. Again, this still is not an ideal solution, as it does not address issue 3, to support multiple versions of Polycom firmware, but the issue exists today. The JIRA issue related to this is http://track.sipfoundry.org/browse/XCF-2751 I'd like to get others' opinion on this. Thanks, Huijun
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
