SIP

SIP Bugfix Changes How Encoding Is Determined in Configuration

The combined fix for the above mentioned SIP bugs alters the way that SIPServer looks up the output encoding in the configuration file (typically oils_sip.xml). SIPServer now looks for the encoding in the following places:

  1. An encoding attribute on the account element for the currently active SIP account.
  2. The encoding element that is a child of the institution element of the currently active SIP account.
  3. The encoding element that is a child of the implementation_config element that is itself a child of the institution element of the currently active SIP account.
  4. If none of the above exist, then the default encoding (ASCII) is used.

Number 3 is provided to ease the transition to the new code. It is the current location of the encoding element in the sample configuration file and as such, where it is likely to be found in actual files. It is recommended that you alter your configuration to move this element out of the implementation_config element and into its parent institution element. Ideally, SIPServer should not look into the implementation config, and this check may be removed at some time in the future.