Re: [OpenSIPS-Users] mhomed=1 and force_send_socket()

2019-08-07 Thread Bogdan-Andrei Iancu
Vitalii, I think this is what you are looking for https://github.com/OpenSIPS/opensips/issues/1671, right ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On

Re: [OpenSIPS-Users] mhomed=1 and force_send_socket()

2019-07-31 Thread Vitalii Aleksandrov
When user is registered everything is OK. The problem appears when I send a call to another proxy or carrier. With UDP transport opensips correctly detects an outgoing interface and forwards a call. With TCP/TLS transport opensips is not that smart. Found the place in code which detects an

Re: [OpenSIPS-Users] mhomed=1 and force_send_socket()

2019-07-30 Thread Johan De Clercq
mhomed =1 will make sure that the outgoing interface towards user A is the interface on which user A has registered. Hence you need to be very very careful with mhomed=1. I use force_send_socket when I a have a mixed environment (e.g users that register, connection to provider without

[OpenSIPS-Users] mhomed=1 and force_send_socket()

2019-07-30 Thread Vitalii Aleksandrov
Hi, Have a problem with a multihomed proxy which doesn't select outgoing interface correctly. Found similar topics where people discussed usage of force_send_socket() when they want to force opensips to use some interface. As far as I understood "mhomed=1" is the option which forces