Skip to main content
I keep getting this error for the past 12 hours.

Initially, I figured it was transient, but it has persisted for a while now.

Is there anything I need to do to get this resolved?

StatusCode: 503, ReasonPhrase: 'Service Unavailable', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
Connection: keep-alive
Retry-After: 40
X-Rate-Limit-Group: light
X-Rate-Limit-Limit: 50
X-Rate-Limit-Remaining: 49
X-Rate-Limit-Window: 60
RoutingKey: SJC12P01
RCRequestId: 16ca2286-be15-11ec-bf06-005056bb9532
Date: Sun, 17 Apr 2022 06:10:32 GMT
Server: nginx
Content-Length: 107
Content-Type: application/json
}
Content: {
"errorCode" : "AGW-110",
"message" : "Internal Server Error. Consult RC Support.",
"errors" : [ ]
}


Request:
Method: GET, RequestUri: 'https://platform.devtest.ringcentral.com/restapi/v1.0/account/~/a2p-sms/messages', Version: 1.1, Content: <null>, Headers:
{
X-User-Agent: Unknown/0.0.1 RingCentral.Net/5.0.0
Authorization: Bearer <removed>
}

Hey @Smit Shah,

I believe A2P SMS permission needs to be enabled for both the number and the app, also the A2P SMS may not be available for sandbox accounts(although this has to be verified)

@Velmurugan B is correct about A2P SMS not being available in sandbox. To call these endpoints, you will need to work with the support team to manually graduate your app to production. Vel is also right in asserting that in order for A2P SMS to work:

- The app needs the A2P SMS scope or permission.
- The phone number needs to be enabled for A2P SMS, which can be [requested via a form][1]. Please note, that only account admins can request numbers to be provisioned for SMS.


[1]: https://gamechanging.dev/sms/

Reply


Terms & ConditionsCookie settings