Re: [SR-Users] Dispatcher call id hash for server side invite

Thanks for the explanation! I finally got the dispatcher working in an active / passive Kamailio cluster in front of three FreePBX servers. I was using the Asipto Kamailio and Asterisk real time guide as a starting point so it had the WITHINDLG route. I ended up modifying the TOASTERISK route to call ds_select_dst and the FROMASTERSK route uses an htable for matching IPs off a mySQL view of the Kamailio dispatcher table. I also have some modifications to the REGFWD route. We'll see how performance is today as I did have to use a sqlops query to lookup the dispatcher set ID for TOASTERISK and REGFWD depending on the authentication ID. This setup is responsible for around 1000 extensions with 2000 devices for a high volume call center. Ryan On Thu, Aug 10, 2017 at 4:16 AM, Daniel Tryba &lt;d.tryba(a)pocos.nl <mailto:d.tryba@pocos.nl>> wrote: On Wed, Aug 09, 2017 at 01:21:36PM -0400, Ryan Wagoner wrote: It is the latter, in dialog replies should be routed on headers only. In the "default" config these replies/reINVITES are handled in the WITHINDLG route, the dispatcher should only be called for new dialogs. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users