I tried so many port combinaison, and so many tutorial on google, but my call button refuse to work. Can someone who have a working webrtc, show me the configuration ???
Bring up the Asterisk console (asterisk -r from your terminal) and set verbose (CLI> core set verbose 9). Then try to place a call with webrtc. See whether it tries, and whether any errors appear in the console.
Also try bringing up the Javascript developer console in your browser (in Chrome, it’s View - Developer - Javascript Console). You will see informational messages there as you attempt to place a call. Mine looks like this:
That may not be a firewall issue. I believe it is due to your HTTPS settings in Advanced Settings. Why did you set those custom values for HTTPS TLS Certificate Location and HTTPS TLS Private Key? If your Let’s Encrypt certificate is set as default (and it appears to be), you should reset those to the defaults which will point at /etc/asterisk/keys/integration/…
Click the circling-arrows icon to return to the defaults.
HTTPS TLS Certificate Location (?) (@) <- the icon at the end
You will need to restart Asterisk too.
After you do, from the Asterisk CLI (asterisk -r), do
CLI> http show status
mine looks like this:
bell*CLI> http show status
HTTP Server Status:
Prefix:
Server Enabled and Bound to 127.0.0.1:8088
HTTPS Server Enabled and Bound to [::]:8089
Enabled URI's:
/httpstatus => Asterisk HTTP General Status
/static/... => Asterisk HTTP Static Delivery
/ws => Asterisk HTTP WebSocket
Enabled Redirects:
None.
Go back to the certificate manager and again set your Letsencrypt certificate as default. It should fill in the fields. If not, the fields are “/etc/asterisk/keys/integration/certificate.pem” for the certificate and “/etc/asterisk/keys/integration/webserver.key” for the key.
You should see a message from Asterisk saying “Upgrade required” (it means you are supposed to connect with websocket and not HTTP, but it is useful for a test)
If you don’t see this, maybe your browser will show you a certificate error or if the connection times out altogether you still need to investigate your firewall further.
