Getting TCP RST instead of TCP FIN

[AlexisXavierLamas]

Hello,

I am using SIPSorcery's SIPTCPChannel to make a SIP call following SIP protocol. However, on SIPTCPChannel.close I am getting a TCP RST instead of TCP FIN. I did some reading and believe it has to do with the SIPTCPChannel class setting LingerOption(enabled: true, seconds: 0) which is only accessible privately within the SIPTCPChannel class. To my knowledge setting LingerOption(enabled: false, seconds: 0) would send a TCP FIN if immediate closure is needed, or LingerOption(enabled: true, seconds: >0) if immediate closure is not needed. Is there a reason why TCP RST is preferred over TCP FIN?

[sipsorcery]

See here and here .

td;dr the goal is to be able to quickly close a TCP socket and then re-open & bind wit the same port.

[AlexisXavierLamas]

Question, would it be likely to make changes to add the ability to set the lingeroption when initializing SIPTLSChannel/SIPTCPChannel? Reason I ask is because I am working on a SIP Client and need the ability to send TCP FIN (best practice) when the socket closes. Right now I have no way of doing so.

[sipsorcery]

Yes, I don't see any problem with that. The default behaviour would need to stay as is to avoid affecting existing library users but modifying based on a constructor property should be ok.

[AlexisXavierLamas]

Perfect thank you!

FWIW, I am using SIPSORCERY version 6.2.4 built using NET CORE 6.0. When do you think an updated version will be available?

[sipsorcery]