McDewey

GC2 CallActiveEvGC2 ConnCreatedEv B GC2 CallCtlConnEstablishedEv B GC1 ConnDisconnectedEv 1000 GC1 CallCtlConnDisconnectedEv 1000 Gc2 CallChangedEv GC1 ConnCreatedEv B GC1 ConnConnectedEv B GC1 CallCtlCallEstablishedEv B GC2 ConnDisconnetedEv B GC2 CallCtlConnDisconnectedEv B GC2 CallInvalidEv Caveats for Release 8.6(1) This section lists the JTAPI caveats for Release 8.6(1). • Limitation While Using a Cisco Telepresense MCU, on page 1714 Limitation While Using a Cisco Telepresense MCU In scenarios, where a conference chaining is done across cluster, the number of connection seen by the application might not be correct and application may not see the connection for the external conference bridge getting created. Example: A, B and B' are in Cluster 1D is in cluster 2 Application is observing D GC1: A calls D; Call offered on D and D answers GC2: D consults B; B answers B' CBarges into the call D completes conference - GC1.conference(GC2) After the conference is complete the application will see only the connection for A and D but not that of the conference bridge. Caveats for Release 8.5(1) This section lists the JTAPI caveats for Release 8.5(1). • Discouraged Use of JTAPIProperties.updateCertificate(), on page 1714 • Delete SecurityProperties Before Re-Use, on page 1715 • No ConnDisconnectedEv Event When Call Is Rejected, on page 1715 Discouraged Use of JTAPIProperties.updateCertificate() Applications are encouraged to move away from using the JTAPIProperties.updateCertificate() method to download certificates. The JTAPIProperties.setSecurityPropertyForInstance() method is superior for most applications, as it will store the security information in the jtapi.ini file, giving all the information to JTAPI Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1714 Caveats Caveats for Release 8.6(1)