Thanks for the feedback.
It's tricky, alright, making all of these things work together.
Asterisk should not be re-writing the RR header fields, alright. At
least you found a solution. I can't think of anything better than
that, if it works for you.
James
On Wed, 3 May 2023 at 17:07, Dr. Barabás
Hi James,
thanks for the reply. Yes, record_route() is used in INVITE request.
Meanwhile I found the cause I think here:
https://community.asterisk.org/t/asterisk-rewrites-record-route-header-with-incorrect-tcp-port/91202
So the Record-Route header contains kamailio’s IP and listening TLS port
If the 200-OK to client A also contains Record-Route header fields,
then the routing of the ACK from client A should be done using that
route, not using the internal IP address of asterisk.
Are you using record_route() function from the rr module?
James
On Wed, 26 Apr 2023 at 09:20, Péter Dr.
Hello,
On 2/5/23 12:10, Daniel-Constantin Mierla wrote:
[...]
Somehow inspired from Debian, my first idea would be to create a
"x.y-backports" branch, where "x.y" is the branch for the stable release
series. For example, with 5.6 release series built from branch "5.6",
there could be
> On 2 May 2023, at 12:10, Daniel-Constantin Mierla wrote:
>
> Hello,
>
> during past on-site/online devel meetings as well as on mailing lists or
> tracker, there were various discussions around the idea or requests to
> make new features available quicker to stable branches.
>
> Of
Hello,
the sip3.txt contains just a SIP message, nothing really special about it.
Cheers,
Henning
From: Patrick Wakano
Sent: Mittwoch, 3. Mai 2023 08:02
To: mico...@gmail.com
Cc: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Re: Clarification of 'return false' behaviour
Thanks
Thanks Henning and Daniel for taking the time to check this out!
I will double check my env but anyway will review my script and follow
Daniel's recommendations!
Hennig, would you be able to disclose the contents of your /root/sip3.txt
file? It really got my interest in this nc usage!
Appreciate
