Tariscope 4.5.x. Administrator's guide
Chapter 4 Tariscope configuration
4.15. Call export and Hotel systems
Tariscope can provide information about guests' calls to the hotel system. If you wish to use Tariscope together with a hotel system or export the call information to another system, in the Tariscope menu, select Additional options → Integrations → Hotel systems. The Hotel systems page appears as shown in Figure 4.15.1.
Figure 4.15.1
Click on the Open settings button. The Hotel systems page will be as shown in Figure 4.15.2.
Figure 4.15.2
In the External system connection type list, select the desired option. There are the following options of the connection:
- Rlogin client. Information from Tariscope is sent to an external system using Rlogin client.
- Serial port. Tariscope is connected to the hotel system through a serial port.
- SSH client. Tariscope is connected to the hotel system using SSH protocol.
- TCP/IP client. Tariscope is connected to TCP/IP server of the hotel system.
- TCP/IP server. Tariscope works as TCP/IP server, to which the hotel system is connected using TCP/IP client.
- Asterisk AMI. Tariscope uses the Asterisk Manager Interface to interact with Asterisk.
Click on the Configure button to setup the connection parameters. The Settings window appears which is specific for each connection type.
The configuration of any type of connection is the same as described in section for the Tariscope Observer configuration. Execute settings in the window and click Save.
If you need the Call export service is connected to the hotel system at once on the service start, turn on the Open external system connection on start switch. By default, the switch is on. If the switch is off, the time of connection will be defined with the script.
Tariscope can interact with any hotel system if you know the interaction protocol with the system. The implementation of this protocol is executed in the script, written in the language of VB Script or C# (Microsoft). Tariscope contains several predefined scripts:
- hotel-uni-reference5.vb,
- print.vb,
- savefile.vb.
These scripts are located in the folder: ...\Program Files (x86)\SoftPI\Tariscope\CallExport\CallExport
The hotel-uni-reference5.vb script is intended to interact with a hotel system using UNI interface. This interface can be used to interaction with the following hotel systems: Opera, Fidelio v.8 (Oracle, Micros), epitome PMS (Libra Hospitality) and others.
The print.vb script allows to print calls information on a local or remote printer.
The savefile.vb script saves calls data in a file.
Select the desired script in the Export script list. If you want to change the selected script, click on the Edit button. The Edit window appears. Change the script and close the window.
If these are no scripts that suit for your hotel system, you can develop the script yourself or contact the technical support of SoftPI.
Select one of the following levels of logging of the service, where every next option increases the level of details:
- Status.
- Critical error.
- Error.
- Warning.
- Information.
- Advice.
- Debug.
The log is needed to identify the causes of malfunction of the Call export service. If you using the log have not identified the cause of incorrect operation of the service and resolve this problem, send the log to the technical support service of SoftPI. The log file is in the folder: ...\ProgramData\Tariscope and has a name: callexport.log
To save settings, click on the Save icon on the toolbar.
Return on the Hotel systems page shown in Figure 4.15.1.
To install the service, click on the Install service button. In the Service status position the value of "Stopped" is displayed. The Install service button is replaced to the Uninstall service button and the Run service button is active.
To start the service, click on the Run service button. In the Service status position the value of "Running" is displayed. The Run service button is replaced to the Stop service button. The Uninstall service button is inactive.
After the service was started, we recommend clicking on the Open service log button or select the Service log item of the menu and make sure there are no errors. If the log contains errors, stop the service, return to the settings, and validate the settings and script. After that, try to start the service.
To stop the service, click on the Stop service button. The Stop service button is replaced to the Run service button, and the Uninstall service button is active. The Service status position displays "Stopped".
To uninstall the service, click on the Uninstall service button.
