McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 102

↗ View in doc context
page
102
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::47

• com.cisco.jtapi.extensions.CiscoTerminal getTerminal () Returns the terminal at which this address AutoAccept status gets changed. For details on the interface changes, see Cisco Unified JTAPI Extensions, on page 249 To view the message flow for AutoAccept on CTIPort and RoutePoint, see Message Sequence Charts, on page 761 Autoupdate of API Be aware that when the Cisco Unified Communications Manager is upgraded to a higher version, the APIs may or may not be compatible with the new Cisco Unified Communications Manager version. Ensure that the APIs are upgraded to a compatible version, so the applications work as expected. Because the APIs are installed locally on the client server, the upgrade must take place on multiple machines. In the case of fewer client applications, you can easily do this by connecting to the Cisco Unified Communications Manager Administration and downloading and installing the Cisco Unified Communications Manager compatible plug-in. For multiple client applications, this feature provides a facility by which an application at startup can identify itself to a web server via an HTTP request and receives a response with the version of the required JTAPI API. The application compares the version that is available on the server to the local version in the application classpath and determines whether an upgrade is necessary. This allows applications to refresh the jtapi.jar component to match the Cisco Unified Communications Manager and provides a way to centrally deploy the jtapi.jar to which applications can auto update. The API that is required to perform this functionality gets packaged in the form of an updater.jar. The jtapi.jar and updater.jar get packaged with the standard manifest, which can be used to compare versions. This feature does not update JTAPI Preferences, JTAPITestTools, Updater.jar and javadoc components. If applications require these components, install JTAPI from the Cisco Unified Communications Manager plug-in pages. Auto Update supports JTAPI Release 2.0 and later. Note Refer to Cisco Unified JTAPI Installation, on page 217 for more information. The following new or changed interfaces exist for autoupdate of APIs: Class com.cisco.services.updater.ComponentUpdater queryLocalComponentVersion (java.lang.String componentName, java.lang.String path) Throws an IOException, IllegalArgumentException. Component queryServerComponentVersion (java.lang.String componentName, java.lang.String urlString) Throws an IOException, IllegalArgumentException, and sends an HTTP query to the server to determine the remote server installed components version. Component Interface com.cisco.services.updater.Component Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 38 Features Supported by Cisco Unified JTAPI Autoupdate of API