Kumba wrote:WebRTC/ViciPhone ready
- Requires a valid SSL and web accessible FQDN
- There is a template called 'webRTC' under Admin --> Templates that needs updated with your SSL certificate
- Asterisk also needs /etc/asterisk/http.conf updated with your valid SSL certificate
- The server needs it's 'Web Socket URL' under Admin --> Servers set to it's FQDN
- Still have to get the rest of the ViciPhone install together, but the above makes WebRTC work
Kumba wrote:Once you have verified that your SSL setup is working correctly (https:// works), you need to do a few additional setup tasks in ViciDial. This is only for a all-in-one setup. A cluster setup is more of a pain as templates have to be made for each individual telephony server and assigned to different phones and stuff.
Go to Admin --> Servers and click on the Server ID. The Web Socket URL for it needs to be set to : wss://<FQDN>:8089
Next you need to go to Admin --> Templates and select the webRTC template. Here you need to change the dtlscertfile= and dtlsprivatekey= directives to :
dtlscertfile=/etc/certbot/live/<FQDN>/cert.pem
dtlsprivatekey=/etc/certbot/live/<FQDN>/privkey.pem
After that, you need to go to Admin --> System Settings and change the Webphone URL to : https://phone.viciphone.com/viciphone.php
Then when you are adding phones, you will change 'Set to Web Phone' to 'Y' and the Template ID to 'webRTC'.
Also I allowed the wrong port in the firewall config. Here's how you fix that:
1) sed -i 's/8088/8089/g' /etc/sysconfig/scripts/SuSEfirewall2-custom
2) SuSEfirewall2
I've also added the fix to the ViciBox v.8.1 bugfix thread.
Unfortunatley the complexity of getting SSL working and all that means that this last bit of set-up has to be done by the admin after install. Probably the only thing I'll add in ViciBox v.8.1.1 is setting the Web Phone URL under System Settings. Anything else I set, without knowing that SSL is working properly, has the potential to just mess everything up.
An alternative to above what i did is download viciphone from Github and upload it to /srv/www/htdocs/viciphone. Then i specified /viciphone/viciphone.php in Admin>System settings>Webphone URL.
ccabrera wrote:Can we trust https://phone.viciphone.com/viciphone.php to be always available, or should we install our local copy?
I tried to read more about it at viciphone.com (same URL Google has currently indexed) but I can't reach it. Seems https://viciphone.com is currently unavailable, so that's why I'm asking about the stability of phone.viciphone.com
Kumba wrote:That's a DNS thing. phone.viciphone.com is going DNS load balanced across three data centers. One in Tampa, FL, one in Columbus, OH, and one in San Francisco, CA. The same datacenters are responsible for the nameservers hosting viciphone.com. Currently phone1.viciphone.com and phone3.viciphone.com are up and functional. Once I get phone2.viciphone.com (columbus) up that will be all three sites. Each site will have multiple servers serving that sites domain.
But you can download and install ViciPhone on your own server. Just change the "Webphone URL" on the Admin --> System Settings to be wherever you installed it on your server. I.E. https://<FQDN>/viciphone.php
My SSL is working fine and i already made all those changes because during the cert setup the script gave me the above instructions as well. But i just double checked them and everything is as you mentioned. System settings URL done, edited webRTC template, changed my phone to web and used the template and set web to Y. I also applied the firewall fix you provided. I enabeld debug=Y for the phone but i don't see an error. Only thing i see is that the server it's connecting to is displayed by IP in the debug out and not FQDN. Could that be it?
