McDewey

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

Page 1045

↗ View in doc context
page
1045
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::1059

Table 137: Application Initiates a Whisper Coaching Session Events, Requests, and Responses Action At A: CONNECTED Calling = A, Called = B, Connected = B At B: CONNECTED Calling = A, Called = B, Connected = A A initiates call to B and B answers 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 Note Media events are not received at B. At C: 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 LineDevSpecific(SLDSMT_START_TRANSMISION) LineDevSpecific(SLDSMT_START_RECEPTION) C issues CciscoLineDevSpecificStartCallMonitoring with: permLineId = B permLineId mode = MonitorMode_Whisper_Coaching tone = PlayToneDirection_LocalOnly Application Updates the Monitoring Mode Service Parameter Setting: Observed Target = true, Observed Connected Parties = false Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1013 Message Sequence Charts Application Updates the Monitoring Mode

Page 1045 diagram