McDewey

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 answers the call. 10. PartyD completes the transfer by pressing Transfer. 11. 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 partyE. 12. Because partyB is now connected to a new far-end party, partyE, Cisco Unified Communications Manager sends two UPDATE messages to the recorder. 13. The recorder receives and answers the recording call UPDATE message that is sent from Cisco Unified Communications Manager for the partyB (agent) voice through a SIP trunk. The agent IP phone forks the agent voice stream to the recorder. 14. The recorder receives and answers the recording call UPDATE message that is sent from Cisco Unified Communications Manager for the partyE (customer) voice through a SIP trunk. 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: • Far-end party and transfer-to party are both in the remote (Cisco Unified CM2) cluster. The near-end party sees the far-end party via the SIP trunk that links the two clusters. • When the transfer-to party answers, the recorder receives an UPDATE message that contains the far-end address. Note the header information of the INVITE message from step6 and the UPDATE message from step12. The SIP header enhancement feature adds the information in bold text to the message headers. Step 6 INVITE Message Header Information From: <sip:2000@ucm1;x-nearend;x-refci=ci2;x-nearenddevice=deviceB; x-farendrefci=ci1;x-farenddevice=SIPTrunkTocluster2;x-farendaddr=3000>;tag=fromtag1 Step 12 UPDATE Message Header Information From: <sip:2000@ucm1;x-nearend;x-refci=ci2;x-nearenddevice=deviceB; x-farendrefci=ci1;x-farenddevice=SIPTrunkTocluster2;x-farendaddr=3100>;tag=fromtag1 Far-End Party in Remote Cluster Blind-Transfers Call In this use case for automatic call recording, the far-end party in the remote cluster blind-transfers the call to a remote party that does not answer and has Call Forward No Answer (CFNA) configured. The following figure illustrates this use case. 21