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:
- Basic Call
- Forward Registration
- Forward Registration After Local Processing
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.
- In Local Registrar mode, the Outbound Proxy configuration item is disabled and its value is not used.
- If a SIP Server table which has Monitoring enabled, is associated with a SG having an Outbound Proxy configured, all the SIP OPTIONS requests generated by the SBC for monitoring purposes, are sent to the Outbound Proxy address configured on the SG.
Outbound Proxy Configuration or Basic Call mode
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to SIP Server Tables
Create a SIP Server Table (i.e., fe2.uxtestlab.com with the relevant port, protocol, profile, etc.)
- In the left navigation pane, go to Signaling Groups > (the SIP Signaling Group you plan to use for your deployment).
- Configure the SIP Signaling Groupto use an Outbound Proxy.
- Select the SIP Server table you created above from the SIP Server Table list box.
- Enter the IP Address of FQDN of the Proxy Server in the Outbound Proxy text box.
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:
Using the Log Exchange utility, you can verify the Outbound Proxy configuration in action —