# Direct Inward Dialing Service

## Purpose

Use this form to configure a pool of external DID numbers mapped to their destination numbers (that is, internal directory numbers or other answer points on the system).

Use this form when performing the following tasks:

- Programming Direct Inward Dialing (DID) Service

NOTES

- You can configure this form without activating the DID Service. To activate the service, you must enable the Direct Inward Dialing Service option in the Trunk Attributes form.

- It is recommended that before using the DID Service feature, all nodes in the network (or at least the resilient pair related to the specific DN) be upgraded to Mitel MiVoice Business Release 7.0.

- If you are currently using user-based System Speed Calls for DID routing, you will need to migrate them to DID Service.

## Conditions

- Data configured in this form is stored in the Call Recognition Service (CRS) database. Use the Call Recognition Service form to search and view DID records configured in this form.

NOTE: The CRS form contains all records configured through the DID Service form and all External Hot Desk Users (EHDU) records. However, no EHDU entries can be configured or retrieved through the DID Service form. The DID Service form displays only DID-related data, retrieved from the CRS form and filtered by the CRS Service Type.

- The DID Service form data is shared network-wide through the Call Recognition Service (CRS) form. Changing sharing scope—for example, stop sharing—for DID Service data must be done through CRS in the SDS Form Sharing form.

- Import and Export operations are supported for all fields. Only DID records are imported and exported; however, if the Export Range is set to "All", all the CRS records - EHDU and DID - are exported.

- An answer point for a DID number can be any valid MiVoice Business destination, but not all destination types are suitable for use as the DID Service answer points. The following destination number types should be avoided or used with caution:

- Automatic Route Selection (ARS) Digit Strings - use with caution; possibility of toll fraud

- System Access Points - not recommended

- Feature Access Codes - not recommended

- Primary Node Identifier (PNI) - use with caution

- Cluster Element Identifier (CEID) - use with caution

- EHDU number - use with caution

- Original Dialed Number Identification Service (DNIS) - use with caution

## Field Descriptions

Parameter | Description | Default Value
DID Number | Enter a unique 1- to 26-digit external Direct Inward Dialing (DID) number provided by the CO. Valid digits are: 0-9, *, and #. Complete DID numbers are preferred, but partial numbers are accepted; the format is determined by the Dial-In Trunks Incoming Digit Modification process, as configured in the Trunk Attributes form. This number can also be defined in the User and Services Configuration form. NOTE: This field corresponds to the "Digit String 2" field in the Call Recognition Service form. | Blank
Primary Node ID (PNI) | Enter a 1- to 7-digit Primary Node Identifier of the cluster where the Destination Number is hosted. Valid digits are: 0-9, *, and #. NOTE: This field corresponds to the "Primary Node ID (PNI)" field in the Call Recognition Service form. | Blank
Destination Number | Enter a unique 1- to 26- digit Destination Number (internal Directory Number or any other termination point) to which the DID Number will be redirected. Valid digits are: 0-9, *, and #. The system accepts any digit combination, but certain destination number types are not recommended. See Conditions. NOTE: This field corresponds to the "Digit String 1" field in the Call Recognition Service form. | Blank
DID Type | Select Standard DID or Emergency DID as the Direct Inward Dialing type. For more information, see Direct Inward Dialing (DID) Service. NOTE: This field corresponds to the "CRS Type" field in the Call Recognition Service form. | Standard DID