McDewey

Figure 6: Calls Prior to Chaining After the conference chain is created, the calls will look like the following figure. Figure 7: Calls After Chaining Applications may get all the participants of a chained conference from the CiscoChainedConference object, which provides conference chain connections from all the conference calls that are chained together. By browsing through the connections list, applications can get a list of all the chained conference calls; however, applications must have at least one participant of each conference that is observed. For any conference scenario that involves chaining conferences or adding parties to a chained conference call, JTAPI will not provide ConferenceStarted/Ended event. Note For more information, see the following topics: • CiscoCall, on page 332 (for the getConferenceChain() interface) • CiscoConferenceChain, on page 371 • CiscoConferenceChainAddedEv, on page 372 • CiscoConferenceChainRemovedEv, on page 375 Consult Without Media Applications can inform Cisco Unified Communications Manager that a consultation call for a transfer is being placed without establishing the media path. The system does not require establishing the media path for the intermediate call, if the consultation call is being placed to determine whether an agent is available before the actual transfer. The consultWithoutMedia method as defined in the CiscoConsultCall interface creates a consultation call without establishing the media path. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 68 Features Supported by Cisco Unified JTAPI Consult Without Media