NEC's TAPI Implementation
In NCS Ware 4.0, NEC has implemented an innovative solution to overcome the problems mentioned above. The new solution does not rely on Microsoft's middleware to support remote clients and implements that functionality by itself using TCP/IP. This new architecture is depicted in Fig. 2
TAPI
Figure 2. NEC’s TAPI Implementation
TAPI Gateway consists of two components:
1.TAPI Proxy Server - this component should be installed on the NCS Serv system and this component actually implements all the TSP functionality by communicating with the NCS Serv software components. It runs as an NT service.
2.TAPI Service Provider (TSP) - this component should be installed on each client system that intends to use a TAPI application.
These two components communicate with each other using NEC's own TCP/IP based protocol called NCS LinkPlus. Since there is no requirement other than that the client and the server systems should have a TCP/IP connection, the installation, maintenance and support for TAPI applications should be very easy and straightforward.
