IPO v9 fix TAPI in Windows 8? 3

[nmessick]

anyone know? current version does not pickup any inbound events.

 

[tlpeter]

Funny, i have seen no inbound call with TAPI on Windows 8.
I do not know why and i changed out the PC with a Windows 7 PC.
If you know the answer then i want to know too

BAZINGA!

I'm not insane, my mother had me tested!

 

[nmessick]

looks like no changes. the user pack is the same as v8.

windows 8 gets no inbound TAPI events. Apparently MS changed some of the underlying handlers and everyone has to update their code. Who knows how long avaya will take.

 

[intrigrant]

Here are the latest tsp files, this should solve the win 8 problem
64bitTSP
32bitTSP

 

[Bas1234]

In TAPI 1.0.0.38 the Windows 8 problem should be solved.

On the Avaya system, prior to accepting an inbound call, you could enable tracing for 'tapisrv' by executing
the following in a command window:

"netsh ras set tracing tapisrv enable"

Then try your inbound call.

The trace log will be located in %SystemRoot%\tracing\tapisrv.LOG.
When operating correctly (within the context of XP/Windows 7),
the following line entries would be recorded.

NOTE: The two LineEventProcSP' entries are the two LINEEVENT messages
that TSP generates to TAPI ( a.) LINE_NEWCALL and (b.) LINE_CALLSTATE)

when handling an inbound call.

[4984] 15:46:18:464: [INFO ] LineEventProcSP: HTapiLine=0000000000010300, HTapiCall=0000000000000000, msg=1f4, P1=x5f48790, P2=x5f487b0, P3=x0
[4984] 15:46:18:464: [TRACE] LineEventProc
[4984] 15:46:18:464: [TRACE] CreatetCall: enter, ptLine=0000000005025B30
[4984] 15:46:18:464: [INFO ] CreatetCall: calling NewObject ptCall 0000000005025C50
[4984] 15:46:18:464: [TRACE] CreatetCall: NewObject returned 0x101ee
[4984] 15:46:18:464: [TRACE] CreatetCall: exit, new ptCall=0000000005025C50
[4984] 15:46:18:464: [INFO ] LineEventProcSP: HTapiLine=0000000000010300, HTapiCall=00000000000101EE, msg=2, P1=x2, P2=x1, P3=x0

When not working on Windows 8, a trace looks like:

[3344] 15:37:25:615: [INFO ] LineEventProcSP: HTapiLine=00000000000103BB, HTapiCall=0000000000000000, msg=1f4, P1=x187b06c0, P2=x187b06e0, P3=x0
[3344] 15:37:25:615: [TRACE] LineEventProc
[3344] 15:37:25:615: [TRACE] CreatetCall: enter, ptLine=000000EA18125250
[3344] 15:37:25:615: [INFO ] CreatetCall: calling NewObject ptCall 000000EA18125370
[3344] 15:37:25:615: [TRACE] CreatetCall: NewObject returned 0x10322
[3344] 15:37:25:615: [TRACE] CreatetCall: exit, new ptCall=000000EA18125370
[3344] 15:37:25:662: [TRACE] DestroytCall: enter, ptCall=x000000EA18125370


The tapisrv is killing the call immediately after creation.


Also note that when finished testing, you need to turn tracing off by executing the following in a command window:

"netsh ras set tracing tapisrv disable"

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[intrigrant]

I posted the 1.0.0.38 version

Here more details the post from BAS1234

 

[tlpeter]

Star for both.
I have seen it and it was frustrating as i was at the other side of the country.
In the end i replaced the PC for a windows 7 PC.
The tapi driver caused disconnected RDP and teamviewer sessions where a 3rd party service using tapi was rebooted.


BAZINGA!

I'm not insane, my mother had me tested!

 

[chda]

Has anyone tried Win 8.1?

 

[intrigrant]

@chda it is up to you to test and let us know...

 

[nmessick]

8.1 still has the same problems. TAPI 1.0.0.38 is in the user CD for 8.1SP5 and did not fix it for me.

What do you do with the TSP files? Just overwrite the ones on the PC?

 

[kotles]

thanks intrigrant! I replaced yours file in system32 folder and everythink is OK!! uffff!!