On Thu, Aug 10, 2017 at 04:48:48PM -0400, Ryan Wagoner wrote:
> In my REGFWD route I have this chunk of code to lookup the dispatcher
> IP/port from the same hash table before calling uac_req_send(). The
> regserver column contains the dispatcher set id. Is there a way I can call
> ds_select and th
On Thu, Aug 10, 2017 at 9:05 AM, Daniel Tryba wrote:
> On Thu, Aug 10, 2017 at 08:51:24AM -0400, Ryan Wagoner wrote:
> > 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 Kam
You can always add a bit of caching to avoid too many sql queries and
improve the performances. Just use the htable module to store in memory
the value associated with authid that you fetch from database.
Then you can llok first in htable, and if not found store in htable. You
can set a lifetime f
On Thu, Aug 10, 2017 at 08:51:24AM -0400, Ryan Wagoner wrote:
> 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 ha
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
ca
On Wed, Aug 09, 2017 at 01:21:36PM -0400, Ryan Wagoner wrote:
> How do I mark these server side invites so the call hash is known by
> kamailio? Or am I thinking about this the wrong way?
It is the latter, in dialog replies should be routed on headers only. In
the "default" config these replies/re
For a call invite from a phone to an load balanced asterisk server farm I
can use ds_select_dst with hash over callid for the algorithm. What I don't
understand is what happens for a server side invite. Say user A calls user
B. The server will send and invite to user B's device. User B's device wil