<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[WebRTC - Does it work with the latest FreePBX?]]></title><description><![CDATA[<p dir="auto">Does anyone know how to get the WebRTC plugin working on the latest FreePBX?  The instructions provided in the WebRTC Guide seem to be specific to IssabelPBX and don't line up completely with the options available on FreePBX.</p>
<p dir="auto">I have the plugin installed and the extension configured as close as possible to the example in the guide.  When I load up FOP 2, the extension appears to register, as shown in FOP2 as well as in the asterisk logs, however it is not able to send or receive calls in any way.  It just says "Trying ##########" in the UI and nothing at all in the asterisk logs.  I cannot even cancel the call in the WebRTC UI, it just stays kind of frozen until I close the FOP2 page entirely and reload.</p>
]]></description><link>http://localhost:4567/topic/2898/webrtc-does-it-work-with-the-latest-freepbx</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 04:22:24 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/2898.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 29 Sep 2020 17:48:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to WebRTC - Does it work with the latest FreePBX? on Mon, 05 Oct 2020 11:48:05 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/edi" aria-label="Profile: Edi">@<bdi>Edi</bdi></a> said:<br />
do you have latest fop2</p>
</blockquote>
<p dir="auto">Yep, latest FOP2, latest FreePBX and latest versions of Chrome and Firefox.</p>
]]></description><link>http://localhost:4567/post/12082</link><guid isPermaLink="true">http://localhost:4567/post/12082</guid><dc:creator><![CDATA[sgladio]]></dc:creator><pubDate>Mon, 05 Oct 2020 11:48:05 GMT</pubDate></item><item><title><![CDATA[Reply to WebRTC - Does it work with the latest FreePBX? on Thu, 01 Oct 2020 19:10:33 GMT]]></title><description><![CDATA[<p dir="auto">do you have latest fop2</p>
]]></description><link>http://localhost:4567/post/12081</link><guid isPermaLink="true">http://localhost:4567/post/12081</guid><dc:creator><![CDATA[Edi]]></dc:creator><pubDate>Thu, 01 Oct 2020 19:10:33 GMT</pubDate></item><item><title><![CDATA[Reply to WebRTC - Does it work with the latest FreePBX? on Wed, 30 Sep 2020 19:07:57 GMT]]></title><description><![CDATA[<p dir="auto">Final update for today:<br />
It would seem as though it DOES work!  Just not in Google Chrome.  For the heck of it I just tried it in Firefox and it worked first try.<br />
What would cause this to work in Firefox but not Chrome?</p>
]]></description><link>http://localhost:4567/post/12080</link><guid isPermaLink="true">http://localhost:4567/post/12080</guid><dc:creator><![CDATA[sgladio]]></dc:creator><pubDate>Wed, 30 Sep 2020 19:07:57 GMT</pubDate></item><item><title><![CDATA[Reply to WebRTC - Does it work with the latest FreePBX? on Wed, 30 Sep 2020 15:32:52 GMT]]></title><description><![CDATA[<p dir="auto">Another minor update:<br />
I got calls going through now by delecting a different Media Encryption and transport setting, but one way audio only, whether it's in out outbound calls.  I can hear everything via the WebRTC client, but the other side doesn't hear anything.  RTP debug in asterisk shows the right IPs and ports, and everything is being passed by the firewall.  My browser is configured to allow microphone access as well.</p>
<p dir="auto">The settings within FreePBX I applied to the extension I am testing with are as follows, everything else is default settings:<br />
Transport: 0.0.0.0-wss<br />
Enable AVPF - Yes<br />
Enable ICE Support - Yes<br />
Enable rtcp Mux - Yes<br />
Enable WebRTC defaults - Yes<br />
Media Encryption - DTLS-SRTP (not recommended)<br />
Enable DTLS - Yes<br />
Use Certificate - I selected the real, not self-signed SSL cert configured for my server</p>
<p dir="auto">So what am I missing?</p>
]]></description><link>http://localhost:4567/post/12079</link><guid isPermaLink="true">http://localhost:4567/post/12079</guid><dc:creator><![CDATA[sgladio]]></dc:creator><pubDate>Wed, 30 Sep 2020 15:32:52 GMT</pubDate></item><item><title><![CDATA[Reply to WebRTC - Does it work with the latest FreePBX? on Wed, 30 Sep 2020 12:19:47 GMT]]></title><description><![CDATA[<p dir="auto">Minor update:<br />
I was loading FOP2 in HTTP but WebRTC needs HTTPS, so I fixed up the ssl configuration in fop2.cfg and reloaded in HTTPS.  Now the WebRTC phone behaves slightly differently.  Instead of getting stuck on "Trying ##########" it just immediately flips to Call Ended when trying to dial a number.<br />
When receiving a call it rings, I see the callerID, but when answering it immediately flips to Call Ended as well.<br />
So something is still not right...  Any ideas?</p>
]]></description><link>http://localhost:4567/post/12078</link><guid isPermaLink="true">http://localhost:4567/post/12078</guid><dc:creator><![CDATA[sgladio]]></dc:creator><pubDate>Wed, 30 Sep 2020 12:19:47 GMT</pubDate></item></channel></rss>