Replacement to TAPI?

[nmessick]

I read awhile ago somewhere that Avaya as working on a replacement interface for TAPI. Was I imagining that, or can someone confirm thats in the pipline somewhere. I'd love have that.

 

[intrigrant]

In all my years working with Avaya i've heard lot of nice things were comming, i'm stilll waiting....

A simple mind delivers great solutions

 

[amriddle01]

Like hot swappable cards and the ability to reset them individually, gig ports, unique ringing, tenancy support etc etc. The list of unfulfilled intentions goes on

 

[intrigrant]

Shortcodes to switch time profiles, a real chef/secretary function, interactive call pickup like the INDeX had ( promised years ago )

Instead we got "Call appearance" buttons making the use of the phones more difficult, phone rings as a external call with a transfer which is driving the users crazy, Call center software presenting reports with fuzzy data

And we still are enthousiastic explaining the customer how great the solution is, are we stupid or what?

A simple mind delivers great solutions

 

[tlpeter]

We are nuts
I still like the IPO by the way you can program it (flexible)
But indeed it should get some new rich solid features to keep up with the rest.


BAZINGA!

I'm not insane, my mother had me tested!

 

[hairlessupportmonkey]

Ximasoft have been pushing to get web APIs written / released by Avaya so they can enhance their call centre offerings such as being able to put users in and out of group via Chronicall, in the same way you can with CCR + One-X Portal.

ACSS - SME
General Geek

 

[latitude12]

nmessick - Do you mean for 1st or 3rd party control? 1st party-wise I think Avaya got rid of the TAPI driver for one-X Communicator and have something proprietary instead, but that's CM only. I always thought TAPI made sense for IPO because it's very Windows focused, why would you want something else? (serious question)


HSM - There already is one:

"IP Office Configuration Web Service and SDK
The IP Office Configuration Web Service enables System Integrators and Independent Software Vendors to incorporate robust configuration changes in their solutions via a web service interface, expressing configuration changes via an XML document. The web service enables changes to be made to the following IP Office entities:

User
Group

Subsets of the available fields are supported for each entity that fulfil the majority of use-cases."

https://devconnect.avaya.com/public/dyn/d_dyn.jsp?fn=138

amriddle01 - So you want it to be CM then?

 

[amriddle01]

amriddle01 - So you want it to be CM then?

No, that's expensive and convoluted hardware to say the least, but most of these features are in the competitions SME systems, it's hardly enterprise level stuff

 

[intrigrant]

CM use JTAPI ( Java Telephone API ) which is adopted by most of the softwarehouses and thus widely supported.
JTAPI has proven to be reliable and open for all platforms ( UNIX/LINUX / Microsoft / iOS / Android ) so it is a "must have" for IPO

A simple mind delivers great solutions

 

[latitude12]

Well if Avaya were going to replace TAPI with anything then it should be DMCC, that has (or at least will have) more functionality than JTAPI/TSAPI. It has Java and .Net interfaces as well.