McDewey

The DMS switch sends a PriSetup message to the local cluster (Cisco Unified CM1) through a PRI DMS gateway. The message contains information about partyD. 3. 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 local 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 local 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 across the DMS gateway initiates a consultation transfer (presses Transfer) and dials DN9725550002 deviceE, which is also across the DMS gateway. 9. PartyE answers the call from partyD. 10. The DMS switch sends a PriNotify message to the local cluster (Cisco Unified CM1) through a PRI DMS gateway. The message contains information about partyE. Note the following particularities of call processing that apply in this use case: • In general, when a far-end party on the PSTN side transfers a call, Cisco Unified Communications Manager does not know about the transferring nor transferred-to parties. If the DMS switch or PBX supports PriNotify, however, Cisco Unified Communications Manager receives the PriNotify message when the far-end party changes and can update the far-end information to the recorder. 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=PriDMSGW;x-farendaddr=9725550001>;tag=fromtag1 Desktop Pickup of Mobile Phone Call In this use case for automatic call recording, mobile phone user sends call to desk phone for pickup. The following figure illustrates this use case. 27