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
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@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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
On 01/28/2012 09:51 PM, Spencer Thomason wrote:
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?
Actually it's just a warning, we see that too when the register had been processed by a different machine than the one processing the invite, and it doesn't cause an issue with us.
If it really doesn't work, come back with a trace and the error messages.
Andreas
Hi Andreas, Everything is working correctly. I looked into it and it seems the socket address is simply ignored in the event that it doesn't match a local address. As I don't have clients behind NAT this is not causing any problems.
Thanks for your confirmation.
On Jan 29, 2012, at 3:46 PM, Andreas Granig wrote:
Hi,
On 01/28/2012 09:51 PM, Spencer Thomason wrote:
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?
Actually it's just a warning, we see that too when the register had been processed by a different machine than the one processing the invite, and it doesn't cause an issue with us.
If it really doesn't work, come back with a trace and the error messages.
Andreas
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Andreas Granig -
Sammy Govind -
Spencer Thomason