[OpenSIPS-Users] dispatcher ds_probing_sock with virtual ip

[Ovidiu Sas]

You should not set net.ipv4.ip_nonlocal_bind=1 unless you *really*
know what you want to do (a true hot standby).
You set the listen param correctly and you should try to start
opensips *only* on the active node.
If opensips is not able to start (to bind to the HA IP) it means that
your HA setup is wrong.

You need to set net.ipv4.ip_nonlocal_bind=1 only if you want to mirror
registration on the hot standby and when the HA IP migrates from one
host to another, opensips is already up and running.  This setup
require a well crafted config.
My suggestion would be to keep opensips running *only* on the active
node.  When the HA IP migrates from active to standby, just let the HA
scripts to start opensips.  It is easier to setup and troubleshoot.


Regards,
Ovidiu Sas

-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

On Sun, Dec 25, 2011 at 2:54 PM, Matt Hamilton <mistral9999 at hotmail.com> wrote:
>
> I'm trying to deploy opensips in a HA environment (pacemaker/corosync) on
> two multihomed servers.
>
> server 1: 10.0.1.76
> server 2: 10.0.1.77
> virtual ip: 10.0.1.75
>
> I was able to get OpenSIPS to start and bind to to the virtual ip by
> editing  /etc/sysctl.conf:
> net.ipv4.ip_nonlocal_bind=1
>
>
> my opensips.cfg:
>
> listen=udp:10.0.1.75:5060
> ...
> modparam("dispatcher", "ds_ping_from", "sip:proxy at 10.0.1.75")
> modparam("dispatcher", "ds_probing_sock", "udp:10.0.1.75:5060")
> ...
>
> The problem is with the dispatcher module - it fails to send the OPTIONS
> message, and marks the resource as "P":
>
>
> The log shows:
>
> opensips1 /usr/local/sbin/opensips[3764]: ERROR:core:udp_send:
> sendto(sock,0x7f516e6f7208,323,0,0x7f516e6f5978,16): Invalid argument(22)
>  opensips1 /usr/local/sbin/opensips[3764]: CRITICAL:core:udp_send: invalid
> sendtoparameters#012one possible reason is the server is bound to localhost
> and#012attempts to send to the net
>  opensips1 /usr/local/sbin/opensips[3764]: ERROR:tm:msg_send: udp_send
> failed
>
> How can I fix this?
>
> Thanks,
> Matt