Essential to co-ordinate with local representatives of Micros-Fidelio prior to installation.
-
IFC7.40.XX or higher (for Fidelio DOS version 6.x).
- IFC7w 2.5.3.x (for OPEA V2.5) / IFC7w 2.6.x (for OPEA V2.6) and IFC7w 3.0.x.(for OPEA V3).
- Fidelio product number: Smart Butler 5004-106 SBU FIAS, TCP/IP supported.
- On Fidelio 6 it provides guest's marketing details, while on version 7 or Opera it does not yet.
Interface to
Micros:
The interface provides information to SmartButler® about room service orders entered into MICROS 9700 HMS, which allows SmartButler® to automatically open room service call tickets.
Interface to
OnQ (PMS):
We have an approved interface to OnQ which is TCP/IP based and FIAS compatible. It is essential to co-ordinate with relevant OnQ representatives prior to installation.
Interface to
Cellular phones:
This is our preferred messaging interface due to its ease of implementation and limited up-front costs.
SmartButler® is able to interface with
cellular networks in order to make use of the SMS text messaging capability
for the purpose of:
-
Automatically forwarding to the
required runner or service provider a text message containing details of
guest calls.
- Enabling the runner or service
provider to update a call status on the system remotely by returning a
text message.
- Automatically sending an escalation
text message in the event that guest calls are not adequately taken care
of.
As opposed to other forms of
messaging such as DECT messaging, cellular messaging is JAYBEE’s preferred
messaging interface due to its ease of implementation and limited up-front
costs. Costs are incurred for each message sent to and received from
SmartButler®. Payments for these messages are made to your local cellular
operator.
For more
information please see
Cellular Messaging
Interface to
Dect phones:
May work via TCP/IP or V24 platforms. Interfaces to Tenovis, Alcatel 4400 and Philips PBX and are already available. If any other interface is required, the relevant technical documentation should be provided to JAYBEE by the PBX provider in order to evaluate the possibility of building the interface.
- An appropriate license should be installed by PBX provider to allow text messaging from PBX to handsets.
- All handsets should be capable to receive SMS of length of minimum 90 characters.
- In case PBX provider is Tenovis, a dedicated serial port should be used to connect to Tenovis's Messaging Server.
- In case PBX provider is Alcatel, PBX model should be OMNIPCX or 4400 Enterprise supporting CSTA protocol version 2.
Please note that Alcatel requires the installation of a separate platform and license in order to support the text-messaging interface to SmartButler®. This should be arranged well in advance (2 months) and has a significant additional cost attached to it, the details of which should be determined from your Alcatel representative.
Interface
to Fire Alarm and Control System:
Requires a dedicated serial port to be connected to third provider relay. Relay should support ModBus
standard protocol.
Interface
to PBX:
Requires prior discussion with your PBX provider and receipt of technical information well in advance of installation.
- Preferred interface is based on TCP/IP using XML protocol, or on existing interface used for other 3rd party applications.
- PBX should support the following: (1) Incoming calls: Caller ID, Destination ID, Actual answered extension, call status (Idle/Ring/Answer/Disconnect) and Detect DTMF
Tones (2) Outgoing calls: Call to a specific number, status of
call (Ring/Answered/Busy), Sending voice data.
Other
Interfaces:
To be coordinated on a case-by-case basis with JAYBEE.
Continue to the
Technical Specifications
page.
