Tapi issue 1

[MrIPO]

Having a fault on XP Pro machines running Outlook 2002 setup as standard domain users on a WIN 2K domain

We have had this at a few sites and never found a true resolve

8/10 clients would install correctly eg: TAPI seen Ok in Phone and modems and Outlook sees the driver correcly

2/10 TAPI driver seen in phone ad modems, not seen in outlook

I am thinking it may be some sort of new security update for Outlook 2002 but they seem to be at exactly the same version of both XP being SP1 and Outlook 2002
10.3513.3501 SP1

Has anybody seen this before and knows a resolve

 

[wyi]

I also found this issue in my W2k & outlook 2002, But I only tested 1 PC, sometimes i can not see IPO tapi in outlook, I just remove the driver and readd it in Control Panel. and then outlook again.
I ofen use dialer.exe in Windows to test whether IPO driver installs properly.

 

[5ascent0]

After our 2.0 {16) update none of our XP machines with Outlook 2002 will work. We get an error stating that the dialer could not be opened. Already tried uninstall/install.

 

[nime]

hello!
Try this...

1.Install TAPI as usual from the Avaya Disc
2Once installed, remove the TAPI telephony drivers within Control Panel->Phone and modem->advanced
3.Then copy the contents of the TAPI2 folder off the Avaya Disc to winnt/system ( 3 files )
4. Run the it.exe you have just copied accross once it's in the winnt/system dir... this will produce an error which just needs to be closed.
5.Re-instate the TAPI telephony drivers within
Control Panel->Phone and Modem->advanced->Add
6.Try Outlook or 3rd Party dialer again.

bye

 

[NickBall]

We experience this problem on several machines. I have tried the fix detailed, but still the problem persists.
When you make a call from an outlook contact it throws the internal error in automatic phone dialler.
Anyone any other ideas or suggestions?

 

[weaselthend]

I have the same problem. Any ideas.

 

[thefunz52]

If you go in to control panel, remove the microsoft H323 driver, then restart your machine this should solve all of your problems.

 

[telepaul]

Hello

If you have don a update of the phonemanager it is possible that the “tspi2w.tsp” file in the C:\WINDOWS\system32 is not update. Only in C:\Program Files\Avaya\IP Office\TAPI. If this version is lower then 1.0.0.17 than it is buggy.
You can activate a trace on the tapi on start-up

Tapi Trace on IPO

To start the tapi debug trace file you need to setup the following registry entry.
HKEY_LOCAL_MACHINE\Software\Avaya\IP400\TSPI\DebugFile
This is a string key (REG_SZ) value that specifies the name of the tapi debug file.

For example:

DebugFile REG_SZ c:\tspiTrace.txt

After start-up look for the txt file c:\tspiTrace.txt and maybe you can see of it is correctly logged on to the IPO

Paul