McDewey

The following interface gets added to CiscoRTPInputStoppedEv, CiscoRTPInputStartedEv, CiscoRTPOutputStoppedEv, and CiscoRTPOutputStartedEv: { public CiscoCallID getCallID(); } GetCallInfo GetCallInfo interface on address provides applications with the ability to query CallInfo on an address. A query returns the CiscoAddressCallInfo object, which contains information about the number of active or held calls, maximum number of active or held calls, and the call object for current calls on the address. This interface also specifies what calls are at a specific address at a specific time. Use the following interface to get information about calls that are present at the terminal: { public CiscoAddressCallInfo getAddressCallInfo(Terminal iterminal);} GetGlobalCallID GetGlobalCallID provides an interface on the CiscoCallID to get the nodeID and the Global Call ID (GCID) of the call; this exposes the GCID information that is available in the internal call object. The following methods get added to the CiscoCallID interface: { /**

• returns the callmanager nodeID of the call */ public int getCallManagerID(); /**
• returns the GlobalCallID of the call */ public int getGlobalCallID (); } } Hairpin Support A hairpin call happens when the call leaves one cluster to some other device across the gateway, then comes back to a device in the same cluster. The GCID for the call coming back into the cluster would differ from the GCID that originally initiated the call, even though both are in the same cluster. In previous releases, if JTAPI controlled both parties, there were two connections: one for CiscoAddress.Internal and the other for CiscoAddress.External. JTAPI supports hairpin calls when an application monitors both ends of the hairpin call. Previously, only one end of the hairpin call could be monitored because the address was represented only as a DN. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 101 Features Supported by Cisco Unified JTAPI GetCallInfo