TAPI driver

[mikeduncan]

Hi,

We have just installed our IP office system and are very pleased with it overall. One major problem we are having however, is with installing the TAPI driver. The TAPI function was part of the reason for our purchase of the IP Office.

We run Windows 2000/XP pc's in a 2000 AD domain environment, and a mixture of Outlook 2000 and 2003.

I have tried installing the driver on 2000 and XP with both outlook 2000 and 2003, and cannot get it to appear as an option under 'Dialing Properties' when running the dialer applet in Outlook. However it does show up in 'Phone and Modem' options in control panel.

I have tried all of the fixes explained in previous threads in this forum, such as manually installing from Phone and Modem options, but it still does not show when using a TAPI capable application (outlook, phone dialer, etc).

Any help would be appreciated.

 

[IPGuru]

can you get microsoft Phone Dailer to talk to the tapi driver?
this is the simplest way to confirm that tapi is correctly configured.

 

[mikeduncan]

Yes tried phone dialer also on all configs. Also tried this afternoon with a win2k PC and outlook 2000 that was not a member of our domain (standalone) as i have read some stuff about domain issues with the TAPI driver, but once again, no luck.

Is anyone else in the same boat, surely it cant just be me?

 

[raknas]

Try testing using a Win 98 machine,I had this once before with W2K but work fine win98, Luckily the site upgraded all OS to Xp and they work fine. Is all your service packs up to date with W2K?

 

[mikeduncan]

It doesn't work with Windows XP or Windows 2000, using either Office 2000 or 2003. Tried with a fresh build of 2k, then xp, then with them added to the domain, service packs etc. No luck.

Looks like my only option is to get very nasty with Avaya here in Australia. Basically their TAPI driver is an absolute mess, and the product should not be sold in its current state claiming to support dialing through TAPI.

 

[daffymd]

I spent many weeks trying to get IP Office TAPI to work on an XP machine and experiencing the same problems as you until I went to site, upgraded the unit to 1.4(25) and used the version of TAPI on the 1.4 CD.

I was told by our distributor to select the required user as I stepped through the installation which I did and it worked perfectly.

I also have TAPI running on Windows 2000 Professional Service Pack 3 with Outlook 2000 in the office without any problems.

 

[mikeduncan]

Finally a solution!

The steps that seem to work for all of our PC's are:

1. Install IP Office user suite, choosing 'Phone Manager', and 'TAPI' options only.
2. Reboot after install as requested for correct TAPI install.
3. Remove the IP office user suite from within 'Add Remove Programs'.
4. Reboot as requested to allow successful removal of TAPI.
5. Reinstall the IP office user suite choosing 'Phone Manager' and 'TAPI' options.
6. Reboot after install as requested for correct TAPI install.
7. Configure the 'Avaya IP Office TAPI2 Service Provider' from within 'Phone and Modem Options' in control panel, entering user information EXACTLY is it appears in the Manager application when configuring the IP office control unit.
8. Open Microsoft Phone Dialer (Start, Run, type dialer), in phone dialer go to 'Edit' menu, choose 'Options', check that you can see the "IP Office Phone: XXX" as an option in "Line used for Phone Calls" dropdown. If so, choose this option and test dialing.
9. Close dialer, Open Outlook, and configure dialing properties to use 'IP Office Phone:XXX' If it does not appear here, try uninstalling IP Office User suite and reinstall/reconfigure again.
10. Drink beer

This procedure has worked for these combinations so far:

Win2k - Outlook 2000
WinXP - Outlook 2000
WinXP - Outlook 2003 (Yes! Office 2003!)

 

[kflounders]

Another thing to try is to remove the TAPI driver from your Phone/Modem options under Control Panel then add them again. It works sometimes.

 

[IPGuru]

& make sure that when installing you have local admin rights!

 

[spridge]

Glad to see you have it working

I recently installed the Phone Manger Pro / TAPI application on 30+ Windows XP Pro PC's

Only problem was IP Office:Extn No not displayed as option in Line to use pull down option.

I simply selected the H323 option .

Then by closing options box and reopening and reselecting the line option the IP office extn option suddenly appeared.

 

[weaselthend]

I've tried all the suggestions here. Went though all of mikeduncan's steps several times. Here is what I have happening.

When I get to the configuration in the Phone Dialer, I don't have an option for IP Office under lines, only the h323. I tried that and it doesn't work. I also tried to select that and go back as spridge's stated, but it doesn't change anything.

Whenever I try and make a call from Outlook, or if I try to configure the lines, I get an error message asking me to close and reopen the dialer.

Can anyone help on this. I would really like to use the TAPI feature to make calls.

I've tried this on two diffent workstations. Configuration is Win2000 SP3, Office 2000 SP3.

Thanks in advance.

 

[mikeduncan]

Weaselthend,

The only thing I can think of is to check and double check the configuration of the Avaya TAPI driver under 'phone and modem options'. Make sure you have the username entered exactly as you have configured it on the IP Office control unit (using the manager application), and password respectively. Remember the configuration of the TAPI driver requires 'user' details and not 'extn' details.

If these details are not entered correctly, you will not see the 'IP Office Phone:xxxx' as an available line in any TAPI compliant applications.

