/mcpinterface and event; and a new JTAPI event is also introduced to identify recording failure as described below. With this new Gateway Recording feature, either the gateway or the built-in bridge (BIB) can be used as the recording resource based on the end user's preference and the availability. The following interfaces extend TermConnEv and are delivered to callobserver. For shared lines, the system delivers these events to call observers on the address or terminal of the talking terminal connections. Applications receive no events if they have only the terminal whose connection is in the INUSE or BRIDGED state. CiscoTermConnRecordingStartEv CiscoTermConnRecordingStartEv Indicates the start of recording and is delivered to the call observer of the recording initiator. Auto recording configuration or an application request can trigger recording. CiscoTermConnRecordingEndEv CiscoTermConnRecordingEndEv Indicates the end of recording and is delivered to the recording initiator. CiscoTermConnRecordingFailedEv CiscoTermConnFailedEv This interface is added for Cisco Unified Communications Manager Release 10.0(1) and indicates when a call recording failed. Exposing Recording Media Forking Info on CiscoRecorderInfo Cisco JTAPI provides new APIs for Release 10.0(1): getMediaForkingDeviceType(), getMediaForkingDeviceName(), getProtocolReferenceGUID(), and getMediaForkingClusterID() to expose various call recording media forking information of a recording call to JTAPI application. These capabilities are exposed on the existing interface of CiscoRecorderInfo, where applications can extract from CiscoTerminalConnection and CiscoTermConnRecordingTargetInfoEv. Exposing Recording Media Forking Device Type on CiscoCall With Release 10.0(1), Cisco JTAPI introduces three new forking device types: • CALL_RECORDING_MEDIA_FORKING_DEVICE_TYPE_NONE • CALL_RECORDING_MEDIA_FORKING_DEVICE_TYPE_PHONE • CALL_RECORDING_MEDIA_FORKING_DEVICE_TYPE_GW Exposing Cluster ID on CiscoProvider Cisco JTAPI provides API of CiscoProvider.getClusterID(), which returns the clusterID enterprise parameter configured for the cluster. (Note that the cluster ID is an Enterprise parameter configurable from CUCM admin page, and when this parameter is changed by administrator, the CTIManager service and CallManager service would need to be restarted for it to take effect). Secured Recording With this enhancement a recording device can record a secure call if its device security capability is same as or more than that of the agent. A recording request fails if the recording is attempted for an authenticated device, or if the security capability of the recorder is non-secured and that of the agent is encrypted. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 146 Features Supported by Cisco Unified JTAPI Recording