TAPI no longer working

[rgelb]

I tried asking this before in this forum, but I dropped the ball, so here it goes.

I am wrote an app for a company to run their business. I noticed that they had a ShoreTel system, so I hooked into TAPI and allowed to dial from their application. Everything was good.

Then their phone guy came over and upgraded the system and TAPI no longer works. I mean I see it in Control Panel/Phone and Modems Options/Advanced, but the lines can no longer be initiated.

The Main Server Maintanance page states that the version is 12.16.2700.0.
The About screen for the ShoreTel Call Manager on the client states the following versions:

ShoreTel 7.5
ShoreTel Advanced Call Manager Build 12.16.2700.0

Per a suggestion, I downloaded Exceletel TeleScope (among a ton of other utilities) to see what's going on.

When I try to activate the phone line (via Tapi), I get the following error:

Hex = 90000013
Number = -1879048173
Text = PHONEERR_INVALPHONEHANDLE

When I try to configure the line, I get this error:

Hex = 80000049
Number = -2147483575
Text = Unknown

This problem is present on every workstation in the building (quite a few).

Could someone provide some guidance on what is the issue and how to fix it?

Thanks

[400degreez]

What Os is your client using?

[rgelb]

My clients are all on Windows XP Service Pack 3 (with all the latest patches).

[rgelb]

Anyone? Anything?

[Palitto Consulting]

Problems like this usually need hands-on work to locate the source unless it is a very common problem. When he upgraded ShoreTel, did he also upgrade the Call Managers as well? Do they work properly? Did you try uninstalling and reinstalling Call Manager yet?

[rgelb]

CallManager works properly and, yes, it was upgraded. And I've tried reinstalling CallManager, all to no avail.

How would I go about locating the source of the problem?

[crimson.falconer]

I'll take a stab at it.

What language is the application in?

Can we see a snippet of the code that is failing.

You would get that error if the hPhone was incorrect in your code...It also might be permissions check TAPIMGMT.msc

[rgelb]

@crimson

The application is written in VB6 (or English if that is what you were asking).

I access TAPI through a 3rd party component from Kaed (KDTele Tools - Introduction). I've used this control on multiple other jobs and can vouch for how solid it is. The app fails on the line of code where I attempt to Activate the line. It comes back with an error "Could not setup the device". Don't know

I get similar errors with other generic TAPI client apps.

I am not sure how and where to check the permissions. On the client I installed TAPIMGMT.msc and got the following screenshot:



The extension I highlighted is the one connected to my instance of the Call Manager. I am not sure where to check the permissions.

Or did you mean, do this on the server?

Thanks for the advice.