# Unified CM CTI and JTAPI integrations

Canonical: https://warmtransfer.net/knowledge/cucm-cti-jtapi

Last verified: 2026-09-25

Computer Telephony Integration (CTI) on Cisco Unified Communications Manager (Unified CM) starts with the Cisco CTIManager service: activating it in Cisco Unified Serviceability is the first task in the Unified CM 15 CTI application task flow[^1]. Applications integrate with Unified CM by consuming Java Telephony API (JTAPI) or Telephony Application Programming Interface (TAPI) client software, which is downloaded from Unified CM[^34][^53].

## How it works

Activating the Cisco CTIManager service in Cisco Unified Serviceability is the first task in the Unified CM 15 CTI application task flow[^1]. In Cisco Unified JTAPI, the `Provider` object acts as the primary contact point between an application and the JTAPI implementation, obtained via `JtapiPeer.getProvider()` using credentials and the Unified CM hostname or IP address[^35]. Nonsecure CTI connections between CTIManager and an application operate over port 2748[^32]. Application Heartbeat Minimum Interval and Application Heartbeat Maximum Interval are CTIManager service parameters configured during the CTI task flow[^22].

Unified CM defines virtual device types for call handling that do not use SCCP or SIP protocols: CTI Port, CTI Route Point, and CTI Remote Device[^60]. A CTI route point is a virtual device capable of receiving multiple simultaneous calls for application-controlled redirection[^40]. In the Cisco Unified Telephony Service Provider (TSP), route point lines carry the `LINEADDRCAPFLAGS_ROUTEPOINT` capability flag, allowing applications to redirect incoming calls with an infinite queue depth[^55]. Administrators configure the number of simultaneous active calls on a CTI route point, though the Unified CM 15 CTI documentation states neither a default nor a maximum value for this parameter[^41]. CTI ports provide first-party call control in Cisco Unified TSP, where each port is limited to 1 active audio stream at a time[^50]. For a JTAPI application to control a new CTI port, administrators must add the port to the application user's list of controlled devices[^9].

For deskphone control using Cisco Jabber, users cannot control a desk phone if the "Allow Control of Device from CTI" option is not selected on that phone[^17].

## Access control groups

Unified CM regulates application and user privileges using specific access control groups:[^47][^2][^42][^36][^6][^33][^5][^46][^18]

* **Standard CTI Enabled**: Allows applications to connect to Unified CM and utilize CTI functionality; the CTI task flow adds application users and end users here[^47].
* **Standard CTI Allow Control of All Devices**: Permits an application to monitor or control any CTI-controllable device across the system[^2].
* **Standard CTI Secure Connection**: Enforces secure TLS connections between the application and Unified CM[^42].
* **Standard CTI Allow Call Recording**: Grants an application permission to record calls[^36].
* **Standard CTI Allow Call Monitoring**: Grants an application permission to monitor calls[^5].
* **Standard CTI Allow Calling Number Modification**: Permits an application to alter calling party numbers[^6].
* **Standard CTI Allow Call Park Monitoring**: Delivers notifications to applications when calls are parked or unparked[^33].
* **Standard CTI Allow Reception of SRTP Key Material**: Delivers the SRTP key material needed to decrypt encrypted media streams[^46].
* **Standard CTI Allow Control of Phones supporting Connected Xfer and conf**: Required for Jabber deskphone control users on 8800, 8900, 9900, or DX series phones[^18].
* **Standard CTI Allow Control of Phones supporting Rollover Mode**: Required for Jabber deskphone control users on 6900 series phones[^18].

## Security and certificates

Securing CTI connections requires validating that the cluster security mode is set to mixed mode[^28]. Secure CTI exchanges Quick Buffer Encoding (QBE) messages between CTIManager and applications over TLS port 2749[^48]. To configure secure JTAPI or TAPI connections, administrators adjust the CTIManager Connection Security Flag and CAPF Profile Instance ID for Secure Connection to CTIManager service parameters[^44].

Issuing Certificate Authority Proxy Function (CAPF) certificates to applications requires activating the Cisco Certificate Authority Proxy Function service on the publisher (first) node[^7]. Secure CTI relies on two CAPF profile types—the Application User CAPF Profile and the End User CAPF Profile—which issue locally significant certificates (LSCs) used by users to authenticate to CTIManager[^8]. If a secure-configured JTAPI or TAPI client cannot download the CTL file, such as when no CTL file exists, the client will not connect on any port[^30].

