Hi Mohammed,
This is more or less a limitation ; as opensips is doing parallel
processing , you may have concurrent DB access (like inserting the
siptrace record for 200OK and the one for ACK)...Also the DB ops
(requiring locks) may change the sequence of the ops ( the order of the
queries and the order of the actual db ops).
There is no way to guarantee the order of the package in DB.
Regards,
Bogdan
MohammedShehzad wrote:
Hello everybody,
I am facing an issue in sip message sequence while I log the siptrace
using siptrace module.
The issue is random, means, generally it is fine, but sometimes the
SIP messages are out of sequence i.e. ACK get logged before 200OK,
even sometimes INVITE comes after 100 Trying or 180 ringing.
I found that, when CDRTool list siptrace of call, the SIP messages are
ordered by ID, which is auto increment field. So it seems that the
siptraces are not being inserted properly in sequence from siptrace
module itself.
My Opensips Version : opensips-1.5.3-notls
MySQL database is used, and is on remote system.
Is there anything I should try to resolve this issue? Or is this
bug/limitation of siptrace module itself?
Regards,
MohammedShehzad
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
15 - 19 November 2010, Edison, New Jersey, USA
www.voice-system.ro
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
