The Location Code defines the segmentation of the dialed numbers. The Location Code is derived from the Prefix Access Code.
The Location Code is segmented into Country Code (L2), Area Code (L1) and Local Office Code (L0). If the matching Location Code contains also digits which are part of the extension numbers, those need to be skipped.
As soon as an extension number is assigned to a subscriber, the administrator has begun the process of creating a private numbering (and dialing) plan. The most basic form of a private numbering plan (PNP) is extension dialing. A subscriber with an extension number has two identities:
A public identity (the subscriber ID, which is usually a public DID number)
A private identity (the extension number) that can be dialed within the business group
Lotus Sametime Unified Telephony also supports the concept of Level 0, 1, and 2 private numbering plans, including location codes. Just as public numbers have multiple forms (with or without the country code, with or without the city code/area code, and so on), private numbers also have multiple forms.
A PNP L0 (level 0) private number is the private network equivalent of a local subscriber number in the public network; in the US, this is a 7-digit number.
A PNP L1 private number is the private network equivalent of a national number in the public network.
A PNP L2 private number is the private network equivalent of an international number in the public network.
Using Telephony Control Server Assistant, the administrator can create an L0, L1, or L2 private number by assigning a location code to each local BG numbering plan, and repeating the process for each Lotus Sametime Unified Telephony switch in the private network.
Lotus Sametime Unified Telephony Assistant allows the administrator to define the L0, L1, and L2 forms of the PNP location code digits. For a given BG numbering plan, Telephony Control Server Assistant allows the administrator to define the:
Location code digit string (up to 14 digits)
Number of digits in the L2 part of the location code
Number of digits in the L1 part of the location code
Number of digits in the L0 part of the location code
Number of skip digits (number of digits in the location code which must be deleted to reach the first digit of the PNP extension number)
The network designer must decide whether the network requires the use of location codes, and if so, how many levels. Few networks require more than L0 location codes.
A network designer needs to know when to define and use location codes. There are two basic instances:
To resolve numbering conflicts between sites. If two sites within the network want to call each other, but both have extension numbers in the 1xxx block, the location code provides a way to remove the ambiguity between the numbers. Both groups can keep their extension numbers and still call each other.
In large networks, to provide additional subscriber numbering capacity without forcing subscribers to dial 5, 6, or 7 digits on every internal call.
When a BG numbering plan is assigned a location code, other BG numbering plans can route calls to that location code as a destination (destination type “home location” in Assistant).
Location codes are defined and assigned at the BG numbering plan level. This means that each BG numbering plan can have one or more unique location codes.
Creating a location code does not put it fully into use. After the location code is defined, it must be assigned to one or more extension number blocks, using the Assistant BG “Extensions” screen. The location code definition instructs the translation logic how to parse an L1, L2, or L3 private number to determine the private extension number. The extension block definition then links the location code and extension number block (for example, 1xxx) to the appropriate subscriber IDs, giving the system the ability to translate a subscriber ID into a private number, and vice versa.
It is worth noting that the main function of the location code definitions and extension block definitions is not call routing; complex multilevel private dialing plans can be created without using these tables. The number type of the dialed destination number is determined and set in the prefix access code tables of the appropriate numbering plan. The primary function of the location and extension tables is to permit proper handling and display of caller ID information.
The number modification tables are used to send a caller ID in proper format (E.164 or private network format) to a SIP destination, such as a SIP phone or SIP gateway, and will use the location code information as appropriate, when the caller is a BG subscriber.
Over SIP-Q, both the fully qualified public and private number are transmitted as caller ID. The receiving switch or gateway determines which number to display or forward.
Location code definition for a Level 3 PNP network might look like the one shown in the following table:
Table 1. Location Code—Level 3 Example
|Location code digit string||1408492||This is a level 3 PNP location code.|
|Digits to skip||6||The 2 in 492 is part of the extension number.|
An example location code definition for a L0 PNP network might look like the one shown in the following table:
Table 2. Location Code—L0 Example
|Location code digit string||994||This is a level 1 PNP location code.|
|L1 length||0||No level 1 digits.|
|L2 length||0||No level 2 digits.|
|Digits to skip||2||The 4 in 994 is part of the extension number.|Parent topic: Numbering Plan
Subscriber Routing topics
How to Assign a Destination to a Destination Code/E.164 Code
Overlapping Location Code and Extension Digits
Using PNP Location Codes
The network designer can set up a private numbering plan with location code-like dialing, without ever making an entry in the location code table.
How to Add/Edit Location Codes
This procedure describes how to create/edit Location Codes at the subscriber level.
How to Delete Location Codes
This procedure describes how to delete Location Codes at the subscriber level.