{"id":1015,"date":"2013-11-26T10:03:11","date_gmt":"2013-11-25T23:03:11","guid":{"rendered":"\/?p=208"},"modified":"2013-11-26T10:03:11","modified_gmt":"2013-11-25T23:03:11","slug":"avaya-ip-office-tapi-2-1-tapi-3-0","status":"publish","type":"post","link":"https:\/\/infinititelecommunications.com.au\/avaya-ip-office-tapi-2-1-tapi-3-0\/","title":{"rendered":"Avaya IP Office CTI and working with TAPI 2.1 and TAPI 3.0"},"content":{"rendered":"
Microsoft TAPI 2.1 and 3.0 are simply open specifications and developers interfaces for controlling and monitoring a telephone system (Avaya IP Office phone system for example<\/a>).\u00a0 TAPI is simply the common language protocol they use.\u00a0 TAPI allows your Avaya phone system to talk with computer applications that are running TAPI<\/p>\n TAPI 2.1 and TAPI 3.0 are different specifications although they both work the same way.\u00a0 Think of TAPI 3.0 as simply more advanced.\u00a0 Most CTI applications we see for the Avaya IP 500 operate with the more basic Microsoft TAPI 2.1 driver.\u00a0 TAPI 3.0 standard requires that more core functionality is implemented, and additionally defines a series of optional functionality that switch vendors (phone systems) may also implement.<\/p>\nThe following table shows the very extensive Avaya device specific data available via TAPI.<\/h3>\n
\n \n
|