/mcpScenario 21 FI: JAL- devRD (SME), RDD (cluster2), A1, A2 and B (leaf) - RD silent recording and A1 does JAL Events and Call Info Setup and Action Step 5- 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- A2 and B1 are connected. Step 8- JAL. A1, B1 and RD1 in conference. Recording not retriggered on RD1. Step 9- 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 (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) and A2 (1623) configured as: • GW preferred • selective recording enabled • recording profile:rec_profile1: 2000 • devB (SEP3B5F) on cluster 3 has line B1 (3601) configured as: • GW preferred • selective recording enabled • recording profile:rec_profile1: 2000 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. Start silent recording on RD1 6. A2 call B1 7. B1 answer 8. A1 join two calls with primary call = A1 RD1 9. Stop recording on RD1 10. RD1 disconnects the call Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1421 Message Sequence Charts Message Sequence Charts