15 Feb
2019
15 Feb
'19
9:23 p.m.
You are AWESOME!
That's exactly what happened, the call went to first asterisk, that one
sent it further to the client trunk which responded with SIP 500,
kamailio sent it to the next one, sip 500 again and thus blocking both
asterisks from receiving any further traffic.
Thank you very very very much!
Cris
---
Cristian Livadaru
LcX IT Solutions
On 15 Feb 2019, at 18:19, Daniel Tryba wrote:
On Fri, Feb 15, 2019 at 05:13:21PM +0100, Cristian
Livadaru wrote:
Hi,
I have a Kamailio running as Load Balancer and it works great but
since a
couple of weeks I kept noticing 404s in Homer and when looked into it
they
came from Kamailio.
...
The two asterisks behind it seem fine and I
can???t really see why
this
started happening. Also I thing that returning 404 might be
misleading,
wouldn???t it be better if I would return 503 instead?
That is up to you to decide. I'd suggest a 480.
I enabled debugging in Kamailio but can???t
really seem to notice
anything
wrong here:
...
Find out why the dispatcher endpoints are out of order according to
kamailio (look at the OPTIONS in homer).
Also you set a destination inactive if 1 request to a backend fails
(dsmakr ip). You might want to reconsider, it might be the cause of
your
problems. Imagine a call is coming in to a partially deprovisioned
number, the asterisk answers with a failure, gets marked as inactive.
Dispatcher retries to the other one and that also fails and gets
marked
as inactive. Any call that comes in before the probing enables the
backends will fail immediatly.
So also look at INVITEs just before the problem in homer.
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users