Proxy Related Functions - Snom 4S Administrator's Manual

[
S N O M
See the explanations on registrations on details on Path and
registration duration limitation.

Proxy Related Functions

proxy_dest
This is one of the core functions of the proxy. It forks the current
request to the location provided as the first argument. If present and the
request is an INVITE request, the second argument delays the fork. The
delay is measures in seconds.
Forking to a destination can be done without a domain context.
proxy_user
The proxy_user uses the database of registered users for
determining the destination of the forking process. The user account is
provided as first argument.
As with proxy_dest, the second argument delays the forking
process. However, the delay is combined with the registration probability,
so that users with a probability will receive the request immediately; users
with a probability of zero will receive the request after the delay. Users
having a probability between these extremes will receive the request with
a delay that scales linear between the extremes (sequential forking).
If no user is registered with this account, this function sends a
404 response to the request. If there are no other requests forked, this
will be the end result of the request.
reject_request
Sometimes it is helpful to explicitly add a reject code to a
request. For instance, when a user cannot be found, the proxy might
want to signal "404 Not Found". The reject_request takes as argument
the reject code. The optional second argument may contain additional
headers that are inserted into the response. The additional parameters
must be terminated with a CRLF pair.
Example: reject_request("404 Not Found", "Error-Information:
<sip:notfound@media.company.com>\r\n")
46 • Scripting
4 S P / R
R O X Y E G I S T R A R
M ]
A N U A L