In this case it is difficult to distinguish between a cross over BYE and a BYE that is really not matching a dialog.
I was thinking of keeping the dialog in DLG_STATE_DELETED state in the memory for a while and really delete the dialog context on a timer (that can be configurable, just like in the tm module). Like this, we can avoid false warnings in the logs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1275325
Originator: NO
The module cannot absorb the second BYE as the dialog does not exists anymore - it is deleted when the first BYE was received.
bogdan
Logged In: YES
user_id=1395524
Originator: YES
In this case it is difficult to distinguish between a cross over BYE and a BYE that is really not matching a dialog.
I was thinking of keeping the dialog in DLG_STATE_DELETED state in the memory for a while and really delete the dialog context on a timer (that can be configurable, just like in the tm module). Like this, we can avoid false warnings in the logs.
Logged In: YES
user_id=1275325
Originator: NO
Hi Ovidiu,
I re-clasify the report as a feature request - to keep the dialog in memory long enough to catch any delaied messages belonging to the dialog.
Let's work on it in 1.4.
Regards,
Bogdan