JTAPI CUCM Compatibility Matrix
Last update 03/30/2021
Cisco JTAPI generally preserves CUCM's backward compatibility wrt to the JTAPI Client. That is to say, older JTAPI clients will be compatible with newer CUCM versions. Exception applies to development CUCM versions however, please refer to "Note 2" below for details.
JTAPI preserve's this backward compatibility of CUCM along the CUCM upgrade path.
Below is a table showing this.
| Cisco JTAPI Version | Cisco Unified Communications Manager Version |
|---|---|
| 15(x) | 15(x) |
| 14(x) | 14(x), 15(x) |
| 12.5(x) | 12.5(x), 14(x), 15(x) |
| 12.0(1.x) | 12.0(1.x), 12.5(x), 14(x), 15(x) |
|
11.5.1.10000-3 and above including SUs (JTAPI plugin from cm_11_5_1) |
11.5.1.10000-3 and above including SUs 12.0(1.x) 12.5(x) 14(x) 15(x) |
|
11.5.1.10000-1 – 11.5.1.10000-2 (JTAPI plugin from cm_11_5_1) |
11.5(1.x), 12.0(1.x), 12.5(x), 14(x), 15(x) |
|
11.0.1.22900-1 and above (Because 11.0.1.22900-11 build has 11.0.1.22900-1 as plugin version) (JTAPI Plugin from cm_su2_11_0_1) |
11.0.1.22049-2 and above 11.0.1.22900-11 and above 11.5.1.10000-3 and above including SUs 12.0(1.x) 12.5(x) 14(x) 15(x) |
|
11.0.1.22050-1 and above (Because 11.0.1.22049-2 build has 11.0.1.22050-1 as plugin version) (JTAPI plugin from cm_11_0_1) |
11.0.1.22049-2 and above 11.0.1.22900-11 and above 11.5.1.10000-3 and above including SUs 12.0(1.x) 12.5(x) 14(x) 15(x) |
|
11.0.1.10000-1 – 11.0.1.10000-3 (Because 11.0.1.22049-1 build has 11.0.1.10000-3 as plugin version) (JTAPI plugin from cm_11_0_1) |
11.0(1.x), 11.5(1.x), 12.0(1.x), 12.5(x), 14(x), 15(x) |
|
10.5.2.14900-1 and above (JTAPI Plugin from cm_su4_10_5_2) |
10.5.2.14094-1 and above on 10.5.2 10.5.2.14900-8 and above on 10.5.2 su4 11.0.1.22049-2 and above 11.0.1.22900-11 and above 11.5.1.10000-3 and above including SUs 12.0(1.x) 12.5(x) 14(x) 15(x) |
|
10.5.2.14093-1 and above (Because 14094-1 has 10.5.2.14093-1 as plugin version) (JTAPI plugin from cm_10_5_2) |
10.5.2.14094-1 and above on 10.5.2 10.5.2.14900-8 and above on 10.5.2 su4 11.0.1.22049-2 and above 11.0.1.22900-11 and above 11.5.1.10000-3 and above including SUs 12.0(1.x) 12.5(x) 14(x) 15(x) |
|
10.5(2.x) 10.5.2.10000-1 – 10.5(2.10000)-3 (Because 14093-1 has 10.5(2.10000)-3 as plugin version) (JTAPI plugin from cm_10_5_2) |
10.5(2.x), 11.0(1.x), 11.5(1.x), 12.0(1.x), 12.5(x), 14(x), 15(x) |
| 10.5(1.x) | 10.5(1.x), 10.5(2.x), 11.0(1.x), 11.5(1.x), 12.0(1.x), 12.5(x), 14(x), 15(x) |
| 10.0(1.x) | 10.0(1), 10.5(1.x),10.5(2.x), 11.0(1.x), 11.5(1.x), 12.0(1.x), 12.5(x), 14(x), 15(x) |
| 9.1(1.X) | 9.1(1), 10.0(1), 10.5(x) |
| 9.0(1.X) | 9.0(1), 9.1(1), 10.0(x),10.5(x) |
| 8.6(2.X) | 8.6(2), 9.0(1),10.0(1) |
| 8.6(1.X) | 8.6(1), 8.6(2), 9.0(1) |
| 8.5(1.X) | 8.5(1), 8.6(X), 9.0(1) |
| 8.0(3.X) | 8.0(3), 8.5(1), 8.6(X), 9.0(1) |
| 8.0(2.X) | 8.0(2), 8.0(3), 8.5(1), 8.6(X), 9.0(1) |
Note 1: This table represents JTAPI Client compatibility with CUCM, it doesn't represent its backward compatibility with any application. Application's compatibility depends on the version of API being used by application (e.g. some applications may require 8.5 JTAPI Client to work with 8.5 CUCM). For application specific JTAPI Client requirement, please refer to the application documentation.
Note 2: JTAPI maintains the CUCM's backward compatibility only in the versions that customer see (i.e. FCS/ES), it might not apply to development branches. This is because we can have changes happening in multiple development branches at the same time, and jtapi.jar from one branch/version may not work with CUCM on other branch/version. If development branches are used to run JTAPI, it is expected that the user uses the jtapi.jar directly from corresponding CUCM. For example, if a CiscoJTAPITestTool user wants to connect to a CUCM running on a development branch, he/she can copy the file of "http://plugins/jtapi.jar" to his or her CiscoJTAPITestTool\lib folder before running the JTAPI test tool.
Note 3 : From 10.5(2.x) and above release, The JTAPI which contains the TLS1.2 support will be compatible with the specific build on wards. This is because of the protocol version update during Spark remote device development, the jtapi compatibility with UCM is affected (jtapi from 10.5(2), 10.5(2)su4, 11.0(1), 11.0(1)su2 will not be compatible with the earlier builds of the same version train). We have updated the supported version in above table.