Use this page to configure the SIP proxy.
Navigation: SERVICES > Proxies > SIP.
|Session Initiation Protocol|
|Enabled||Indicates if the SIP proxy service is turned on.|
|SIP client internal address||The interface for the SIP proxy to listen for internal connections on. This is the interface SIP clients use.|
|SIP client external address||The interface for the SIP proxy to listen for external connections on.|
|Maximum number of clients||The maximum number of clients that can use the proxy. Setting the maximum number of clients is a useful way to prevent malicious internal users performing a Denial of Service (DoS) attack on your registering proxy.|
|Diffserv mark for RTP packets||The Diffserv mark to apply to SIP RTP packets. The built-in RTP proxy can apply a diffserv mark to all RTP traffic for which it proxies. This is useful because it's otherwise quite tricky to define RTP traffic, because it might occur on a wide range of ports. Prioritizing SIP traffic on port 5060 would not make any difference to VoIP calls. The standard mark is BE and is the equivalent to doing nothing. Other marks might be interpreted by upstream networking equipment, such as that at your ISP.|
|Transparent||The SIP proxy might be configured in both transparent and nontransparent mode. Select this option if you want a transparent SIP proxy. When operating transparently, the SIP proxy isn't used as a registrar, but means that internal SIP devices can communicate properly with an external registrar such as an ITSP.|
|Log calls||Indicates if individual calls are logged.|
|Exception local IP addresses||The hosts that should not be forced to use the transparent SIP proxy. Each entry must be on a new line. You can either list individual IP addresses, or enter a range using a hyphen “-” as the delimiter.|
Things you can do here
Something not right? Send us feedback.