Localization

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.

Often it is important to let users to dial different format numbers to reach same destination. It depends on the location where user (or his device) is located.

For that purpose each device has field Location. It describes the physical location of device and rules how this device can dial destination. In other words – each device IS (belongs) in some Location where some specific dialing rules apply.

Location describes where caller IS - not where he is calling!

By default device has location 'Global'. Global rules apply to ALL devices. If user belongs to some other location and his dialed destination has some rule for his destination then global rules are not activated – they have lower priority upon 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 Global location. You can't delete this location. It's default for all devices.

You can add new Location by entering this Location's name in field at the bottom of table:

and pressing :

In the column Rules press icon on to access Location's rules:

Following settings should be explained for rule:

• Name – just for informational purposes
• Cut – what prefix from the number should be cat
• Add – what prefix to the number should be added
• Min Len – what's the minimum length of number we are trying to apply this rule
• Max Len – what's the maximum length of number we are trying to apply this rule
• Tariff - which Tariff to apply when this Rule is applied. It is used in special cases, 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 enter all values (Cut or Add can be left empty) press .

Example:

• Normal Lithuania MOB prefix is: 3706
• 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

To describe this situation we will create 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.

See also

• Number Manipulation
  • Provider Rules
  • DID handling by Localization
  • Number Manipulation Examples