From klaus.feichtinger@gmx.net Mon Jun 14 15:01:52 2010 From: Klaus Feichtinger To: sr-dev@lists.kamailio.org Subject: Re: [sr-dev] Dialog module: "CRITICAL bogus event 6 in state 2 Date: Mon, 14 Jun 2010 15:01:45 +0200 Message-ID: <20100614130145.51840@gmx.net> In-Reply-To: <4C114A14.8060904@gmx.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0939814068==" --===============0939814068== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Ovidiu, I've been testing reproducablility of the described error and found that it i= s reproducable in "standard" mode onyl. This should mean: forked application = with child processes. As soon as I start the application even as non-forked o= r with only one child (children=3D1), the error was not reproducable until no= w. I've fastened reproduction with SIPp the call generating tool and in stand= ard mode this error messages are visible after about 1-2 minutes (the call ra= te is one call per second with a pause of 1500ms between ACK and the followin= g BYE). Under these test circumstances no subscription for presence or dialog state w= as active; it was tested on a "isolated" server where no other UAs were activ= e; only SIPp and one other UA were active. I found that this problem is UserAgent-independent, too. Do you have an idea = how to find out any more details about this problem? regards, Klaus Feichtinger > Datum: Thu, 10 Jun 2010 22:24:52 +0200 > Von: Klaus Feichtinger > An: Ovidiu Sas > CC: sr-dev(a)lists.sip-router.org > Betreff: Re: [sr-dev] Dialog module: "CRITICAL bogus event 6 in state 2 > Hello, >=20 > according tcpdump-traces on the linux machine and log entries in syslog > (see below) the 200 OK passed the SIP Router (this means - the call was > accounted and afterwards the bogus event was noted): >=20 > Jun 10 18:29:09 debian /usr/sbin/kamailio[20026]: INFO: