Hi Alex,
That is working, however, on subsequent messages in the dialog (e.g., ACK,
INFO, BYE) the proxy tries the failed destination for each message. Eventually
it gets to the right place, but, is there a way to delete the failed
destination from the XAVP so this doesn't happen? Or just to fo
Hi,
The documentation for the `enum` module says:
"Finally, enum_query associates a q value with each new URI based on the
of the corresponding NAPTR record."
Then just read this whole section of the TM module docs. :-)
https://kamailio.org/docs/modules/5.6.x/modules/tm.html#tm.serial_forking
Maybe there is a memory leak or maybe the system is not provisioned
with enough memory to cope with the traffic. Increase the amount of
allocated memory and monitor it, see how it evolves over time.
Regards,
Ovidiu Sas
On Tue, Dec 13, 2022 at 6:14 AM George Diamantopoulos
wrote:
>
> Hello all,
>
I have the following basic script:
request_route{
record_route();
$var(enumres) = enum_query();
switch( $var(enumres) ) {
case -1:
xlog("enum_query lookup failure - To URI $tU");
sl_reply("503",
Hello,
difficult to say, it could be also some random memory error or virtual/physical
hardware issue. Are you seeing more error related to that, maybe it’s a memory
leak? Make probably sense to observe it further. If it happens again, a diff
between the rtpengine in 5.6.1 and 5.6.2 might get m
Hello,
regarding limiting the number of gateways retries, you can use different
failure routes (e.g. jump from first to second and then stop), you can keep an
counter, or probably just rely on ds_next_dst() reaching the end of available
gateways in the XAVP (did not checked code).
Cheers,
Hen
Hello,
not that tomorrow, Dec 14, 2022 starting after 09:00UTC (10:00Berlin),
is planned some maintenance work on kamailio.org server. It will be
unavailable from time to time, hopefully not for long time.
Affected services:
- web site
- mailing lists
- wiki site (alternative use the githu
Hi Henning/All,
After some digging we realized the system was already retrying thanks to this
block on kamailio.cfg
# Try next destionations in failure route
failure_route[RTF_DISPATCH] {
if (t_is_canceled()) {
exit;
}
# next DST - only for 500 or local timeout
if (t_chec
Hi,
The destination address and port match with what is expected. I don't have
policy routing nor network namespaces. I do have containers, including for
Kamailio, but all are using host networking. I am also using gre tunnels
which might be causing the issue. I am still investigating that
pos
On 13/12/2022 09.04, [EXT] Michel Pelletier wrote:
Hello,
Thank you for your reply. I checked the versions and they look good.
xt_RTPENGINE is 11.1.1.3 and the daemon is 11.1.1.3-1~bpo11+1.
Looking at /proc/rtpengine/0/list I see the packet and byte counters
incrementing normally with 0 er
Hello,
Thank you for your reply. I checked the versions and they look good.
xt_RTPENGINE is 11.1.1.3 and the daemon is 11.1.1.3-1~bpo11+1. Looking at
/proc/rtpengine/0/list I see the packet and byte counters incrementing
normally with 0 errors. In wireshark, capturing on any, I see the stream
c
> On Dec 13, 2022, at 3:14 AM, Daniel-Constantin Mierla
> wrote:
>
> change of cseq results in a different transaction, there should be two
> at the same time for a short interval. Try to see if debug=3 offers any
> hints.
Makes sense. What I'm wondering is why the ACK for the negative reply
Hi Rick
A quick update. Now it works. I guess the newly added DNS hostname was
not yet fully propagated to all DNS caches.
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G-Leiter Commerce Kunden
__
Zurlindenstrass
Hi Rick
> Add the fqdn as the alias after the listen.
>
> listen=tcp:127.0.0.1:5060 advertise "sip.dns.example.com":5060
Thank you for pointing me the right direction.
I just also read:
http://www.kamailio.org/wiki/cookbooks/devel/core#listen
But I don't get the hostname added.
I attempted (x
Hello all,
I'm testing out release 5.6.2 on one production kamailio instance, and
today our monitoring system triggered an alarm for lack of disk space on /.
Indeed, kamailio.log started growing at an alarming rate at some point.
At about the same time disk space started being depleted, the follo
Hello Benoît,
Add the fqdn as the alias after the listen.
listen=tcp:127.0.0.1:5060 advertise "sip.dns.example.com":5060
Best
Rick
> On 13. Dec 2022, at 10:45, Benoit Panizzon wrote:
>
> Hi Folks
>
> We use two 'core' instances and two 'registrar' instances.
>
> The pairs sync their informa
Hi Folks
We use two 'core' instances and two 'registrar' instances.
The pairs sync their information (Dialogues + Locations) via DMQ.
But I noticed that they record the Via and Record-Routes by IP
addresses. So I guess if one fails, signaling would not automatically
switch to the remaining host
Hi Lars,
this should be the relevant check: „sr_dst_max_branches>=MAX_BRANCHES_LIMIT“.
So, it should be 32, biggest value is then 31. I’ve added some more logging to
the git master branch to also log the maximum value and verified it.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.d
Hello,
change of cseq results in a different transaction, there should be two
at the same time for a short interval. Try to see if debug=3 offers any
hints.
For clarification: do you need to do authentication two times? Second
time with pv function?
Cheers,
Daniel
On 12.12.22 21:53, Alex Balash
Hello,
do not reply to Digest messages on the mailing list, there is no value
from knowledge base, no easy reference what this discussion is about.
If you want to engage in discussions on the mailing list, subscribe
normally and respond to the individual messages. Digest subscriptions
are useful
20 matches
Mail list logo
