Page Comparison

<div id="fb-root"></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

...

Introduction and requirements

...

Supported Oracle and FIAS versions:

• Oracle Hospitality OPERA Version: 5.0.05.00
• Oracle Hospitality Interface IFC8 Version: 8.10.2.20
• FIAS Version: 2.20.12

...

• Go to WMS Settings -> PBX -> Hotel Integration
• FIAS PMS Integration -> click Install
  
  

• After installtioninstallation, there appear three new tabs: Rooms / FIAS-PMS / PBX Services:
  
  

Step 2. Auto generate rooms

...

1. FIAS RN – room number identificator used in commands from FIAS interface

2. Extension – internal extension number inside the PBX, shown on the phone

3. Description / Building / Floor / Category – room description, location and category for hotel staff

4. ID – identificator used by XOpen interface (described in the next chapter)

• Click Apply to save and confirm changes

...

• PMS Status – status of connection to Fidelio software
• Host – address for connection to software
• Port – port for connection to software
• Delimiter – delimiter used inside commands from FIAS interface
• Billing Type – billing type used: Duration Only / Duration and cost (see the chapter Call Billing)
• Minibar Type – minibar charging by Cost only / Article only (see the chapter Minibar Charges)

Step 4. Wake up service settings (optional)

Go to tab PBX Services and enter the following parameters:

Parameters:

• Timeout – period of time during which the wake up call must be answered (in seconds)
• Number of tries – number of repetitive calls in case wake up call was not answered
• Sound – audio file to be played to the guest who answered a wake up call

(See the chapter Wake Up Call for more information).

Step 5. Restart WHotel daemon

• Go to General tab 
• "Service" option -> click Restart

XOpen SW for integration with Bticino / Legrand

...

HW 

Anchor
xopensw xopensw

For processing of key / badge programming and sync of events from Bticino/Legrand terminals, such as DND / MuR statuses, it is necessary to enable XOpen integration.

Step 1. Enable xOpen integration

Go to General tab -> xOpen integration, click Enable.

In Hotel Integration menu there appear additional tabs which serve to enable connection to Legrand software by XOpen protocol:

• Common Areas
• Workstations
• Xopen

Step 2. Enable connection to the software

Go to Xopen tab and enter the related data:

Configuration parameters:

• Status – the status of the connection to Hotel Supervision Server
• Host –  address for connection to software
• Port – a port for connection to software
• FC – function code as parameter for Hotel Supervision Client
• UC – univocal code as parameter for Hotel Supervision Client
• Secret – the secret for authorization with Hotel Supervision Server
• Badges control – enable/disable badges processing

Step 3. Upload XOpen project file

• Go to Rooms tab
• Click Choose file to load a config file from Hotel Supervision software (file with extension *.hsprj) with actual information about device identifier
  
  

• Common areas data (Common Areas tab) can be loaded from described above config from Hotel Supervision software:
  
  

Step 3. Set up the mapping between PMS key generators and XOpen key generators

• Go to Workstations tab
• Add workstation instance (like Hotel Supervision GUI) with following data:

1. 1. FIAS WS – an identifier on the FIAS side

   2. Client UC – an identifier on the XOpen side (retrieved from HS Client)

   3. Client IP – an IP address of the workstation PC:

Step 4. Extend configuration for Fidelio software by data for key service client (FIAS PMS Automation interface)

Go to FIAS-PMS tab.

There appears an additional section Automation interface.

Now it is possible to set up two FIAS-PMS interfaces:

• Telephony interface (PBX)
• Automation interface (DLS – door-lock system)
  
  

Step 5. Restart WHotel daemon

• Go to General tab 
• "Service" option -> click Restart

Hotel ACLs (CoS) and call barring for vacant room

There are two types of ACL in the Wildix Hotel Integration:

• Standard PBX ACL settings
• ACL (CoS – Class of Service) from FIAS (PMS) interface (they have the effect only for outgoing external calls)

They are processed in the following way:

• Room state “vacant”: standard PBX ACLs are applied
• Room state “occupied”: calls are processed based on ALCs set up on PMS side. Emergency call class is managed by Wildix PBX ACL

To realize the scenario of call barring for vacant room, it is necessary to restrict possibility to call externally for the ACL group to which rooms belong: when the room is in “occupied” state, CoS from PMS are applied, when the room is in “vacant” state, the possibility to call externally is disabled.

It is recommended to create a separate ACL group "WHotel" in  in WMS -> Users -> Groups, with default permissions set up as such:

You can add additional restrictions to manage call barring for room in status “vacant”, for example, add such rules:

• “Cannot call” -> “All”
• “Can call” call” -> “Internal”

In this case it will be possible to make only internal calls from room with status “vacant”.

After you have created a dedicated ACL group for managing rooms permissions, go to Users page and assign this ACL group to all the rooms:

It is possible to skip CoS (Hotel ACLs) via authentication, which can be useful to allow some authorized hotel staff to make calls from the rooms which are vacant. Read the next chapter for more info.

To disable ACL checking on the PMS side and always use standard PBX ACL: set up Global Dialplan variable (WMS Dialplan -> General Settings): CHECKFIASACL = no.

Depending on the CoS, the PBX can correctly process external calls.

In PMS room can be assigned to one of the following CoS:

• Barred/hotel internal only
• Local
• National
• No restrictions

While in PBX there are many call classes; in the table below it is explained how they are related:

In a normal scenario, rooms follow the procedure “users” or some other dedicated Dialplan procedure (indicated in WMS -> Users, Dialplan). Usually in this Dialplan procedure “Trunk group” or “Dial the trunk” application is used for processing external calls. Note than in both applications, call class is detected by the system automatically, however, it is possible to set up the call class manually.

Take into consideration, that you can set up caller ID name to some static value, otherwise real guest’s name is displayed while making a call through trunk. Example:

Skip call barring via

...

authentication 

Anchor
skipbarring skipbarring

In this chapter it is explained how to skip hotel ACL (CoS) in case call barring is enabled for the room which is in status “vacant”. This scenario can be useful to allow authorized hotel staff to place calls from vacant rooms after successful authentication.

As explained in the previous chapter, it is possible to skip hotel ACL check by adding the Global Dialplan Variable: CHECKFIASACL = no.

In our example we will see how to skip hotel ACL just for one call:

In this example an authorized staff, suppose, a housekeeper, can call any destination by:

• Calling an extension 55 <housekeeper account> <destination number>
• Enter the password for housekeeper account

Call will be processed without checking hotel ACL for current room and without billing.

...

Events must be sent from PBX via Feature codes on the phone by hotel staff (see the chapter Hotel Feature Codes).

MuR statuses:

• Dirty / Vacant
• Dirty / Occupied
• Clean / Vacant
• Clean / Occupied

...

Minibar charges must be sent via feature codes on the phone by hotel staff (see the chapter Hotel Feature Codes).

Minibar charges information can be sent with different mapping:

...

On PBX side: wake up call can be set up by guest via feature code on the phone (see the chapter Hotel Feature Codes).

...

Some custom configuration parameters can be changed in the file /etc/wildix/whoteld_manager_custom.conf. 

Information about these parameters is available in Custom config parameters List.

...