Details

The ISUP message version is determine by one of two things: the content type of the SIP message or the MIME content-type. When the base and version parameters do not match, the Oracle® Enterprise Session Border Controller first uses the base parameter value to determine the format. If there is no base, the Oracle® Enterprise Session Border Controller then checks the version parameter. And if there is neither, the Oracle® Enterprise Session Border Controller uses the isup-version configured in the sip-isup-profile configuration from the inbound realm, session agent, or SIP interface. Available values for that parameter are ansi-2000, itu-99, gr-317, or etsi-356. The Oracle® Enterprise Session Border Controller considers unknown any value for the version that fails to match one of these or is missing.

Messages that contain an unknown ISUP format pass through the Oracle® Enterprise Session Border Controller untouched. If there are operations to be performed on them, however, SIP ISUP HMR will take place. After the body has been converted, the Oracle® Enterprise Session Border Controller updates both the base and version parameters of the content-type.

Custom formats are not supported.