Martin
2006-12-19 14:58:32 UTC
We are using a Windows 2000 sp4 server, which is a dedicated TAPI server.
This server is connected via Panasonic TSP USB to our Panasonic KX-TDA-30.
We shared the lines and registered these on the client with tcmsetup /c
tapiserver. In our client application, written in VB .NET 2.0, we use the
ExceleTel Teletools 3.7 component for our tapicommunication.
It is all working well, but at some moment the telephony service on the
service decides to terminate. The following event occurs:
The Telephony service terminated unexpectedly. It has done this 1 time(s).
The following corrective action will be taken in 60000 milliseconds: Restart
the service.
And after 1 minute:
The Service Control Manager tried to take a corrective action (Restart the
service) after the unexpected termination of the Telephony service, but this
action failed with the following error: An instance of the service is
already running.
The clients completely lose tapi connection and after restarting the server
and the client applications everything is working again.
We absolutely have no clue what could cause this behaviour, and hopefully
you can help us with that.
This server is connected via Panasonic TSP USB to our Panasonic KX-TDA-30.
We shared the lines and registered these on the client with tcmsetup /c
tapiserver. In our client application, written in VB .NET 2.0, we use the
ExceleTel Teletools 3.7 component for our tapicommunication.
It is all working well, but at some moment the telephony service on the
service decides to terminate. The following event occurs:
The Telephony service terminated unexpectedly. It has done this 1 time(s).
The following corrective action will be taken in 60000 milliseconds: Restart
the service.
And after 1 minute:
The Service Control Manager tried to take a corrective action (Restart the
service) after the unexpected termination of the Telephony service, but this
action failed with the following error: An instance of the service is
already running.
The clients completely lose tapi connection and after restarting the server
and the client applications everything is working again.
We absolutely have no clue what could cause this behaviour, and hopefully
you can help us with that.