Difference between revisions of "Localization"
| Line 29: | Line 29: | ||
[[Image:localization3.png]] | [[Image:localization3.png]] | ||
In the Rules column, click [[Image:rules.png]] icon | In the Rules column, click the [[Image:rules.png]] icon to access Location's rules: | ||
[[Image:localization4.png]] | [[Image:localization4.png]] | ||
The following settings should be explained for rules: | |||
* '''Name''' – just for informational purposes | * '''Name''' – just for informational purposes. | ||
* '''Cut''' – what prefix from the number | * '''Cut''' – what prefix should be cut from the number. | ||
* '''Add''' – what prefix to the number | * '''Add''' – what prefix should be added to the number. | ||
* '''Min Len''' – | * '''Min Len''' – the minimum length of number to which the rule is being applied. | ||
* '''Max Len''' – | * '''Max Len''' – the maximum length of number to which the rule is being applied. | ||
* '''Tariff''' - which Tariff to apply when this | * '''Tariff''' - which Tariff to apply when this rule is applied. It is used in special cases, for example [[LCR/Tariff change based on call prefix | here]]. Leave this empty in most cases. | ||
* '''LCR''' - which LCR to apply when this | * '''LCR''' - which LCR to apply when this rule is applied. It is used in special cases, example [[LCR/Tariff change based on call prefix | here]]. Leave this empty in most cases. | ||
When you | When you have entered all the necessary values (Cut or Add can be left empty), click [[Image:add.png]]. | ||
For example: | |||
* | * The normal Lithuania MOB prefix is: 3706. | ||
* | * The user's device is located in Lithuania Vilnius. | ||
* By current Lithuanian regulations local customer can dial 9 digit numbers starting with 86 to reach Mobile subscribers | * By current Lithuanian regulations, the local customer can dial 9-digit numbers starting with 86 to reach Mobile subscribers. | ||
To describe this situation we | To describe this situation, we create the following rule: | ||
[[Image:localization5.png]] | [[Image:localization5.png]] | ||
Revision as of 23:16, 2 May 2010
Description
Localization transforms received number to E.164 format number.
The main idea of localization: No matter how the user dials the number (destination), when localized it should be in E.164 format.
Localization has nothing in common with numbers you send to providers. It operates with numbers received from the caller.
Depends on the location of the user (or his device), it is often important to allow users to dial differently formated numbers to reach a destination. For this purpose, each device has a field Location, which describes the physical location of the device and provides rules for how th3 device can dial a destination. In other words each device IS in (or belongs to) some Location where specific dialing rules apply.
Location describes where a caller IS - not where he is calling to!
By default, a device has the location 'Global'. Global rules apply to ALL devices. If a user belongs to some other location and his dialed destination has some rule for his destination, then global rules are not activated – they have a lower priority in location rules.
You can access Localization settings in SETTINGS – Billing – Functions – Localization.
In the main window you can see available Locations:
At first there is only the Global location. You can't delete this location. It's the default for all devices.
You can add a new Location by entering this Location's name in the field at the bottom of the table:
and clicking 
:
In the Rules column, click the 
icon to access Location's rules:
The following settings should be explained for rules:
- Name – just for informational purposes.
- Cut – what prefix should be cut from the number.
- Add – what prefix should be added to the number.
- Min Len – the minimum length of number to which the rule is being applied.
- Max Len – the maximum length of number to which the rule is being applied.
- Tariff - which Tariff to apply when this rule is applied. It is used in special cases, for example here. Leave this empty in most cases.
- LCR - which LCR to apply when this rule is applied. It is used in special cases, example here. Leave this empty in most cases.
When you have entered all the necessary values (Cut or Add can be left empty), click .
For example:
- The normal Lithuania MOB prefix is: 3706.
- The user's device is located in Lithuania Vilnius.
- By current Lithuanian regulations, the local customer can dial 9-digit numbers starting with 86 to reach Mobile subscribers.
To describe this situation, we create the following rule:
Rules can be enabled or disabled pressing 
icon or 
accordingly in the Enabled? column.
- This icon let's you edit rule's details.
- This icon let's you delete rule
Now in the main Localization window:
Press on 
in Devices column to access Devices in Global Location:
Here all Devices with selected location are listed. Choose other location for selected Device and press on icon to activate this change. Device will be assigned to the selected Location.
NOTE: It's possible to change Device's Location in Device's settings (SETTINGS – Users – Devices).
Now our device belongs to Location Lithuania Vilnius. And if we dial mobile number in Lithuanian format for example:
863042438, MOR cuts 86 (remaining part 3042438) and adds 3706. Result is: 37063042438 which is E.164 compatible and MOR can bill it correctly.
NOTE: make sure that after localization your number always is E.164 compatible. Call Tracing can help you do this.
Special cases
Cut everything till Hash
This option is available starting from MOR 9
With rule Cut: *# it is possible to cut everything till # (# included) in the dialed destination:
Example:
- Dialed number: 1aaaaaaaaa#37063042439
- After Localization: 37063042439
This function can be used in fancy MNP (Mobile Number Portability) schemes and maybe elsewhere.
NOTE: Add value still can be used to add any value after Cut is used on the Destination.
