Date: Thu, 28 Mar 2024 17:59:11 +0000 (GMT) Message-ID: <680292191.4583.1711648751277@wiki.4psa.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4582_640854784.1711648751277" ------=_Part_4582_640854784.1711648751277 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page contains instructions on how to add an outgoing routin= g group.
To set up an outgoing routing rule group:
The Add Outgoing Routing Rules section provides the con= trols that allow you to define the rules for routing the VoipNow users' out= going calls.
Set the conditions that must be matched in order for the rule to be = applied.
> If call is matching conditions
Target number matches <target_number> and call is= made in time interval <time_interval> and call is c= oming from <caller_number>
Where:
For all extension/destination numbers, you can specify any combination o= f the digits 0-9 and the characters '.' , '*'. The number entry supports th= e Asterisk number matching.
Choose the action(s) to be performed on the outgoing calls when the conditions define=
d earlier are matched.
VoipNow directs the call through a particular channel. If you select thi= s action, the following call rule is displayed:
> Execute actions
<Route through> <channel_select> and <first_action> target number (with)
Where:
Best cost
, =
in which case, VoipNow searches the lowest cost route and uses it to connec=
t the outgoing call. If the transfer fails, the application searches for th=
e next available lowest cost route and so on, moving upwards to more expens=
ive routes.This rule can be used to perform complex operations (e.g. deleting or in= serting digits, adding a prefix, etc.) on one number before directing the c= all through a particular channel. The options available to design the rule = are the same ones as for the Route through action, with th= e difference that you cannot choose the channel. The one previously selecte= d for the Route through rule is used.
This rule is used for identifying the network a number belongs to and ch= oosing the appropriate charging method that determines the call cost. The r= outing rules that follow this one select the call cost based on the results= provided by this rule.
This routing rule is not available unless the Number portability=
engine option is enabled. By default, this option is disabled. To=
enable it, navigate to the Unified Communications =E2=86=
=92 Zero Priority =E2=86=92 Charging tab.=
VoipNow provides the engine that checks for portability, but if a certain =
customer wants to create a portability client, they should contact the cust=
omer support center for detailed information.
To identify the number, the portability client makes a portability reque= st to a remote or a local engine. Two situations are possible.
First, the portability client cannot find the network which the number b= elongs to, hence the number is not ported and nothing is changed in the cal= l flow.
In the other case, the number is in the portability database. The portab= ility client may return: the network, the cost of the call (using the defau= lt currency) and the cost of the call per unit (in seconds). In this situat= ion, the call is ported through the appropriate channel and charged accordi= ngly to the information returned by the portability client.
If the portability client returns only the network, the number is ported= , but the charging rules must be taken from the channel through which the c= all is routed. There are two possibilities:
This rule prevents the call from being initiated to the provided <target_number>. If you select this action, the following r= outing rule is displayed:
<Block> <channel_select>= p>
You cannot choose the channel. The channel previously selected for the <= strong>Route through rule is used.
Choose the position of the rule you set up.
=
span>
> And add its position
Make rule <type> and add in position <= position>
Where:
<position>: Specify the position of the rule = inside the group. The position in the group is very important because it de= fines the order in which VoipNow matches the call rules. The Block<= /strong> rule is final. This means that, when a rule is matched, the other = rules are no longer checked. The Route through rule can be= made final as described above. When final, an extra (F) w= ill be displayed in the Action column of the Exist= ing Outgoing Call Rules table.
A target number can only have one final rule. But you can set up multipl= e rules which are final for different target numbers.
In order to better understand how to set up outgoing routing rules, we h= ave created some examples for the available actions:
= p>
If an extension dials a number starting with 02 followed by any other 8 = digits, 02XXXXXXXX, during the Business hours time interval, then the call = is routed through the cheapest channel, i.e. Best cost.
The destination number is prefixed with 325. This means the matching num= ber becomes 32502XXXXXXXX.
Also, 004 is added to the extension's CallerID before the first digit if= its public number matches any 07XXXXXXXX combination. The resulting Caller= ID is 00407XXXXXXXX.
The rule is added in the third position and it is considered final.
It is advisable to place the Route through action on th=
e last position inside the outgoing rules group. The logical sequence is to=
first Block calls to certain destinations, next to
You can add a sequence of Process target number rules. = In a sequence, each one of the rules operates on the number resulted from t= he previous rule.
=
For instance, you can have a rule that deletes the first 3 digits of the= dialed number, 021XXXXXXX (this is the number in the <target_nu= mber> field). You may leave the CallerID number fields blank.= p>
Then you can have another rule that adds a prefix (i.e. 555) to the numb= er resulted from the previous rule. Again, you may leave the CallerID numbe= r fields blank.
Note that the second rule will add the 555 prefix to the number resulted= from the previous rule. This means the resulting number will be 555XXXXXXX= , not 555021XXXXXXX.
If you have a sequence of Process target number rules r= eferring to the same external number, the matched number is the original di= aled number, no matter the other intermediary rules.
For instance, you can have a rule that prefixes the dialed number, 123XX= XXXXX (this is the number in the <target_number>= field) with 4. You may leave the CallerID numb= er fields blank. The resulted dialed number is 4123XXXX= XXX.
Then you have another rule which prefixes the dialed number with 0. Voip= Now will add this prefix to the number resulted from the previous rules, i.= e. 4123XXXXXXX. Again, you may leave the CallerID number= fields blank. The resulting prefixed number will be 04123XXXX= XXX.
Next, you may have another rule which prefixes the dialed number with 5.= Just like before, you may leave the CallerID number fields blank. The resu= lted dialed number is 504123XXXXXXX.
This example shows that the second and the third rules refer to the exte= rnal number resulted from the previous rule, and not to the initially diale= d number, 123XXXXXXX.
All calls made by the users to any destination number starting with 03 a= nd followed by any other 8 digits, 03XXXXXXXX, are blocked.
The rule is applied Anytime and the CallerID is not modified.
The position is set to 1 as it is advisable to first block certain desti= nations and later process and route the calls.
To edit the properties of an outgoing routing rule group:
For more information about the first two sections, please see read how y= ou can in the Add a= n outgoing routing rules group section.