Hi Olle, Thanks for getting back to me. Kamailio seems to be receiving inbound sip udp correctly on the virtual IP's - and is able to respond to that received traffic. The issue seems more to be related to the mhomed mechanism where Kamailio tries to identify the correct interface to use for for new outbound traffic. I do not understand your references to sysctl - can you provide any example? Many Thanks, Mark Hall ----- Original Message ----- From: Olle E. Johansson To: Kamailio (SER) - Users Mailing List Sent: Friday, February 13, 2015 9:06 AM Subject: Re: [SR-Users] Unable to route outbound with multiple VRRP IP's On 13 Feb 2015, at 09:48, &lt;mark(a)brightvoip.co.uk&gt; &lt;mark(a)brightvoip.co.uk&gt; wrote: Hi, I am trying to install a Kamailio server in a HA configuration, with IP's for 3 attached networks. I am using Keepalived/VRRP to manage the VIP's. I have tested v 4.1.6 and latest 4.2.2 I have 3 x listen entries, one for each network and mhomed=1. Also, for info, we have net.ipv4.ip_nonlocal_bind = 1 in sysctl.conf listen=udp:my.public.net.46:5060 listen=udp:192.168.106.46:5060 listen=udp:192.168.116.46:5060 On a Linux system, kamailio can not listen to an address not assigned to the system, without a specific sysctl. If the 3 virtual IPs are independently moving between the servers, and you have fixed the sysctl (which I can not remember right now) you will always have kamailio's that can't reach the network since the address is not there. You may want to start Kamailio that listens to one IP when that IP is assigned by Keepalived. Keepalived has scripts executed when an IP is assigned or lost on the system. Hope this helps. /O mhomed=1 I have dispatcher set up to load balance over two seperate groups of Asterisk servers, one on each private network. Dispatcher does probing to know which Asterisks are 'alive'. When I ran the system, Kamailio/Dispatcher was not able to send any probing OPTIONS to any Asterisk (normal PINGS work fine in all networks in/out of Asterisk/Kamailio) Looking at the log, I see these entries for all 3 networks: Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: <core> [forward.c:218]: get_out_socket(): no socket found Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: <core> [forward.c:220]: get_out_socket(): no corresponding socket found for(u dp:192.168.116.38:5060) Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: tm [ut.h:345]: uri2dst2(): no corresponding socket found for "192.168.116.38" af 2 (udp:192.168.116.38:5060) Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: tm [uac.c:307]: t_uac_prepare(): t_uac: no socket found Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: dispatcher [dispatch.c:2564]: ds_check_timer(): unable to ping [sip:192.168.1 16.38:5060] I notice from other logging that Kamailio is receiving and processing incoming OPTIONS messages, and sending appropriate replies. Now, this might not be a Kamailio issue, as when I run the same config with 3 IP's, but NOT using VRRP/Keepalived/Aliased IP's, everything works normally. However, I do need to run this setup in HA, so would welcome any suggestions as to how I might resolve this issue. Kind regards, Mark Hall ---------------------------------------------------------------------------- This email has been checked for viruses by Avast antivirus software. www.avast.com _______________________________________________ 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 ------------------------------------------------------------------------------ _______________________________________________ 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 --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com