[OpenSIPS-Users] Unable to make the load balancer work

[Maysoon Aaziz Alduwais]

Hello Mr. Paiu & Mr. Khamis,

Thank you both for your instant responses.


I don't know if the packets reached the balancer but I don't think so.

Because when I compiled the load_balancer.cfg it gives me the following error:

[2920] ERROR: core: yyparse: module 'mi_xmlrpc.so' not found.

Then I search for it in my computer but I couldn't found it. I found only 'mi_xmlrpc.c' , 'mi_xmlrpc.h', and 'mi_xmlrpc.xml'

Thank you,

________________________________________
From: users-bounces at lists.opensips.org [users-bounces at lists.opensips.org] On Behalf Of Vlad Paiu [vladpaiu at opensips.org]
Sent: Wednesday, November 09, 2011 4:45 PM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] Unable to make the load balancer work

Hello,

Do the actual SIP packages reach the load balancer ?
Or are the SIP packages reaching it, but it does not forward them to
your proxies ?

Regards,

Vlad Paiu
OpenSIPS Developer


On 11/09/2011 03:03 PM, M.Abdulaziz wrote:
> Hello Everyone,
>
> I 'm  trying to run the load balancer module but I couldn't make it work
> properly. I know it is due to my lack of experience. But I couldn't figure
> out where is my mistake, can any one help please...I implemented it as
> follows:
>
>
>
>
>                                  >  Proxy1>--->UAS1
> UAC-->LoadBalancer>
>                                  >  Proxy2>--->UAS2
>
> Where:
>
> sipp(UAC):192.168.1.70:5062
> opensips(Load Balancer):192.168.1.69:5060
> opensips(Proxy1):192.168.1.69:5061
> opensips(Proxy2):192.168.1.69:5062
> sipp(UAS1):192.168.1.70:5060
> sipp(UAS1):192.168.1.70:5061
>
> I run the sipp command for the caller as follows:
>
> sipp -sn uac -rsa   192.168.1.69:5060 192.168.1.70:5060
>
> When I traced the packets using wireshark I saw the error message :
>
> Destination unreachable (port unreachable)
>
>
> The load Balancer table contains the following:
>
>   ---- ----------- ----------------------------- ----------------------------
>   |  id  | group_id | dst_uri                           | resources
> |
>   ---- ----------- ----------------------------- ----------------------------
>   |  1  |        1      | sip:192.168.1.69:5061    |  pstn=32
> |
>   |  2  |        1      | sip:192.168.1.69:5062    |  pstn=32
> |
>   ---- ----------- ----------------------------- ----------------------------
>
>
> the load balancer configuration file is exactly as the one in the load
> balancer tutorial(http://www.opensips.org/Resources/DocsTutLoadbalancing)
> except the listen line:
>
> listen=udp:xxx.xxx.xxx.xxx:5060
>
> I changed it to
>
> listen=udp:192.168.1.69:5060
>
>
>
> Note: When I tried to send UAC calls directly to the proxy (e.g: sipp -sn
> uac -rsa  192.168.1.69:5061 192.168.1.70:5060) without passing through the
> load balancer it worked properly which means that my problem is in the load
> balancer.
>
> Best Regards,
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Unable-to-make-the-load-balancer-work-tp6977880p6977880.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Disclaimer:
This communication is intended for the above named person and is confidential and / or legally privileged. Any opinion(s) expressed in this communication are not necessarily those of KSU (King Saud University). If it has come to you in error you must take no action based upon it, nor must you print it, copy it, forward it, or show it to anyone. Please delete and destroy the e-mail and any attachments and inform the sender immediately. Thank you.
KSU is not responsible for the political, religious, racial or partisan opinion in any correspondence conducted by its domain users. Therefore, any such opinion expressed, whether explicitly or implicitly, in any said correspondence is not to be interpreted as that of KSU.
KSU may monitor all incoming and outgoing e-mails in line with KSU business practice. Although KSU has taken steps to ensure that e-mails and attachments are free from any virus, we advise that, in keeping with best business practice, the recipient must ensure they are actually virus free.