Trouble with Tapi Driver

[anthonymo]

We use the Avaya Tapi driver to dial our 5610's thru windows XP.
It has always worked great until this weekend one machine developed an issue.

If you start dialer.exe it can place calls without issues, however when you try and close it remains in the system tray and the process must be killed. If the program is launched again it losses the ability to make calls and the system has to be rebooted before it will work again.

I have uninstalled/re-installed the latest Tapi driver but the problem persists.

My windows XP laptop shows no such problem.

Nothing new was installed or changed on the computer.

I'm not sure if this is a problem with Tapi drivers or telephony components.

Any ideas other then a re-install?

 

[amriddle01]

Sure sounds like a pc specific issue, nothing to do with the TAPI driver or system

 

[tlpeter]

Indeed, the TAPI driver did not change.
And the "nothing changed" is something i have heard a thousand times and i think 999 times of it there changed something.


BAZINGA!

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

 

[intrigrant]

perform a windows restore from a dat it was working and see if that helps.

If it ain't dutch it ain't much

 

[anthonymo]

tlpeter:
That computer is part of a domain, users do not have admin access, so the likely hood of something changing is somewhat reduced.

Intrigrant:
The problems were reported starting the 12th so I performed a windows restore back to the 11th, no change except the service "Remote access Connection Manager" that I had disabled was set back to manual... this hangs and causes Telephony not to start.

I'm starting to think a full re-install is my best bet as I am not able to find help thru Google.

 

[tlpeter]

I did not say it is a user error.
I know enough examples where the ICT department where messing things up while nothing changed.
I remember a complete DC replacement being done and still nothing changed


BAZINGA!

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

 

[Edata]

My thinking is were did you get the drives from. the correct drives will come for either the def connect site or from the One_X app. it might have work before with the wrong drivers.

 

[anthonymo]

Thanks for all the assistance, at this point I'm just going to reinstall windows (after running sfc)