You cannot expect SIP MESSAGE messages to arrive in the same order as they were sent. There is no physical or logical relation between 2 SIP Message messages, not in the client and not in the network. These messages may follow different network paths, may be retransmitted multiple times and or arrive in completely different order at the destination and even multiple times.
So technically speaking there is nobody to blame and you cannot fix any of these issues by switching to TCP.
The only way to have text chat sessions where messages arrive in the original order is to use MSRP media.
On Oct 19, 2011, at 3:00 PM, Barsan Liviu wrote:
We have implemented an OpenSIPs-MediaProxy based solution for our client, which sometimes (rarely, when are sent many messages) does not deliver (page based) messages in the right order.
We were thinking that maybe UDP is to blame and we would like to switch to TCP for OpenSIPs.
Can somebody tell us what we have to do beside changing the listen:upd:x.y.z.w:5060 to listen:tcp:x.y.z.w:5060 in opensips.cfg?