Hi Charles, dialog module does have support of in memory support and multiple options for how it writes back into a database table (or disable database altogether and just use memory). However, I suspect, this would only be usefull again if a single loadbalancer is in use, as the second loadbalancer wont have access to the dialog state in the first loadbalancers memory tables (and vice-versa).
I had a look at the memcache module, and it could be an option to use that as a shared state indexer, my only concern at the moment with it is that it only supports a single memcache server at the moment, however, it may be worth investigating this option too. Would be a nice feature to have dialog module stored its state in the memcache module, however I wonder if memcache would be suited to dialog modules structures :) On 27/04/12 12:29, charles.cha...@sipcentric.com wrote: > Regarding shared state across the two kamailios, have you considered > memcached module? > > Or you could make domain table in db in-memory? > > Best, > > Charles > > > > _______________________________________________ > 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
