Hi David,
This error is created from the dialog state machine, as you already guessed. In the worst case the dialog will be expired then after the expiration timeout. So if you do not getting
tons of this errors, it should be not critical for kamailio internal operation.
Regarding the SIP race condition, you can lookup the particular RFC (e.g. 5407) and then address it in the UA, if appropriate.
Cheers,
Henning
From: sr-users <sr-users-bounces@lists.kamailio.org>
On Behalf Of David EscartÃn
Sent: Wednesday, May 12, 2021 8:03 AM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: [SR-Users] bogus event with terminated dialogs with late 200ok responses
Hello all
using kamailio version 5.4.4, we are seeing some errors like
CRITICAL: dialog [dlg_hash.c:1205]: next_state_dlg(): bogus event 3 in state 5 (with BYE) for dlg 0x7f6ca2304b48 [15135:39671] with clid '00463385_20210512_002_HPRA_1.1.4.40.sp3_7532_0_54533900281' and tags 'Out-55089-0000000CB27947F9'
'170cB11c48vmj'
which seem to be generated when we receive a BYE from the remote UA but we were expecting an ACK also,
For example
INVITE ---------->
<---------------183
<---------------200
BYE ------------->
(no ACK)
<--------------200
<--------------200
....
so the b2bua (freeswitch) keeps retransmitting the 200ok, and on each 200ok retransmission we are getting this type of message.
These seem to be like race conditions since 200/BYE flow almost at the same time, and as I understand, the UA should send the ACK.
But my doubt is if these errors can be harmful for the kamailio or they can be ignored and address the issue to the remote UA on each case
thanks a lot and regards
david
--
|
||||||||||||||||||||
|