HotelKey

• Each vendor typically has their own documentation for configuring their interface to work with DuVoice.
  • If not, our default configuration could be used as a reference.
• Please keep in mind that for DuVoice, the best practice is to set up a translation on the PMS.
  • All rooms should be references as their extension numbers.
    • This is so the DuVoice server can map the guest information to the mailbox (which is tied to the room's extension number).

Note that this is considered a 'template' for installation, as each site has its own specific details that will need to be configured as well.

DuVoice services must be shutdown before updating the DuVoice configuration.

1. Open 'Manager' or 'System Configuration' application.
2. Click 'features' drop down menu.
3. Click on 'hospitality'.
4. Click on the server you wish to edit, or click add if there are no servers.

Since this is an FIAS interface (the link for check-in/out information is guest-ID based) using InnDesk web UI, DV2000 Manager application or the Hospitality Tester application for CHECK-IN testing can cause the DV2000 database to get out of sync with the PMS. Subsequent checkouts from the PMS and other functions may not work because the Guest IDs do not match. The solution is to check out any mailboxes from the DV2000 before recieving a check in from PMS.

Packets that are sent back and forth from each system, will appear as 'missing' from each systems' logs if the system time for the DuVoice server and the PMS interface server are too far off-sync.

While doing your configuration, if you don't see the option for the protcol listed in the DuVoice PMS link configuration table above, you can substitute 'Oracle Opera FIAS' in its place as a workaround. It is recommended to update DuVoice to the latest version to avoid needing to do this.