The first choice of CTI field standard API - TAPI 3.0

zhaozj2021-02-08  265

CTI 3.0 US Music Telecom's technical support for TAPI 3.0, Wang Hong TAPI, has taken a long time, from the TAPI version 1.0 released in 1993, passed through 1.3, 1.4, 2.0, 2.1 until Windows 2000 TAPI is also updated to version 3.0. In fact, 2.x previous TAPI, although there is also its unique, such as open structure (WOSA), equipment has nothing to do, but there is no more concern. With the development of the CTI industry and the Internet frenzy swept, TAPI 3.0 built in Windows 2000 finally tuning people's appetite. The CTI application interface involves various aspects in computer applications in CTI applications, while phone voice technology is the core. Therefore, various application interfaces (APIs) must be used to build their own application. Although each equipment supplier provides its own API, but for users, it is more desirable to use a standard API, abstract from the hardware layer, can no longer write code for each different hardware, and use system equipment independent Features Do not need to repeat the code, bringing great convenience to development. On the other hand, from decision makers, the standard API-independent standard API can avoid repeated investment, reduce cost, and retain existing resources when upgrading and update. Therefore, the choice of API is very important. At present, various application interfaces are also developing, and the Identity Standards of the CTi industry have not yet formed. There are three recognized APIs: Microsoft TAPI, Novell, and AT & T TSAPI and SUN JTAPI TSAPI are developed by Novell and AT & T, and implement the telephone system with NetWare networks together. TSAPI is the earliest voice application interface, and some achievements have been achieved in the market. However, due to the company's business strategy and expensive customer license fees, NetWare has lost its lead in the competition of the network operating system, so it has lost its driving force. JTAPI is a Java-based application interface proposed by Sun. Since JTAPI is a Java-based application interface, JTAPI's object is independent of the operating system and hardware platform, support cross-platform applications. JTAPI defines a set of libraries, including telephone features and expansion. JTAPI combines traditional telephony services and Web processing capabilities with strong features. However, based on Java-based characteristics, JTAPI has lost the basis of popularization and promotion while having powerful functions. TAPI 3.0 Features TAPI is provided by Microsoft and has been built in a Microsoft operating system. Define equipment (line and phone) and media streams are defined in TAPI. Through the LINE steering, speech card, modem, etc., can operate the telephone, microphone and other equipment via Phone. Through the media flow, different media can be distinguished, such as data, voice, fax, etc. to trigger different processing processes. TAPI is part of the Windows Open Services (WOSA). It can be combined with other Windows APIs, construct flexible, powerful applications. However, although the powerful Microsoft is based on Windows broad users, TAPI 2.x previous versions did not show, more prominent features exceeded exceeding other telephone programming interfaces. It is, with the release of Windows 2000, with the vigorous development of the CTI industry, TAPI 3.0 with better characteristics has finally caused extensive attention.

TAPI 3.0 (The Microsoft® Windows® Telephony Application Programming Interface is an improved TAPI while supporting traditional public exchange telephone network (PSTN) and IP networks. IP telephony technology makes sound, data and videos in existing IP-based local area network (LAN), WAN (WAN), and Internet. Because of the open IETF (Internet Engineering Task Force) standard, multimedia transmission can be performed on any support IP network, providing a variety of media (POTS, ADSL, ISDN, coaxial cable) , Twisted pair, satellite line, etc.), not being applied. Therefore, omnipotent networks can provide a variety of applications such as Web, E-mail, and Data, connect individuals, commerce, schools, governments such as the world. Compared with previous versions, TAPI 3.0 brings new shock, providing new features. 1. Combine traditional telephone technology and IP telephony technology based on COM system, and expand the application from simple phone voice calls to a multimedia multi-point IP conferencing system containing Quality Assurance (QoS). TAPI 3.0 provides an enhanced development tool to help developers create modern global communication systems. TAPI 3.0 API uses popular COM implementations that enable developers to generate application systems in a variety of languages, such as Java, Visual Basic, C / C to play its own special. COM-based systems also make the application system development and upgrade simple. TAPI 3.0 provides support for ActiveX controls. You can use thousands of reusable ActiveX controls to avoid writing a large number of code, only focusing on your system logic design, rapid and efficiently creation of large applications. 2. In TAPI 3.0, support for IP telephony technology is expanded. Here, "call" may not have actual telephone participation, but only video information is transmitted on IP network. IP telephony technology enables CTI's territory to quickly expand from traditional telecommunications networks to the Internet. When building TAPI 3.0 applications, it is no need to consider that it is connected to the public telephone network or on the IP network. 3, TAPI 3.0 enhances support for creating call centers. TAPI 3.0 Call Center Control Adds Auto Call Assignment (ACD) object, implements automatic management of calls through five main ACD objects. These five objects are: Agent Handler, Queue, ACD Group, Agent, and Agent Session. With these objects, you can complete the pre-dynamist, call queue maintenance, call routing management and other transactions, plus comprehensive monitoring of the seat control and agent status, making the construction call center very simple. 4, TAPI 3.0 adds support for multi-point IP conference to assist developers to create multimedia multi-point IP conferencing systems. Combine with the call center control to facilitate building an online call center. TAPI 3.0 Structure TAPI 3.0 The structure is as follows: It can be seen from above, TAPI 3.0 consists of four main components: TAPI 3.0 COM API

TAPI Server

Telephony Service Providers (TSP) Media Stream Providers (MSP)

TAPI Server is extracted from TAPI 3.0 and TAPI 2.0 to make TAPI 3.0 can use TAPI 2.1 TSP. TSP and MSP constitute Service Providers. They certainly have to appear together, TSP is a call control service, while MSP is a Media Control service. Telephony Service Providers (TSP) accepts a call from TAPI and protocol and converts them into a call of the relevant protocol. Two IP-related TSPs: H.323 TSPs: H.323 TSP, and IP Multicast Conferencing TSP (IP Multi-Point Transfer TSP) are bound to TAPI 3.0. The Media Service Providers (MSP) provides a consistent interface to handle various media streams in the call. TAPI 3.0 Programming TAPI 3.0 contains three control interfaces to use to developers:

Call and Media Controls (Calls and Media)

Call Center Controls (Call Center)

IP Multicast Conferencing (multi-point meeting)

转载请注明原文地址:https://www.9cbs.com/read-2431.html

New Post(0)