Do SIP UAC TCP/TLS implementations tend to use ephemeral port for the source port for initiated requests (ie, bind port 0 for source port, allowing OS to choose port)?
I know many implementations (including my own) fixes UDP source port to 5060, and by setting the REUSEADDR socket option so can keep binding to the same source port all the time. However, I ran into problem doing that for TCP/TLS. I was able to bind the same 5060 source port no problem, but when I tried to connect to the same UAS they would reject my TCP connection. (I imagine their TCP/IP stack didn't like that the exact same 5-tuple (src ip/port, dst ip/port, tcp) was reused within the 2*MSL timeout. I thought REUSEADDR solved that.... but apparently not. So... that raises the question of do most people use ephemeral source port for TCP/TLS SIP connections that are initiated. Regards, -Russ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
