/mcpThe recording feature lets applications record conversations on any observed address. Three recording configurations are available: The silent monitoring feature lets applications listen to a live conversation between two other parties. The monitor initiator cannot talk to either the monitor target or the caller. The feature provides notification tones when legal compliance is required. Only an application request can initiate monitoring. The application must send a monitor request for each call that it wants to monitor. The system can only monitor calls that are in a connected state. On the successful completion of a monitor request, the audio stream between the monitor target and the caller streams to the monitor initiator. The monitor target receive a tone: • if the monitor target is configured to receive a tone, or • if the application requests a tone when it starts the monitor Applications can monitor calls if they belong to the Standard CTI Allow Call Monitor user group or can be used outside of contact center. The system delivers monitoring-related events to all call observers. “Monitor” is a reserved word that should not be configured as display names for any lines in the system. Other reserved words are “Conference, ” “Park Number, ” “Barge, ” and “CBarge.” When a monitoring session is established, the terminal observer on the monitoring initiator receives Cisco RTP events. Although the media for a silent monitoring call flows only in one direction, getMediaConnectionMode() would return CiscoMediaConnectionMode.TRANSMIT_AND_RECEIVEinstead of CiscoMediaConnectionMode.RECEIVE_ONLY. Applications should expect to find the same behavior in CiscoMediaOpenLogicalChannelEv if a CTIPort is used as the monitor initiator. When a monitoring call (the call used by the monitor initiator) is conferenced, the final call does not have any connection to the monitor target. When the monitor initiator conferences another party into a monitoring call, both parties can listen to the audio between the monitor target and the caller. The following interfaces extend TermConnEv and are delivered to the call observer. 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. CiscoTermConnMonitoringStartEv CiscoTermConnMonitoringStartEv Indicates the start of monitoring and is delivered to the call observer on the monitor target. Using getMonitorType() on this event returns the monitor type. CiscoTermConnMonitoringEndEv CiscoTermConnMonitoringEndEv Indicates the end of monitoring and is delivered to the call observer on the monitor target. CiscoTermConnMonitorInitiatorInfoEv Exposes monitor initiator information and is delivered to the call observer of the monitor target. This interface has one method:CiscoMonitorInitiatorInfo getCiscoMonitorInitiatorInfo () Returns a CiscoMonitorInitiatorInfo that exposes the terminal name and address of the monitor initiator. CiscoTermConnMonitorTargetInfoEv Exposes monitor target information and is delivered to the call observer of monitor target. This interface has one method:CiscoMonitorInitiatorInfo getCiscoMonitorTargetInfo() Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 168 Features Supported by Cisco Unified JTAPI Silent Monitoring