The DNM Definitions table specifies the definitions of numbering schemes that exist within a numbering plan, business group or even system wide. It allows Lotus Sametime Unified Telephony to decompose a number from the public or private numbering scheme into the code components.
Table granularity: numbering plan level.Note:
This table assumes that the same definitions apply to all subscribers and endpoints using a specific numbering plan.
Business group-specific entries can be defined by creating a Definitions table entry for that specific business group and the 'ANY' numbering plan.
System-wide entries can be defined by creating a Definitions table entry for 'ANY' business group and 'ANY' numbering plan.
It is highly recommended to provide system-wide Definitions for all public office codes and business group specific Definitions for all private office codes. Other definitions should not be necessary if the normalizations table is correctly filled out.
System-wide definitions can be defined by creating table entries for the ANY
Figure 1. DNMDefinitions Number Breakdown
Required content for each component:
The following subsections describe the required content for each component.
In the DNM Definitions table, the business group of an entry is entered with one of the following values:
When business group is ANY, the numbering plan must be ANY as well.
When business group is empty, the numbering plan must be E164NANP. However, the opposite is not necessarily true: when the numbering plan is E164NANP the business group may or may not be empty.
When a particular business group is specified, the numbering plan may be ANY, E164NANP or a numbering plan name belonging to that business group.
In the DNM Definitions table, the numbering plan of an entry is entered with one of the following values:
When numbering plan is ANY, the business group may be ANY or a specific business group.
When numbering plan is E164NANP, the business group may be empty or a specific business group.
When a particular Numbering Plan is specified, the business group must be the numbering plan's business group.
NPI (Numbering Plan Indicator)
The NPI (Numbering Plan Indicator)
column of an entry is used to specify whether the definition is for a private or a public numbering scheme. This is the same identifier that is also supported by ISDN and can have the values Public or Private.
Depending on the value of the Numbering Plan Identifier, this field contains either the Country Code (NPI = Public) or the L2 Code (NPI = Private).
Depending on the value of the Numbering Plan Identifier, this field contains either the Area Code (NPI = Public) or the L1 Code (NPI = Private).
Depending on the value of the Numbering Plan Identifier, this field contains either the Local Office Code (NPI = Public) or the L0 Code (NPI = Private).
Skip (Number of Digits to Skip)
This indicates the numbers of digits to skip in the Local Office Code (NPI = Public) or the L0 Code (NPI = Private) to create an extension.
Min/Max. (Min. Digits/Max. Digits)
This indicates the minimum and maximum number of digits of the Home Directory Numbers of the office codes for which the definition is provided.
The Local Toll
specifies how public numbers are defined for subscribers with Home Directory Numbers that match this DNM Definitions table entry..
Per default it is assumed that users that have a specific public number actually follow the basic rules that they need to dial local numbers within their own area code, national numbers within their country and international numbers elsewhere. As long as these rules apply, there's no need for a local toll entry on the public number definition. However, if these rules change, as they certainly can in the American market, then the local toll table entry specified on the number definition will be used to find out how a number received from the public network can be optimized to the national or subscriber level for the subscribers of that office code.
There are 2 situations where the local toll table is mandatory:
When a standalone private office code is created without a number conversion entry that allows the DNM library to find the accompanying public number then the local toll table entry will allow the DNM library to optimize incoming public numbers correctly for these users. E.g. if a branch office has a single access number and all branch office members have private extensions not reachable directly from the public network, then the subscribers of the branch office need to be provisioned with private numbers and the private number definition table entry needs a local toll entry to define the local and national public numbers in the context of the private number subscribers
When a public office code is created with subscribers that need to dial within split or overlapping area codes. This is the case in e.g. Boca Raton, FL in case the numbers presented to the subscribers need to be in the exact format as specified by the public network.
The number definition library uses a best match (most digits match) algorithm to find a matching rule.
In case the type of number of the digit string for which a definition is searched is known (one of international, national, subscriber, L2, L1 or L0) each entry in the table is checked for a possible match given that knowledge. The best match (i.e. most digits match) is returned.
In case the type of number of the digit string for which a definition is searched is unknown, the definition table is searched assuming a specific type of number in the following order:
Table 1. Number Definition Rules Priorities for Unknown Numbers
|Rule Priority Number||Type of Number assumed||Note|
|1||International||All entries are searched for a best match on country codes + area codes + local office codes|
|2||National||All entries are searched for a best match on area codes + local office codes|
|3||Subscriber||All entries are searched for a best match on local office codes|
|4||L2||All entries are searched for a best match on L2 codes + L1 codes + L0 codes|
|5||L1||All entries are searched for a best match on L1 codes + L0 codes|
|6||L0||All entries are searched for a best match on L0 codes|How to Create/Edit Display Number DefinitionsParent topic: Routing and Translation
This procedure describes how to create/edit Display Number Definitions table at the system wide or subscriber level.The Display Number Definitions window contains a Context Setting section where a business group name and a numbering plan name can be selected. Within the specified context the definition section allows specifying: Numbering Plan Indicator (Public or Private), Country code/L2 code; area code/L1 code; local office code/L0 code; skip on the local office code/L0 code, minimum digits of the defined number; maximum digits of the defined number and it allows to assign a local toll table to be used for optimization of public numbers presented to subscribers of this office code.
How to Delete Display Number Definitions