/mcpScenario 28 FI: Monitoring- devRD (SME), RDD (cluster2), A (leaf) and B (leaf) - RD selective recording and B start monitoring Events and Call Info Setup and Action Step 5- Check A1 get CiscoTermConnMonitoringStartEv. A1: CiscoTermConnMonitorTargetInfoEv B1: CiscoTermConnMonitorTargetInfoEv 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 Check A1 get CiscoTermConnMonitoringEndEv. 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 (CTIRD3) on cluster 1 has line RD1 (9008) (active remote destination: 1711681 on cluster2) configured as: • selective recording enabled • GW preferred Remote Destination RDD on cluster 2. • devA (SEPDB17) on cluster 3 has line A1 (2303) configured as: • GW preferred • selective recording enabled • rec_profile1: 2000 • devB (SEP3B5F) on cluster 3 has line B1 (3601) configured as: • GW preferred • selective recording enabled • rec_profile1: 2000 • 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 monitoring 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 1429 Message Sequence Charts Message Sequence Charts