Tuxic Geek <tuxic.g...@gmail.com> writes: > I was testing and realized that any SIP library initialized 4 sockets when > using TLS *without* any call in progress. > *2 TCP* Conncetions > *1 UDP* Connections > *1 TCP* Connection to the TLS connection. > > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 0.0.0.0:48110 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:5080 0.0.0.0:* LISTEN > tcp 0 0 192.168.1.227:59232 xxx.xxx.xxx.xxx:443 > ESTABLISHED > udp 0 0 0.0.0.0:5070 0.0.0.0:* CLOSE > > I want to understand what are those used for?
None of those are standard SIP ports. That doesn't mean that your SIP library is using them, but it makes it hard to guess *what* your SIP library is using them for (which may not be SIP communication per se). (I assume you've verified that those sockets have been opened by the process that's running the SIP library, but I don't see the "netstat -p" output column there.) What is the name and version of the SIP library you are using? Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
