McDewey

PartyB (near-end party = agent in local cluster) answers the call. 4. 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. 5. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyB (agent) IP phone for the customer voice. 6. 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. 7. 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 PBX initiates a consultation transfer (presses Transfer) and dials DN81000 deviceA, which is in the local cluster. 9. The remote PBX sends an setup message to the local cluster (Cisco Unified CM1) through a PRI QSIG gateway. The message contains information about partyD. 10. PartyA answers the call from partyD. 11. PartyD presses Transfer to complete the transfer. 12. Remote PBX sends UPDATE. Note the following particularities of call processing that apply in this use case: • When the far-end party in a remote cluster transfers the call to a party in the local cluster, Cisco Unified Communications Manager sends a SIP UPDATE message with farendaddr for the transferred-to local-cluster party. • This transfer specifies a hairpin transfer: the far-end address changed to the local DN1000 in the UPDATE message. Note the header information of the INVITE messages from step6. The SIP header enhancement feature adds the information in bold text to the INVITE message header. Step 6 INVITE Message Header Information From: <sip:2000@ucm1;x-nearend;x-refci=ci2;x-nearenddevice=deviceB; x-farendrefci=ci1;x-farenddevice=PriQSIGGW;x-farendaddr=3000>;tag=fromtag1 Remote PBX Far-End Party Transfers Call to Local Phone In this use case for automatic call recording, a remote PBX far-end party transfers the call to a local phone by using path replacement. The following figure illustrates this use case. 24