This article describes the necessary steps to configure a SIP Outbound Proxy on the SBC Edge (SBC).
The Outbound Proxy feature sends all SIP outbound requests to an Outbound Proxy Server of choice regardless where the Request URI points to. Outbound Proxies are configured in the SIP Signaling Groups (SIP SG) and are valid for Signaling Groups who's SIP Mode is set to one of the following:
In the Basic Call mode, the outbound INVITE request is constructed using the Server table as the destination. If an Outbound Proxy is configured, the outbound INVITE is sent to the outbound proxy instead of the available server from the Server table.
In both Fwd Registration and Fwd Reg. After Local Processing modes, the outbound REGISTER request is constructed using the Registrar address as the destination. If Outbound Proxy is configured, the outbound REGISTER is sent to the outbound proxy instead of the Registrar address.
Create a SIP Server Table (i.e., fe2.uxtestlab.com with the relevant port, protocol, profile, etc.)
Enter the relevant port number in the Outbound Proxy Porttext box.
Once an Outbound Proxy is configured on a SIP Signaling group, all SIP calls landing on that SIP SG are routed through a Proxy to the actual end points. This is typical in a SIP Trunking scenarios whereby the SBC offloads all the enterprise SIP traffic onto an ITSP (Internet Telephony Service Provider) SIP network which exposes a Proxy configured as an Outbound Proxy on the SBC.
In this example, entities are configured with following:
SBC | ITSP | Outbound Proxy |
---|---|---|
134.56.227.204 | 134.56.227.73 | 134.56.227.73 |
testux204.uxtestlab.com | fes1.uxtestlab.com | fes1.uxtestlab.com |
Using the Log Exchange utility, you can verify the Outbound Proxy configuration in action —