From 5272f4e4e302e44ad870bd8b8936c2517848c0ca Mon Sep 17 00:00:00 2001 From: Daniel-Constantin Mierla Date: Mon, 28 Aug 2017 12:25:09 +0200 Subject: [PATCH] rtpengine: documented the flag for call recording - reported by GH #1221 --- src/modules/rtpengine/doc/rtpengine_admin.xml | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/src/modules/rtpengine/doc/rtpengine_admin.xml b/src/modules/rtpengine/doc/rtpengine_admin.xml index 4a7272629a3..15355bb8c0b 100644 --- a/src/modules/rtpengine/doc/rtpengine_admin.xml +++ b/src/modules/rtpengine/doc/rtpengine_admin.xml @@ -2036,7 +2036,7 @@ rtpengine_offer(); no-redis-update - this flag can be used by Kamailio in order to tell rtpengine not to persist the call into Redis upon receiving offer/answer() - control commands. If flag is not set, default action is rtpengine persists call + control commands. If flag is not set, default action is rtpengine persists call to redis. @@ -2273,7 +2273,16 @@ rtpengine_offer(); in the Sipwise rtpengine proxy. This is especially useful when the first call leg is handled by some rtpengine machine while the second call leg is handled by other rtpengine machine. + + record-call=on - instructs RTPEngine to record the session. Use + it in rtpengine_offer() to start recording immediately and save the call metadata, + as alternative to start_recording(). + + + Check also the documentation of RTPEngine, these flags are documented there as well: + https://github.com/sipwise/rtpengine. + @@ -2466,8 +2475,11 @@ rtpengine_manage(); start_recording() - This function will send a signal to the &rtp; proxy to record - the &rtp; stream on the &rtp; proxy. + This function will send a signal to the &rtp; relay to record + the &rtp; stream flowing through it. See also the option + record-call=on for rtpengine_manage()/rtpengine_offer(), + which offers an alternative for call recording, saving also call + metadata from SDP. This function can be used from REQUEST_ROUTE and ONREPLY_ROUTE.