<div dir="ltr"><div><div><div>answering myself, there were two issues:<br></div>1. The certs directory was a symlink <br></div>2. The port is 7443 and not 7433 <br><br></div>I hope it will help others.<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jun 23, 2014 at 12:03 PM, ik <span dir="ltr"><<a href="mailto:idokan@gmail.com" target="_blank">idokan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hello,<br><br>I'm using Freeswitch 1.4.6 on CentOS 6 .<br><br></div>I'ved configured Freeswitch to work with webrtc, and created certification based on <a href="http://wiki.freeswitch.org/wiki/SIP_TLS" target="_blank">http://wiki.freeswitch.org/wiki/SIP_TLS</a>.<br>
<br></div>I have also enabled the ws-binding and wss-binding at internal.xml.<br><br></div>When doing netstat, I can see both 5066 and 7433 binded:<br><br>netstat -lnpt | grep freeswitch<br>tcp 0 0 37.139.XXX.XXX:7443 0.0.0.0:* LISTEN 27937/./freeswitch<br>
<br><br></div>When I try to access the insecure ws (5066), I have a connection:<br><br>tport.c:2749 tport_wakeup_pri() tport_wakeup_pri(0x7f095c00b530): events IN<br>tport.c:862 tport_alloc_secondary() tport_alloc_secondary(0x7f095c00b530): new secondary tport 0x7f095c09b6a0<br>
tport.c:2620 tport_accept() tport_accept(0x7f095c00b530): incoming secondary on ws/37.139.XXX.XXX:5066/sip failed. reason = WS_INIT<br><br></div>But when I try to use the wss connection, I'm getting connection refused.<br>
</div>I'm testing it on the same machine with the following command:<br><br>openssl s_client -connect 37.139.XXX.XXX:7433<br><br></div>My cert folder has the following certifications:<br>drwxr-x--- 2 root root 4096 Jun 23 08:42 CA<br>
-rw-r----- 1 root root 1270 Jun 23 08:42 agent.pem<br>-rw-r----- 1 root root 729 Jun 23 08:42 cafile.pem<br>-rw-r--r-- 1 root root 1270 Jun 23 08:46 dtls-srtp.pem<br>-rw-r--r-- 1 root root 1270 Jun 23 08:46 wss.pem<br><br>
</div><div>When using wireshark, I can see that the ACK packet get a reset flag after sending a SYN request.<br></div><div><br></div>What am I missing here or doing wrong ?<br><br></div>Thanks,<br></div>Ido<br></div>
</blockquote></div><br></div>