[reSIProcate] TCP Behavior - on Windows at least...

[Scott Godin]

I've been noticing the following behavior when using TCP transport (on
Windows):

 

1.	Resip disconnects socket connections immediately after receiving SIP
requests from the far end.
2.	For UAC Invites - resip closes the socket after receiving the 200
and reopens a new one for sending the ACK.
3.	For UAS Invites - resip does not close the socket after sending a
200, but waits for the ACK before closing.

 

For 1 - is this correct?

For 2 and 3 - which of these are correct?

Should resip be closing socket connections that it did not create?

 

Any plans to implement connection re-use?

 

Thanks,

 

Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050421/2c7ce288/attachment.htm>