Hello,
this is the day for v5.5.0 -- as usual when a release is prepared, any
commit to branch 5.5 should be announced to sr-dev mainling list or
irc/matrix channels and wait for ack, in order to avoid packaging
conflicts. Once the announcement is out, commits can go in branch 5.5 as
usual.
Hello,
do you track both legs of the call in kamailio? From freeswitch comes
back a completely new call.
Cheers,
Daniel
On 04.05.21 16:59, David Villasmil wrote:
> Hello guys,
>
> I'm using the dialog module, params are:
>
> # - dialog params -
> modparam("dialog", "db_mode", 0)
>
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
Hello,
are you running the latest version in the X.Y series? Likely you have a
version with an issue that was fixed, iirc.
Cheers,
Daniel
On 05.05.21 17:32, Ilie Soltanici wrote:
> Hello,
>
> No, that's not the case, see below the INVITE sent to the branch:
>
> INVITE
Hello,
the CANCEL to be sent is generated locally by tm module from the INVITE
that was sent on the branch, so the errors is actually about a duplicate
To header in that INVITE. Check it on the network to see if that's the case.
Cheers,
Daniel
On 05.05.21 16:25, Ilie Soltanici wrote:
> Hello,
>
Hello,
No, that's not the case, see below the INVITE sent to the branch:
INVITE sip:123456789@1.2.3.4:5060;transport=UDP SIP/2.0
Record-Route:
Via: SIP/2.0/UDP 1.2.3.4:5060
;branch=z9hG4bK0f41.5079ae8da835958ee58ca1e8a4eb057b.0
Via: SIP/2.0/UDP 192.168.1.10:40769
Hello,
We are having an issue here where Kamailio is complaining about duplicate
To header, while in the SIP Packet there is just one. See below the log
message:
DEBUG: tm [t_msgbuilder.c:391]: build_local_reparse(): duplicate To header
ERROR: tm [t_msgbuilder.c:531]: build_local_reparse():
Kamailio v5.5.0 is out – it comes with 6 new modules and a considerable
set of improvements touching again more than 80 existing modules.
You can read detailed release notes at:
* https://www.kamailio.org/w/kamailio-v5-5-0-release-notes/
Many thanks to all developers and community members
Hello,
Yes, initially I was trying with version 5.4.5, then I upgraded to the
latest version from 5.5 branch - but this didn't fix the issue.
version: kamailio 5.5.0 (x86_64/linux) d4c1a1
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE,
USE_MCAST, DNS_IP_HACK,
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,
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,
can you try the TOH header scenario with any of latest 5.4, 5.5 or
master branches? I just pushed a commit that should fix it.
Cheers,
Daniel
On 05.05.21 18:32, Ilie Soltanici wrote:
> Hello,
>
> Thank you Daniel for looking into this, I think I found the problem
> and it was in the
Hello,
hmm, 5.4.5 should have been also good, being the last in 5.4.x series,
with the fix that I was thinking of. I will look at the code.
Cheers,
Daniel
On 05.05.21 17:56, Ilie Soltanici wrote:
> Hello,
>
> Yes, initially I was trying with version 5.4.5, then I upgraded to the
> latest
Hello,
Thank you Daniel for looking into this, I think I found the problem and it
was in the header:
*TOH: 123456789*
For some reason kamailio parsed it as a "To" header, by removing this
header the Cancel message was delivered successfully out.
Thank you.
On Wed, 5 May 2021 at 17:28,
15 matches
Mail list logo
