McDewey

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

Page 82

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

CiscoObjectContainer Interface The CiscoObjectContainer interface allows applications to associate an application-defined object to objects that implement the interface. In Cisco Unified JTAPI, the following interfaces extend the CiscoObjectContainer interface: • CiscoJTAPIPeer • CiscoProvider • CiscoCall • CiscoAddress • CiscoTerminal • CiscoConnection • CiscoTerminalConnection • CiscoConnectionID • CiscoCallID JtapiPeer and Provider The Provider object, which gets created through the implementation of the JtapiPeer object, acts as the main point of contact between applications and JTAPI implementations. The Provider object contains the entire collection of call model objects, Addresses, Terminals, and Calls, which are controllable at any time by an application. The JTAPI Preferences (JTPREFS) application administers JtapiPeer.getServices(), which returns server names. The Provider entails two basic processes: initialization and shutdown. Ensure that the following information is passed in the JtapiPeer.getProvider() method for applications to obtain a CiscoProvider: • Hostname or IP address for the Cisco Unified Communications Manager server • Login of the user who is administered in the directory • Password of the user that is specified • (Optional) Application information (This parameter may comprise a string of any length.) Applications must include enough descriptive information, so if the appinfo were logged in and an alarm were to occur, administrators would know which application caused the alarm. Applications should not include hostname or IP address where they reside, nor the time at which they were spawned. Also, ensure that no “ = ” or “;” characters are included in the appinfo string because they delimit the getProvider () string. When the appinfo is not specified, you can use a generic and quasi-unique name (JTAPI[XXXX]@hostname, where XXXX represents a random, four-digit number) instead. The parameters get passed in key value pairs that are concatenated in a string as follows: JtapiPeer.getProvider(“CTIManagerHostname;login = user;passwd = userpassword;appinfo = Cisco Softphone”) Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 18 Overview CiscoObjectContainer Interface