From volodyaivanets@gmail.com Wed Apr 28 16:54:00 2021 From: =?utf-8?b?0JLQvtC70L7QtNC40LzQuNGAINCG0LLQsNC90LXRhtGM?= To: sr-users@lists.kamailio.org Subject: [SR-Users] start_recording and stop_recording inside event_route[xhttp:request] Date: Wed, 28 Apr 2021 17:53:47 +0300 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1858035153==" --===============1858035153== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello! I'm testing call recording with Rtpengine. It works fine when the "record-call=3Don" flag is added to the *rtpengine_offer* or *start_recording= * is used in the *request_route*. But I was wondering if the call recording can be managed by a separate application. So I add the following lines to the *event_route[xhttp:request]* and triggered it with an HTTP request after the call was established. The call-id value was taken from the Rtpengine log and sent with the request. * if ($hu =3D~ "^/CALL_RECORD_START/") {* * $var(call_id) =3D *"call-id=3D" + *$(hu{s.select,2,/});* xlog("L_DBG", "$var(call_id)"); * start_recording($var(call_id));* exit; * }* In this case, Kamailio will log errors and will not send the Rtpengine command to start call recording. *Apr 27 18:25:00 test /usr/sbin/kamailio[5347]: DEBUG: