McDewey

Figure 15: Far-End Party in Local Cluster Creates Conference In this use case, the following entities participate: • The far-end customer call originates from DN1000 deviceA. • The near-end agent receives the call at DN2000 deviceB. • PartyA creates a conference by conferencing in DN1100 deviceC. During an automatic call recording session where the far-end (customer) party in the local cluster creates a conference by bringing an additional far-end party into the call, 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 partyB (agent) IP phone for the agent voice. 4. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyB (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 partyB (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 partyA (customer) voice stream to the recorder. 7. PartyA initiates a conference by pressing Confn and dialing DN1100. 8. PartyC DN1100 deviceC answers the call. 9. PartyA completes the conference by pressing Confn again. 17