# Clustered Hospitality Programming

- Programming New Installations

- Upgrading an Existing Cluster

- Changing the Gateway to a Different MiVoice Business System

- Re-adding Removed Elements

## Programming new installations

1. Configure the Network Elements and create the cluster. See IP Networking Programming for instructions.

2. (Optional) Dimension Selection form

- Adjust the parameters as required depending on the number of suites and linked suites in the cluster.

3. Enable SDS at each element in the Hospitality Cluster.

   IMPORTANT: If SDS is off, or the Hospitality Gateway and hosting MiVoice Business system are not sharing at the Cluster level (and the Resilient Pair level for resilient systems), data inconsistency between them is highly likely. An indication that SDS is improperly configured is the absence of room data in the Guest Rooms form for rooms NOT hosted by the Hospitality Gateway.

4. Network Elements form

Share and synchronize the following forms:

4. Class of Restriction Groups

5. Class of Service Options

6. Cluster Elements (Cluster Definition and Members)

7. Feature Access Codes

8. System Speed Calls

9. Interconnect Restriction

10. Intercept Handling

11. SMDR Options

12. Telephone Directory (see Notes below)

13. Hotel Options

14. Guest Rooms

15. Linked Suites – Members

NOTES

- The last four forms listed are shared by default.

- The Linked Suites – Members form can only be synchronized from the Hospitality Gateway to the Hospitality MiVoice Business system.

- Because of the frequent telephone directory changes in a hospitality environment, the recommended sync behavior for the Telephone Directory form is Overwrite instead of the default Merge.

Uniform Route and ARS configuration is recommended and can be achieved by sharing the following forms throughout the cluster:

- ARS Digits Dialed

- ARS Leading Digits

- ARS Digit Modification Plans

- Maximum Dialed Digits

- ARS Routes

5. Hotel Options form

- Select the Hospitality Gateway and choose the options required for the entire hospitality cluster.

  NOTE: Once the Hospitality Gateway is selected it cannot be changed until all remote Guest Rooms are removed from the Guest Rooms.

6. System Options form

- Enable Send Travelling Class Marks.

7. Class of Service Options form

Enable the following options as required:

7. Hotel Room Monitor Setup Allowed

8. Hotel Room Monitoring Allowed (for each console, line, or trunk used as a room monitor listener device)

9. Suppress Delivery of Caller ID Display between Sets (for each guest room extension)

10. Suppress Delivery of Caller ID Display between Sets - Override (for front desk, room service, and other extensions requiring calling party identification)

8. Suites ( ) or Multi-device Suites form ( )

- Add and configure any suites.

  NOTE: Use the Suites form to program a suite containing members that are licensed individually with IP User licenses. Use the Multi-device Suites form to program the suite itself with a Multi-device Suites license (and allow the members to remain unlicensed).

9. Telephone Directory form

- Add an entry (name and number) to the directory for each Suite Pilot Number and each Suite Extension.

  NOTE: The suite pilot number and member extensions must have TelDir entries to enable IP Console applications(MiVoice Business Console) to display room data for the suite.

10. Guest Rooms form on the Hospitality Gateway

- Add guest rooms.

  NOTE: When adding a resilient device to the Guest Rooms form, ensure that the device's RDN is present in both the primary and secondary MiVoice Business systems. Otherwise, changes to the room that the device is in may fail to propagate to its host system. For instructions on identifying and correcting missing RDNs, see Correcting Inconsistent RDNs.

11. Linked Suites form on the Hospitality Gateway

- Add and configure any linked suites.

12. (Optional) Program a printer port to output Hotel reports.

## Upgrading an existing cluster or migrating standalone MiVoice Business systems to a Hospitality Cluster

Follow this procedure to upgrade a cluster of MiVoice Business systems that are each providing standalone hospitality service to a Hospitality Cluster or to migrate standalone (non-clustered) hospitality systems to a Hospitality Cluster.

1. Upgrade the standalone controllers to 3300 ICP Release 8.0 (or later). See the MiVoice Business Technician's Handbook for upgrade procedures.

   NOTE: When performing the data restore from a pre-3300 ICP Release 8.0 system, all room extensions and suites are restored subject to Hospitality configuration restrictions in Release 8.0. This may result in the removal of previously allowed configurations. Check the log file for any conflicts.

2. If migrating standalone MiVoice Business system to a Hospitality Cluster, configure the cluster and SDS as described in steps 1-3 for a New Installation.

3. Export the Linked Suite data in the Linked Suites form from all Hospitality systems (previously, the standalone MiVoice Business systems that hosted guest rooms).

4. Remove all linked suites from the Hospitality systems.

5. Disconnect the PMS and any IP consoles that are providing guest services.

6. Configure the Hospitality Gateway.

7. Move (or delete and add) the IP consoles to the Hospitality Gateway.

8. Import the previously exported (in step 2) Linked Suites to the Hospitality Gateway.

9. On each Hospitality system, synchronize the data in the Guest Rooms form with the Hospitality Gateway.

10. Reconnect the PMS and IP consoles to the Hospitality Gateway.

## Changing the Hospitality Gateway to a different MiVoice Business system

Follow this procedure to change the configured Hospitality Gateway to another MiVoice Business system in the cluster.

1. From the currently configured Hospitality Gateway, complete the following tasks:

2. Remove all linked suites

3. Export all guest rooms from the Guest Rooms form

4. Remove all guest rooms

2. In the Hotel Options form, select the new Hospitality Gateway.

3. Import the previously exported (in step 1) guest rooms to the new gateway.

4. Recreate any Linked Suites using the System Administration Tool or the PMS.

## Re-adding elements removed from the Hospitality Cluster

Follow this procedure to resume data sharing with an element that was removed from the Hospitality cluster and then re-added after its initial configuration:

1. From the Network Elements form ( ) of a Hospitality cluster member, start sharing data.

2. Perform a form comparison and data synchronization or manually fix the configuration.

3. (Optional) Perform a PMS database swap (GRS).

Related Topics

- Clustered Hospitality Description

- Clustered Hospitality Conditions