McDewey

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

Page 499

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

CiscoJtapiProperties Cisco Unified JTAPI behavior and functionality is tailored by many parameters which are read in from the jtapi.ini file when an instance of CiscoJtapiPeer is instantiated. These parameters are now exposed to applications for control via this CiscoJtapiproperties interface. Applications can query the CiscoJtapiproperties properties object and change these parameters to better suit the application functionality. Exposing these properties via the CiscoJtapiproperties interface also allows applications to have a single point of administration (at the application end) for these parameters. The most visible parameters are those describing the tracing levels and tracing destinations. Usage JtapiPeer peer

JtapiPeerFactory.getJtapiPeer ( null ); if(peer instanceof CiscoJtapiPeer) { CiscoJtapiProperties jProps

((CiscoJtapiPeer)peer).getJtapiProperties(); jProps.setTracePath("\D:\Traces\WorkFlow"); jProps.setUseJavaConsoleTrace(false); MyProviderObserver providerObserver

new MyProviderObserver (); provider

peer.getProvider ( providerName ); } In the above example an application has set the Java console tracing to off and set the trace path to D:\Traces\WorkFlowApp1.When the peer is obtained an object implementing CiscoJtapiProperties is created by reading parameters set in the jtapi.ini file. If no jtapi.ini file exists in the classpath default settings are used to create this object. The parameters used by Cisco Jtapi are read in and frozen when the first getProvider () call is made. Interface History Description Cisco Unified Communications Manager Release Number Created history table to track changes. 7.1(1 and 2) Enhanced with methods to enable/disable the HuntList feature. 8.0(1) Enhanced with methods for applications to specify a desired level of FIPS compliance when they download certificates. 8.6(1) Enhanced with methods for applications to specify the minimum TLS version desired when communicating to CAPF or CTI Manager. Four new fields have been introduced: TLS_V1_0 TLS_V1_1 TLS_V1_2 TLS_V1_3 15SU3 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 435 Cisco Unified JTAPI Extensions CiscoJtapiProperties