Does anybody know a trick to get TAPI or TAPI2 to install smoothly? I've been installing it for years and very seldom does it "take" the first time. Usually after you launch, configure and reboot, when it finishes installing you can look in phone and modem settings and see it there and configured, but in Outlook it simply just does not show up as a line option. So then you try another reboot and when that doesn't work you uninstall and start all over. There is no error or indicator of what's wrong, and no documentation as to what you can check other than phone and modem settings and outlook line settings, or is there? I have waisted an hour or more on one PC getting TAPI to work when there is no other underlying issue other than the install just doesn't take. So what if I have 20 of these to get working, should it be reasonable to spend 2 days doing this with the customer having to log me in everytime I reboot? Anyone who has experienced this and found a sure fire way or even halfway reliable method, please reply, thanks.
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
TAPI Woes
- Thread starter cdavis18
- Start date
amriddle01
Programmer
This is just the way TAPI is with Avaya, I have the exact same issues. Now I just try to avoid selling/installing it, if that means losing a sale then so be it, it's too much of a liability
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
I've always just verified there was no firewall blocking the application, that the user is ALREADY configured with a password, and that it's being run as an administrator. It works 70% of the time, all the time.
-Austin
ACE: Implement IP Office
-Austin
ACE: Implement IP Office
amriddle01
Programmer
It totally depends on OS and version, I'd say more 50/50 overall...and that's being generous. Even once working it can fail after a number of days/week and require a full uninstall and re install to clear, if we installed it for every system we sell we would quickly go out of business funding all the maint work/visits required to keep it going.... that's for sure
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
If Windows 7 64-bit, install by running as administrator. Make sure Windows firewall is turned on. It WILL NOT work if it is off. I know that is stupid but it is true. After installing, run the Avaya firewall script. After reboot, go to control panel for phone and modem. On the advanced tab, setup the IP Office information and then Outlook should work.
- Thread starter
- #7
amriddle01
Programmer
Indeed, the only thing I can get to work consistently and consistently well is Phone Manger...and they ditched that for a method of working that dates back to mainframes
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
- Thread starter
- #9
amriddle01
Programmer
cdavis18, that signature image is far too big, you will need to shrink it or you will be chastised by the staff
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
- Thread starter
- #11
amriddle01
Programmer
Yeah, still works
"No problem monkey socks
"No problem monkey socks
I did 10 different machines yesterday with the method above. Worked like a charm as long as Windows Firewall was on. With it off it would not work at all. One reboot was all it took. No uninstall and reinstall. Good luck though, I have been messing with this pos TAPI for the past year and finally got it somewhat simplified.
We might have not done as many of the TAPI installs as those above; but luckily (already knocked on wood), we haven't had much of a problem with TAPI since 7.0 - We usually have the customer's IT department deploy it because we don't want customer passwords, etc...
Notes that seem to have a 90+ success rate:
*Win7+ - Need to have firewall on. (Thank you Microsoft for making something basic confusing)
*Run as administrator (Fixes a lot of the issues and why we have IT go around and do it during our cutover coverage)
*Reboot
Only 2 wishlist items here is to not show the user list in a drop down, and to be able to automate deployment on domains by appending the startup script to determine if it has been installed already, and if not - pop up a dialogue box asking One-X name and password.
The above is for TAPI found on User CD (47) and below... On the new User CD (48), there is now TAPI2 and TAPI3 - nothing in the release notes regarding it, and by default the User CD tries to install both (which is necessary). Haven't had time to play with it this week to see the difference between install steps and other "concerns."
TAPI2 vs TAPI3 - quick reference -
Notes that seem to have a 90+ success rate:
*Win7+ - Need to have firewall on. (Thank you Microsoft for making something basic confusing)
*Run as administrator (Fixes a lot of the issues and why we have IT go around and do it during our cutover coverage)
*Reboot
Only 2 wishlist items here is to not show the user list in a drop down, and to be able to automate deployment on domains by appending the startup script to determine if it has been installed already, and if not - pop up a dialogue box asking One-X name and password.
The above is for TAPI found on User CD (47) and below... On the new User CD (48), there is now TAPI2 and TAPI3 - nothing in the release notes regarding it, and by default the User CD tries to install both (which is necessary). Haven't had time to play with it this week to see the difference between install steps and other "concerns."
TAPI2 vs TAPI3 - quick reference -
Just played with the User (48) CD...
At first glimpse, here's what to do:
Tried from the setup (Run as Admin) - Failed on TAPI install.
So -
Uninstall TAPI first.
Manually Install TAPI2 (Run as Admin)
Configure IPO/User
** System will reboot **
Install TAPI3 (Run as Admin)
On mine, it failed to download the user list from the IPO, So I manually entered my credentials.
Once done, system needs to reboot again.
Under Phone and Modem:
TAPI2 shows up as "Avaya IP Office TAPI2 Service Provider", items configured are editable and changeable.
TAPI3 shows up as "tsp3w_64.tsp", no configuration options at all.
Tested Dialing - Dialing through applications works without issue
It appears that TAPI2 is just a rename of the old TAPI install - But, Avaya might not be done with TAPI3 at this time, or, Since TAPI3 is really used for interop between 3rd party packages, Avaya has just made it easier to find the file by including it on the User CD, eliminating the need to go to the support site and download it. Hopefully someone has more info
At first glimpse, here's what to do:
Tried from the setup (Run as Admin) - Failed on TAPI install.
So -
Uninstall TAPI first.
Manually Install TAPI2 (Run as Admin)
Configure IPO/User
** System will reboot **
Install TAPI3 (Run as Admin)
On mine, it failed to download the user list from the IPO, So I manually entered my credentials.
Once done, system needs to reboot again.
Under Phone and Modem:
TAPI2 shows up as "Avaya IP Office TAPI2 Service Provider", items configured are editable and changeable.
TAPI3 shows up as "tsp3w_64.tsp", no configuration options at all.
Tested Dialing - Dialing through applications works without issue
It appears that TAPI2 is just a rename of the old TAPI install - But, Avaya might not be done with TAPI3 at this time, or, Since TAPI3 is really used for interop between 3rd party packages, Avaya has just made it easier to find the file by including it on the User CD, eliminating the need to go to the support site and download it. Hopefully someone has more info
- Status