What if you set the default dialog timeout to a value much less than 12/14 hours, maybe 2 hours. It's very unlikely that a session last that long.
On Tue, Jul 2, 2013 at 9:23 AM, Charles Chance < charles.cha...@sipcentric.com> wrote: > Hi, > > I don't think this will help at all, as regardless of DB mode, unconfirmed > dialogs are not stored in DB anyway. > > The important thing to remember is that if you are calling dialog_manage() > in your config, to only do it once you are ready to forward the request. If > you call it but then exit for some reason without actually forwarding, you > will probably end up with a stuck dialog. > > Maybe someone else can suggest other possible causes? > > To my knowledge, there is no existing way to clear these without > restarting. > > Regards, > > Charles > > > > > On 2 July 2013 14:10, Gary Chen <gchen3...@gmail.com> wrote: > >> Thanks for suggestion. I will give it try. >> Since every call will have to check database, will this effect the >> performance of Kamailio for high volume server? >> >> Gary >> >> >> On Tue, Jul 2, 2013 at 8:55 AM, I.Pavlov <i...@izhnet.ru> wrote: >> >>> Hi, Gary. I had same problem. Try to use “db_mode” parameter of dialog >>> module with 1 value.**** >>> >>> ** ** >>> >>> *1 - REALTIME* - any dialog information changes will be reflected into >>> the database immediatly.**** >>> >>> ** ** >>> >>> Then you can kill the dead dialogs through database.**** >>> >>> ** ** >>> >>> *From:* sr-users-boun...@lists.sip-router.org [mailto: >>> sr-users-boun...@lists.sip-router.org] *On Behalf Of *Gary Chen >>> *Sent:* Tuesday, July 02, 2013 4:14 PM >>> *To:* Kamailio (SER) - Users Mailing List >>> *Subject:* [SR-Users] How to cleanup unconfirmed dialog in memory?**** >>> >>> ** ** >>> >>> ** ** >>> >>> Kamailio 3.3.3**** >>> >>> I am using dialog module to do the concurrent call limit. Once a while I >>> got a dead unconfirmed dialog hung in memory. The only way I know to >>> cleanup this is to restart kamailio. So my questions are: >>> 1) Does anybody know a better way to cleanup the dead dialog without >>> having to restart the kamailio server? This is a production server. I >>> really really hate to restart the server.**** >>> >>> 2) How easy to modify the source code to timeout the dead unconfirmed >>> dialog in memory? **** >>> >>> Gary **** >>> >>> _______________________________________________ >>> 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 >> >> > > > www.sipcentric.com > > Follow us on twitter @sipcentric <http://twitter.com/sipcentric> > > Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered > office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham > B7 4EJ. > _______________________________________________ > 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 > > -- Carlos http://caruizdiaz.com +595981146623
_______________________________________________ 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
