Using Private IPv4 Addresses

In addition to supporting multiple registries, the Oracle® Enterprise Session Border Controller (E-SBC) can also distinguish user locations by their private IPv4 address and the IPv4 address of the public firewall. Using this information, the E-SBC adds private endpoint and public firewall information to Contact headers.

For example, entering this information causes a Contact header that formerly appeared as the following:

Contact:<sip:0274116202@63.67.143.217>

to subsequently appear as the following:

Contact:<sip:0274116202@63.67.143.217;ep=192.168.1.10;fw=10.1.10.21>

The E-SBC SIP proxy reads this information and populates the contact-endpoint and contact-firewall fields with the appropriate values.