TAPI - simple question

[m-jennings]

If I was to develop a TAPI application, would a simple architecture include CUCM, Windows app server with the TSP and then the clients also with the TSP installed?

This is for a Dynamics CRM pop/click2call app.

Thanks

[dstaudt · Accepted solution]

Generally, there are two common architectures:

* Client/Server: TAPI application links to TAPI32/CiscoTSP installed on the local Windows PC, talks directly to CUCM/CTI Manager over IP for commands/events.  Limits the client to a Windows native app; simpler architecture; required if you need to do softphone stuff with the Cisco TSP media driver, and the PC's mic/speaker; requires installing/configuring/updating of the Cisco TSP.
* Three-tier: CUCM/CTI-Manager -> Windows app server - Client.  The app server handles all TAPI commands/events, using RPC of some kind to proxy commands/events to the clients.  More complex architecture, but the clients can be anything (mobile apps, web apps, Mac/Linux, etc.).  Simplifies configuration/maintenance/troubleshooting to the single app server.
In general would recommend a three-tier architecture, unless you are unable to implement the middle-tier app server.