Using TAPI with NCS Ware 4.0
As is evident from Fig. 2, when a client application registers with TAPI for controlling a telephony device such as an extension, NCS Serv will send all events happening on that device to the TAPI proxy, which will, in turn send the events to the client system's service provider. The service provider will report these events to the TAPI middleware on the client system and TAPI will report them to the client application. Similarly, when the client application sends a command to TAPI, it is transported all the way to the NCS Ware system software and the results are sent back via the same components.
The important point to note is that all the communication that goes on below the TAPI layer on the client system is transparent to the application itself. Thus, the support for TAPI applications has been greatly simplified in NCS Ware 4.0.