Hello,
Is there any way to advertise a different IP Address in the Record-Route
header individually per branch?
I have a setup here - where Kamailio is listening on 2 different
interfaces: Local IP and External IP. At the moment if the packet is coming
through the internal interface - I'm checkin
Have you tried calling *t_save_lumps()* before relaying, even before RR?
On Thu, Jun 16, 2022 at 7:59 AM Ilie Soltanici wrote:
> Hello,
>
> Is there any way to advertise a different IP Address in the Record-Route
> header individually per branch?
>
> I have a setup here - where Kamailio is liste
Hello,
Thank you, added it now - still the same, unfortunately.
Regards,
On Thu, 16 Jun 2022 at 13:29, Sergiu Pojoga wrote:
> Have you tried calling *t_save_lumps()* before relaying, even before RR?
>
> On Thu, Jun 16, 2022 at 7:59 AM Ilie Soltanici
> wrote:
>
>> Hello,
>>
>> Is there any way
It only work for request route.Le 16 juin 2022 14:19, Ilie Soltanici a écrit :Hello,Thank you, added it now - still the same, unfortunately.Regards,On Thu, 16 Jun 2022 at 13:29, Sergiu Pojoga wrote:Have you tried calling t_save_lumps() before relaying, even before RR?On Thu, Ju
Have you tried just *record_route()* with *enable_double_rr* option
enabled? All things considered, RR should take care of it all by itself,
per branch.
A script snippet could help.
On Thu, Jun 16, 2022 at 10:05 AM Patrick Karton
wrote:
> It only work for request route.
>
> Le 16 juin 2022 14:1
I just did this quick POC test which worked as expected, it added a single
RR with public advertised and double RR with both public and private
advertise for the branch that routes to a private interface.
Prerequisites:
- mhomed=1
- modparam("rr", "enable_double_rr", 1)
- listen=YOUR_PUB
Hi,
On 6/15/22 11:46, Daniel-Constantin Mierla wrote:
Hello,
good news, indeed! Thanks to all involved!
Not being very familiar with all Debian releasing policies, does that
mean the next Debian stable (v 12) will ship it? Or is it going to take
one more release cycle, to go from Debian Unsta