/mcpEvents and Call Info Setup and Action .getMediaForkingClusterID() = name of cluster1 Step 8- Check RD1 get CiscoTermConnRecordingEndedEv Scenario 16 FI: Redirect- devRD (SME), RDD (leaf), A (leaf) and B (cluster2) - RD silent recording and A redirect Events and Call Info Setup and Action Step 5- Start recording should fail on RD1 (error = CTIERR_RESOURCE_NOT_AVAILABLE??) Step 8- 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 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 (CTIRD4) on cluster 1 has line RD1 (9008) (active remote destination: 1802303 on cluster3) configured as: • selective recording enabled • GW preferred Remote Destination RDD on cluster 3. • devA (SEP3B5F) on cluster 3 has line A1 (3601) configured as: • GW preferred • selective recording enabled • recording profile:rec_profile1: 2000 • devB (SEP723F) on cluster 2 has line B1 (4008) 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. App start silent recording on RD1 6. A1 redirect to B1 thru GW (i.e. A1 redirect to 171XXXX) 7. B1 answer 8. Start app recording on RD1 9. App stop recording on RD1 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1416 Message Sequence Charts Message Sequence Charts