I am trying to use Skyetel as it is one of the preferred providers and after seeing that the latest release supports SMS with them. I believe incoming SMS messages use the webhook generated by 3cx, and those are working just fine. Outgoing, I imagine, uses the configured API id and secret to send SMS messages via the provider's API, and that is failing for me. I've tested on both StartUp, and hosted. So far the only thing I can find in the logs is in the "events" and it's a message like this:
I've tested changing the main trunk did to just "1250xxxxxxx" (without the +) as well since their API doesn't like the plus if you use it directly.
On that, I've also tested sending an SMS directly using the same API id and key as in the sms settings using curl, and that works just fine. If I break one of the three rules (https://support.skyetel.com/hc/en-us/articles/360056299914-SMS-MMS-API ) that the skyetel docs say results in the Unauthorized response, I get an identical response from curl as from the events log:
Because of that I feel somewhat confident that the API call is reaching Skyetel, but something about it is wrong.
Failed to send message(s) to the provider 'skyetel' from '+1250xxxxxxx' to '+1250yyyyyyy'. Exception: {"message":"Unauthorized"}I've tested changing the main trunk did to just "1250xxxxxxx" (without the +) as well since their API doesn't like the plus if you use it directly.
On that, I've also tested sending an SMS directly using the same API id and key as in the sms settings using curl, and that works just fine. If I break one of the three rules (https://support.skyetel.com/hc/en-us/articles/360056299914-SMS-MMS-API ) that the skyetel docs say results in the Unauthorized response, I get an identical response from curl as from the events log:
{"message":"Unauthorized"}Because of that I feel somewhat confident that the API call is reaching Skyetel, but something about it is wrong.
