McDewey

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

Page 1494

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

Scenario 29 FI: Whisper coaching- devRD (leaf), RDD (cluster2), A (SME) and B (SME) - RD selective recording and B start whisper coaching Events and Call Info Setup and Action Step 5- Check A1 get MonitoringStartEvent. A1:CallAttributeInfoEvent with type = coaching B1:CallAttributeInfoEvent with type = coaching Step 6- Check recording started on RD1. Check RD1 get CiscoTermConnRecordingStartedEv and CiscoTermConnRecordingTargetInfoEv. Check RD1 TermConnection.getCiscoRecorderInfo(): .getRecordingType() = CALL_RECORDING_TYPE_APPLICATION _INITIATED_SILENT .getTerminalName() = central recorder device name .getAddress() = Recording profile (DN 2000) .getMediaForkingDeviceType() = CALL_RECORDING_MEDIA_FORKING_ DEVICE_TYPE_GW .getMediaForkingDeviceName() = SIP trunk device name - SIP GW .getProtocolReferenceGUID() = .getMediaForkingClusterID() = name of cluster1 Step 7- Check RD1 get CiscoTermConnRecordingEndedEv Cluster 1 (SME): • "Allow trunk use GW recording" is enabled • Central recorder: 2000 Cluster 2: Cluster 3 (leaf): • "Allow trunk use GW recording" is enabled • Branch recorder: 2000 • devRD (CTI_RD3) on cluster 3 has line RD1 (1622) (active remote destination: 1721711681 on cluster2) configured as: • auto recording enabled • GW preferred Remote Destination RDD on cluster 2. • devA (SIP2) on cluster 1 has line A1 (9001) configured as: • no recording • devB (SIP3) on cluster 1 has line B1 (9002) configured as: • no recording • devB is the Supervisor 1. Open provider Prov1, Prov2, Prov3 2. Observe RD1, RDD1, A1, and B1 in Prov1/Prov2/Prov3 accordingly 3. A1 call RD1 4. Remote destination answer the call 5. B1 start whisper coaching on A1 6. App start recording on RD1 7. App stop recording on RD1 8. RD1 disconnects the call Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1430 Message Sequence Charts Message Sequence Charts

Page 1494 diagram