I know about dispatcher but it not always canbe heplfull. Sometimes i need my own logic that not implemented at the dispatcher.
For checking kamailio live from asterisk im use qualfy for keepalives, if i use asterisk only as media server but it not always usefull. Sometimes scenarios need to use another logic. 2016-09-08 17:50 GMT+03:00 Federico Cabiddu <federico.cabi...@gmail.com>: > 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. > > Cheers, > > Federico > > On Thu, Sep 8, 2016 at 4:33 PM, Daniel Tryba <d.tr...@pocos.nl> wrote: > >> On Thu, Sep 08, 2016 at 03:38:32PM +0300, Yuriy Gorlichenko wrote: >> > I didnt thought about keepalive. I suppose it can help. >> >> Better than using qualify in asterisk is to use the dispatcher module in >> kamailio. The idea is the same, but more configurable and it is just 1 >> keepalive mechanisme so the amount of keepalives doesn't scale linear >> with the number of registered users :) >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
