/mcpNear-End Party Transfers Call to Another Near-End Party in Local Cluster In this use case for automatic call recording, the near-end party transfers a call to another near-end party in the local cluster. The following figure illustrates this use case. Figure 13: Near-End Party Transfers Call to Another Near-End Party in Local Cluster In this use case, the following entities participate: • The customer call originates from DN1000 deviceA. • The agent receives the call at DN2000 deviceB. • The agent transfers the call to DN2001 deviceD. During an automatic call recording session where the agent on the call transfers the call to another party in the same local cluster, the following steps take place: 1. PartyA (far-end party = customer in local cluster) calls partyB (near-end party = agent). 2. PartyB (near-end party = agent in local cluster) answers the call. 3. 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 agent IP phone for the agent voice. 4. Cisco Unified Communications Manager makes the second recording call to the BIB of the agent IP phone for the customer voice. 5. 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 agent voice stream to the recorder. 6. 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 customer voice stream to the recorder. 7. PartyB initiates the consultation transfer. This action implicitly places the call on hold. 8. Cisco Unified Communications Manager terminates recording of the agent voice by sending a BYE message to the recorder through a SIP trunk. 13