29 Jan
2012
29 Jan
'12
12:50 p.m.
Hi,
Can you copy/paste the error message here. I've recently made kamailio work
with floating IP(Heartbeat) and I was having similar issue but then I
resolved due to help from community memebrs here.
This is how I made kamailio work with floating IP.
in */etc/sysctl.conf* file insert this line
*net.ipv4.ip_nonlocal_bind = 1*
on console execute "*sysctl -p*"
Then on my linux server I had to explicitly set the routes to use the
Floating IP interface(s) as default
*route add -net 192.168.2.0/24 dev eth0:0*
Where eth0:0 was the virtual IP interface for that particular subnet.
After that all I had to do was change the listen=192.168.2.15 field on my
kamailio server where 192.168.2.15 was floating IP on interface eth0:0
restart kamailio and you shouldn't be receiving this error.
Regards,
Sammy
On Sun, Jan 29, 2012 at 1:51 AM, Spencer Thomason <
spencer(a)5ninesolutions.com> wrote:
Hello,
I'm working on building a HA setup with separate registrar and proxy
servers. The registrar server writes to a master database that is
replicated to a local database on each of the proxy servers. A load
balancer then sits in front of the proxys. When routing to a registered
user on the proxys I receive an error message that the socket is unknown
and ignored (obviously because its on another machine). Is this just a
warning message or are there any consequences to doing it this way? Is my
topology flawed and would there be a better way?
Thanks for your input,
Spencer
*Connected by DROID on Verizon Wireless*
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users