> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dutkiewicz, Marek > Sent: August 1, 2008 6:28 PM
> 4. Preserving the sip.cfg and phone1.cfg files This is > STRONGLY RECOMMNEDED practice. Polycom cannot guarantee that > some parameters might change between releases that can cause > subtle problems - the most obvious real issues from the past > were some audio settings which caused poor audio quality if > they were not updated between releases. We'd like to clean > this up, but where we are now with the number of models of > phones and different releases out in the field we can only > test and guarantee proper performance if the software and > configuration files are matched. Marek: Can you tell us what those audio settings were? Can you also advise what items might encounter a similar problem in the future? In particular, are frequently configured items at risk? Would the absence of newly added parameters be likely to cause a problem? We are struggling with this recommendation. The issue is that sipXconfig facilitates configuration of so many Polycom SoundPoint IP parameters. In doing so, our code replicates the default value for each, so that they can be displayed in sipXconfig and included in the generated profile. If we move to the "override" approach, we will generate one overrides for every parameter that can be configured in sipXconfig. Would that essentially nullify the benefit of preserving the sip.cfg and phone1.cfg files from the firmware? Thanks. -Paul _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