For deployments implementing both TLS signaling and SRTP media encryption, users must belong to three access control groups: Standard CTI Enabled, Standard CTI Secure Connection, and Standard CTI Allow Reception of SRTP Key Material[^43]. A CTI port that registers to CTIManager across a TLS connection registers securely, and its media is encrypted using SRTP[^16].

## Capacity and system timers

Unified CM enforces device capacity limits and timers through service parameters:[^27][^26][^29]

| Service Parameter | Default Value | Functional Scope |
| --- | --- | --- |
| Maximum Devices Per Provider | 2000 | Maximum devices a single CTI application can open[^27] |
| Maximum Devices Per Node | 800 | Maximum aggregate devices all CTI applications can open on one CTIManager node[^26] |
| CTI New Call Accept Timer | 4 | Configures allowable call answer duration; documentation does not print the unit[^29] |

## Redundancy and failover

System behavior during failures depends on whether the fault occurs at the node, service, or application layer:[^38][^37][^3]

* **Unified CM node failure**: CTIManager recovers affected CTI ports and route points by reopening them on an alternate Unified CM node[^38].
* **CTIManager service failure**: Connected applications reopen affected devices by selecting from configured primary and backup CTIManagers within the application[^37]. Following a CTIManager failover, applications do not rehome to the primary CTIManager when it returns to service[^31].
* **CTI application failure**: CTIManager closes the failed application and redirects unterminated calls at its CTI ports and route points to the configured call forward on failure (CFOF) destination number[^3].

## Client software and versioning

Both the JTAPI client and Cisco TSP software are downloaded from Unified CM Administration under Application > Plugins[^34][^53]. Applications requiring IPv6 support must use a JTAPI or TAPI client version that explicitly supports IPv6 addresses[^23].

### Cisco Unified JTAPI

The JTAPI client is distributed as `CiscoJTAPIWindows.zip` or `CiscoJTAPILinux.zip` in 32-bit and 64-bit packages[^34]. The installed client version on Windows or Linux can be verified by executing `java CiscoJtapiVersion`[^59]. From release 14SU2, the JTAPI classpath includes the Bouncy Castle FIPS archives (`bc-fips.jar`, `bcpkix-fips.jar`, and `bctls-fips.jar`) along with `jtapi.jar`[^21].

Cisco's policy provides interface backward compatibility for Cisco Unified JTAPI covering at least 1 previous major Unified CM release, although Cisco recommends retesting applications with each major release[^4]. Conversely, upgraded Cisco Unified JTAPI clients do not operate with earlier Unified CM releases[^58]. Because event ordering can alter across releases, applications must not rely on specific event sequences and should ignore unrecognized interface elements[^20].

JTAPI does not support Cisco Unified IP 7960 and 7940 phones running SIP[^45]. Additionally, while Cisco Unified IP 7931G phones support conference or transfer across differing addresses in RollOver mode, JTAPI cannot monitor or control them in that mode[^39].

### Cisco Unified TSP

The Cisco Unified TSP implements TAPI 2.1; it does not support TAPI 3.0 applications[^56]. 64-bit Windows environments require the native 64-bit Cisco TSP client, and the TSP can only be installed on systems where Windows resides on the C: drive[^52]. Up to 10 Cisco TSP instances may be installed[^51]. From Unified CM 15SU2 onward, TSP configuration supports a tertiary CTI Manager used when both primary and secondary nodes are unreachable, whereas versions through 15SU1 allowed only primary and backup assignments[^57]. In Unified CM 15SU4, the x64 TSP plugin size increased to 53.7 MB from 26.5 MB in earlier builds[^49]. Cisco recommends rebooting the host computer whenever Cisco TSP configuration settings are modified[^54].

## Troubleshooting and tracing

JTAPI diagnostic tracing is configured using Cisco JTAPI Preferences (JTPREFS), supporting WARNING, INFORMATIONAL, and DEBUG levels[^25]. Selecting DEBUG adds tracing categories such as `CTI_DEBUGGING` and `PROTOCOL_DEBUGGING`[^25].

The error code `CTIERR_DIRECTORY_LOGIN_TIMEOUT` occurs when CTI sends no authentication response to a `ProviderOpenRequest`[^19]. Documented causes include LDAP connectivity issues, CTIManager unavailability, or database delays; the application must retry upon receiving this error[^19].

