Tariscope 4.x. Administrator's guide
Chapter 3. Tariscope configuration
3.17. Call export and Hotel systems
If you wish to use Tariscope together with a hotel system or export the call information to another system, select the Call export/Hotel systems configuration page. The Tariscope window will be shown in Figure 3.17.1.
Figure 3.17.1
If the program works without the administrator rights and in Windows the User Account Control (UAC) is enable, Windows displays the UAC is blocking this applet. Restart application elevated link. Click on the link. The program will restart.
Click on the Configure link. The Tariscope window willbe as shown in Figure 3.17.2.
Figure 3.17.2
In the Tariscope connection section, specify a name of computer where the Tariscope server service works and if necessary, enter a user name which the rights will be used to connect. If necessary, change these settings by clicking the Change Tariscope connection options link.
In the External system connection type list, select a 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 connects to a hotel system through serial port.
- SSH Client. Tariscope connects to a hotel system using SSH protocol.
- TCP/IP Client. Tariscope connects to TCP/IP server of a hotel system.
- TCP/IP Server. Tariscope works as TCP/IP server, to which a hotel stystem connects using TCP/IP client.
- Asterisk AMI. Tariscope uses the Asterisk Manager Interface to interect with Asterick.
Click on the Configure link. As a result, the Data source configuration window appears where you should specify the connection data. The configuration of any type of connection is the same as described in section for the Tariscope Observer configuration.
If you need the Call export service connects to a hotel system at once on the service start, select the Open external system connection on start check box. By default the check box is selected. If the check box is not selected, 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-reference2.vb,
- hotel-uni.vb,
- print.vb,
- savefile.vb.
These scripts are located in the folder: ...\Prgogram Files (x86)\SoftPI\Tariscope4\CallExport
The first two scripts are similar and they are 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 (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.
If these are no scripts that suit for your hotel system, you can develop the script yourself or, please, contact the technical support of SoftPI.
Before starting the service you can 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 located in the folder: ...\ProgramData\Tariscope and has a name: callexport.log
To save settings, click on the Save icon on the toolbar.
To install the service, click on the Install service link. The Service status position is displayed "Stopped" in the case of a normal installation. The Install service link is replaced to the Uninstall service link and the Start service link is active.
To start the service, click on the Start service link. The Service status position is displayed "Running". The Start service link is replaced to the Stop service link. The Uninstall service link is inactive.
After the service start we recommend to click on the Service log link or select on the same branch in the configuration tree and make sure there are no errors. If the log contains errors, stop the service, return to the configuration and validate the configuration data. After that, start the service.
To stop the service, click on the Stop service link. The Stop service link will be replaced to the Start service link and the Uninstall service link is active. The Service status position will be displayed: "Stopped".
