[SR-Users] Unable to route outbound with multiple VRRP IP's

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 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. http://www.avast.com