Routing; Protected Destinations - Snom 4S Administrator's Manual

Sip proxy/registrar version 2.30
Table of Contents

Advertisement

Routing is one of the most important task of the proxy. As you
already could see in the scripting part of this manual, the snom 4S
SIP proxy supports numerous ways to support even complex routing
scenarios.
This chapter focuses on the web interface to the routing. This
interface controls variables which are interpreted by the default script.
If you override functions of the default script, the respective parts of the
routing does not apply.
This chapter describes both the settings in administrator mode
and in domain mode.

Protected Destinations

When the proxy needs to forward a request, it first checks this
field for protected destinations. If one of the destinations match the
requested URL, the proxy first challenges the client for authentication.
The protected destinations are seperated by space and contain a
pattern according to the rules described in the Dial Plan (see below).
Typically, you want to protect access to the PSTN (because this
requires payment). For example, if your PSTN gateways are located at
192.168.0.248 and 192.168.0.249 and the dial plan starts using the PSTN
gateway after 4 digits, you would enter a pattern like "sip:$$$$%@~
sip:$$$$%@192.168.0.24[8-9]". The first pattern makes sure that every
request that would be redirected to the PSTN gateway is challenged,
the other patterns make sure that direct access to the PSTN gateway is
challenged.
If you leave the field blank, the proxy will forward any packet
without challenging. If you enter just "*", the proxy will challenge every
request.

Routing

snom technology AG • 73

Advertisement

Table of Contents
loading

Table of Contents