> [mkd] There are a variety of audio settings in the sip.cfg file. These > fall mostly under voice.XXX.YYY. In particular there are a set of > voice.gain.rx.XX and voice.gain.tx.YY. If you open the template files > included with the release you will see a generic setting and then > several phone specific settings e.g. > voice.gain.rx.analaog.ringer.IP_6000. These settings are used by the > audio developers to 'tune' the phone behavior and should not be changed > by customers as there can be bad side effects of changing them. However > sometimes in a new feature release changes to the audio algorithms may > require changes to the gain settings. If these changes are not made poor > audio performance may result. I would recommend that any ability to set > these be removed from the sipXconfig administrator interface.
> Another area that has recently undergone some change is the 'LineSeize' > behavior (i.e. what happens when I lift the handset does it grab a new > line to make a call or attempt a call on the current line. For some call > servers this behavior is important. These are: call.stickyAutoLineSeize > (in sip.cfg) > The intention is that new default settings preserve previous behavior > and the code should have built in 'null' defaults that retain previous > behavior. However this is not a rule that is rigorously tested. > This design has some history behind it and we are planning to clean it > up such that parameters that should not be user/administrator changed > are built in to the code, but this will take some time to achieve > especially since we require maintenance of backward compatibility. > [mkd] The recommendation I would make to the sipXconfig team is that the > configuration files are set up such that the <MAC-ADDRESS>.cfg file or > 000000000000.cfg file contains a list of files as follows: > <MAC-ADDRESS>-settings.cfg, site-settings.cfg, sipexcs.cfg, sip.cfg, > phone1.cfg For list of configuration files, we can go with <MAC-ADDRESS>-sipx-phone.cfg, sip.cfg, phone1.cfg. For site specific settings, it can be done via group settings through sipXecs, which will be writen into <MAC-ADDRESS>-sipx-phone.cfg for phones applied, therefore, there is no need to have sperarte configuration files like site-settings.cfg and sipexcs.cfg. Question to Marek: does every firmware version starting from 2.0 contain sip.cfg and phone1.cfg? If so, I am expecting the correct default values correspond to each version are provided in sip.cfg and phone1.cfg respectively? sipXconfig is generating profile with some hardcoded values for some parameters such as voice.gain.rx.XX and voice.gain.tx.YY. If every software version is provided with sip.cfg and phone1.cfg with default values, we can remove those hardcoded values from sipXconfig and safely rely on sip.cfg and phone1.cfg. In this way, we will eliminate the problem with wrong default values for different versions mentioned above. If sip.cfg and phone1.cfg are only provided with the most recent version, then apparently there is more to consider with regarding to how to handle old versions. 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
