Yeah, this was fixed only in 1.5 by myself (backport from opensips): http://openser.svn.sourceforge.net/viewvc/openser?view=rev&revision=5748
The problem was there since the dialog module was created (in all versions prior to 1.5) - this is what I meant by "This is an old problem, since the creation of the dialog module". In kamailio 3.0, this is a regression due to the new ser tm module. The sip-router tm module must be updated in order to avoid this regression.
Regards, Ovidiu Sas
On Mon, Jun 14, 2010 at 9:56 AM, Timo Reimann timo.reimann@1und1.de wrote:
Ovidiu Sas wrote:
This is an old problem, since the creation of the dialog module.
Don't think so. Please have a look at 1.5:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=kamailio;a=blob;f=modules/dia...
Cheers,
--Timo
On Mon, Jun 14, 2010 at 9:21 AM, Henning Westerholt henning.westerholt@1und1.de wrote:
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
-- Timo Reimann Software-Developer
1&1 Internet AG - Consumer Core Ernst-Frey-Straße 9 · DE-76135 Karlsruhe Telefon: +49 721 91374-8122 timo.reimann@1und1.de
Amtsgericht Montabaur / HRB 6484 Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Gert Nowotny, Jan Oetjen Aufsichtsratsvorsitzender: Michael Scheeren