<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Brian,<br>
<br>
I've made some progress, after about 5 hours (on and off) digging
around the source code and trying rebuilds of Freeswitch I found a
reference to the cert dir in argv, and then found that there is a
command line parameter in Freeswitch called -certs<br>
<br>
Hurrah! A quick modification to my start up script so it looks like
this:<br>
<br>
freeswitch -certs /etc/freeswitch/certs<br>
<br>
And then copying the same combined cert/key/chain file I used for
the WSS cert into<br>
<br>
/etc/freeswitch/certs/dtls-srtp.pem<br>
<br>
And now I don't get those cert errors, and I can actually make and
receive a call (over IPv4 WSS only).<br>
<br>
It would be great to put a quick note on the webrtc page about
needing to configure the certs dir. It would save newbies like me so
much time. <br>
<br>
I used an /etc/hosts entry on my client machine to allow me to use
my external domain cert - to bypass the IPv6 issue for the moment.<br>
<br>
<br>
So now there are only 2 issues remaining:<br>
<br>
<ol>
<li>IPv6 WS/WSS sockets don't stay up more than 3s - shall I open
a bug for this?</li>
<li>When making or receiving a call, the Firefox client could send
audio (I heard it on my desk phone), but it could not receive
audio (even though I could see UDP packets arriving from
Freeswitch onto my client machine on the correct port
negotiated).<br>
</li>
</ol>
<br>
Any ideas, presumably this is a codec issue, but I've tried just
doing the echo test (i.e taking the handset out of the equation) and
still no luck. Also tried with PCMU and Opus, no difference.<br>
<br>
Thanks<br>
Tom<br>
<br>
<div class="moz-cite-prefix">On 27/07/14 14:09, Tom Parrott wrote:<br>
</div>
<blockquote cite="mid:53D4FA1F.9010505@tomp.co.uk" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi,<br>
<br>
I am experimenting with WebRTC and am failing quite dismally -
mainly due to lack of documentation.<br>
<br>
I realise this is an emerging technology and the standards are
moving, but presumably it does work in some scenarios and it would
be great if a working setup could be documented.<br>
<br>
Anyway, I think I might have found a bug, but have no way to tell
because I've never been able to get WebRTC working with
Freeswitch.<br>
<br>
Here's my setup so far:<br>
<br>
<ul>
<li>FreeSWITCH Version
1.5.14b+git~20140725T212415Z~c411f8c7a9~32bit (git c411f8c
2014-07-25 21:24:15Z 32bit)</li>
<li>IPv6 addresses - due to shortage of global IPv4 address, I
am forced to use IPv6</li>
<li>SIPJS - <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://sipjs.com/">http://sipjs.com/</a></li>
<li>Firefox 31/Fedora 20</li>
<li>Apache 2.4.9/Mod_SSL</li>
<li>Startcom SSL cert (which I have configured with Apache fine)<br>
</li>
</ul>
<br>
What I am able to do:<br>
<br>
If I setup the internal IPv4 profile with ws-binding, I can use
SIPJS to register and can successfully see a user registered in
Freeswitch from the browser.<br>
<br>
I can then use SIPJS to make a call, and my desk phone rings,
however I get no media (UDP packets are being sent but presumably
neither side can decode it).<br>
<br>
I also see these errors in the fs_cli debug output though:<br>
<b><br>
</b><b>2014-07-27 13:04:12.108836 [ERR] switch_core_cert.c:210 FP
FILE ERR!</b><b><br>
</b><b>2014-07-27 13:04:12.108836 [ERR] switch_core_cert.c:210 FP
FILE ERR!</b><b><br>
</b><b>2014-07-27 13:04:12.148104 [ERR] switch_rtp.c:2975 audio
DTLS cert err [5]</b><br>
<br>
But I can find no proper documentation on what is required for
DTLS or where to put the cert files.<br>
<br>
Next up I tried IPv6 in the internal-ipv6 profile:<br>
<br>
<param name="tls-cert-dir"
value="/etc/freeswitch/certs"/><br>
<param name="wss-binding" value=":7443"/><br>
<br>
I concatenated the cert, key and chain certs together into
/etc/freeswitch/certs/wss.pem and can successfully connect using
WSS and SIPJS.<br>
<br>
The problem however is that although I can see a register,
Freeswitch then kills the registration connection a couple of
seconds later.<br>
<br>
It is also showing the registration as using WSS-NAT, how can that
be possible on IPv6? <br>
<br>
How can I turn off NAT detection on the IPv6 profile?<br>
<br>
Any guidance would be very much appreciated and I will post my
setup to my blog and the Freeswitch wiki if I can get it working,
to help people in the future.<br>
<br>
Thanks<br>
Tom<br>
<br>
</blockquote>
<br>
</body>
</html>