SIP-SIPI IWF using HMR

By default, interworking SIP-SIPI messaging requires that you create HMRs that recognize the message types and build messages appropriate for egress. You create these HMRs for each expected message type, with the exception of IAM messages. The Oracle Communications Session Border Controller (SBC) performs IAM interworking when it recognizes that a sip-isup-profile is applied. The Header Manipulation Rules Resource Guide includes full instructions on how to build all HMRs. This guide's MIME Support chapter includes a section on HMR for SIP-ISUP that directly addresses how to create HMRs for this interworking.

The SBC’s HMR functionality can operate on ISDN user party (ISUP) binary bodies. Using the same logic and mechanisms that are applied to SIP header elements, HMR for SIP-ISUP manipulates ISUP parameter fields and ISUP message parts. You can create MIME rules that function in much the same way the SIP header rules do; whereas SIP header rules can change the specific headers of a SIP message, MIME rules can manipulate targeted body parts of a SIP message.