You can add local-only directory numbers through any of the following forms:
ACD Express Group Assignment
Agent ID Assignment
Analog Set Assignment (through Change dialog box)
Agent Skill Group Assignment
DNI Console Configuration (through Change dialog box)
Hunt Group Assignment
IP Console Configuration
Multi-Line DNI Set Configuration (through Change dialog box)
Multi-line IP Set Configuration
Page Group
Path Assignment
Ring Group Assignment
Single Line DNI Set Configuration (through Change dialog box)
Single Line IP Set Configuration
User Configuration (only after migration to RDN Synchronization; prior to migration, if you add a user through this form, it is included in the local telephone and shared to the other cluster elements)
Wireless IP Set Configuration
Note: In a RDN Synchronized cluster, the Local-only Directory Number List form displays all the local-only directory numbers in the cluster.
To add a local-only directory number to an element in a cluster that supports RDN Synchronization:
Access the Maintenance Commands form and use the LOCATE ALL FREE DN command to find a new unused DN.
Access one of the device-based forms listed above.
Click Add.
Enter the new directory number.
Check the Local-only DN box. If you are adding the local-only directory number through the User Configuration form, the Last Name and First Name field are disabled (grayed out).
Complete the other fields as required.
Click Save. The new directory number is reserved as a local-only directory number in the databases of each cluster element.
Note: In Analog device forms and DNI device forms, you click the Change button to add a local-only directory number. To modify an existing local-only directory number, you must first Clear the entry then add it again using the Change button.
To add a local-only directory number to an element in a cluster that has NOT been migrated to support RDN Synchronization:
Access the Maintenance Commands form and use the LOCATE ALL FREE DN command to find a new unused DN.
Access any one of the device-based forms listed above (excluding the User Configuration form).
Click Add.
Enter the new directory number.
Complete the other fields as required.
Click Save. The new directory number is saved in the database of the local element only. It is not written to the Telephone Directory Assignment form, so OPS Manager does not distribute the new directory number to the other cluster elements.
To delete a local-only directory number:
Do one of the following:
In an RDN synchronized cluster, access the User Configuration form or the device-based form that lists the local-only directory number.
In a non-RDN synchronized cluster, access the device-based form that lists the local-only directory number. In a non-RDN synchronized cluster, local-only numbers do not appear in the User Configuration form.
Find the local-only directory number using the Search functionality.
Select the local-only directory number.
Click Delete and then click Ok. The local-only directory number is deleted from the database of the local element.
Note: If other instances of this local-only number exist on remote cluster elements, they are not deleted from the remote elements after you delete the entry from the local element. In addition, the directory number remains as a local-only designated number in the databases of all elements in the cluster. To remove the local-only designation from a directory number, you must delete it from the database of each element in the cluster.
If you are migrating an existing cluster to support RDN Synchronization, you must list any existing local-only directory numbers in the Local-only Directory Number List form before you perform the migration. The steps for migrating local-only directory numbers to a cluster that supports RDN Synchronization are detailed in the Migrate to RDN Synchronization procedure.
