Hi .*,
scenario:
1) kamailio listening on 0.0.0.0:5060 UDP and TCP configured as SIP proxy 2) eth0 private interface, eth1 public interface 3) multiple IP address on eth1 4) firewall open on 5060 UCP/TCP only for 1 IP address x.x.x.x
When from a client I try to register to the SIP proxy, packets are going to IP x.x.x.x but kamailio replies using a different source IP (typically first one configured on the interface) and not the one it received the request to.
Is there a way to configure/workaround this?
Thank you!
Hi Juha,
thanks for your quick reply.
Is there a way to configure/workaround this?
try force_send_socket() function.
Doesn't work because 0.0.0.0 is not the listening address I'm using in force_send_socket():
------- ERROR: <core> [route.c:1057]: fix_actions(): ERROR: fix_actions: bad force_send_socket argument: x.x.x.x:5060 (ser doesn't listen on it) -------
If I force 2 IP addresses using listen directives, it looks like it works though.
Thanks!
Hello,
On 9/25/13 11:36 AM, Marco Londero wrote:
Hi Juha,
thanks for your quick reply.
Is there a way to configure/workaround this?
try force_send_socket() function.
Doesn't work because 0.0.0.0 is not the listening address I'm using in force_send_socket():
ERROR: <core> [route.c:1057]: fix_actions(): ERROR: fix_actions: bad force_send_socket argument: x.x.x.x:5060 (ser doesn't listen on it)
If I force 2 IP addresses using listen directives, it looks like it works though.
as you don't give to kamailio the list of IP addresses to listen to, then I guess is the operating system that selects the interface.
Can you try with mhomed=1 in kamailio.cfg?
Cheers, Daniel
-
Daniel-Constantin Mierla -
Juha Heinanen -
Marco Londero