search

twilio / OpenVBX

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

Voicemail will not play #280

Open Barth907 opened 10 years ago

Barth907 commented 10 years ago

I am new at using OpenVBX. I have installed it and have it setup to make and receive calls. If a voicemail is left on an inbound call, it will appear in the inbox. However, when I click "play" button a message pops up stating:

Authentication Required The server https//:api.twilio.com:80 requires a username and password The sever says: Twilio API.

There is an area to enter a username and password with a "login" button.

I've tried entering my username and password, but it still won't play.

I appreciate any advice! Thank You!

Gipetto commented 10 years ago

I haven't seen this before. I think the username/password is probably the Twilio API wanting your sid & token for authentication. Let me dig in to this a bit.

Barth907 commented 10 years ago

I tried playing the recording directly from my Twilio account and it gave me a similar message. The only difference is that it stated :443 instead of :80

I was able to view the error. It looks like you are right about the SID and Token.

Here's the error message:

20003 Your AccountSid or AuthToken was incorrect. Authentication Error - No credentials provided https://www.twilio.com/docs/errors/20003 401

Unfortunately, I don't have the knowledge to actually fix the problem. Any thoughts?

Barth907 commented 10 years ago

Okay, so I've spent the entire afternoon troubleshooting and here's what I've found.

If I select "disable" in my Twilio account under Enforce HTTP Auth on Media URLs, then I am able to play messages in OpenVBX and my Twilio account without issue.

I'm concerned that the recordings could be unsecured if I go this route. Is it acceptable to leave it like this or is their a better way?

Gipetto commented 10 years ago

I suspected that might be it, but hadn't had a chance to really get in to it. OpenVBX doesn't handle the authenticated urls at all, unfortunately.

As for security I guess it would depend if you're up against any regulations or not. In general the recording urls are pretty random and hard to guess so the likelihood of someone just getting at your recordings is pretty low. If you're subject to any kind of regulation that requires securing the url then you'll probably need to invest some time in to configuring OpenVBX to support those authenticated urls.

At this time OpenVBX is not under active development and gets limited support.