8 Sep
2016
8 Sep
'16
7:13 p.m.
On Thu, Sep 08, 2016 at 04:50:50PM +0200, Federico Cabiddu wrote:
The issue with dispatcher is that, in case of TCP
transport, you cannot set
the sending socket for the same reason.
Basically, each time a client TCP socket is open by Kamailio, the SO select
the port, due to the lack of support for SO_REUSEPORT.
I know, the solution that the dispatcher brings is 1 long living tcp
connection from kamailio to asterisk, with kamailio keeping it alive.
Asterisk stores the ip/port to send the INVITEs to, as long as kamailio
or asterisk isn't restarted the ip/port combo (the same for all devices)
is still valid.