Yes, with reinvites appearing before, or exactly simultaneously to, the point at which the initial invite transaction is completed and the dialogue confirmed with an e2e ACK. These messages hit different worker threads and have somewhat unpredictable exit velocity, based on many stochastic factors.

—
Sent from mobile, with due apologies for brevity and errors.

On Feb 5, 2019, at 12:55 PM, Duarte Rocha <duarterocha91@gmail.com> wrote:

Thank you for your answer Alex. 

Wheb you say you have dealt with this, do you mean this exact scenario with re-invites and ACK or just with general packets order?

I'll look into your solution, thank you.

Best Regards, 

Duarte Rocha 

Na(o) terça, 5/02/2019, 12:42, Duarte Rocha <duarterocha91@gmail.com> escreveu:
Greetings, 

I'm having some problems with keeping the order of the messages in Kamailio.

In some cases i'm receiving an ACK for the first INVITE and immediately after that a RE-INVITE is sent by the client.
What is happening is that the the ACK took double the time of the RE-INVITE to process and as a consequence, the RE-INVITE was relayed before the ACK.

I have two questions : 

1 - Is there a way to keep the order of the messages in a dialog, and if so, what are the downsides to it?

2 - The machine wasn't in a load state (only one concurrent call) and the ACK and the RE-INVITE should go roughly through the same processing methods and should take took the same time to be be relayed. What can be the reason for this?

Best Regards,

Duarte Rocha
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users