84
2N TELEKOMUNIKACE a.s., www.2n.cz
®
1.
2.
3.
4.
5.
6.
Add rule
There is an
icon below the table too. Click on it to display the rule defining
Add rule
form. Fig. 3.72 shows a form for setting the SIP proxy routing rules. The form fields
correspond to the header of the table in Fig. 3.71.
Figure 3.72:
Proxy Routing Rule Adding Form
The form and the table include the following fields
If prefix –
If the called subscriber's URI (Uniform Resource Identifier) starts with
this string, this rule is used for routing. In the SIP environment, the URI is
introduced with the "sip:" prefix, which must be included in the value in this field.
Strip
– Number of characters following the "sip:" prefix to be removed from the
URI before processing.
Add
– String to be inserted in the URI behind the "sip:" prefix.
Do action –
Define what to do with a call. There are six potential actions in the
pop-up menu but, in principle, there are only three of them – rejection,
forwarding and connecting within the SIP proxy registrations. However, let us
mention all the options briefly to have a full picture:
Reject – the called line gets the busy tone;
Rewrite host – forwards the call to the same port of the selected host;
Rewrite port – forwards the call to the selected port of the same host (this can
have the same effect as option 5);
Rewrite host and port – forwards the call to any port of the selected host;
Connect to LCR – connects the call to the selected gateway SIP line and thus to
the LCR; and finally
Lookup registration – tries to search the SIP proxy registered users for the
required URI and forward the call to the appropriate host.
With parameter –
The above actions, except for the first and last ones, require
a parameter to be set. This parameter is a new routing destination for call
forwarding and the SIP line name for the Connection to
action.
2N OfficeRoute
®
In the figure - routing is done according to the prefix. The action might be Connect to
LCR, Reject, Change host and port and Lookup registration. The parameter means here
the routing destination of a call. There is a significant difference against the
Normalising table – the prefix is not removed in the proxy rule.
