<br><br><div class="gmail_quote">2010/8/11 Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wednesday 11 August 2010, dotnetdub wrote:<br>
> I see this in every call setup..<br>
><br>
> CRITICAL: dialog [dlg_hash.c:591]: bogus event 6 in state 2 for dlg<br>
> 0xaf933bd0 [3739:1530909163] with clid<br>
</div>> '<a href="mailto:5959362a340dfa7938cf52ae1ba4b9d7@my.proxy.com">5959362a340dfa7938cf52ae1ba4b9d7@my.proxy.com</a><mailto:<a href="mailto:5959362a340dfa7938cf">5959362a340dfa7938cf</a><br>
<div class="im">> <a href="mailto:52ae1ba4b9d7@my.proxy.com">52ae1ba4b9d7@my.proxy.com</a>>' and tags 'as5b636a8a' ''<br>
><br>
> I am running SIP-Router 3.01<br>
<br>
</div>Hi Brian,<br>
<br>
this message is produced from a UA that sends and ACK to an dialog which is in<br>
the early state, which is invalid. We also see it from time to time in our<br>
logs because of some buggy UAs - its harmless.<br>
<br>
If you see it in every call setup, then this is a but too much to my<br>
understanding, but maybe you could do some traces to get more informations<br>
about the SIP msg flow.<br>
<br>
BTW, if you see some more "bogus event" with other event IDs in the logs, Timo<br>
did a bunch of fixes some time ago that should suppress most invalid messages.<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br></font></blockquote><div><br></div><div>Thanks Henning,</div><div><br></div><div>The same endpoint never causes our Kamailio 1.4.1 servers to generate this message. I have watched the SIP transactions and the ACK always seems to arrive at the correct point in the dialog. The endpoint is Asterisk 1.4.22.</div>
<div><br></div><div>Thanks,</div><div>Brian</div><div><br></div></div><br>