/mcpFigure 18: Far-End Party in Remote Cluster Blind-Transfers Call To Remote-Cluster Party That Has CFNA Configured In this use case, the following entities participate: • The customer call originates from DN3000 deviceD in clusterCisco Unified CM2. • The agent receives the call at DN2000 deviceB in clusterCisco Unified CM1. • AgentD blind-transfers the call to DN3100 deviceE in clusterCisco Unified CM2. • AgentE does not answer and the call forwards to DN3200 deviceF in clusterCisco Unified CM2. During an automatic call recording session where the far-end (agent) party in the remote cluster blind-transfers the call to another party in the remote cluster, but the second party does not answer and the call forwards to a third party in the remote cluster, the following steps take place: 1. PartyD (far-end party = customer in remote cluster) calls partyB (near-end party = agent) in local cluster by dialing 82000. 2. The remote cluster (Cisco Unified CM2) sends an INVITE message to the local cluster (Cisco Unified CM1) through a SIP trunk. The message contains information about partyD. 3. PartyB (near-end party = agent in local cluster) answers the call. 4. Because the agent line appearance is configured for automatic recording, the recording session for the media streams automatically gets triggered. Cisco Unified Communications Manager first makes a recording call to the built-in bridge (BIB) of the partyB (agent) IP phone for the agent voice. 5. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyB (agent) IP phone for the customer voice. 6. The recorder receives and answers the recording call setup messages that are sent from Cisco Unified Communications Manager for the agent voice through a SIP trunk. The agent IP phone starts to fork the partyB (agent) voice stream to the recorder. 7. The recorder receives and answers the recording call setup messages that are sent from Cisco Unified Communications Manager for the customer voice through a SIP trunk. The agent IP phone starts to fork the partyD (customer) voice stream to the recorder. 8. PartyD in the remote cluster initiates a transfer (presses Transfer) and dials DN3100 deviceE, which is also in the remote cluster. 9. PartyE does not answer the call: ringing times out, so Cisco Unified Communications Manager sends the call to partyF DN3200 deviceF. 10. The remote cluster (Cisco Unified CM2) sends an UPDATE message to the local cluster (Cisco Unified CM1) through a SIP trunk. The message contains information about partyE. 11. PartyF answers the forwarded call. 22