[SR-Users] start_recording and stop_recording inside event_route[xhttp:request]
Daniel-Constantin Mierla
miconda at gmail.com
Thu Apr 29 08:58:33 CEST 2021
Hello,
related to the initial config snippet example, the call-id is expected
to be provide as a named flag, like:
start_recording("call-id=$var(call_id)");
See the readme of the rtpengine module for more details.
Cheers,
Daniel
On 29.04.21 08:23, Володимир Іванець wrote:
> Hello Richard,
>
> Thank you very much for the suggestion! I will give it a try.
>
> ср, 28 квіт. 2021, 20:00 користувач Richard Fuchs <rfuchs at sipwise.com
> <mailto:rfuchs at sipwise.com>> пише:
>
> On 28/04/2021 10.53, [ EXT ] Володимир Іванець wrote:
>> Hello!
>>
>> I'm testing call recording with Rtpengine. It works fine when the
>> "record-call=on" 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 =~ "^/CALL_RECORD_START/") {/
>> / $var(call_id) = /"call-id=" + /$(hu{s.select,2,/});/
>> xlog("L_DBG", "$var(call_id)");
>> / start_recording($var(call_id));/
>> / /exit;
>> / }/
>>
> If you have to reason to go through Kamailio for this, you can
> simply trigger the command from any other external application.
> There's a sample script included in the repo that can be used for
> this purpose directly (making use of the Perl module that is also
> included):
> https://github.com/sipwise/rtpengine/blob/master/utils/rtpengine-ng-client
> <https://github.com/sipwise/rtpengine/blob/master/utils/rtpengine-ng-client>
>
> There's also a nodejs client that I'm aware of:
> https://github.com/davehorton/rtpengine-client
> <https://github.com/davehorton/rtpengine-client>
>
> Or you can hand-roll the request and talk to rtpengine via HTTP or
> Websocket for example.
>
> Cheers
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> * sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
> Important: keep the mailing list in the recipients, do not reply
> only to the sender!
> Edit mailing list options or unsubscribe:
> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> * sr-users at lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the sender!
> Edit mailing list options or unsubscribe:
> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20210429/5417d022/attachment.htm>
More information about the sr-users
mailing list