/mcpThe 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. PartyA presses Transfer, dials DN1100 deviceC, and presses Transfer again (performs a blind transfer). 8. Cisco Unified Communications Manager rings DN1100 on deviceC, but this DN and device have CFNA configured: ringing times out, and Cisco Unified Communications Manager forwards the call to DN1200 deviceD. 9. Far-end partyD with DN1200 on deviceD answers the call. 10. After the transfer is completed, Cisco Unified Communications Manager restarts the recording. The agent IP phone forks the customer voice stream to the recorder. Note the following particularities of call processing that apply in this use case: • For local-cluster transfers, Cisco Unified Communications Manager updates the recorder only when a new far-end party answers. • When party D answers the call, Cisco Unified Communications Manager restarts the recording. Note the header information of the INVITE messages from step5. The SIP header enhancement feature adds the information in bold text to the INVITE message header. Step 5 INVITE Message Header Information From: <sip:2000@ucm1;x-nearend;x-refci=ci2;x-nearenddevice=deviceB; x-farendrefci=ci1;x-farenddevice=deviceA;x-farendaddr=1000>;tag=fromtag1 Far-End Party in Local Cluster Creates Conference In this use case for automatic call recording, the far-end party in a local cluster creates a conference. The following figure illustrates this use case. 16