[sr-dev] Dialog module: "CRITICAL bogus event 6 in state 2

[Henning Westerholt]

On Monday 14 June 2010, Ovidiu Sas wrote:
> It is a race between the 200ok being sent out and the update of the
> dialog state machine.  The ACK is received while the dialog state
> machine was not updates for the previously sent 200ok.
> IIRC, in opensips this was fixed by introducing a new tm callback in
> order to update the dialog state machine as soon as the 200ok was sent
> out.
> For now, the only way to avoid this issue is to run with one single
> listener.  This will keep the ACK into the received queue until the
> listener finishes the processing of received 200ok.

Hi Timo,

i don't remember exactly, did you also discussed about this issue in your 
recent dialog re-design proposal, or is this a new problem?

Regards,

Henning