This is the main number associated with the subscriber. The subscriber's Directory Number can be either a Public (E.164) or a Private (L2, L1, or L0) number.
Home Directory numbers are related to an office code and can be assigned as extension numbers to subscribers, phantom lines, endpoints, services or intercept destinations.
If the subscriber's "External Directory Number" field is checked, it means that the Home DN assigned to the subscriber is a Public (E.164) number.Note:
Otherwise, it means that the Home DN is a Private (L2, L1 or L0) number.
The definition on whether the Home DN is a Public or Private number is not stored as part of the Office Code or even as part of the Home DN itself. This information is part of the subscriber profile data.
Default Home Directory Number
- Home DN assigned to an Endpoint Profile
The "Default Home DN" number can be assigned to an endpoint profile.
For 'External' calls to a SIP endpoint (SIP Trunking, SIP Private Networking or SIP-Q Private Networking), if the calling party does not have a Public number, Lotus Sametime Unified Telephony SHALL use the "Default Home DN" (if configured on the SIP endpoint) as the calling party number.
- Home DN used by the Number Modification Library
The "Default Home DN" is also used by the Number Modification Library to optimize all numbers sent to the endpoint (if optimization is required by the Number Modification rule as it is possible to create Number Modification rules where the "Default Home DN" of an endpoint is chosen over the input number to be presented to the endpoint).
The first logical step is the definition of the base E.164 numbering ranges used by the system, effectively defining the public number blocks which will be used to reach the subscribers on the system. These are sometimes referred to as home DNs. This step consists of the following tasks:
- The central office codes of the public switches which provide trunks to the Lotus Sametime Unified Telephony need to be defined. For example, a Lotus Sametime Unified Telephony system may have public DID numbers in the ranges 408-492-xxxx and 561- 923-xxxx. The central office codes 408492 and 561923 would be defined in this case.
- Next, the range of endpoint numbers (DID number blocks) which belong to Lotus Sametime Unified Telephony, within each office code, need to be defined. For example the number block 1000-2999 within the office code 561923 may be used by Lotus Sametime Unified Telephony subscribers. These number blocks are traditionally called DID number blocks.
- Some endpoints on Lotus Sametime Unified Telephony may not have publicly dialable DID numbers. Regardless, they must be defined before they can be configured. This can be done by defining a fictitious office code or number block for these endpoints.
- When defining the office codes, the administrator has the option of including (or not) the country code as part of the office code. However, all office codes should be defined in a consistent manner (with or without the country code) and all are subject to the number length constraints.
These tasks can be done at one time using the Quick Add Business Group wizard (under the Business Group option of Lotus Sametime Unified Telephony Assistant), or by using the Office Codes screen (under Global Translation and Routing).
Global Home Directory Number List
In the Global Home Directory Numbers
List the Business Group Name
column indicates for each HomeDN if it's reserved for a Business Group or not
If nothing is displayed then the HomeDN is not reserved for a Business Group.
There is the option to filter for HomeDNs that are reserved for a specific Business Group or for not reserved HomeDNs.
The administrator can see all the HomeDNs of the system via this list, but he can only edit the HomeDNs that are not reserved for a BG.
The administrator that is BG administrator for a BG can edit non reserved HomeDNs as well as HomeDNs that are reserved for the BG that the user can administer, without having to go the BG specific HomeDN list.
The administrator can reserve new HomeDNs for a BG. He can also unreserve HomeDNs from a BG (need to provide BG name so to avoid mistakes).
The reservation cannot be updated for single HomeDNs.
For the BG administrator that is not System administrator, access to Global HomeDNs list is not allowed. Instead a BG specific HomeDN list is introduced, where edit of single HomeDNs is made possible. (see section 184.108.40.206.2)
BG Specific Home Directory Number List
A Business Group specific Home Directory Number List within the BG menu facilitates the management of the Reserved Directory Numbers.
Parent topic: Routing and Translation
The BG administrator can see all the Reserved DNs of the BG via this list but he can't add or delete Reserved DNs..
The administrator can only edit/modify the Reserved DNs of the BG.
For the System administrator that is not BG administrator, access to BG specific HomeDNs list is not allowed. .
How to Add/Assign a Directory Number Range to an Office Code
The End of Directory Number range is optional and can be used in order to create multiple Directory Numbers at once for the given Office Code.
How to Edit Directory Numbers
Directory Numbers are system resources that can be assigned to Subscribers, Endpoints, Services or Intercept Destinations across the Switch or be reserved for exclusive use within a specific Business Group. Directory Numbers can be vacant or can be assigned to an Endpoint, Service or Intercept Destination.
How to Create a Carrier Profile (for Private and Global Translation and Routing)
How to View/Edit HomeDNs reserved for a Business Group
How to Reserve/Unreserve a HomeDN range for a BG