TAPI Application not showing incoming calls till is restarted

[nLeo]

Howdie all!
Keep getting reports from operators using a third party app connected to IP Office using TAPI2.
Suddenly calls are ceasing to show on the application till is restarted.
I have been reading around and it might be related to Win10... but I suspect it is not just the case.
Windows Event Viewer (System) shows several 'DistributedCOM' (id 10016).
Service Control Manager where 'the Telephony Service terminated unexpectedly.

Did any one experienced similar issue?

Have a great day everyone
Leo

 

[janni78]

We use TAPI on almost all installations in some form and haven't had such issue in a while. (you haven't said which version you're on)

What you need to consider is that if the IPO is rebooted the TAPI application needs to make sure that it reinitializes the TAPI connection again.
On later IPO version TAPI is blocked for 3 minutes after restart.

"Trying is the first step to failure..." - Homer

 

[intrigrant]

Update the AVAY TAPI TSP to the latest version and try again.

 

[nLeo]

Thanks Guys,
tried user 4_2_6, 4_2_64 and 4_2_88
getting the same

 

[nLeo]

I wonder if the thread 1753146 could be related in any ways?

 

[janni78]

Better to link to the thread =) ([URL unfurl="true"]http://www.tek-tips.com/viewthread.cfm?qid=1753146[/url])

I don't have any issues with TAPI on Windows 10 at least, although I only use it when testing my own apps, customers are usually running it on W2012.

"Trying is the first step to failure..." - Homer

 

[nLeo]

not sure if related though..,
Just so you know... it happens randomly
I can see errors in the Event Viewer / System

 

[intrigrant]

I know in early releasers of Windows 10 it was a general complaint (also by Cisco TAPI users) that incoming calls did not show up in TAPI.
I have had that myself but somewhere in time Windows 10 updated and I updated the AVAYA TAPI in Win 10 which made the problem disappear.

 

[nLeo]

What are you running Intrigrant? User 4_2_88 ?

 

[intrigrant]

4_2_64 64bit

 

[nLeo]

there must be something else...

 

[janni78]

You kinda asking us to guess here =)

There should be an error in the application log and Monitor trace when this happens.

"Trying is the first step to failure..." - Homer

 

[nLeo]

Janni
I have updated W10 to 1703
TAPI 4.2.88
got rid of lots of DCOMM errors in event viewer
Isolated the TAPIsrv

From last night.. on the test station
No reports.. fingers crossed?

 

[janni78]

Just as a notice you might need to uninstall TAPI before installing the latest.
There should be a new Timeout setting in the new TAPI driver that wasn't available before, if that isn't available then it isn't installed correctly.

I recently had to do this when I upgraded one of my customers since the old TAPI driver didn't support more than 1500 users =)

"Trying is the first step to failure..." - Homer

 

[nLeo]

Interesting Janni.. I always uninstall first but where is it?

By the way: Event Viewer / Srvice control manager
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. (7032)
and before
The Telephony service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.(7031)

 

[nLeo]

Damn it keeps doing it..
Win10Pro32 ..4.2.88
what else should I do?
Can't get my head around it...
Back to win7 ?

 

[nLeo]

sorry win10pro64

 

[nLeo]

Hello... hope some of you are still subscribed to this thread.
I'd like to get some TAPI logs.
Went to look for HKEY_LOCAL_MACHINE --> SOFTWARE --> AVAYA --> IP400 --> TSPI
but found it under Sopftware / wow6432node / avaya / ip400 / tspi
as per instructions, I set a new string and file...
but doesn't seem to be writing anything (did restart).
Any ideas?

Leo