Hi, what that this error mean? which is event 7 in a dialog?
CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7f1105c7e598 [2729:1042665525] with clid '3734640b7ab3a9e733456af9053c4c13@XXX.XXX.XXX.XXX' and tags 'as61eee052' ''
I use Kamailio 1.5.4 in which AFAIK the race condition between the ACK and 200 is solved with a callback (now included in 3.X).
2010/7/8 Iñaki Baz Castillo ibc@aliax.net:
Hi, what that this error mean? which is event 7 in a dialog?
CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7f1105c7e598 [2729:1042665525] with clid '3734640b7ab3a9e733456af9053c4c13@XXX.XXX.XXX.XXX' and tags 'as61eee052' ''
I use Kamailio 1.5.4 in which AFAIK the race condition between the ACK and 200 is solved with a callback (now included in 3.X).
I've also found some "bogus event 7 in state 1 for dlg".
It occurs in a server usually processing 500-700 concurrent calls, but today the traffic has been increased up to 1000-1200. I didn't see these errores before today.
Hey again,
Iñaki Baz Castillo wrote:
I've also found some "bogus event 7 in state 1 for dlg".
Meaning "received a BYE request for a dialog in the 'unconfirmed' state", i.e., the callee hasn't even replied with a 1xx message.
It occurs in a server usually processing 500-700 concurrent calls, but today the traffic has been increased up to 1000-1200. I didn't see these errores before today.
I don't think it's legal to send a BYE request for a call that hasn't even transitioned to the "early" state, so without further insights I'd speculate the UAC to be flawed.
However, if you had any traces at hand I'd be glad to double-check.
Cheers,
--Timo
2010/7/8 Timo Reimann timo.reimann@1und1.de:
It occurs in a server usually processing 500-700 concurrent calls, but today the traffic has been increased up to 1000-1200. I didn't see these errores before today.
I don't think it's legal to send a BYE request for a call that hasn't even transitioned to the "early" state, so without further insights I'd speculate the UAC to be flawed.
I strongly think something wrong has occured with my Kamailio 1.5.4 today as the number of concurrent calls (~1200) is not true (confirmed by inspecting the CDR's in the gateways). As I told in other mail, Monit service detected that, at some time, the server CPU arrived to 40% of usage (really impossible under normal circunstances) and the dialog module shown exagerate values for the ongoing calls.
- So first I see the message "bogus event 7 in state 2 for dlg" (never seen before and there are no new clients, so very strange).
- After ~3 minutes the CPU goes up (which makes no sense).
- Also LCR load_gw() returns -1 (no gws available) which is just possible if both gateways didn't reply to the OPTIONS (not real), but worse is the fact that LCR didn't log this error (gws OFFLINE) but did log "gws ONLINE" after 4 minutes when the CPU usage decreased again.
- There was not real increase of calls, but dialog module shows it (I've already saw something similar when, for some reason, kamailio 1.5.1 leaked memory and I got PKG memory filled, then the number of dialog is increased more and more, both in the statistics and using dialog MI functions).
With the logs I have there is no way to understand what happened. I also monitor the usage of PKG each 5 minutes for the first UDP listener process and there was no PKG problem during the issue (at least in the first listener).
Well, I must investigate it :)
Hey Iñaki,
Iñaki Baz Castillo wrote:
Hi, what that this error mean? which is event 7 in a dialog?
CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7f1105c7e598 [2729:1042665525] with clid '3734640b7ab3a9e733456af9053c4c13@XXX.XXX.XXX.XXX' and tags 'as61eee052' ''
I use Kamailio 1.5.4 in which AFAIK the race condition between the ACK and 200 is solved with a callback (now included in 3.X).
"Bogus event 7 in state 2" isn't the race condition (that should be "bogus event 6 in state 2"). It means that the proxy received a BYE request (event 7) for a call in the "early" state (state 2).
Of course, sending in-early-dialog BYE requests is perfectly fine, so this log message about a bogus event is, in fact, bogus. :) It was fixed by me last week or so in sr_3.0, kamailio_3.0, and just on last Monday in Kamailio 1.5 SVN too. Check out the SVN log:
$ svn log -r 6014 ------------------------------------------------------------------------ r6014 | mariuszbihlei | 2010-07-05 16:46:48 +0200 (Mo, 05 Jul 2010) | 4 lines
Do not consider in-early-dialog BYE requests to be bogus. Patch from Timo Reimann (timo.reimann at 1und1 dot de )
Consequently, the wrong bogus message shouldn't show up in latest Kamailio SVN anymore.
Cheers,
--Timo
2010/7/8 Timo Reimann timo.reimann@1und1.de:
Hey Iñaki,
Iñaki Baz Castillo wrote:
Hi, what that this error mean? which is event 7 in a dialog?
CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7f1105c7e598 [2729:1042665525] with clid '3734640b7ab3a9e733456af9053c4c13@XXX.XXX.XXX.XXX' and tags 'as61eee052' ''
I use Kamailio 1.5.4 in which AFAIK the race condition between the ACK and 200 is solved with a callback (now included in 3.X).
"Bogus event 7 in state 2" isn't the race condition (that should be "bogus event 6 in state 2"). It means that the proxy received a BYE request (event 7) for a call in the "early" state (state 2).
Of course, sending in-early-dialog BYE requests is perfectly fine, so this log message about a bogus event is, in fact, bogus. :) It was fixed by me last week or so in sr_3.0, kamailio_3.0, and just on last Monday in Kamailio 1.5 SVN too. Check out the SVN log:
Ok, thanks for the clarification ;)
-
Iñaki Baz Castillo -
Timo Reimann