Jump to: navigation, search

Call Recording

This section describes how call recording works.


Callinitiated.png

There are four ways call recording can be initiated. Once started, the recording process is the same, regardless of how it was initiated.

One of the following initiates recording:

  1. SIP Server initiates recording itself, for example, because a DN is configured to always be recorded.
  2. SIP Server informs third party Call Recording of a call with a DN that Call Recording supports. Third party Call Recording has a recording rule for the DN. Third party Call Recording evaluates the rule, determines that the DN must be recorded and requests recording by sending the T-lib request, TrequestPrivateService, to SIP Server.
  3. A third party, for example an agent desktop, requests call recording by sending the T-lib request, TrequestPrivateService, to SIP Server.
  4. A recording can be initiated by a Routing Strategy (extension record=source in TrouteCall).


Sipserver.png

5. Using media control, SIP Server invites Media Server to replicate the RTPs (two invites, one for each RTP stream).



Mediaserver.png

6. The Media Server replicates the RTP streams and:

  • Sends the SIP invite messages to the Call Recording server (two invite messages, one for each RTP stream).
  • Sends the RTPs to the Call Recording Server.

7. Recording starts. 8. The Call Recording server requests additional information, such as user attached data with T-Lib.

Recordingstarts.png

9. At any time the Call Recording Server or a third party (for example, the agent desktop) can use a TrequestPrivateService message for pause, resume, start and stop.

Recordingends.png

10. SIP messages from each stream indicate that the call has ended. The Call Recording Server stops recording.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 22 May 2013, at 06:33.