/mcpThe recorder receives and answers the recording INVITE 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 INVITE 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 presses Send to Mobile on the userA desk phone. 8. Cisco Unified Communications Manager sends a Setup message to the UserA mobile phone. 9. UserA presses answers the ringing call on deviceUserACell. 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 Remote Cluster Creates Conference In this use case for automatic call recording, the far-end party in a remote cluster creates a conference. The following figure illustrates this use case. Figure 24: Far-End Party in Remote Cluster Creates Conference In this use case, the following entities participate: • The far-end customer call originates from DN3000 deviceD. • The near-end agent receives the call at DN2000 deviceB. • PartyD creates a conference by conferencing in DN3100 deviceE. During an automatic call recording session where the far-end party in a remote cluster creates a conference, the following steps take place: 1. PartyD (far-end party = customer in remote cluster) calls partyB (near-end party = agent) by dialing 82000. 2. The INVITE message passes over the SIPTrunkToCluster2 SIP trunk. 3. PartyB (near-end party = agent in local cluster) answers the call. 30