Not really. The LB module uses internal unique ids for all the LB
destinations it manages. So the probing replies will search back the LB
destination based on this ID -> no chance to mismatch.
Regards.
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
h
If the backend servers are both the same instance then this seems to be the
correct behaviour?
I believe the probing is supposed to be a simple SIP response healthcheck
which applies to the destination globally (i.e. 1.2.3.4 is offline), the
groups are just a way of splitting up resources logicall
Hi,
What OpenSIPS version you have? And as I understand, as configuration,
you do permanent probing to the destinations and the disabling happens
because of this probing ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.c
Hi. I have an interesting issue. We have two OpenSIPS servers with load
balancer (with two different group IDs in the lb table) and we have probing
set correctly and we are using the event, E_LOAD_BALANCER_STATUS, to
capture changes to servers that were probed. But we noticed that we have
the sa
