|
Table Of Contents
Introduction
Revised: January 12, 2007This chapter introduces the Cisco Unified Communications Manager Express (Cisco Unified CME, formerly known as Cisco Unified CallManager Express) Telephony Application Programmering Interface (TAPI) implementation, describes the purpose of this document, and outlines the required software. The chapter includes the following sections:
• Purpose
• Audience
TAPI comprises the set of classes and principles of operation that constitute a telephony application programming interface. TAPI implementations provide the interface between computer telephony applications and telephony services. Cisco Unified CME provides a telephony service provider (Cisco Unified CME TSP 2.1). Cisco Unified CME TSP 2.1 allows developers to create customized IP telephony applications for Cisco Unified CME users; for example, voice messaging with other TAPI-compliant systems, automatic call distribution (ACD), and caller ID screen popups.
Cisco Unified CME TSP 2.1 implementation uses the Microsoft TAPI v2.2 specification and supplies extension functions to support Cisco Unified IP Telephony Solutions. To enable a Cisco Unified CME TSP-based solution, you must have the following:
•TAPI support/service that is running on your Windows system
•A TAPI-based software application
•A Cisco Unified CME IP telephone system
Note The system does not support using Cisco Unified CME TSP 2.1 via the TAPI 3.x compatibility layer.
Purpose
This document describes the Cisco Unified CME TAPI implementation by detailing the functions that comprise the implementation software and illustrating how to use these functions to create applications that support the Cisco Unified CME IP telephony hardware, software, and processes. A primary goal of a standard application programming interface (API), such as TAPI, is to provide an unchanging programming interface under which varied implementations may stand. Cisco's goal in implementing TAPI for the Cisco Unified CME platform remains to conform as closely as possible to the TAPI specification, while providing extensions that enhance TAPI and expose the advanced features of Cisco Unified CME to applications.
Audience
Cisco intends this document to be for use by telephony software engineers who are developing Cisco Unified telephony applications that require TAPI. This document assumes that the engineer is familiar with both the C or C++ languages and the Microsoft TAPI specification.
Organization
The organization of this manual is described in Table 1.
Related Documents
The following resources provide more information about TAPI specifications, creating an application to use TAPI, and TAPI administration:
•Getting Started with Windows Telephony http://www.microsoft.com/ntserver/techresources/commnet/tele/getstartedtele.asp
•The Microsoft Windows Telephony Platform http://www.microsoft.com/ntserver/techresources/commnet/tele/tapiwp.asp
•Creating Next Generation Telephony Applications http://www.microsoft.com/ntserver/techresources/commnet/tele/tapi21wp.asp
•Windows Telephony Features with TAPI 2.1 http://www.microsoft.com/ntserver/techresources/commnet/tele/tapi21.asp
•The Microsoft Telephony Application Programming Interface (TAPI) Programmer's Reference
•For the Telephony API, Press 1; For Unimodem, Press 2; or Stay on the Line—A paper on TAPI by Hiroo Umeno a COMM and TAPI specialist at Microsoft
•TAPI 2.1 Microsoft TAPI Client Management
•TAPI 2.1 Administration Tool
Required Software
For more information about TAPI specifications, creating an application to use TAPI, or TAPI administration, see:
Cisco Unified CME TSP 2.1 requires the following software:
•Cisco Unified Communications Manager Express version 12.3.11, 12.4
Supported Windows Platforms
All Windows operating systems support Cisco Unified CME TSP 2.1. Depending on the type and version of your operating system, you may need to install a service pack.
•Windows 2000
•Windows XP
Note Check%SystemRoot%\system32 for these dynamically loaded library (.dll) files and versions:
•msvcrt.dll version: 6.00.8397.0
•msvcp60.dll version: 6.00.8168.0
•mfc42.dll version: 6.00.8447.0
Terminology
The terms shown in Table 2 are used frequently in the manual to identify different kinds of individuals and objects.
Posted: Mon Apr 9 17:29:48 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.