sundance-communications.com/forum Forums Other TDM Phone Systems Executone-Isoetec Telephones & Systems TAPI and TSAPI

I have a client wanting to hook up TAPI for their agent phones and also the possibility of TSAPI for a host server connected to the IDS. Is the CT Link (CSTA) software from Executone current? Is it just a feature activation or a software download? And also the same question for the TSAPI driver - feature activation or download?

What companies make efficient software for TAPI and TSAPI for Executone?

Bill.

TSAPI was originally a Novell spec., and I haven't heard of anything happening on the TSAPI front in many a year. When I was doing development on Novell Netware, I used TSAPI to control an AT&T G3r4 switch (later Lucent, now Avaya) from a Netware 3.12 server over an ISDN link. (Long, long time ago) It was REAL sweet. But like I said, I believe it is a dead dog, now.
TAPI, the Microsoft spec, runs on the desktop, and requires a connection between each workstation and it's phone. It can't do centralized control very well, but it is, I believe, the only game left in phone control.
TAPI needs a phone set with a serial port with which the PC can communicate and control the set.
My Executone experience is limited, but I almost think that Isoetec had a TAPI kit, so Executone should have one. I wouldn't bet on my recollection, though.

https://www.executonesystems.com/tapi-160.htm

https://www.sundance-communications.com/forum/Forum3/HTML/000287.html

https://www.telbon.com/Products/Telephones/tapi2.htm

I was sent a copy of the Eclipse 3.0 info and it states that they don't support TAPI in 3.0 DAMN!

Any work arounds available for 3.0 to allow TAPI to work?

Aable communications should be able to answer any of your questions on this.

And offer any downloads you might need.

https://www.aablecommunication.com/shipping.php?osCsid=2b1f5e95ba930fc13cf9227b7efec14b

Executone stopped supporting TSAPI long ago, and even if you found someone that wanted to use that antiquated standard, the CSTA link that originally supported it (and the 3rd-party TAPI 2.0 referenced in the third link from barster above) was "broken" long before Eclipse 3.0, and never fixed.

3.0 does not officially support 1st-party TAPI (the kind where the phone plugs into the PC), but theoretically it still works - Executone often withdrew support because they didn't want to continue to test & fix bugs for features that didn't sell well, but didn't actually remove it from the software. In this case, they stopped because of the burden created by the fact that the TAPI phone simply sent the entire LCD content out the RS232 port, to be translated by the TAPI driver in the PC into useable event messages. So every time a new software altered the contents of the display even slightly, everything had to be retested. In 3.0 certain call scenarios may not work properly for screen pops etc. because the display changed in a way that the driver can't interpret, but for the most part the event and command set should still be intact.

The real problems with TAPI are that the huge M-160/Agent phone (the only Executone model that supported TAPI; see barster's other two links above) is expensive and in short supply, and the software driver that's required to be loaded into the PC was never fully released in 32-bit form. In other words, it's difficult if not impossible to get it to work under any version of Windows after Win98. There were a few beta versions of the NT/2000 TAPI driver in limited release, but they were never properly debugged.

The M160/agent phones can be used with
Sentinel ACD. The phones were setup using an operator terminal (with a EDCM card installed)
The phones had to be modified with a factory
“debug” and still didn't give the user the correct off hook indication.