Jump to content
Vodia PBX forum
msp_netsec

Windows 10 x64 TAPI

Recommended Posts

Hi All,

I've followed the instructions for the TAPI Provider but can't have any luck even making a call with dialer.exe.   Looking at the log on the PBX (Tried on versions 57.0, 57.4 and 58.3) I don't see anything populate in the logs on the PBX side and even after enabling logging on the Vodia TAPI Provider in the registry nothing is logged on this end either.  

Is anyone else using Windows 10 x64 and have any luck with the TAPI provider?  I require the TAPI provider for a CRM integration (Sage CRM), would love to know if this is something Vodia can confirm is working with windows 10 x64 and if not do you intend to have it working anytime soon?

Thanks in advance,

Jason

Share this post


Link to post
Share on other sites

The Vodia TSP is translating TAPI into CSTA. That means you would need to see CSTA traffic on the PBX (which also requires the appropriate license). The TSP is already a little bit rusty (as TAPI is IMHO) and supports only TLS 1.0. Maybe that could be a problem in Windows 10, where maybe the local firewall might block the traffic. Anyway, I would try to set the log level for the TSP and see if there is anything in the log and/or run WIreshark on the PBX host filtered by the Windows PC IP address to see if there are any signs of live.

Share this post


Link to post
Share on other sites

Thanks for the response, seems I was 3rd time lucky when using my 3rd windows 10 x64 workstation I can successfully dial using dialer.exe now. Not sure why the other 2 machines would be failing but I can move on for now.  Can you tell me does the vodia TSP have functionality for inbound calls or only making outgoing calls?  I've tried it with a test application and outbound seems OK but it's not identifying any inbound - versus say when I try with 3cx TSP it tests find both ways.

Cheers,
Jason

Share this post


Link to post
Share on other sites

In theory inbound calls should also work. However it heavily depends what you are using on top of TAPI. Outlook is a very complex program, and Lync/OCS/Team tends to heavily interfere with it (there is something about this in https://vodia.com/doc/tsp). IMHO if we are talking about a new installation I would steer away from TAPI and try to use HTTP-based methods (glorified click to dial).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×