So issue with the source IP used for dispatcher probing? If Kamailio sends OPTIONS from own IP (not shared VIP), then all will be good?
On Tue, Oct 13, 2020 at 1:17 PM Duarte Rocha <[email protected]> wrote: > Hey. > > I'm already using ip_free_bind, but that is not my problem. > I cannot use probing on those peers and I need to know if Dispatcher can > be able to not include those peers in the destination list since their > socket doesn't belong to the machine and include the peers in the > destination list in case the IP jumps to that machine. > > Cheer > > A segunda, 12/10/2020, 15:34, Duarte Rocha <[email protected]> > escreveu: > >> Greetings, >> >> I have two machines with Kamailio in a HA setup with replicated DB. For >> simplicity let's say each machine has one HA IP and that IP can jump to the >> other machine in case something happens (kamailio stopping, etc). >> >> I'm using Dispatcher with load balance configuration. I have Dispatcher >> configured so that each peer has one instance for socket with HA IP 1 and >> HA IP 2. >> >> In order for this to work correctly on the load balance scenario I must >> disable via RPC command the peer which has the socket that doesn't belong >> to the machine. I also must do it every time the IP jumps back and forth, >> which adds complexety to my system. >> >> Does Dispatcher has any sort of help on this? It could not include peers >> with sockets IPs that don't belong to the machine in the destination set, >> for example. Is this possible? >> >> I could also work with failover support but i would rather avoid having >> so many failovers. >> >> Best Regards,A >> > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
