McDewey

CTI port 1 calls Device 1000. 6. Device 1000 only supports G.729, so an MTP is inserted to provide transcoding. Example 2 1. G729PassThrough set to OFF (default). 2. TSP application registers CTI port 1. 3. CTI port 1 advertises G.711 support (default). 4. Unified CM is not configured with MTPs for transcoding. 5. CTI port 1 calls Device 1000. 6. Device 1000 only supports G.729 and no MTPs are available, so call setup fails. Applications which natively support G.729 can change the default codec advertisement by setting the G729PassThrough registry option to ON (1). The TSP application is then responsible for playing the appropriate media file (G.711 or G.729) based on the compatible codecs supported by the Device receiving the media (see Example 3 below). The Registry key can be found at: • Windows XP: HKEY_Local_Machine/Software/Cisco Systems, Inc./ RtpLib/G729PassThrough • Windows Vista: HKEY_USERS\S-1-5-20\Software\Cisco Systems, Inc.\ RtpLib\G729PassThrough Example 3 1. G729PassThrough set to ON. 2. TSP application registers CTI port 1. 3. CTI port 1 advertises G.711 and G.729 support. 4. Unified CM is not configured with MTPs for transcoding. 5. CTI port 1 calls Device 1000. 6. Device 1000 only supports G.729, so the application plays the appropriate G.729 media file. Typical TAPI Application Message Flow The message flow in the following figure is described in steps 1 and 2. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 424 Cisco TSP Media Driver Typical TAPI Application Message Flow