Also, to add a note:<br><br>If i move the 4th row in the database to the 14th row (with 14 as the PK id), and delete the fourth row, and reload the load balancer list, the new fourth server receives traffic. IE the first four:<br>
<br>"1";1;"sip:1.2.3.4";"handset=75";"server1"<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">"2";1;"sip:sip:1.2.3.5";"handset=75";"server2"<br>
"3";1;"sip:sip:1.2.3.6";"handset=75";"server3"<br>"5";1;"sip:sip:1.2.3.8";"handset=75";"server5"</blockquote><br>Now receives calls.<br><br>
<div class="gmail_quote">On Thu, Jul 9, 2009 at 3:32 PM, Bobby Smith <span dir="ltr"><<a href="mailto:bobby.smith@gmail.com">bobby.smith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br>I've currently got the load balancer set up with a single group (we'll call it "handset", as our opensips server using the loadbalancing is just acting as a registrar/proxy to a softswitch).<br>
<br>This is how it's defined in the database table:<br><br>"1";1;"sip:1.2.3.4";"handset=75";"server1"<br>"2";1;"sip:sip:1.2.3.5";"handset=75";"server2"<br>
"3";1;"sip:sip:1.2.3.6";"handset=75";"server3"<br>"4";1;"sip:sip:1.2.3.7";"handset=75";"server4"<br>"5";1;"sip:sip:1.2.3.8";"handset=75";"server5"<br>
"6";1;"sip:sip:1.2.3.9";"handset=75";"server6"<br>"7";1;"sip:sip:1.2.3.10";"handset=75";"server7"<br>"8";1;"sip:1.2.3.11";"handset=75";"server8"<br>
"9";1;"sip:1.2.3.12";"handset=75";"server9"<br>"10";1;"sip:1.2.3.13";"handset=75";"server10"<br>"11";1;"sip:1.2.3.14";"handset=75";"server11"<br>
"12";1;"sip:1.2.3.15";"handset=75";"server12"<br>"13";1;"sip:1.2.3.16";"handset=75";"server13"<br><br>When active, it seems the load balancer is only sending to the first 4 servers in the list:<br>
<br>[root@cloud_registrar_lb mnt]# opensipsctl fifo lb_list<br>Destination:: sip:1.2.3.4 id=1<br> Resource:: handset max=75 load=75<br>Destination:: sip:1.2.3.5 id=2<br> Resource:: handset max=75 load=75<br>Destination:: sip:1.2.3.6 id=3<br>
Resource:: handset max=75 load=75<br>Destination:: sip:1.2.3.7 id=4<br> Resource:: handset max=75 load=75<br>Destination:: sip:1.2.3.8 id=5<br> Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.9 id=6<br>
Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.10 id=7<br> Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.11 id=8<br> Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.12 id=9<br>
Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.13 id=10<br> Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.14 id=11<br> Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.15 id=12<br>
Resource:: handset max=75 load=0<br>Destination:: sip:1.2.3.16 id=13<br> Resource:: handset max=75 load=0<br><br>I don't see anything in the log identifying that we're even try to send anything beyond the first 4 servers, and an ngrep confirms that it's essentially balancing messages to just the first four without trying the rest.<br>
<br>Any thoughts? I'm using the 1.5.1 version of the load balancer.<br><br>Thanks,<br><br>Bobby S<br>
</blockquote></div><br>