## See also

* [Unified CM security hardening](https://warmtransfer.net/knowledge/cucm-security-hardening)
* [Unified CM virtualization and sizing](https://warmtransfer.net/knowledge/cucm-virtualization-sizing)
* [Unified CM release trains and lifecycle dates](https://warmtransfer.net/knowledge/cucm-versions-lifecycle)
* [CUCM CallManager SDL trace files](https://warmtransfer.net/knowledge/cucm-sdl-trace-files)

## Applicability

Applies to: Cisco Unified Communications Manager, Cisco Unified JTAPI, Cisco Unified TSP, and Cisco Jabber with Unified Communications Manager. Deployments: on-premises. Sources checked 2026-09-25. Unified CM release 15 and service updates cover the core CTI and JTAPI features[^1]. Bouncy Castle FIPS jar inclusions apply to release 14SU2 and later[^21]. Cisco TSP tertiary CTI Manager support applies to release 15SU2 and later[^57]. The 53.7 MB x64 Cisco TSP plugin size applies to release 15SU4 and later[^49]. Deskphone control configuration settings apply to Cisco Jabber[^17][^18].

## What remains uncertain

Release 15 Collaboration Sizing Guide CTI limits are not covered by the sources below. CTI and JTAPI integrations with Webex Calling Dedicated Instance are not covered by the sources below. Supported JVM versions for Cisco Unified JTAPI 15 are not covered by the sources below. The context of the route point limit in the JTAPI AutoAccept section is not covered by the sources below. The maximum number of CTIManager nodes per cluster is not covered by the sources below. Super Provider (Disable Device Validation) semantics are not covered by the sources below. CTI Remote Device for JTAPI and Extend and Connect is not covered by the sources below.

## Sources

[^1]: The first task in the Unified CM 15 CTI application task flow is activating the Cisco CTIManager service in Cisco Unified Serviceability. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Configure CTI Applications Task Flow; Activate the CTIManager Service. Checked 2026-09-25.
[^2]: In Unified CM 15 the Standard CTI Allow Control of All Devices group lets an application control or monitor any CTI-controllable device in the system. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^3]: When a CTI application fails, CTIManager closes the application and redirects unterminated calls at its CTI ports and route points to the configured call forward on failure (CFOF) number. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), CTI Redundancy for Application Failure. Checked 2026-09-25.
[^4]: Cisco's policy is interface backward compatibility for Cisco Unified JTAPI covering at least one previous major Unified CM release. Cisco still recommends retesting applications with each major release. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_00.html), Overview chapter, backward compatibility statement. Checked 2026-09-25.
[^5]: The Unified CM 15 CTI chapter lists a Standard CTI Allow Call Monitoring group that allows an application to monitor calls. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^6]: In Unified CM 15 the Standard CTI Allow Calling Number Modification group lets an application modify the calling party number. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^7]: Issuing CAPF certificates to CTI, JTAPI and TAPI applications requires activating the Cisco Certificate Authority Proxy Function service on the publisher (first) node. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Certificate Authority Proxy Function Service Activation. Checked 2026-09-25.
[^8]: Secure CTI uses two CAPF profile types, the Application User CAPF Profile and the End User CAPF Profile. CAPF issues locally significant certificates (LSCs) through these profiles so that application users or end users can authenticate to CTIManager. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Set Up Application User or End User CAPF Profile; CAPF Functions for CTI, JTAPI, and TAPI Applications. Checked 2026-09-25.
[^9]: For a JTAPI application to control a new CTI port, the port must be added to the application user's list of controlled devices. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Features Supported by Cisco Unified JTAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_010.html), Features Supported by Cisco Unified JTAPI, CTI port configuration steps. Checked 2026-09-25.
[^10]: The CSR 14 CTI resource figures assume at most 6 BHCA per controlled device, and available CTI resources are lower when that rate is exceeded. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Applications and CTI. Checked 2026-09-25.
[^11]: Under the Collaboration Sizing Guide for CSR 14, each Unified CM cluster supports a maximum of 50,000 CTI connections. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Virtual Nodes and Cluster Maximums. Checked 2026-09-25.
[^12]: The CSR 14 sizing guide says that in deskphone control mode, calls from the software client use the CTI interface on Unified CM, so those devices count toward CTI sizing. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Cisco Collaboration Software Clients. Checked 2026-09-25.
[^13]: The CSR 14 guide advises spreading software-client CTI connections across all subscribers running CTIManager, for example with several CTI gateway profiles that each use a different pair of CTIManager addresses. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Cisco Collaboration Software Clients. Checked 2026-09-25.
[^14]: Under the CSR 14 sizing guide, the maximum CTI resources per Unified CM virtual machine are 3,750 for the small OVA, 10,000 for medium and 12,500 for large. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Applications and CTI, Table 1-6. Checked 2026-09-25.
[^15]: The CSR 14 guide calculates required CTI resources as total CTI device count multiplied by the greater of the CTI line factor and the application factor. The line factor is 1.0 for 1 to 5 lines and rises to 2.0 at 10 lines. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Determining CTI Resources Required for a Unified CM Cluster, Tables 1-7 and 1-8. Checked 2026-09-25.
[^16]: A CTI port that registers to CTIManager over a TLS connection registers securely, and its media is encrypted with SRTP. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Encryption for CTI, JTAPI, and TAPI Applications. Checked 2026-09-25.
[^17]: For Jabber deskphone control, if Allow Control of Device from CTI is not selected on the desk phone, users cannot control it. Source: [On-Premises Deployment for Cisco Jabber 12.9 - Configure Deskphone Control](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_deploy-jabber-on-premises-129/cjab_b_deploy-jabber-on-premises-129_chapter_01011.html), Configure Deskphone Control. Checked 2026-09-25.
[^18]: For Jabber deskphone control, users with 9900, 8900, 8800 or DX series phones also need the Standard CTI Allow Control of Phones supporting Connected Xfer and conf group. Users with 6900 series phones need Standard CTI Allow Control of Phones supporting Rollover Mode. Source: [On-Premises Deployment for Cisco Jabber 12.9 - Configure Deskphone Control](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_deploy-jabber-on-premises-129/cjab_b_deploy-jabber-on-premises-129_chapter_01011.html), Configure Deskphone Control, Prerequisites / user roles. Checked 2026-09-25.
[^19]: CTIERR_DIRECTORY_LOGIN_TIMEOUT means CTI sent no authentication response to the ProviderOpenRequest. Listed causes are LDAP connectivity problems, database delays or CTIManager unavailability, and the application must retry. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Troubleshooting Cisco Unified JTAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_appendix_01010.html), Troubleshooting Cisco Unified JTAPI, Unable to Create Provider Directory Login Timeout. Checked 2026-09-25.
[^20]: The Cisco Unified JTAPI guide says event order can change between releases, so applications should not depend on a specific event sequence. They should ignore interface elements they do not recognise. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_00.html), Overview chapter, backward compatibility guidance list. Checked 2026-09-25.
[^21]: From release 14SU2, the Cisco Unified JTAPI classpath includes the Bouncy Castle FIPS jars (bc-fips.jar, bcpkix-fips.jar, bctls-fips.jar) as well as jtapi.jar. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified JTAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_011.html), Cisco Unified JTAPI Installation, classpath settings (Release 14SU2 and later). Checked 2026-09-25.
[^22]: Application Heartbeat Minimum Interval and Application Heartbeat Maximum Interval are CTIManager service parameters listed in the Unified CM 15 CTI task flow. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Configure CTIManager and Cisco Unified Communications Manager Service Parameters. Checked 2026-09-25.
[^23]: To support IPv6 addresses, CTI applications must use a JTAPI or TAPI client version that supports IPv6. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), CTI Applications Prerequisites. Checked 2026-09-25.
[^24]: The release 15 JTAPI overview software requirements say 'Any JDK 1.6 compliant Java environment'. The installation chapter points to a separate developer.cisco.com page for supported JVM versions. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_00.html), Overview chapter, Software requirements. Checked 2026-09-25.
[^25]: Cisco JTAPI tracing is configured in JTPREFS (Cisco JTAPI Preferences). It offers WARNING, INFORMATIONAL and DEBUG levels, and DEBUG adds categories including CTI_DEBUGGING and PROTOCOL_DEBUGGING. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Troubleshooting Cisco Unified JTAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_appendix_01010.html), Troubleshooting Cisco Unified JTAPI, Cisco Unified JTAPI tracing. Checked 2026-09-25.
[^26]: The Unified CM 15 Maximum Devices Per Node service parameter sets the maximum number of devices all CTI applications together can open on any one CTIManager node. Its default is 800. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Configure CTIManager and Cisco Unified Communications Manager Service Parameters. Checked 2026-09-25.
[^27]: The Unified CM 15 Maximum Devices Per Provider service parameter sets the maximum number of devices one CTI application can open. Its default is 2000. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Configure CTIManager and Cisco Unified Communications Manager Service Parameters. Checked 2026-09-25.
[^28]: The Unified CM 15 secure CTI procedure requires checking that the cluster security mode is set to mixed mode. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Securing CTI, JTAPI, and TAPI. Checked 2026-09-25.
[^29]: The Unified CM 15 CTI New Call Accept Timer sets how long a call is allowed to be answered. Its default value is 4, and the chapter does not print the unit. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Configure New Call Accept Timer. Checked 2026-09-25.
[^30]: A secure-configured JTAPI or TAPI client does not connect on any port if it cannot download the CTL file, for example because no CTL file exists. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), CAPF System Interactions and Requirements for CTI, JTAPI, and TAPI Applications. Checked 2026-09-25.
[^31]: After a CTIManager failover, applications do not rehome to the primary CTIManager when it comes back into service. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), CTI Redundancy on CTIManager (note). Checked 2026-09-25.
[^32]: Nonsecure CTI connections between CTIManager and the application use port 2748. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Authentication for CTI, JTAPI, and TAPI Applications. Checked 2026-09-25.
[^33]: In Unified CM 15 the Standard CTI Allow Call Park Monitoring group lets an application receive notifications when calls are parked and unparked. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^34]: The Cisco JTAPI client (CiscoJTAPIWindows.zip or CiscoJTAPILinux.zip, each 32 and 64 bit) is downloaded from Unified CM Administration under Application > Plugins. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified JTAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_011.html), Cisco Unified JTAPI Installation, download procedure. Checked 2026-09-25.
[^35]: In Cisco Unified JTAPI the Provider object is the main point of contact between applications and the JTAPI implementation. An application obtains it with JtapiPeer.getProvider(), passing the Unified CM server hostname or IP address and login credentials. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_00.html), Overview chapter, Provider. Checked 2026-09-25.
[^36]: In Unified CM 15 the Standard CTI Allow Call Recording group lets an application record calls. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^37]: When a CTIManager fails, connected applications can recover the affected resources by reopening the devices on another CTIManager. Each application picks from the primary and backup CTIManagers set up in the application. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), CTI Redundancy on CTIManager. Checked 2026-09-25.
[^38]: When a Unified CM node fails, CTIManager recovers the affected CTI ports and route points by reopening them on another Unified CM node. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), CTI Redundancy on Cisco Unified Communications Manager. Checked 2026-09-25.
[^39]: In RollOver mode, Cisco Unified IP 7931G phones support transfer or conference across different addresses, and JTAPI does not allow controlling or monitoring them in that mode. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Features Supported by Cisco Unified JTAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_010.html), Cisco Unified IP 7931G Phone Interaction. Checked 2026-09-25.
[^40]: A CTI route point is a virtual device that can receive multiple simultaneous calls for application-controlled redirection. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), CTI Route Points Overview. Checked 2026-09-25.
[^41]: Administrators set the number of simultaneous active calls on a CTI route point. The Unified CM 15 CTI chapter does not state a default or maximum for this setting. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Configure Simultaneous Active Calls. Checked 2026-09-25.
[^42]: In Unified CM 15 the Standard CTI Secure Connection group requires the application to use a secure (TLS) CTI connection to Unified CM. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^43]: For TLS signaling plus SRTP media, the Unified CM 15 security guide places users in three groups: Standard CTI Enabled, Standard CTI Secure Connection, and Standard CTI Allow Reception of SRTP Key Material. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Add Application and End Users to Security-Related Access Control Groups. Checked 2026-09-25.
[^44]: Secure JTAPI and TAPI connections are configured through the CTIManager Connection Security Flag and CAPF Profile Instance ID for Secure Connection to CTIManager service parameters. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Set Up JTAPI/TAPI Security-Related Service Parameters. Checked 2026-09-25.
[^45]: Cisco Unified JTAPI does not support Cisco Unified IP 7960 and 7940 phones running SIP. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_00.html), Overview chapter, supported protocols note. Checked 2026-09-25.
[^46]: The Unified CM 15 CTI chapter lists a Standard CTI Allow Reception of SRTP Key Material group, which lets an application receive the SRTP keys needed to decrypt encrypted media. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Access Control Group Configuration Options. Checked 2026-09-25.
[^47]: In Unified CM 15 the Standard CTI Enabled access control group lets an application connect to Unified CM and use CTI functionality. The CTI task flow adds end users and application users to this group. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure CTI Applications](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_011001.html), Add End Users and Application Users; Access Control Group Configuration Options. Checked 2026-09-25.
[^48]: For secure CTI, CTIManager and the application exchange QBE messages over TLS port 2749. Source: [Security Guide for Cisco Unified Communications Manager Release 15 - Authentication and Encryption Setup for CTI, JTAPI, and TAPI](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/15_0/cucm_b_security-guide-release-15/cucm_b_security-guide-1251SU2_chapter_010101.html), Authentication for CTI, JTAPI, and TAPI Applications. Checked 2026-09-25.
[^49]: From Unified CM 15SU4, the Cisco TSP x64 plugin is 53.7 MB. The previous x64 plugin was 26.5 MB. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_00.html), Overview chapter, plugin size note. Checked 2026-09-25.
[^50]: In Cisco Unified TSP, CTI ports are used for first-party call control, and each port can have only one active audio stream at a time. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_00.html), Overview chapter, CTI Port. Checked 2026-09-25.
[^51]: The TAPI installation chapter limits the number of Cisco TSP instances to 10. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified TAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_011.html), Cisco Unified TAPI Installation, TSP instances. Checked 2026-09-25.
[^52]: 64-bit Windows requires the native 64-bit Cisco TSP client, and Cisco TSP can be installed only where Windows is installed on the C: drive. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified TAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_011.html), Cisco Unified TAPI Installation, requirements. Checked 2026-09-25.
[^53]: The Cisco Telephony Service Provider plugin is downloaded from Unified CM Administration under Application > Plugins. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified TAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_011.html), Cisco Unified TAPI Installation, download. Checked 2026-09-25.
[^54]: Cisco recommends rebooting the computer whenever Cisco TSP configuration settings are changed. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified TAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_011.html), Cisco Unified TAPI Installation, configuration note. Checked 2026-09-25.
[^55]: In Cisco Unified TSP, route point lines carry the LINEADDRCAPFLAGS_ROUTEPOINT capability flag, and applications can redirect incoming calls on them with an infinite queue depth. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_00.html), Overview chapter, CTI Route Point. Checked 2026-09-25.
[^56]: The Cisco Unified TSP is a TAPI 2.1 service provider and does not support TAPI 3.0 applications. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Overview](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_00.html), Overview chapter, TAPI version statements. Checked 2026-09-25.
[^57]: From Unified CM 15SU2, Cisco TSP configuration adds a tertiary CTI Manager, which is used when both the primary and secondary CTI Managers are unreachable. Up to 15SU1 only primary and backup were available. Source: [Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified TAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/tapi_dev/15/cucm_b_tapi-dev-guide-15/cucm_b_tapi-dev-guide-1251_chapter_011.html), Cisco Unified TAPI Installation, CTI Manager configuration settings. Checked 2026-09-25.
[^58]: An upgraded Cisco Unified JTAPI client does not work with earlier Unified CM releases. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified JTAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_011.html), Cisco Unified JTAPI Installation, upgrade note. Checked 2026-09-25.
[^59]: The installed Cisco Unified JTAPI version on Windows or Linux can be checked with the command java CiscoJtapiVersion. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified JTAPI Installation](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_chapter_011.html), Cisco Unified JTAPI Installation, verify version. Checked 2026-09-25.
[^60]: The JTAPI CTI-supported device matrix lists CTI Port, CTI Route Point and CTI Remote Device as CTI-supported devices that do not use SCCP or SIP. Source: [Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs - CTI Supported Devices](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/15/cucm_b_cisco-unified-jtapi-developers-guide-15/cucm_b_cisco-unified-jtapi-developers-guide-1251_appendix_01100.html), CTI Supported Devices table, rows CTI Port / CTI Route Point / CTI Remote Device. Checked 2026-09-25.