Also, another quite confusing thing I found with earlier versions of outlook, is that they will only display two drivers in the "Connect using line" dropdown box under dialing properties, and you actually have to scroll down to see the 'IP Office Phone' option.

Hope this helps. Please keep posting if you still have issues, it would be good to have all of these issues sorted out in a single thread so that it can be of help to any new IP Office users.

 

[telepaul]

Hi,

We had also problems with tapi and fond out that there are problems indeed in tapi version 1.0.0.14 /-15 /-16. we changed the tapi to 1.0.0.17 and had no longer problems. One of the problems ware tapi logon problems to the IP Office, and svchost at 100% of the memory on the PC w2k/xp.

When uninstalling the software you also have to look for tspi2w.tsp on the PC's because this file is stored at more place as one. The file tspi2w.tsp in C:\WINDOWS\SYSTEM32 is not deleted and has to be manually deleted
If you ask the properties on the file tspi2w.tsp, you can see the version of the tapi.

You can run a tapilog to check the logon and actions.
Path = HKEY_LOCAL_MACHINE / SOFTWARE / AVAYA / IP400 / TSPI
key = debugfile REG_SZ C:\tapilog.txt

After rebooting your PC you can look in to the log and verify the tapi logon to the IP Office at this path "C:\tapilog.txt".


Success

Paul

 

[rickoshe]

I run a small business and we have an Avaya IP 401.
Dialing through outlook is my goal!

On my laptop - but not the other connected computers I have this problem where we have to keep reinstalling the TAPI s to get outlook to give the ip extension as an option.

Then after reinstalling - it will work for a max of 1 week and then again outlook will start dialing through the ordinary laptop modem, making it necessary to again reinstall the TAPI's.

In simple terms ( I am a novice ) can anyone describe the steps I must take ?

PS I agree with Mike - Avaya should not be selling this and are hopeless at assisting !

Rick

 

[cannonf00]

I have been having a similar problems as Rickoshe and Weaselthend. Both Windows 2000 and XP with Outlook 2000 forget about the IP Office extension. This happens over a period of 1 restart to 1 week. We are using the Avaya 3.0.16 release of phone manager and the bundled TAPI driver.

On the rare occasion that reinstalling tapi or switching to h323 does bring the line back, we get an outlook error message saying (paraphrase) "outlook cannot dial the number, please close and re-open the automatic phone dialer"

The Avaya IP Office TAPI 2 driver is still in the modem and telephony options in the windows control panel and the tapi settings are never changed from when it works and doesn't work.

A phone call to our Avaya distributor (first step towards Avaya support) was no help, the tech only had reloading the driver to suggest which did not resolve the IP Office line being unavailable.

 

[weaselthend]

FYI. I'm still having the same problem. Doesn't work.

 

[Belrick]

In the confusiong some people may have missed the fix. Changes to the tapi driver only take affect after the service is restarted. The simplest way to do this is to make the changes, remove the Tapi driver then click the add button and reselect the tapi driver from the list.

Also note that the avaya tapi driver can conflict with pre-existing tapi drivers. Remove all Tapi drivers that you are allowed to remove.

 

[ITfromZX81]

Hi guys,

I'm having problems with the driver as well.

We are running IPO 3.0(40). We are running Windows 2003 Server and most users are running under terminal services.

At some point when I was testing I got the TAPI driver to work for me(but just me), but I couldn't get it to work for anyone else. Now I can't get it to work at all.

Does anyone know if the TAPI driver for IP Office will work in a terminal server environment? That is, can I have it linked to my extension in my session, another user in their session have the TAPI driver linked to their phone extension, etc.?

I find that Avaya documentation is good for plain vanilla installs but is pretty useless if you have something slightly exotic going...

 

[kristiandg]

I would recommend using a newer version of the TAPI client, perhaps on the USER cd that accompanies 3.0.69 (I believe its 3.0.18).

Also, the TAPI driver checks for the IPO when it initializes (I believe at system bootup). That being the case, you're talking about a laptop. Is it possible the issue is occuring from "suspend mode" or "hibernate"?

Just a thought. Hope this helps...

Kris G.

 

[telepaul]

Hello,

I suggest to uninstall the tapi and after you have don the uninstall look for the file tspi2w.tsp, it still is in the windows dir system32. Delete the file and reinstall the tapi. Now you are shore to use the new driver. Verify in telephone and modem options if the tapi is correct set. User name but not the full name. (it works also with the user number). Reboot the pc and tray to make a call with outlook. If you look up in this thread you can see how to monitor the tapi and see in the log where it possibly went wrong.

For the RDP clients, it will never work for all users, because the tapi is a single user. (Tapi lite standard) On the other hand it can work with the CTI Pro license, but is not supported from Avaya. I have it working properly but only if the IPO is in the same subnet as the RDP-Server. (had other problems if not with PM). Be careful for other tapi applications, the way to access the api is very important. If the application uses not direct access to the api it only takes the first logged on user. (with CTI Pro you will find for every user a tapi connection.)

Actually PhoneManager also is officially not supported on terminal server, but is only supported on Citrix???

I hope this helps.

Paul