Daniel-Constantin Mierla writes: > the bt is from custom timer process, which doesn't handle sip requests > from the network.
ok, that just happened to be the one that according to 'top' used most cpu time. > Do a 'kamctl ps' and the select one of the sip workers to grab the back > with gdb. will do. how does kamailio choose which worker gets to serve next request? on my test laptop, i get: # pres-serv_ctl ps 5432 attendant 5434 slow timer 5435 timer 5436 ctl handler 5437 RLS NOTIFIER 0 5438 tcp receiver (generic) child=0 5439 tcp receiver (generic) child=1 5440 tcp receiver (generic) child=2 5450 tcp receiver (generic) child=3 5452 tcp main process is 'tcp main process' the dispatcher? if yes, can that get stuck and then prevent 'tcp receiver' processes from getting any work? -- juha _______________________________________________ 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
