This article describes the necessary steps to configure a SIP Outbound Proxy on the Sonus SBC 1000/2000 system
Spacevars | ||
---|---|---|
|
Table of Contents |
---|
...
Info | ||
---|---|---|
| ||
|
...
Create a SIP Server Table (i.e., fe2.uxtestlab.com with the relevant port, protocol, profile, etc.)
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter the relevant port number in the Outbound Proxy Porttext box.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
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 Sonus SBC 1000/2000 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 Sonus SBC 1000/2000.
In this example, entities are configured with following:
Sonus SBC 1000/2000 | 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 —
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Pagebreak |
---|