We have an application that archives company meeting recordings using RingCentral APIs. The app is authorized as a Super Admin so that it has permissions to act for all users.
1. Get list of all extensions in company
/restapi/v1.0/account/~/extension
2. For each extension, retrieve list of meeting recordings ($user->id extracted from Query 1)
/restapi/v1.0/account/~/extension/' . $user->id . '/meeting-recordings
3. For each meeting recording for the user, check if the file exists on Company Archive storage. If not, download the file and sync it to Archive storage.
On October 20, we started receiving 401 Unauthorized requests. I observed two changes here: (See below errors)
- The server where meetings are held changed from ringcentral.zoom.us to media.ringcentral.com
- Requests to download now require Authorization header.
Once we added the Authorization header to downloads, we were stable for about 4 days.
https://media.ringcentral.com/restapi/v1.0/account/2190515014/extension/2190559014/meeting/1489635117/recordings/61e6eeaa-71a0-492e-aa70-02ad8a633f62/content
Resolving media.ringcentral.com (media.ringcentral.com)... 199.255.120.135
Connecting to media.ringcentral.com (media.ringcentral.com)|199.255.120.135|:443... connected.
HTTP request sent, awaiting response... 401 UnauthorizedUsername/Password Authentication Failed.
Come October 24, we started consistently seeing 503 Service Unavailable.
https://media.ringcentral.com/restapi/v1.0/account/2190515014/extension/2190559014/meeting/1489635117/recordings/cc2db13f-44f1-4633-a849-ae565949bf95/content
Resolving media.ringcentral.com (media.ringcentral.com)... 199.255.120.135
Connecting to media.ringcentral.com (media.ringcentral.com)|199.255.120.135|:443... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
How can I trace the source of the 503's, as they are consistent and occur regularly?
