[SR-Users] force_send_socket/$fs behaviour when binding to INADDR_ANY

Hello, When binding Kamailio to 0.0.0.0, Kamailio no longer recognises any specific IP address homed on the system as being a "socket" for purposes of forcing traffic out of any specific interface (i.e. setting $fs), or any other purpose for which ingress and egress "sockets" are tracked (e.g. double RR). As I understand it, this is because Kamailio considers only addresses explicitly specified via the 'listen' core config directive to be valid "send socket" arguments. Kamailio _will_ accept addresses already attached to the interface if it is bound interface-wise, e.g. listen=eth1:5060 but not when addresses are added to the interface without restarting the proxy: # ip addr add dev eth1 172.30.110.10/24 Aug 10 17:31:35 centosity6 /usr/local/sbin/kamailio[28627]: WARNING: pv [pv_core.c:2285]: pv_set_force_sock(): no socket found to match [udp:172.30.110.10:5060] Is there any straightforward way to modify this behaviour, so that it would be possible to dynamically add addresses to existing physical interfaces and get Kamailio to utilise them as if they were bound at boot time? Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/