McDewey

The Cisco TSP is a TAPI 2.1 service provider. Note From Release 15SU4 onwards, DLLs are unloaded 2 minutes after Cisco TSP closes. This delay happens because of how Windows works and is not caused by Cisco TSP. If you log in again within 2 minutes, trace lines will be added to the same log file. However, this does not affect how Cisco TSP works. Important From Release 15SU4 onwards, the size of the Cisco TSP plugin has increased. This is because it now includes updated runtime dependencies and new Visual Studio Redistributables. For example, the old x64 plugin was 26.5 MB, but the new x64 plugin is 53.7 MB. Important Cisco Unified TSP Concepts The following are described in this section: • Basic TAPI Applications, on page 13 • Cisco TSP Components, on page 14 • Cisco Media Drivers, on page 14 • TAPI Debugging, on page 14 • Cisco TSP Components, on page 14 See Basic TAPI Implementation, on page 143 and Cisco Device-Specific Extensions, on page 317 for lists and descriptions of interfaces and extensions. Basic TAPI Applications Microsoft has defined some basic APIs which can be invoked/supported from application code. All Microsoft defined APIs that can be used from the TAPI applications are declared in TAPI.H file. TAPI.H file is a standard library file that is with the Windows SDK installation. For example: • If Windows SDK 8.0 is used, the path would be C:\Program Files (x86)\Windows Kits\8.0\Include\um\TAPI.H. • If Windows SDK 10 or 11 is used, the path would be C:\Program Files (x86)\Windows Kits\10\Include<version>\um\TAPI.H. To use any specific API which is added or provided by Cisco TSP, the application needs to invoke that API by using the LineDevSpecific API. Simple application Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 13 Overview Cisco Unified TSP Concepts