Difference between revisions of "Device Rules"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<br><br>
<br><br>
<big><big><big>'''Device Rules transforms an E.164-compatible number to any number format the Device requires.'''</big></big></big>
<big><big><big>'''Device Rules transform an E.164-compatible number to any number format the Device requires.'''</big></big></big>
<br><br>
<br><br>


Line 11: Line 11:
Device Rules can be reached by clicking the [[Image:rules.png]] icon next to a Device in the Devices window:
Device Rules can be reached by clicking the [[Image:rules.png]] icon next to a Device in the Devices window:


'''IMPORTANT: Device Rules are applied ONLY to those devices which are accessible over DID!'''


[[Image:dev_rules1.png]]
[[Image:dev_rules1.png]]


We see a similar window as the one in Localization. The rules to manage Provider Rules are identical to those for Localization management, which are covered [[Number Manipulation | here]].
We see a similar window as the one in Localization. The rules to manage Device Rules are identical to those for Localization management, which are covered [[Number Manipulation | here]].




Line 20: Line 21:
= Destination Localization Rules =
= Destination Localization Rules =


Let's say our provider expects to get a number with the technical prefix 89765#. We can do this in following way:
'''IMPORTANT: Localization Rules only matter to the Trunks (Devices marked as Trunks). Simple Devices do not care about Destination.'''


[[Image:dev_rules2.png]]
Let's say our device/trunk expects to get a number with the international prefix 00. We can do this in the following way:


That's it – very simple. Now every number that is sent to this provider will be transformed by adding our created tech. prefix.
[[File:Device_dst_rules_1.png]]


For example, if 37063042438 should be sent to this provider, this rule will be activated and the number 89765#37063042438 will be sent to provider.
That's it – very simple. Now every number that is sent to this Device will be transformed by adding our created int. prefix.


'''REMINDER''': You can check whether Provider Rules are applied correctly in [[Call Tracing]]
For example, if 37063011111 should be sent to this Device, this rule will be activated and the number 0037063011111 will be sent to Device.


== Special cases ==  
== Special cases ==  
Line 36: Line 37:
With rule '''Cut: *#''' it is possible to cut everything till # (# included) in the dialed destination:
With rule '''Cut: *#''' it is possible to cut everything till # (# included) in the dialed destination:


[[Image:dev_rules3.png]]
[[File:Device_dst_rules_2.png]]


For example:
For example:
Line 51: Line 52:
=== Destination same as received ===
=== Destination same as received ===


If you want to send a number to a Provider exactly as it was received, set Cut = '-' (minus sign as shown in the screenshot).
If you want to send a number to a Device exactly as it was received, set Cut = '-' (minus sign as shown in the screenshot).


That way, the same number that comes to MOR also leaves MOR:
That way, the same number that comes to MOR also leaves MOR:


[[Image:dev_rules4.png]]
[[File:Device_dst_rules_3.png]]


<br><br>
=== Destination overwrite ===
It is possible to overwrite any Destination before sending a call to such a Device.
In Device Rules (for this Device) set up the Rule:
[[File:Device_rules_dst_overwrite.png]]
In this example, all calls going to this Device will have Destination = 37063033333


<br><br>
<br><br>
Line 62: Line 73:
= CallerID Localization Rules =
= CallerID Localization Rules =


Source Rules manages CallerID which is sent to this particular Provider.
Source Rules manages CallerID which is sent to this particular Device.


In the example bellow we will add international prefix to every CallerID sent to this Test Provider:
In the example bellow we will add international prefix to every CallerID sent to this Device:


[[File:dev_rules5.png]]
[[File:Device_src_rules_1.png]]




== Special Case ==
== Special Case ==
=== CallerID localize Name part ===
If Name part of CallerID should be localized as well, then check '''Change CallerID name''' checkbox.<br>
For example, if CallerID is "00123456789" <00123456789>, then after localization (given bellow) CallerID will look like "123456789" <123456789>
[[File:Device_src_rules_3.png]]


=== CallerID overwrite ===
=== CallerID overwrite ===


Sometimes Providers only accept calls with CallerID.
Sometimes Trunks only accept calls with special format CallerIDs.


It is possible to overwrite any CallerID before sending a call to such a Provider.
It is possible to overwrite any CallerID before sending a call to such a Device.


In [[Provider Rules]] (for this Provider) set up the Rule:
In Device Rules (for this Device) set up the Rule:


[[Image:dev_rules6.png]]
[[File:Device_src_rules_2.png]]


In this example, all calls going to this Provider will have CallerID = 9999999999
In this example, all calls going to this Device will have CallerID = 37063033333


<br><br>
<br><br>
Line 91: Line 109:
** [[DID handling by Localization]]
** [[DID handling by Localization]]
** [[Number Manipulation Examples]]
** [[Number Manipulation Examples]]
** [[Device Rule Groups]]

Latest revision as of 13:51, 20 August 2019



Device Rules transform an E.164-compatible number to any number format the Device requires.

Description

Different Devices expect different number formats from you. You can send them whatever they want using Device Rules.

Device Rules are only used when Device is reached over DID. Local calls between Devices will not use Device Rules.

Device Rules can be reached by clicking the Rules.png icon next to a Device in the Devices window:

IMPORTANT: Device Rules are applied ONLY to those devices which are accessible over DID!

Dev rules1.png

We see a similar window as the one in Localization. The rules to manage Device Rules are identical to those for Localization management, which are covered here.




Destination Localization Rules

IMPORTANT: Localization Rules only matter to the Trunks (Devices marked as Trunks). Simple Devices do not care about Destination.

Let's say our device/trunk expects to get a number with the international prefix 00. We can do this in the following way:

Device dst rules 1.png

That's it – very simple. Now every number that is sent to this Device will be transformed by adding our created int. prefix.

For example, if 37063011111 should be sent to this Device, this rule will be activated and the number 0037063011111 will be sent to Device.

Special cases

Cut everything till Hash

With rule Cut: *# it is possible to cut everything till # (# included) in the dialed destination:

Device dst rules 2.png

For example:

  • Dialed number: 999#37063042439.
  • After Localization: 37063042439.

This function can be used in fancy MNP (Mobile Number Portability) schemes and perhaps elsewhere.


NOTE: Add value still can be used to add any value after Cut is used on the Destination.



Destination same as received

If you want to send a number to a Device exactly as it was received, set Cut = '-' (minus sign as shown in the screenshot).

That way, the same number that comes to MOR also leaves MOR:

Device dst rules 3.png



Destination overwrite

It is possible to overwrite any Destination before sending a call to such a Device.

In Device Rules (for this Device) set up the Rule:

Device rules dst overwrite.png

In this example, all calls going to this Device will have Destination = 37063033333



CallerID Localization Rules

Source Rules manages CallerID which is sent to this particular Device.

In the example bellow we will add international prefix to every CallerID sent to this Device:

Device src rules 1.png


Special Case

CallerID localize Name part

If Name part of CallerID should be localized as well, then check Change CallerID name checkbox.
For example, if CallerID is "00123456789" <00123456789>, then after localization (given bellow) CallerID will look like "123456789" <123456789>

Device src rules 3.png

CallerID overwrite

Sometimes Trunks only accept calls with special format CallerIDs.

It is possible to overwrite any CallerID before sending a call to such a Device.

In Device Rules (for this Device) set up the Rule:

Device src rules 2.png

In this example, all calls going to this Device will have CallerID = 37063033333



See also

Retrieved from "https://wiki.kolmisoft.com/index.php?title=Device_Rules&oldid=24981"