Difference between revisions of "Provider Rules"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(3 intermediate revisions by the same user not shown)
Line 14: Line 14:


<br><br>
<br><br>
= Destination Localization Rules =
= Destination Rules =


Let's say our provider expects to get a number with the technical prefix 89765#. We can do this in following way:
Let's say our provider expects to get a number with the technical prefix 89765#. We can do this in following way:
Line 38: Line 38:


* Dialed number:  999#37063042439.
* Dialed number:  999#37063042439.
* After Localization: 37063042439.
* After transformation: 37063042439.


This function can be used in fancy MNP (Mobile Number Portability) schemes and perhaps elsewhere.
This function can be used in fancy MNP (Mobile Number Portability) schemes and perhaps elsewhere.
Line 76: Line 76:
  To: <sip:37012345678TEXT@sip.provider.com:5060>
  To: <sip:37012345678TEXT@sip.provider.com:5060>


 
= CallerID 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 Provider.
Line 88: Line 87:
== Special Case ==
== Special Case ==


=== CallerID localize Name part ===
=== CallerID transform Name part ===


If Name part of CallerID should be localized as well, then check '''Change CallerID name''' checkbox.<br>
If Name part of CallerID should be transformed 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>
For example, if CallerID is "00123456789" <00123456789>, then after transformation (given bellow) CallerID will look like "123456789" <123456789>


[[File:Provider_src_rules_3.png]]
[[File:Provider_src_rules_3.png]]

Latest revision as of 14:23, 23 February 2021

Description



Provider Rules transforms an E.164-compatible number to any number format the Provider requires.

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

Provider Rules can be reached by clicking the Rules.png icon next to a provider in the Providers window:

Provrules1.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 here.




Destination Rules

Let's say our provider expects to get a number with the technical prefix 89765#. We can do this in following way:

Provrules2.png

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

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.

REMINDER: You can check whether Provider Rules are applied correctly in Call Tracing



Special cases

Cut everything till Hash

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

Provider rules cuttillhash.png

For example:

  • Dialed number: 999#37063042439.
  • After transformation: 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 Provider 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:

Prov rules dst as received.png

Replacement

If you want to replace one prefix with another you have to Cut the original prefix and Add' the new one. For example:

If the number is 306936525113 and you want to replace 30 with 6516 this is how the rule should look:

Provrules replace.png

Only one rule can be applied, the one that fits the number the best.

Add Suffix

Add anything to destination number.

Provrules suffix.png

If the dialed number is 37012345678, then TEXT will be added to it and destination number became 37012345678TEXT. Example:

INVITE sip:37012345678TEXT@sip.provider.com:5060 SIP/2.0
To: <sip:37012345678TEXT@sip.provider.com:5060>

CallerID Rules

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

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

Provider src rules 1.png

Special Case

CallerID transform Name part

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

Provider src rules 3.png

CallerID overwrite for Provider

Sometimes Providers only accept calls with CallerID.

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

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

Provider src rules 2.png

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



Change Tariff

Provider Rules allow to change Provider's Tariff based on Source or Destination number

Provider src rules change tariff.png

Copy Rules to Provider

At the top of Provider Rules page you can find Copy Rules to Provider button which allows to copy Provider Rules to any other Provider. This is convenient when you have a lot of rules which need to be applied to several providers.



Copy provider rules.png

Set PAI

Set CallerID to Anonymous. PAI will contain modified CallerID by Provider rule.

Provider src rules pai.png

See also