Preparing PBXact for its integration with utile h+ (PBX-PMS middleware)

Versión en Español disponible

Utile h+ is a middleware that aims to integrate IP-PBX platforms with Property Management Systems (PMS). This guide describes the configurations needed on the PBXact server for the integration to be established.

Services that will get implemented

Features supported in PBXact:

• Class of service (calls permissions whether checked-in or checked-out)

• Room Status (room cleaned status ; for hotel cleaning employees to register in the PMS that the room has been cleaned)

• Minibar (minibar IVR for easy ordering)

• Alarm management (wake-up calls)

• Billing (billing for external calls dialed)

Previous Considerations in the PBXact server

1. SAMBA file sharing software must be installed for being able to exchange information between utile h+ and PBXact.

2. Within the configuration of the extensions in PBXact, the variable HABITACION must be defined, with the room number.

3. Trunks for placing external calls must have the parameter "Outbound CallerID" properly set with the DID of that trunk, complying with what the Carrier expects. You may have to set it with the format:
   "Hotel Name" <#######>
   (where: ####### is the Hotel's DID)

4. Each and every hotel room extension must be created with a single same SIP channel driver, either PJSIP (default for utile h+ integration) or CHAN_SIP, for all the rooms.

We'll be configuring points 1 & 2 next.

Integration Scheme

Open

Directories Structure

For the information exchange between PBXact and utile h+ , a directory will be used within the PBXact system, for example, /opt/CHAR . This directory has to be visible from within the Windows computer where utile h+ is installed.

That is why, the SAMBA Server need to be installed:

Once installed, place the following minimum settings in its configuration file ( /etc/samba/smb.conf ):

Once the SAMBA configuration has been set, it is necessary to create the following directory structure inside the  /opt/CHAR path:

• Directory

/opt/CHAR/checking → Directory where the AGI files of each room will be found

• Directory

/opt/CHAR/despertador → Symbolic link to /var/spool/asterisk/outgoing for the Alarm Service

• Directory

/opt/CHAR/tarificacion → Symbolic link to /var/log/asterisk/cdr-csv

• File

/opt/CHAR/codigos.txt → Employees codes so that they can get validated when calling to register the room as clean and also for registering in the log files which employee cleaned the room

NOTE: remember to assign the correct owner and give appropriate permissions, just execute the following:

You will also have to copy the default agi:

Restart the SAMBA service to apply the changes made before on its configuration file:

Enable it to autorun every time the server boot, as well:

The following minimum contexts can be defined within the asterisk file: /etc/asterisk/extensions_custom.conf where we specify certain configuration parameters for the room extensions:

• [habitaciones] → Outgoing Context for room extensions.

• [hab-libre] → Outgoing Context when the room is empty.

• [hab-ocupada] → Outgoing Context when the room is occupied.

• [servicios] → Context where the hotel services are located.

• [extensiones] → Outgoing Context for internal calls from room to room.

• [internacionales] → Outgoing Context for external calls outside the hotel (so that they get billed).

• [roomservice] → Outgoing Context for cleaning service status (so that the cleaning person can register once the room has been cleaned).

• [minibar] → Outgoing Context for calls to minibar service.

• [despertador] → Incoming Context for the wake-up calls.

We'll configure them next, within the following sections:

Checked-in / Checked-out Status

This service is used when a room is occupied (Checked-In) or empty (Checked-Out).

So, it is necessary to control the type of outbound calls to be allowed in each of these states. To do it, in the directory /opt/CHAR/checking the utile h+ application will modify the AGI Script that will select the Context where it should look for the number to call.

All room extensions must belong to the "habitaciones" context and have defined a variable with the Room Number (HABITACION), as follows:

[101]
type=friend
secret=clave
defaultuser=101
canreinvite=no
nat=no
context=habitaciones
setvar=HABITACION=101

As indicated, the last two lines (context and setvar) are the ones allowing the integration of PBXact with utile h+ . For these lines to be properly added to the room extensions, the /etc/asterisk/pjsip.endpoint_custom_post.conf  (or /etc/asterisk/sip_custom_post.conf  if the hotel room extensions rather use the CHAN_SIP channel driver) file should be edited as follows (example):

NOTE: for CHAN_SIP extensions, the correct nomenclature is setvar (and not set_var which is for PJSIP extensions)

And so forth for all hotel room extensions.

The [habitaciones] context, point in asterisk's dialplan from where the room extensions will start at for each placed call, should be as follows (place these lines in the /etc/asterisk/extensions_custom.conf file):

Once configured, room extensions will be able to call hotel services or any number, depending on the result of the executed AGI script executed, as it will set a call with the context [hab-ocupada] or with the context [hab-libre], which may be configured as follows:

• [hab-libre] → It should only allow to place hotel services calls and calls to other room extensions, configured as follows  (place these lines in the 

/etc/asterisk/extensions_custom.conf file):

• [hab-ocupada] → It should allow to make any call, configured as follows  (place these lines in the 

/etc/asterisk/extensions_custom.conf file):

To be able to dial to other rooms and to place external calls, the contexts [extensiones] and [internacionales] have to be added to the /etc/asterisk/extensions_custom.conf file as well respectively:

NOTE 1: ZXX  will allow for the dialing of any extension from 100 to 999 (see DIAL PATTERN INFO), if the hotel room extensions follow rather a different pattern (perhaps four digits numbers), this has to be adjusted accordingly.
NOTE 2: PJSIP/${EXTEN} may need to be changed to SIP/${EXTEN} if the hotel room extensions were rather created using the CHAN_SIP channel driver.

NOTE: AGIs are generated by utile h+ directly.

Room Cleaned Status

This service will be used by the hotel’s employee to indicate if the room is clean or dirty. To do so, utile h+ will read the information from the file “/opt/CHAR/roomservice.log”.

To access the service, it is necessary to add a code in the service context, as follows (place these lines in the /etc/asterisk/extensions_custom.conf file):

With this configuration, we will be able to access the roomservice context, where the service calls will be configured. To configure this, at least 1 audio file is recommended to be generated (see System Recordings Module User Guide):

• room-cleaning-service.gsm → “Room Cleaning Service. Press 0 if the room is clean, or press 1 if it is not clean”.

The file “/opt/CHAR/codigos.txt” will be used to validate the code entered by the employee and be able to log it for the PMS (date, time, employee cleaning which room). The following context can be used (place these lines in the /etc/asterisk/extensions_custom.conf file): 

NOTE: the format for each one of the lines that will get stored in the log to be transferred to the PMS (roomservice.log) is the following:

Room Service Identifier (RS), Date and Hour of the input, Room Number, Room Status (0 - clean, 1 - dirty), Employee Code

Minibar Service

This service is used to indicate the minibar charges. To do it, utile h+ will read the information from the file /opt/CHAR/roomservice.log

To access to the service it is necessary to add a code in the [servicios] context, as follows (place the bold lines in the /etc/asterisk/extensions_custom.conf file under the previous lines already added to the [servicios] context):

[servicios]
exten=>*01,1,NoOP(-- Servicio de Habitaciones --)
exten=>*01,n,Goto(roomservice,s,1)

exten=>*02,1,NoOP(-- Servicio de MiniBAR --)
exten=>*02,n,Goto(minibar,s,1)

With this configuration we will be able to access to the minibar context where its service will be configured. It is recommended to generate at least 7 audio files for it:

• minibar.gsm → "Welcome to the Minibar service"

• intro_cantidad.gsm → "Introduce the quantity"

• intro_articulo,gsm → "Introduce the aritcle code"

• cantidad.gsm → "Quantity introduced…"

• articulo.gsm → "Article introduced…"

• menuarticulo.gsm → "Press 1 to confirm and continue, press 2 to cancel, press 3 to confirm and finish and * to access to the article list."

• listacodigos → "Whenever you want to stop hearing the article list, press a key. The article list is the following: ..."

The following context can be used (place these lines in the /etc/asterisk/extensions_custom.conf file):

Alarm Clock Service (Wake-up calls)

This service is used when the guest ask to be woke up to a certain hour in the morming. It is based in the Call files of Asterisk that it will be generated by utile h+ and saved in the directory /opt/CHAR/despertador . That is not more than a symbolic link with /var/spool/asterisk/outgoing.

The context for the wake up service is the “despertador” context and it can be as follows (place these lines in the /etc/asterisk/extensions_custom.conf file):

NOTE: it may be necessary to modify the template file for generating the wake-up calls according to the SIP channel driver the hotel room extensions were created with (CHAN_SIP or PJSIP). This is done by editing the reminder_template.call file inside the Windows computer running the utile h+ software, specifically located at: C:\CHARWIN\asterisk\hlink\reminder_template.call  Simply change in the first line from PJSIP to SIP if the hotel room extensions use the CHAN_SIP channel driver and not the PJSIP driver:

Channel: PJSIP/%EXTENSION% → Channel: SIP/%EXTENSION%

Allow calls from administrative extensions (Reception and others) to rooms

Add the following lines at the end of the /etc/asterisk/extensions_custom.conf file

Billing

Every external call placed from a room extension is accounted and transferred accordingly to utile h+ which in turn sends the information to the PMS. For this integration, the following has to be included in the /etc/asterisk/cdr.conf file:

The final step is to make sure the Asterisk changes get applied, just execute:

APPENDIX A

Optional bash Scripts for batch automations

Populating the SIP custom_post.conf file

For automatically populating the /etc/asterisk/pjsip.endpoint_custom_post.conf  (or /etc/asterisk/sip_custom_post.conf  if the hotel room extensions rather use the CHAN_SIP channel driver and not PJSIP) file, the optional bash script   could be used:

