McDewey

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

Page 193

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

Backward Compatibility This feature is backward compatible. Noncontroller Adding of Parties to Conferences Any party in a conference can now add participants into the conference. In previous releases, only the conference controller could add participants. • CiscoConferenceStartEv, on page 382 contains an identifier for the requestor party. • The method getConferenceControllerAddress returns the terminal connection of the requestor. • The new method getOriginalConferenceControllerAddress() for CiscoConferenceStartEv, on page 382 returns the terminal connection of the original controller. Park DN Monitor Cisco Unified JTAPI applications can register to receive events when calls are parked and unparked. CiscoProvCallParkEv events will be delivered to provider observer when the application registers for this feature. To successfully register for this feature, ensure that the “call park retrieval allowed” flag for the user is turned on. You can access this flag with the user configuration on Cisco Unified Communications Manager Administration. After registering for this feature, the application will receive CiscoProvCallParkEv events whenever a call is parked or unparked from any device in the cluster. The following new interfaces allow applications to register and unregister for this feature: public interface CiscoProvider { public void registerFeature ( int featureID ) throws InvalidStateException, PrivilegeViolationException; public void unregisterFeature ( int featureID ) throws InvalidStateException; } The featureID is CiscoProvFeatureID.MONITOR_CALLPARK_DN. Park Monitoring and Assisted DPark Support This feature provides a new park reversion behavior to applications invoking park request. Currently, when the park reversion timer expires, the call is reverted to the address of the parker. With the new behavior, the call remains parked at the park DN, even as the Park Monitoring reversion timer expires. This feature also enables status monitoring of the parked call at the address of the parker. After a call is parked using the existing CiscoConnection.park() JTAPI API on newer phones or directly from the phone itself, Cisco Unified JTAPI delivers a new event CiscoAddrParkStatusEv, which includes the current status of the parked call. The application must then add AddressObserver on the address of the parker, and enable a filter to receive this event. If application adds an observer after the call is parked, then the events are delivered with CAUSE_SNAPSHOT. The park status in the new event can be one of the following: • Parked—Indicates a call was parked by the user of the application. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 129 Features Supported by Cisco Unified JTAPI Noncontroller Adding of Parties to Conferences