If your cluster has been migrated to support RDN Synchronization, the following conditions and behaviors apply to local-only directory numbers:
You cannot change a local-only directory number nor can you reassign a local-only number as a cluster dialable number. You must delete the associated device or group feature from the System Administration Tool form (for example, Multiline IP Set Configuration form) and then add it back into the database to modify the directory number. In a RDN Synchronized cluster, SDS then updates all cluster elements with the deletion and addition. In a cluster that is managed by OPS Manager, OPS Manager updates the cluster element telephone directories.
You cannot assign local-only directory numbers to the following:
Suites,
Linked Suites, or
Guest Rooms.
You cannot assign group features (for example Hunt Groups, Ring Groups, or Agent Skill Groups) with local-only directory numbers if the group feature is configured for resiliency.
You cannot assign local-only directory numbers to resilient devices.
You cannot add a new telephone directory entry with a number that is currently assigned as a local-only directory number. Also, you cannot change a telephone directory number to reference an existing local-only directory number.
For a system that has been migrated to support RDN Synchronization, the Add dialog boxes for device-based forms and the User Configuration form contain a check box that allow you to designate a new directory entry as a local-only directory number.
By default, local-only directory numbers are shared by System Data Synchronization at the "All Cluster Member" scope. The only other supported sharing scopes are "All 3300 ICP Network Elements" and "All Network Elements".
In a RDN Synchronized cluster when you configure a single-line key with a non-prime line, the directory number behavior follows that of the prime line. That is,
if the prime line is local-only, the non-prime line that you assign to the key will be local-only
if the prime line is cluster dialable, the non-prime line that you assign to the key will be cluster dialable.
When you clear a single-line key from a set that has a local-only DN, if the single-line key is the last reference to that DN, the local-only DN entry is deleted from the system database.
There are no restrictions on the DNs of multi-call keys. On a set that is programmed with a local-only DN as it's prime line, you can program multi-call keys with either local-only or cluster dialable DNs.
In a system or cluster that has been migrated to support RDN Synchronization, the Local-only Directory Number List form displays all the local-only directory numbers for the cluster in read-only format.
In a system or cluster that has not been migrated to support RDN Synchronization (the telephone directories are managed from OPS Manager), the Local-only Directory Number List form allows you to specify directory numbers that you want to be assigned as local-only during the migration to RDN Synchronization. Entering numbers in this form has no impact on the system until you perform the migration.
In a system or cluster that has not been migrated to support RDN Synchronization:
you cannot overwrite existing entries in the Local Only Directory Number List form using the import spreadsheet tool. If you attempt to import a directory number that already exists in the form, the import operation fails. You must delete the duplicate entries from either the form or from the import spreadsheet.
you cannot add a directory number that exists in the telephone directory to the Local-only Directory Number List form. The system will present an error message. However, it is possible to add a directory number that is listed in the Local-only Directory Number List form to the Telephone Directory. In this case, the system doesn't check the entry against existing entries in the Local-only Directory Number List form. Any entry conflicts will be identified though prior to the migration process if you run the Migration Precheck command.
