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
Are you looking ip_free_bind = 1? https://www.kamailio.org/wiki/cookbooks/5.4.x/core
On Mon, Oct 12, 2020 at 5:34 PM Duarte Rocha duarterocha91@gmail.com wrote:
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 sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
How useful that Kamailio can now do this independently!
On 10/13/20 12:48 AM, Sergey Safarov wrote:
Are you looking ip_free_bind = 1? https://www.kamailio.org/wiki/cookbooks/5.4.x/core
On Mon, Oct 12, 2020 at 5:34 PM Duarte Rocha <duarterocha91@gmail.com mailto:duarterocha91@gmail.com> wrote:
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 sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 duarterocha91@gmail.com 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
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 duarterocha91@gmail.com 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 duarterocha91@gmail.com 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 sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi,
I'll try to better clarify my scenario.
I can't use probing in this situation, as my peer won't allow it.
This is my scenario :
SET: { ID: 102 TARGETS: { DEST: { URI: sip:Peer_IP:5060 FLAGS: AX PRIORITY: 0 ATTRS: { BODY: duid=Peer_01;socket=HA_IP_1:5060 DUID: Peer_01 MAXLOAD: 0 WEIGHT: 0 RWEIGHT: 0 SOCKET: HA_IP_1:5060 SOCKNAME: OBPROXY: } RUNTIME: { DLGLOAD: 0 } } DEST: { URI: sip:Peer_IP:5060 FLAGS: AX PRIORITY: 0 ATTRS: { BODY: duid=Peer_02;socket=HA_IP_2:5060 DUID: Peer_02 MAXLOAD: 0 WEIGHT: 0 RWEIGHT: 0 SOCKET: HA_IP_2:5060 SOCKNAME: OBPROXY: } }
In this case, HA_IP_1 is on this machine and HA_IP_2 is on another machine. When dispatcher with loadbalance is called on this scenario, it fails when choosing Peer_02 as destination.
What i propose is Dispatcher removing Peer_02 from the destination list as long as HA_IP_2 isn't present on that machine. Is this possible?
A segunda, 12/10/2020, 15:34, Duarte Rocha duarterocha91@gmail.com 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
you one dispatcher destination failed you can try other
Example https://github.com/2600hz/kazoo-configs-kamailio/blob/master/kamailio/dispat...
Think you can find more examples.
On Thu, Oct 15, 2020 at 2:49 PM Duarte Rocha duarterocha91@gmail.com wrote:
Hi,
I'll try to better clarify my scenario.
I can't use probing in this situation, as my peer won't allow it.
This is my scenario :
SET: { ID: 102 TARGETS: { DEST: { URI: sip:Peer_IP:5060 FLAGS: AX PRIORITY: 0 ATTRS: { BODY: duid=Peer_01;socket=HA_IP_1:5060 DUID: Peer_01 MAXLOAD: 0 WEIGHT: 0 RWEIGHT: 0 SOCKET: HA_IP_1:5060 SOCKNAME: OBPROXY: } RUNTIME: { DLGLOAD: 0 } } DEST: { URI: sip:Peer_IP:5060 FLAGS: AX PRIORITY: 0 ATTRS: { BODY: duid=Peer_02;socket=HA_IP_2:5060 DUID: Peer_02 MAXLOAD: 0 WEIGHT: 0 RWEIGHT: 0 SOCKET: HA_IP_2:5060 SOCKNAME: OBPROXY: } }
In this case, HA_IP_1 is on this machine and HA_IP_2 is on another machine. When dispatcher with loadbalance is called on this scenario, it fails when choosing Peer_02 as destination.
What i propose is Dispatcher removing Peer_02 from the destination list as long as HA_IP_2 isn't present on that machine. Is this possible?
A segunda, 12/10/2020, 15:34, Duarte Rocha duarterocha91@gmail.com 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 sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
When you have detected a failed target, you can update the dispatcher table and then reload dispatchers
On Thu, Oct 15, 2020 at 9:57 PM Sergey Safarov s.safarov@gmail.com wrote:
you one dispatcher destination failed you can try other
Example
https://github.com/2600hz/kazoo-configs-kamailio/blob/master/kamailio/dispat...
Think you can find more examples.
On Thu, Oct 15, 2020 at 2:49 PM Duarte Rocha duarterocha91@gmail.com wrote:
Hi,
I'll try to better clarify my scenario.
I can't use probing in this situation, as my peer won't allow it.
This is my scenario :
SET: { ID: 102 TARGETS: { DEST: { URI: sip:Peer_IP:5060 FLAGS: AX PRIORITY: 0 ATTRS: { BODY: duid=Peer_01;socket=HA_IP_1:5060 DUID: Peer_01 MAXLOAD: 0 WEIGHT: 0 RWEIGHT: 0 SOCKET: HA_IP_1:5060 SOCKNAME: OBPROXY: } RUNTIME: { DLGLOAD: 0 } } DEST: { URI: sip:Peer_IP:5060 FLAGS: AX PRIORITY: 0 ATTRS: { BODY: duid=Peer_02;socket=HA_IP_2:5060 DUID: Peer_02 MAXLOAD: 0 WEIGHT: 0 RWEIGHT: 0 SOCKET: HA_IP_2:5060 SOCKNAME: OBPROXY: } }
In this case, HA_IP_1 is on this machine and HA_IP_2 is on another machine. When dispatcher with loadbalance is called on this scenario, it fails when choosing Peer_02 as destination.
What i propose is Dispatcher removing Peer_02 from the destination list as long as HA_IP_2 isn't present on that machine. Is this possible?
A segunda, 12/10/2020, 15:34, Duarte Rocha duarterocha91@gmail.com 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 sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi Yufei,
I've tried to do that but unfortunately i'm facing a weird issue.
I have nodes on probing mode, but dispatcher only sends probing via one of the sockets and then, in some cases, wrongfully updates the status of the elements of the pair.
I've even tried to manually disable one of the Dipsatcher destinations, first the one with the VIP and then the other, and Kamailio still sends requests via one of the sockets, usually the second in the list. This only happens if i have two destinations with same IP but different sockets. In scenarios with different IP and different sockets it all works correctly.
I'm currently on Kamailio v5.4.1. What version are you on? Any special parameter to make that work?
Best Regards,
A segunda, 12/10/2020, 15:34, Duarte Rocha duarterocha91@gmail.com 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
-
Alex Balashov -
Duarte Rocha -
Sergey Safarov