Sweet, thanks for the detective work!
That's a tough call.
The client had to have nulled those values manually to get to that
state.
I do agree that a tenant without a valid Sid and Token pair shouldn't
be given an application, but this also leaves then in an awkward state
of not having an application. I guess here its safe to assume that
nulled Sid & Token pairs on a tenant should indicate an inactive
tenant. And we deal with that later (if it ever comes up again).
I'm working on upgrading the Twilio REST library in OpenVBX (am
working on the upgrade routine now, actually) and I'll skip over
tenants that don't have a valid sid/token pair.
On a side note, you might ask your client if he/she remembers doing
this and what the reason was. It very well could be that tenants
currently can't be deleted or disabled. Providing that option in the
future would probably get around running in to this again. I'll put
that on our list of things to do (a very long list!).
Shawn
On Aug 24, 2:28 pm, James Cuzella <
james.cuze...@standingcloud.com>
wrote:
> Shawn,
>
> Good news... I've setup xdebug on a local VM and traced the issue back to a
> REST request to the twilio API in '/updates/50.php' on line 34 during the '*
> create_application*' function.
>
> The request is being made for a tenant named 'mim' which our client set up
> on his system. It looks like $twilio_sid and $twilio_token are empty for
> this tenant... which is probably why the API server returns a 404.
>
> Here's the response from
api.twilio.com/2010-04-01:
>
> <?xml version="1.0"?>
> <TwilioResponse><RestException><Status>404</Status><Message>The requested
> resource was not found</Message></RestException></TwilioResponse>
>
> It looks like this is what's holding up the upgrade process for our client.
> Is this a simple misconfiguration issue on his part, or should the REST
> requests not even be made for users without a $twilio_sid?
>
> James Cuzella
> Jr Systems Administrator
> Standing Cloud, Inc.
>
(303) 747-3844 x 907http://www.standingcloud.com/