2011/7/7 Iñaki Baz Castillo <i...@aliax.net>: > 2011/7/7 Iñaki Baz Castillo <i...@aliax.net>: >> 2011/7/7 Brez Borland <brez...@gmail.com>: >>> I think transport/transaction layers should work to prevent cases like this. >>> Personally I would look to close the previous connection associated with the >>> transaction, and use the new connection for any further associated >>> communications. >> >> It could be a good choice. > > Mmmm, danger, what about if the first connection is opened by a proxy > which currently mantains more than one transaction with the server? > why to close such connection just because a retransmission of some one > of those transactions has arrived via other connection? > > As you said before, it would be better just to use the new connection > after the server realizes that the previous one is > terminated/closed/broken.
Well, the approach I've implemented right now in my server is: - If a retransmission arrives using a different TCP or TLS connection (than the original connection) then update the associated server transaction so new responses will be delivered to the client via the new transaction. I think it's the best choice as I expect that a retranmission coming via other connection means that the client has lost the initial connection and expects responses in the new one. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
