McDewey

Events, Requests, and Responses Action At B: LineDevSpecific(SLDST_START_CALL_MONITORING) CONNECTED devSpecific type = CallAttribute_WhisperMonitorCall dn = C, partition = C’s Partition, deviceName = C’s device transactionId = xxxx, tone = PlayToneDirection_RemoteOnly CallSecurityStatus = OverallCallSecurityStatus_Encrypted Note Media events are not received at B and SRTP keys are not available. At C: LineDevSpecific (dwparam1 = DevSpecificData, dwparam2 = SLDST_SRTP_INFO, dwParam3 = MEDIA_ENCRYPT_KEYS_AVAILABLE) SRTP keys are available CONNECTED Calling = C, Called = B/B’s Name Connected = “”/Whisper, Redirection = “”/Whisper, Redirecting = “”/Whisper, devSpecific type = CallAttribute_WhisperMonitorCall_Target dn = B, partition = B’s Partition, deviceName = B’s device transactionId = xxxx, tone = PlayToneDirection_RemoteOnly CallSecurityStatus = OverallCallSecurityStatus_Encrypted LineDevSpecific(SLDSMT_START_TRANSMISION) LineDevSpecific(SLDSMT_START_RECEPTION) C issues a CciscoLineDevSpecificStartCallMonitoring with: permLineId = B permLineId mode = MonitorMode_Whisper_Coaching tone = PlayToneDirection_LocalOnly Application Updates the Monitoring Mode on an Agent Call That Is on Hold The application updates the monitoring mode on an agent call that is on hold as follows: 1. A initiates Call to B and B answers Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1031 Message Sequence Charts Application Updates the Monitoring Mode on an Agent Call That Is on Hold