1. Configuration Guide
  2. SIP Signaling Services
  3. SIP SIP-I Interworking
  4. SIP-SIPI IWF using Native Processing

SIP-SIPI IWF using Native Processing

The Oracle Communications Session Border Controller (OCSBC) can natively interwork ISUP parameters to and from SIP as defined by 3GPP TS 129.163 Interworking between IP Multimedia (IM) Core Network (CN) Subsystem and Circuit Switched (CS) Networks, Control Plane Interworking. Support for the capabilities of SIP and SDP that are interworked with BICC or ISUP are defined in 3GPP TS 24.229. The information the OCSBC interworks is a subset of all possible interworking, but results in successful sessions for the vast majority of interworked calls. Configure deployments that need additional interworking with HMR.

You configure the OCSBC to natively interwork specific information in specific messages by setting the sipi-behavior option within the sip-config to iam-anm. This configuration also allows the OCSBC to achieve session stateful awareness for the applicable sessions.

The OCSBC supports native interworking for the following ISUP messages:

  • Initial Address Message (IAM)—Interworks with SIP INVITE messages

    Note:

    The OCSBC performs IAM insertion regardless of the sipi-behavior setting. IAM removal, as well as all other ISUP message interworking requires the iam-anm setting.
  • Address Complete Message (ACM)—Interworks with SIP 180 and 183 messages
  • Call Progress Message (CPG)—Interworks with SIP 180 and 183 messages
  • Answer Message (ANM)—Interworks with SIP 200 OK messages
  • Connect (CON), which is an alternate to ANM when no ACM is received—Interworks with the 200 OK of an INVITE
  • Release (REL)—Interworks to SIP BYE and, if applicable, error responses
  • Release Complete (RLC)—Interworks to the 200 OK of the BYE

This document presents the information interworked by native interworking.

Excluding 183 Message Interworking

Some standards do not require you to map 183 messages into ACM/CPG messages. When disabled, the iwf-for-183 parameter in the applicable sip-isup-profile supports these environments. The default value is enabled. This parameter operates for native interworking. It is not relevant unless you have set the sipi-behavior option in the sip-config to iam-anm.

When enabled, the OCSBC:

  • Inserts ACM to first 183 or 180;
  • Inserts a CPG into any subsequent 18x;
  • Inserts the REL into the SIP BYE
  • Inserts the RLC into the 200 OK of the BYE, and
  • Inserts the ANM into the 200 OK.

When disabled, the OCSBC:

  • Does not insert any ISUP body into 183s;
  • Inserts the ACM into the 180 instead of any 183;
  • Inserts a CPG into all further 180s; and
  • Inserts the ANM into the 200 OK.

If the session setup sequence uses only 183s, the OCSBC inserts a CON into 200 OK instead of an ANM.