Welcome to the RingCentral Community

Phong,

No changes on our end. I'm using the https://developers.ringcentral.com/api-reference/Subscriptions/createSubscription user interface to create the new subscription. I've successfully removed the old but having trouble getting the "createSubscription" to work. Am currently getting a "WebHook server response is invalid" SUB-525 error. It may have to do with the value I'm specifiying for "verificationToken". What value should be supplied for that parameter?

Thanks

Ok. Webhooks still not delivering to our production account (w/new subscription). What to check next?

Can you test if it works for your local address using e.g. ngrok? Where, btw do you run your code? Is that on AWS and is behind an AWS Load Balancer etc.?

Phong,

I've just tested locally w/ngrok. It's working, but it appears that my production subscription is also, now working again so not sure that this tells us anything at this point.

Now I am sure that it relates to this issue.

https://community.ringcentral.com/articles/98296/alert-interruptions-of-service-to-push-notificatio.html

Thanks for the update Phong. So, in the process of getting our webhook process re-started I removed all the subscriptions in our list. Unfortunately, I didn't realize that each subscription was on behalf of each of our RC companies (using our product). I've been trying to re-create the subscriptions on behalf of these clients (companies) without any luck. I have all TokenInfo and accees/refresh tokens for these clients. Will each client have to log back in to establish these subscriptions, or is there a way for me to do that?

No, you don't have to ask your clients to login again. As long as the tokens are valid and you can refresh them using the refresh tokens, you are good to call APIs. The only problem is to create new, update or renew subscriptions will be interrupted during the downtime when it happens. Fortunately, the team is actively working on it so they will restore the operation as soon as they can. My experience on this is that some time it is down for just a few minutes. But there last week once it was down for around 3 hrs. All you need to do now is if you can change the implementation, just handle the failure gracefully by setting a timer to retry every minute.

Actually, our prod servers are behind a Rackspace load balancer.

I have heard from others that they experience the same problem with certificates and load balancers. Are you able to try with a local address or direct server?

Nevermind Phong. I "fat fingered" our server address. The new subscription has been created. Will check again for events and report back. Thanks