Feedback
Table Of Contents
Preface
This section introduces the Cisco Unified Telephony Application Programming Interface (TAPI) for Service Providers implementation, describes the purpose of this document, and outlines the required software. The section includes the following topics:
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
•
IntroductionThe Cisco Unified Telephony Application Programming Interface (TAPI) comprises the set of classes and principles of operation that constitute a telephony application programming interface. The Cisco Unified TAPI implementations provide the interface between computer telephony applications and telephony services. The Cisco Unified Communications Manager (formerly Cisco Unified CallManager) includes a TAPI Service Provider (Cisco Unified TSP), which allows developers to create customized IP telephony applications for Cisco users; for example, voice messaging with other TAPI-compliant systems, automatic call distribution (ACD), and caller ID screen pop-ups. Cisco Unified TSP enables the Cisco Unified Communications system to understand commands from the user-level application such as Cisco SoftPhone via the operating system.
The Cisco Unified TAPI implementation uses the Microsoft TAPI v2.1 specification and supplies extension functions to support Cisco Unified Communications Solutions.
To enable a Cisco Unified TAPI-based solution, you must have the following items:
•
•
•
Note
PurposeThis document describes the Cisco Unified 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 Communications hardware, software, and processes. You should use this document with the Cisco Unified Communications Manager manuals to develop applications.
A primary goal of a standard Application Programming Interface (API) such as TAPI specifies providing an unchanging programming interface under which varied implementations may stand. The goal of Cisco in implementing TAPI for the Cisco Unified Communications Manager 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 Communications Manager to applications.
As new versions of Cisco Unified Communications Manager and Cisco Unified TSP are released, variances in the API should be minor and should tend in the direction of compliance. Cisco stays committed to maintaining its API extensions with the same stability and reliability, though additional extensions may be provided as new Cisco Unified Communications Manager features become available.
AudienceCisco intends this document to be for use by telephony software engineers who are developing Cisco 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
New and Changed InformationThe Release Notes for each release describe new features and/or changes for Cisco Unified TAPI or Cisco Unified TAPI Service Provider (TSP) that are pertinent to a specified release of Cisco Unified Communications Manager.
This document contains the cumulative definition of the interface, not just the new information for the current release.
Related DocumentationFor more information about TAPI specifications, creating an application to use TAPI, or TAPI administration, see
•
http://www.microsoft.com/ntserver/techresources/commnet/tele/tapi21.asp•
http://www.microsoft.com/NTServer/commserv/deployment/planguides/getstartedtele.asp•
http://www.microsoft.com/NTServer/commserv/exec/overview/tapiabout.asp•
http://www.microsoft.com/NTServer/commserv/techdetails/prodarch/tapi21wp.asp•
•
•
•
Required SoftwareCisco Unified TSP requires the following software:
•
on the Cisco Unified Communications Manager server•
ConventionsThis document uses the following conventions:
Notes use the following conventions:
Note
Tip
Timesaver
Obtaining Documentation, Obtaining Support, and Security GuidelinesFor information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security OverviewThis product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html .
If you require further assistance please contact us by sending email to export@cisco.com.
