<div dir="ltr"><div>When you have detected a failed target, you can update the dispatcher table and then reload dispatchers</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 15, 2020 at 9:57 PM Sergey Safarov <<a href="mailto:s.safarov@gmail.com">s.safarov@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">you one dispatcher destination failed you can try other<div><br></div><div>Example</div><div><a href="https://github.com/2600hz/kazoo-configs-kamailio/blob/master/kamailio/dispatcher-role-5.4.cfg#L205-L222" target="_blank">https://github.com/2600hz/kazoo-configs-kamailio/blob/master/kamailio/dispatcher-role-5.4.cfg#L205-L222</a><br></div><div><br></div><div>Think you can find more examples.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 15, 2020 at 2:49 PM Duarte Rocha <<a href="mailto:duarterocha91@gmail.com" target="_blank">duarterocha91@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hi, <div dir="auto"><br></div><div dir="auto">I'll try to better clarify my scenario.</div><div dir="auto"><br></div><div dir="auto">I can't use probing in this situation, as my peer won't allow it.</div><div dir="auto"><br></div><div dir="auto">This is my scenario : </div><div dir="auto"><br></div><div dir="auto">SET: {</div><div dir="auto"> ID: 102</div><div dir="auto"> TARGETS: {</div><div dir="auto"> DEST: {</div><div dir="auto"> URI: sip:Peer_IP:5060</div><div dir="auto"> FLAGS: AX</div><div dir="auto"> PRIORITY: 0</div><div dir="auto"> ATTRS: {</div><div dir="auto"> BODY: duid=Peer_01;socket=HA_IP_1:5060</div><div dir="auto"> DUID: Peer_01</div><div dir="auto"> MAXLOAD: 0</div><div dir="auto"> WEIGHT: 0</div><div dir="auto"> RWEIGHT: 0</div><div dir="auto"> SOCKET: HA_IP_1:5060</div><div dir="auto"> SOCKNAME:</div><div dir="auto"> OBPROXY:</div><div dir="auto"> }</div><div dir="auto"> RUNTIME: {</div><div dir="auto"> DLGLOAD: 0</div><div dir="auto"> }</div><div dir="auto"> }</div><div dir="auto"> DEST: {</div><div dir="auto"> URI: sip:Peer_IP:5060</div><div dir="auto"> FLAGS: AX</div><div dir="auto"> PRIORITY: 0</div><div dir="auto"> ATTRS: {</div><div dir="auto"> BODY: duid=Peer_02;socket=HA_IP_2:5060</div><div dir="auto"> DUID: Peer_02</div><div dir="auto"> MAXLOAD: 0</div><div dir="auto"> WEIGHT: 0</div><div dir="auto"> RWEIGHT: 0</div><div dir="auto"> SOCKET: HA_IP_2:5060</div><div dir="auto"> SOCKNAME:</div><div dir="auto"> OBPROXY:</div><div dir="auto"> }</div><div dir="auto"> }</div><div dir="auto"> </div><div dir="auto">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. </div><div dir="auto"><br></div><div dir="auto">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?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">A segunda, 12/10/2020, 15:34, Duarte Rocha <<a href="mailto:duarterocha91@gmail.com" target="_blank">duarterocha91@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Greetings, <div dir="auto"><br></div><div dir="auto">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).</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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?</div><div dir="auto"><br></div><div dir="auto">I could also work with failover support but i would rather avoid having so many failovers.</div><div dir="auto"><br></div><div dir="auto">Best Regards,A</div></div>
</blockquote></div>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div>
</blockquote></div>