Closed wiserweb closed 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
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."
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.
Note: OpenVBX and Twilio will work with Let's Encrypt SSL Certificate.