Hi all,
I am using Kamailio 5.8.1 on a Debian 12 machine with topos and topoh
hiding the topology.
I have observed with modparam("topos", "mask_callid", 1), in-dialog
requests are relayed with the incorrect caller-id.
In the scenario, A calls B. The call is set up and the call-id for the
B-Leg
Hi all,
I am using Kamailio 5.7.4 on a Debian 12 machine. I used ansible to
template some files, and a newline was omitted at the end of the uacreg
table due to a templating issue.
This caused kamailio to crash on start up, with the error:
20(27) CRITICAL: [core/pass_fd.c:281]: receive_fd():
After digging through old mailing posts I've been able to resolve this by
applying the changes in the BRANCH route. This fixes the corruption,
although the logs still show a warning for applying it twice.
Cheers
On Thu, 7 Mar 2024 at 09:23, Benoit Panizzon wrote:
> Hi Matthew
>
> > However in
Hi all,
I am using uac_replace_to to replace the TO header on requests. I
understand it can only be called once per message and the recommendation is
to store the updated value in a pvar and apply it in the branch route.
However in my scenario I wish to first try one endpoint and then if it gets
Hi Richard,
Thanks for the tip, I had indeed overlooked the return value.
Cheers
Matthew
On Tue, 5 Mar 2024 at 05:34, Richard Chan wrote:
> In the method can you put
>
> return 1
>
> at the end. KEMI python is very strict on an int return value.
>
> On Tue, 5 Mar 2024,
Hi all,
I am using Kamailio 5.7.4 on a Debian 12 machine, with a Python Kemi based
config. I am seeing some intermittent failures when accessing an instance
variable within a function called by rtimer.
I'm using the rtimer module with the following parameters:
modparam("rtimer", "timer",
> I have this setup where one side is TLS and the other UDP. Normally this
works fine, but we have this provider sending sips
In theory SIPS should be TLS end-to-end. Some UAs will reject the call or
misbehave if it's not.
I'm not sure this is the issue you're experiencing but it's worth keeping
> Hello,
>
>
>
> you are running out of private memory. Please try to increase the PKG
> memory pool (e.g. by changing /etc/default/kamailio or similar). You can
> verify with “ps aux”.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
&g
; memory pool (e.g. by changing /etc/default/kamailio or similar). You can
> verify with “ps aux”.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
&
sers] Re: TOPOS + Forcing the send socket
>
>
>
> In the header of the topic you talking about topos, but inside the
> messages you talking about topoh.
>
> They are 2 different modules. If you usr them together - they can
> conflictin case how they affect message. Try use or just to
Hi all,
I've dug into this a bit more. Firstly I enabled debug logs and spotted the
following record-route header being loaded from redis:
21(28) DEBUG: PY3 {ACK}: topos_redis [topos_redis_storage.c:1079]:
tps_redis_load_dialog(): r[5]: s[,]
127.0.0.8 is the wrong IP which explains why the ACK
Hi all,
I am using Kamailio (5.7.2, Debian 11, Python KEMI) in a
mutli-homed environment with the topos module to hide the topology.
I have noticed that when I use `set_send_socket` or `$fsn` to force the
socket it's sent from, it breaks topos and the ACK is not proxied to the
other leg of the
12 matches
Mail list logo
