SIP-SIPI IWF using Native Processing

The Oracle Communications Session Border Controller (SBC) 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 SBC 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 SBC 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 SBC to achieve session stateful awareness for the applicable sessions.

The SBC supports native interworking for the following ISUP messages:

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

  Note:

  The SBC 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, as well as Re-INVITE and UPDATE messages, to support Hold/Resume flows
• 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