TAPI Driver

Here all TAPI drivers which are registered in the system are listed. With selection of a TAPI driver all accompanying devices are listed below.

Delete: The xtelsio CTI Server stores the names of all TAPI drivers installed one day. If a driver is not visible for the Server, it can be that the driver was uninstalled or is not available only temporarily. If the driver was uninstalled, you can remove it by the Delete button in xtelsio CTI Server too. The button is only enabled if none of the driver's devices is available.


List of the TAPI devices

In the lower list all devices of the current selected TAPI driver are shown.

Possible states of the TAPI devices:
Available The properties of the TAPI device could be queried via the TAPI interface. The does not mean, however, yet that the device can be also opened successfully.
Not Available The properties of the TAPI device could not be queried via the TAPI interface. Then the TAPI driver is not available either or the TAPI driver couldn't establish a connection with its hardware (phone or PBX).
Opened At least one Client has opened this device. Then it should work.
Open Error License problem in the TAPI driver (TAPI for Asterisk or TAPI for Snom)
Open Error Error message after a click on the button [Test Open]. Device could not be opened.
Open OK Successful message after a click on the button [Test Open]. Device could be opened.
Special selection "Non-CTI Lines":

These Devices are probably useless for CTI. This rating is carried out by the xtelsio CTI Server with the help of the driver's name. Some drivers supports only the data communication and are useless in connection with CTI Server. The rating "probably useless" is only a hint, you can still try it of course.

Columns:
  • <Owner>: Number of the Clients who have owner rights on this device. The counters in parenthesis indicates the number of active clients and the number of clients with offline-monitor.
  • <Monitor Clients>: Number of the Clients who have only monitor rights on this device. The counter in parenthesis indicates the number of active clients.
  • <J - Journal>: If checked, this device can log call in main journal. However, logging only takes place if the device has also been opened (either by a tick in the "M - Monitoring" column or by a client). Hint: Click the columns header to set/remove all ticks.
  • <M - Monitor>: If checked, the server keeps the device open permanently. This ensures that the clients can always display the current device state after login. Hint: Click the columns header to set/remove all ticks.

Buttons

Refresh: A click on this button updates the view. All devices are queried once again from the server. If a client has just opened a device, here this is visible only after a Refresh.

Test Open: With click on this button it is tried to open the device in the Server. With success "Open OK" is shown or "Open Error" in the negative case. You can take defailed information about the reason of "Open Error" from the file "server\trace.txt" if the suitable trace option was activated under State.

Device Settings ...: Opens a setting dialog for the selected devices.

Driver Settings ...: Opens a Setting Dialog for the selected TAPI driver. The settings refer to all Lines of the driver.