search

twilio / OpenVBX

OpenVBX is a web-based open source phone system for business.
http://openvbx.org
Other
699 stars 342 forks source link

Updated README, mandatory valid SSL Certificate #355

Closed wiserweb closed 8 years ago

wiserweb commented 8 years ago

It is mandatory to utilize a valid SSL Certificate with OpenVBX and Twilio. If a certificate is expired, self-signed or otherwise Twilio will not allow the connection and the calls will be dropped immediately.

If calls are dropped verify (https://www.twilio.com/user/account/monitor/alerts)

Error

Twilio tried to validate your SSL certificate but was unable to find it in our certificate store.

You are using a self signed certificate.
The certificate authority you are using is not on our list of approved certificate authorities.
Do not use a self signed certificate.
Twilio uses CAs that are approved by Mozilla, you can find the full list [here]. (https://mozillacaprogram.secure.force.com/CA/IncludedCACertificateReport).

Note: OpenVBX and Twilio will work with Let's Encrypt SSL Certificate.

Gipetto commented 8 years ago

This is a good idea, but I decided on more verbose addition to the ReadMe: https://github.com/twilio/OpenVBX/commit/e36a3b1febe06f1431eaed774aa6bb7dd65bd002

wiserweb commented 8 years ago

Ok, that's great.

Perhaps consider adding note that you should not run OpenVBX in HTTP mode (clear text) unless you have it secured in internal network behind firewall.

Also, maybe add the symptom if your certificate expires or is self-signed. This took some time to troubleshoot initially so it could save admins some grief.

"Self-signed certificates and expired certificates are not supported and will caused dropped calls."