McDewey

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

Page 19

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

PartyA (far-end party = customer in local cluster) calls partyB (near-end party = agent). 2. PartyB (near-end party = agent in local cluster) answers the call. 3. 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. 4. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyB (agent) IP phone for the customer voice. 5. 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. 6. 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 partyA (customer) voice stream to the recorder. 7. PartyB, the near-end party, initiates a conference by pressing Confn. When the near-end party makes a consultation call for a conference participant, the near-end party call automatically gets put on hold. 8. Cisco Unified Communications Manager terminates recording of the partyB (agent) voice (the consultation call) by sending a BYE message to the recorder through a SIP trunk. 9. Cisco Unified Communications Manager terminates recording of the partyA (customer) voice by sending a BYE message to the recorder through a SIP trunk. 10. Near-end partyB dials DN1100 partyC. 11. PartyC answers the call. 12. Because the agent line appearance is configured for automatic recording, the recording session for the media streams automatically gets triggered. Cisco Unified Communications Manager makes a recording call to the built-in bridge (BIB) of the partyB IP phone for the near-end (agent) voice. 13. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyB IP phone for the far-end (customer) voice. 14. The recorder receives and answers the recording call setup messages that are sent from Cisco Unified Communications Manager for the partyB (agent) voice through a SIP trunk. The agent IP phone starts to fork the near-end (agent) voice stream to the recorder. 15. The recorder receives and answers the recording call setup messages that are sent from Cisco Unified Communications Manager for the far-end (customer) voice through a SIP trunk. The agent IP phone starts to fork the customer voice stream to the recorder. 16. PartyB completes the consultation conference by pressing Confn. All parties connect to the conference bridge (CFB_2). 17. Cisco Unified Communications Manager initiates recording for the agents. Note the following particularities of call processing that apply in this use case: • Near-end party creates a conference; the first recording session gets torn down. • Connection of the consultation call re-establishes the recording session. Note the header information of the INVITE messages from step5 and step14. The SIP header enhancement feature adds the information in bold text to the INVITE message headers. 19