You must use either RDN Synchronization or OPS Manager to distribute telephone directory entries within the network. Both synchronization modes cannot be used in the same network. However, OPS Manager can still be used in the network for other management functions, such as alarm monitoring and database backups.
Before you can migrate a network or cluster to support RDN Synchronization:
All the 3300 ICPs in the network or cluster have MCD Release 4.0 or later software.
The network or cluster must consist of only 3300 ICPs.
Each element in the network or cluster is configured to share data via System Data Synchronization.
Each element that belongs to the network or cluster must be migrated to support RDN Synchronization.
You must disable Property Management System (PMS) support. Access the Hotel Options Assignment form and set the "Property Management System Installed" option to "No". If Clustered Hospitality is configured, disable PMS at the gateway element. If standalone Hospitality systems are configured on elements in the cluster, disable it at each element that is connected to a PMS.
Hot Desk users—including External Hot Desk users—must be logged out. To log out hot desk users:
Set "Hot Desk Login Accept" in all Class of Services to "No" to prevent hot desk users from logging in.
Set "Hot Desk External User - Permanent Login" in all Class of Services to "No".
From a phone that has "Hot Desk Remote Logout Enabled" set to "Yes" in it's COS, log out all hot desk users by entering the "Hot Desk Remote Logout" feature access code. (Or, you can enter the "Busy Reset" command against the DN of each hot desk user from the Maintenance Commands form).
Perform the migration.
After the migration is complete, reset any COS that you changed back to the original settings. Hot desk users will now be allowed to log back. As well, the system logs in any external hot desk users who have "Hot Desk External User - Permanent Login" set to "Yes".
During a network or cluster migration:
With the exception of the System Administration Tool session that you use to perform the migration, all other System Tool sessions on all sharing elements in the network or cluster are shut down. Access to new System Tool sessions is denied for the duration of the migration.
Hospitality operations are rejected during migration.
TUI hospitality features (such as Maid Status, Message Registration, and Wakeups) are not allowed. If a user attempts to initiate a TUI hospitality feature, the system provides reorder tone.
Toggle Call Block (Automatic Hotel Operation) is not allowed. If a user attempts Toggle Call Block, a hotel log is generated to indicate that this operation failed.
The 5550 IP Console Guest Services cannot retrieve guest room information while the hospitality gateway is migrating. However, if the hospitality ICP is also in the process of migration, then the Guest Services Application can retrieve remote guest room information, but will be unable to save changes.
Guest Services Application cannot save changes to guest rooms.
After the migration:
You cannot
synchronize an element that has pre-MCD Release 4.0 software with an element that has MCD Release 4.0 software or later.
start sharing data from an element in the migrated network or cluster to an element that has pre-MCD Release 4.0 software.
start sharing from a pre-migration MCD Release 4.0 element to a post-migration MCD Release 4.0 element.
distribute a directory entry to a specific list of elements. With RDN synchronization, SDS shares directory entries at the specified sharing scope. All elements within the specified scope, share the directory entries. Unlike OPS Manager, you cannot distribute a directory entry to a specific list of elements.
Do not downgrade an element in the migrated network from MCD Release 4.0 software to pre-MCD Release 4.0 software. This downgrade is not supported and will result in shared data updates on the element that is running pre-MCD Release 4.0 software.
It is possible to return a network that has been migrated to support RDN Synchronization back to being a non-RDN Synchronized network. However, this process is not recommended or supported. You must restore a pre-migration database on every node in the network. Then, you will need to re-enter any configuration changes that were made after the migration took place.
You must download an updated version of the Import/Export Spreadsheet after the migration is complete. And, any data that you exported prior to the migration cannot be re-imported.
You cannot export data from a pre-migrated system and then import the data into a system that has been migrated to RDN Synchronization with the exception of the IP Console Configuration form. You can export data from the IP Console Configuration form on a pre-migrated system and then import it into a system that supports RDN Synchronization.
By default, non-prime DNs will be hosted on the same element as the associated set. For example, consider a set with DN 1111, hosted on element A. If the administrator programs button 3 to be a single line with DN 1112, then DN 1112 will default to being hosted on element A.
After the migration, the following System Administration Tool changes take effect:
By default, telephone directory entries are shared as General System Data at the "All 3300 ICPs" scope. You can edit any telephone directory entry from any element that is included in the SDS sharing scope assigned to the Telephone Directory.
There are two new restrictions that apply to Telephone Directory Assignment form:
If the directory number (DN) for an entry is a device DN, you cannot change it to a non-device DN (ARS string or group feature DN).
If the DN for an entry is a non-device DN, you cannot change it to a device DN.
An "Add" operation that you perform from the User Configuration form always creates a new user entity, even if a user already exists with the same name.
There are modifications to the fields in the User Configuration and User Authorization Profile Assignment forms.
In forms that allow you to add or modify the directory name, such as the Telephone Directory Assignment form, the first name and last name can be up to 64 alphanumeric characters in length.
The Remote Directory Assignment form becomes read-only and the Add, Change, and Delete buttons are no longer available in this form. View is available instead.
The Department Assignment and Location Assignment forms do not display the Index column after the migration, so you can no longer search by Index number. However, you can search on department name or location in these forms when the system has been dimensioned to support large lists in the database.
The list of forms in the Shared Forms Configuration form is modified:
The "General System" group of forms contains the Telephone Directory Assignment form.
The "User Definition" group of forms contains entries for the following data: Department Assignment, Location Assignment, User Configuration - User Attributes, User Authorization Profiles.
"Service Hosting Data" is a new group of forms that allow the sharing of local-only directory numbers, hosted system data, and hosted user data.
You can configure device resiliency from the User Configuration form and IP Console resiliency from the IP Console Configuration form of the primary element. After the migration, you cannot use OPS Manager to configure device resiliency.
Simultaneous changes to data records are not shared via SDS. If two administrators perform changes on the same data record at the same time, shared updates will not be generated and the data record will be different on both systems.
