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.
The location code table is not primarily used for routing. It is used to properly manage and present the nature of address (NOA/TON) of the calling party to the network, on a call from the BG. As such, the only entries in this table should be for location codes that are within this BG. Most commonly there will be only one entry.
The location code entry instructs the system how to parse the service ID and calling party number into fields, so that the signaling logic can properly set NPI and TON on an outbound call.
The parameters input to create a location code entry include the following:
The location code – this may be the office code part of the BGL service IDs (for example 1561923) or a completely unrelated value.
L0 length – the length of PNP Level 0 prefix digits within the location code. The L0 prefix is the PNP equivalent of the PSTN office code. In the example 1561923, the length would typically be 3.
L1 length – the length of the PNP equivalent of the PSTN city code/area code part of the location code (in the example above, that would probably also be 3 – the digits 561).
L2 length – the PNP equivalent of the PSTN country code part of the location code (1 in the example)
Digits to skip (the number of digits to be deleted from location code to get the first digit of the extension number (in the example, this would be 6 if the BG is using 5 digit extension numbers).
The network designer has the option of choosing a network with no location codes, level 0, level 1, or level 2 location codes. Few networks use more than Level 0 location codes. If the network is using L0 location codes, L1 and L2 lengths above will be 0, and the location code itself is 923.
On outbound calls (to a gateway or peer switch in the network), the system normally sends the subscriber ID of the caller (the E.164 number assigned to the subscriber endpoint). There is a system option flag (rarely used) which, when set, causes Lotus Sametime Unified Telephony to send the private number as caller ID, that number being constructed from the PNP location code and the extension number. This option applies to all outbound calls, systemwide.
The location code information also can also play a role in determining how the caller ID is displayed on the Lotus Sametime Unified Telephony subscriber endpoints and call logsOn calls between subscribers belonging to different numbering plans, the Display Number Modification logic can be configured to display the appropriate PNP number of the other party number, rather than public number.
Parent topic: Location Codes and Private Numbering Plans