TAPI compliant Tserver interface

[faheemzaman]

Hi,

I am developing a CTI application using Tlib/Tserver combination. I have come to know that Genesys also provide modules to interface Genesys with TAPI (CTAPI or JTAPI). But unfortunately could not find any information on internet about TAPI/Genesys combination. If there is any such proprietary module available, I will be happy to know about that (Where i can get this).

Following link says about Genesys optional TAPI interface modules.
http://www.sggu.com/smf/index.php/topic,95.msg1714.html#msg1714

Regards,
Faheem

[René]

Hi Faheem,

If you want to talk with Genesys TServer you have to use Genesys TLibrary protocol. There is no other way. The other protocols like TAPI, JTAPI etc. are used by TServer to talk to switch. Of course, you can use these to talk directly without using Genesys TServer but I would say that isn't way you'd like to go

R.

[faheemzaman]

Hi Rene,
Thanks for your response. It really helped me.

Accroding to you there could be following two topologies we can use.

1- Tlib ->  TServer - Genesys  ->  Switch 

2- TAPI  -> TSP (Switch Driver) -> Switch

Can you please compare the above two points? What disadvantages and problems it can bring using TAPI instead of TServer or where one approach is superior to use over the other?

Thanks
Faheem

[René]

Hi Faheem,

That's not easy task to compare these options especially in situation I don't know what you're trying to achieve.

Briefly...

Genesys TServer - proven solution used by thousands customers over the world, supports multiple switches, opens the "door" to other Genesys solutions like intelligent routing, reporting, workforce management etc. There are SDKs available to talk with TServer allowing development of agent desktop applications or any other integrations. It's commercial so you have pay to get it.

Writing your own TServer - it's possible but it means you're going to "re-invent the wheel" .

Pros
- You know what are running as it's your code
- You can implement features not supported by TServer

Cons
- Your TServer won't be compatible with "Genesys world" so you have to develop reporting,routing and other solutions as well
- Your TServer will support only your switch and you have to check the functionality every time you upgrade your switch
- It could be a tricky to get official support from switch vendor
- You need someone with excellent knowledge of the switch to support developers during testing
- I assume you have to pay some fee to switch vendor
- Time for development and testing - talking about months IMHO
- Cost of such development

Hope it helps you
R.