Hello,
ok, good that it works now. You should still be able to take them from
headers with $ci and $ft, but they have to be provided in the parameter
of start_recording()/stop_recording() if used with a non-SIP message.
Cheers,
Daniel
On 05.05.21 18:20, Володимир Іванець wrote:
> Hello,
>
> I
Hello,
I did not. I misunderstood your previous message. Now I called
start_recording() and stop_recording() with *call-id* and *from-tag* flags
and everything worked fine.
Thank you very much!
ср, 5 трав. 2021 о 16:46 Daniel-Constantin Mierla пише:
> Hello,
>
> do you pass "from-tag=xyz" to
Hello,
do you pass "from-tag=xyz" to the start_recording() function?
Cheers,
Daniel
On 05.05.21 13:51, Володимир Іванець wrote:
> Hello Daniel,
>
> Sorry, I was out of the office and could make a test only now. As you
> told, the HTTP request is now processed differently. Unfortunately, I
> can
Hello Daniel,
Sorry, I was out of the office and could make a test only now. As you told,
the HTTP request is now processed differently. Unfortunately, I can no
longer start call recording. I tried the following options and got the
"rtpp_function_call(): can't get From tag" error message each
I pushed a commit to master branch that should make it work to use the
function for non-SIP message processing, by giving call-id=... and
from-tag=... via flags parameter -- these two attributes seemed to be
used by expecting to be set, even if the rtpengine application may
ignore one of them.
If
I looked in the code and indeed it first takes the values from headers
for Call-Id, To (tag), From (tag), failing if the headers are not found,
but then it updates the values from the flags parameter. So the call-id
can be anything in the headers if you provide it as "call-id=xyz" parameter.
I run Kamailio with debug=3 and Rtpengine with LOG_LEVEL=6.
Rtpengine logs offers, answers and deletes but there is nothing when I
trigger *start_recording* with HTTP request. Below is the full Kamailio log
for the request. It looks to be failing right on the *start_recording*
function and I
Ohhh, blindly missed the assignment before. You should run both kamailio
and rtpengine with higher debug level and see if you get any hints from
the log messages.
Cheers,
Daniel
On 29.04.21 11:51, Володимир Іванець wrote:
> Hello Daniel,
>
> That is correct. My /$var(call_id)/ variable contains
Hello Daniel,
That is correct. My *$var(call_id)* variable contains concatenation of the
"call-id=" string and a Call-Id value.
*Apr 27 18:25:00 test /usr/sbin/kamailio[5347]: DEBUG:
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,
>
>
Hello Richard,
Thank you very much for the suggestion! I will give it a try.
ср, 28 квіт. 2021, 20:00 користувач Richard Fuchs пише:
> 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
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
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
13 matches
Mail list logo
