SIP IP Address Hiding and NATing in XML

Adding to its topology hiding and NAT capabilities, the Oracle® Enterprise Session Border Controller now performs those functions for pertinent IP addresses that are not part of the standard SIP message header format. Previously, such addresses were visible to the next hop in the SIP session path.

Note that this feature adds to the Oracle® Enterprise Session Border Controller’s pre-existing ability to perform this function for XML messages; this new support is specifically for the keyset-info message type.

For incoming SIP NOTIFY messages, the Oracle® Enterprise Session Border Controller searches for the application/keyset-info+xml content type in the message. When it finds this content type, it searches further to detect the presence of <di:remote-uri> or <di:local-uri> XML tags and then NATs the IP addresses in the tags it finds. Specifically, the Oracle® Enterprise Session Border Controller changes:

• The <di:remote-uri> IP address to be the egress SIP interface’s IP address
• The <di:local-uri> IP address to be the Ip address of the next hop to which the message is being sent