Adding an ISUP Body to a SIP Message

Unlike the MIME manipulation you can use by setting the SIP header rules accordingly, you can add MIME parts to SIP messages using the MIME rules configuration.

You can configure a SIP header manipulation to add an ISUP body to a SIP message. and the Oracle® Enterprise Session Border Controller adds them after any SDP parts if they are present. You can add an ISUP body to a SIP message in two ways:

• You can create a mime-isup-rule with the action type set to add, and enter the entire body in string hexadecimal form in the new-value parameter.
• You can leave the new-value parameter empty at the mime-isup-rule level and create an add rule for an isup-param-rule.

  In this case, the Oracle® Enterprise Session Border Controller creates the corresponding ISUP message based on the isup-msg-type value and supply all of the parameters with their default values. Since the isup-msg-type takes a list of values as a valid entry, for this case it only uses the first one. However, the Oracle® Enterprise Session Border Controller ignores the isup-msg-type value if you set the new-value parameter. And the isup-param-rule, if configured, overwrite the default value or add a new parameter based on the defined parameter type.

  It is also possible that you might supply a new-value both at the mime-isup-rule level and at the isup-param-rule level. If you do, the new-value entry from the mime-isup-rule is parsed into an ISUP object and the isup-param-rule operates on that object.