McDewey

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

Page 130

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

In Cisco Unified Communications ManagerRelease3.0, not all parties who are involved in the transfer of calls received these events Note Applications should not rely on the order of events between CiscoTransferStartEv and CiscoTransferEndEv or between CiscoConferenceStartEv and CiscoConferenceEndEv for transferring and conferencing when porting applications from Cisco Unified Communications ManagerRelease3.0 to 3.1. Note Conference and Join The Conference Feature provides the ability to conference more than two people into a single call. Events at CTI layer change, and Cisco Unified JTAPI gets enhanced to support the new CTI events. Join Feature provides the ability to join multiple calls into one single conference call. This functionality now supports multiple calls. Applications need to pass an array of calls to be conferenced together. The following new or changed interfaces exist for conference and joining of multiple calls into one conference call: • The following interface allows Join to conference multiple calls into one conference call: Call.Conference(Call[] otherCalls) A precondition requires that all the otherCalls must have controller as one leg of the call. Note • The following new or modified interfaces exist in CiscoConferenceStartEv: • TerminalConnection getHeldConferenceController()—This interface proves useful only for the arbitrary conferencing of two calls and returns only one of the held calls. • TerminalConnection[] getHeldConferenceControllers()—This interface gets all of the held calls when multiple calls are joined. • TerminalConnection getTalkingConferenceController()—This interface returns the talking conference controller; however, if no talking conference controller exists when all the calls that are being joined into conference are held, this interface returns null. • Call getConferencedCall()—This interface returns only one of the many calls that are going to join into a conference and may not have any meaning for a join conference when more than two calls exist. • New interface in CiscoConferenceEnded event Boolean isSuccess(): This interface returns true or false depending on whether conference is successful or failed. Application can use interface to find whether conference is successful. The following events get defined as conference failure: Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 66 Features Supported by Cisco Unified JTAPI Conference and Join