Base SIP-SIPI IWF Functionality

By default, the SBC does not perform SIP-SIPI interworking. You configure one or more sip-isup-profile and sip-profile sub-elements within the session-router element, and then specify the profiles to use on a session-agent, sip-interface or realm. The SBC follows that order for the configuration's operation precedence.

• sip-isup-profile—This object specifies multiple SIP-SIPI IWF controls for the object to which it is applied. At a minimum, this parameter specifies the ISUP version for parameter interworking. Additional IWF configuration includes ISUP version interworking and disabling 183 message interworking.
• sip-profile—This object includes the redirection parameter that defines the basic SIP-SIPI insertion and removal behavior for the object to which it is applied. (You also use this object to configure functions not related to this IWF.)

The SBC performs the following insertion and removal actions based on the ingress and egress sip-profile, redirection settings:

• When you set the ingress sip-profile, redirection to none and the egress to:
  • none—Perform no action
  • isup—Add ISUP content and, if INVITE, generate the IAM ignoring diversion headers
  • diversion—Perform no action
• When you set the ingress sip-profile, redirection set to isup and the egress to:
  • none—Remove ISUP content
  • isup—Convert ISUP version if needed and enforce sip-isup-profile specific attributes
  • diversion—Remove ISUP content and, if INVITE, generate diversion header from the IAM
• When you set the ingress sip-profile, redirection set to diversion and the egress to:
  • none—Perform no action
  • isup—Add ISUP content and, if INVITE, generate IAM from the diversion headers.
  • diversion—Perform no action

You further specify your interworking behavior using other controls, including HMR, Session Translation and Native Interworking.