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
I would rather say:
1) make opensips to insert in the time_stamp col the time when the
message was received and not the time when the insertion in done (this
will preserve the order of the packages)
2) probably a time stamp (sec only) is not eough and some microsecs
needs to be
What is the idea you are trying to hack ? maybe to brains are better
than one ;)
Regards,
Bogdan
MohammedShehzad wrote:
Hi Bogdan,
Thanks for your prompt response. I was hacking into the code of
siptrace module but no success yet. Anyway something is better than
nothing.
Regards,
Hi Bogdan,
Thanks for your prompt response. I was hacking into the code of
siptrace module but no success yet. Anyway something is better than
nothing.
Regards,
MohammedShehzad
Hi Mohammed,
This is more or less a limitation ; as opensips is doing parallel
processing , you may have
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
