I am working on getting inbound calls for webrtc running.
The Wiki uses the terms
“Phone” and “webrtc” interchangeably but I can place outbound calls with 2 way audio without problems. So I suppose I was able to create and upload the SSL certificates correctly on my freepbx-server as well as the client browser.
I did notice that a “webrtc extension” 99XXXX does not exist in the extensions list.
A previous post
hinted at the FQDN to be set “in the certificate”. I am assuming this refers to the Freepbx-server’s certificate as the client browser’s “Certificate of the Certificate Authority” wouldn’t have use for that?
My Setup:
Freepbx v16
chan_sccp & sccp_manager
Modules up to date, System is live in production.
Background: The Company wants to establish a road warrior setup for remote workers. Not having to rely on zoiper etc. would improve employee acceptance.
As it stands: which steps need I take to establish inbound calls on webrtc?
The best webrtc phone for FreePBX is Sangoma Phone (desktop or browser). Requires the softphone licensing.
I used the simple webrtc phone in UCP for a while. It does not work over IPv6. It works best in Chrome, not at all in Safari, and I don’t know about Firefox.
If you able to place outbound calls, you have connectivity. Use the Asterisk Info reports page to ensure the 99xxxx device is registered. (It does not show up in your extensions list. It is a “device” and not a “user.”) Check Asterisk logs to see whether any errors appear when you expect to receive a call. Enable PJSIP logging to trace the SIP traffic (the webrtc phone is SIP over websocket).
Alrighty, I finally have time to get back to this post.
I checked the logs and as advised, the device shows up. Evaluation of different browsers yielded mixed results. Chrome works best and Firefox is mixed box of chocolates. What I can gather is that configuration is possible but I don’t have the time to go through the documentation. I have not touched Safari due to a lack of experience.
The configurability of Firefox via preference file makes it interesting for a corporate deployment. As such I am going to keep looking into it but as more of a passion project with reduced priority.
For the solution at hand, I went with the softphone licensing.