Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TAPI driver

Status
Not open for further replies.

mikeduncan

IS-IT--Management
Apr 23, 2004
32
AU
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.

 
From the AVAYA docs:

TAPI support in a Terminal Services or Citrix environment
Neither 1st nor 3rd Party IP Office TAPI is supported in a Terminal Services or Citrix environment. This is due to the fact that our TAPI offering was not designed to operate within the tight constraints of these environments.
 
Hi

I have experienced problems like that if you cnfigure the tapi, under phones and modem options, and you put in the user name. You have to use the extension number instead.

Also tapi works fine on a terminal server, if you use distributed tapi, from a 3rd party tapiserver "not ms own tcmsetup because it is crap!
 
Hi Juldal,

Can you give details on how you can get the tapi to work under terminal server because I'm not getting anywhere at all.

Thanks.
 
I found a workaround, going into the services and making sure that the telephony service was working and started. try restarting the service, then giving the dialler.exe a try.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top