McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 23

↗ View in doc context
page
23
source
cucm/v15/recording-use-cases/cucm-15-recording-use-cases.md
chunk_id
cucm::v15::recording-use-cases::cucm-15-recording-use-cases::22

The remote cluster (Cisco Unified CM2) sends an UPDATE message to the local cluster (Cisco Unified CM1) through a SIP trunk. The message contains information about partyF. Note the following particularities of call processing that apply in this use case: • Far-end partD in remote cluster transfers call to partyE in remote cluster; the remote Cisco Unified Communications Manager updates the recorder. • PartyE CFNA timer expires and Cisco Unified Communications Manager redirects call to partyF; the remote Cisco Unified Communications Manager again updates the recorder. • The call state of the local Cisco Unified Communications Manager remains call-active, so Cisco Unified Communications Manager updates the recorder for each forwarded remote device. 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=SIPTrunkTocluster2;x-farendaddr=3000>;tag=fromtag1 Far-End Party in Remote PBX Transfers Call to Phone in Local Cluster In this use case for automatic call recording, the far-end party in a remote PBX transfers a call to a phone in the local cluster. The following figure illustrates this use case. Figure 19: Far-End Party in Remote PBX Transfers Call to Phone in Local Cluster In this use case, the following entities participate: • The customer call originates from DN3000 deviceD in PBX1. • The agent receives the call at DN2000 deviceB in clusterCisco Unified CM1. • AgentD transfers the call to DN1000 deviceA in clusterCisco Unified CM1. During an automatic call recording session where the far-end (agent) party in a remote PBX transfers the call to another party in the local cluster, the following steps take place: 1. PartyD (far-end party = customer in remote PBX) calls partyB (near-end party = agent) in local cluster by dialing 82000. 2. 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. 23