Oracle Opera

The Opera certified DuVoice interface provides a TCP/IP middleware protocol for PBX, voice mail, wakeup call, housekeeping and minibar features. The “Oracle part number B92299 Hospitality OPERA IFC_DUV2 TMS Interface for DV2000 - Duvoice Corporation” interface must be ordered by the property. The old Micros part number was 5001-333.

If Call accounting has been purchased, Opera will also need separate interface purchased for Genesis Call Accounting. Interface part number: Genesis Part Number - 5001-226, Product ID-IFC_GEN, Description -CAS I/F – Genesis

  • Oracle Interface Version 8 (FAIS) P/N B92299
    • Oracle Interface Part Number: TMS Telephone Management System interface part number IFC_DUV2
    • Do NOT use the older VMS Voice Mail System interface part number IFC_DUV
  • DuVoice DV2000 V7 or V8

EXTENSION or ROOM? Opera can send either the guest extension or guest room on check ins. The mailboxes in the DV2000 must match what Opera is sending. We recommend using and extension based protocol so room/extension translation tables can be avoided. The extension number is entered into the “LINES” field in the Opera room profile.

Data Sync: If a data sync is initiated from Opera any mailboxes not found on the DV2000 will be automatically created.

Settings:

PMS Vendor: Oracle Opera

  • Link Type:TCP Client
  • PMS Protocol:Oracle Opera FIAS (TCP)
  • DuVoice PMS Interface settings
  • Enable ACK over TCP Checked
  • Enable Checksum N/A
  • Always ACK ENQ N/A
  • Send ENQ N/A
  • Poll Interval 300
  • Request DB swap Optional
  • Forward Wakeup Data Optional
  • Serial Over TCP N/A
  • Use Name for Password Unchecked
  • Unique guest ID N/A
  • Enable Opera DID N/A
  • Enable Opera GF?GT name fields Checked
  • Ignore NAM1 (Mitel) Unchecked
  • MWI for non-room Unchecked
  • Move fix Unchecked

{{:pmslink:oracle:opera1.png?400|(screenshot)}}

Housekeeping codes will be sent to Opera based on what codes are dialed from the room telephone. Below are the defaults but may change with each property.

  • 1 - Vacant Dirty
  • 2 - Occupied Dirty
  • 3 - Vacant Clean
  • 4 - Occupied Clean
  • 5 - Vacant Inspected
  • 6 - Occupied Inspected

On check in and check out the guest room telephone will be restricted and unrestricted. If there are just two options you do not need to touch this section and the defaults will work.

CS - Class of Service (COS) Code Meaning

  • 0 Barred/hotel internal only
  • 1 Local
  • 2 National
  • 3 No restrictions

(screenshot)

The DuVoice system can play different languages based on the guest profile. For domestic US applications US English is all that is needed. Note: International languages must be installed on the DV2000 for this to work.

GL - Guest Languages The following are the most commonly used defaults. Language Code

  • English / American EA
  • French FR
  • German GE
  • Italian IT
  • Japanese JA
  • Spanish SP

(screenshot)

Opera will keep track of any new guest voice mail messages. This must be set up in the DV2000 for both message light and PMS notifications to be sent.

There are a few prerequisites required to ensure a smooth cut over when the site changes the Oracle Opera PMS from an on premise solution to a cloud based solution. Oracle will set up a virtual instance that is used as an intermediary; DuVoice will communicate with that instance, and that instance communicates with Oracle's cloud. Assuming the only change to the PMS is moving to the cloud (and that there are no network issues) the update process is straight forward.

Required updates to the DuVoice configuration

  • New Oracle system's IP address.
  • New port number for the PMS link.
  • The DuVoice system must be able to ping and telnet to the Oracle system using these details.

If there have been any changes to the following options on the Oracle system. Those changes will need to be updated on the DuVoice system as well.

  • Room status code numbers and their respective function.
  • Room or extension numbering scheme.

Since Opera 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 Opera. Subsequent checkouts from Opera 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 checking from Opera.

  • Last modified: 2024/08/29 15:08
  • by jd