Hi, I witness (through wireshark) that sipXecs sometimes does change the order of the packets when it proxies them.
Here is an example where it results in a bad situation. When you subscribe to a resource, you get a 200 OK response that creates a dialog, then a notification. When the 200 OK & NOTIFY are sent in a row, sometimes sipXecs proxies the NOTIFY before the 200 OK. The result is that the NOTIFY is received while the dialog is not yet established (because the 200 OK has not been received yet) then it is refused with 481 which results in the remote dialog/subscription being destroyed. I can reproduce this scenario at will, do you want a snapshot/pcap of it ? Regards. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
