/mcpCisco Unified Communications Manager terminates recording of the customer voice by sending a BYE message to the recorder through a SIP trunk. 10. PartyB calls partyD (another far-end party = agent in local cluster). 11. PartyD answers the call from partyB. 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 agent voice. 13. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyB IP phone for the 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 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 partyA (customer) voice through a SIP trunk. The agent IP phone starts to fork the customer voice stream to the recorder. 16. 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 partyD IP phone for the agent voice. 17. Cisco Unified Communications Manager makes the second recording call to the BIB of the partyD IP phone for the customer voice. 18. The recorder receives and answers the recording call setup messages that are sent from Cisco Unified Communications Manager for the partyD (agent) voice through a SIP trunk. The agent IP phone starts to fork the agent voice stream to the recorder. 19. The recorder receives and answers the recording call setup messages that are sent from Cisco Unified Communications Manager for the partyA (customer) voice through a SIP trunk. The agent IP phone starts to fork the customer voice stream to the recorder. 20. PartyB completes the transfer. 21. 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. 22. Cisco Unified Communications Manager terminates recording of the partyA (customer) voice by sending a BYE message to the recorder through a SIP trunk. 23. As party D is connected to the far-end party A, Cisco Unified Communications Manager restarts the recording. Note the following particularities of call processing that apply in this use case: • When the near-end partyB presses Transfer, the call is implicitly put on hold, and the recording session with partyA terminates. • When partyB dials partyD and partyD answers, a new recording session starts for partyD. • When partyB completes the transfer, partyD and partyA get connected and the recording is restarted as the information about new far-end party A is updated. Generally, each time an agent puts a recording call on hold, the current recording session terminates. Each time the agent invokes a supplementary service, such as Transfer or hold, the call is implicitly put on hold. Each time the far-end information changes, Cisco Unified Communications Manager restarts the recording. Note the header information of the INVITE messages from step5, step14, step18. The SIP header enhancement feature adds the information in bold text to the message headers. 14