SIP Registration Via Proxy

The Oracle® Enterprise Session Border Controller supports a number of features that require it to cache registration information for UAs (endpoints) registering and receiving requests through it. For those features to operate correctly, the Oracle® Enterprise Session Border Controller must act as the outbound proxy through which these endpoints register.

In order to support deployments where a proxy sits between the Oracle® Enterprise Session Border Controller and the endpoints, the Oracle® Enterprise Session Border Controller must consider the bottom Via header it receives from endpoints when constructing and matching cache registration entries. And when you use SIP port mapping, the system must use the bottom Via header as a way to determine the endpoint uniquely so that it can have a unique mapping port when the SIP interface is configured with the reg-via-key=all option.

Using the reg-via-proxy option, you can enable your Oracle® Enterprise Session Border Controller to support endpoints that register using an intervening proxy. You can set this option either for a realm or for a SIP interface. If you use it for a SIP interface, add to the SIP interface pointing toward the proxy and endpoints—the access side.