Skip to main content
Question

Renew Subscription fail

  • August 23, 2017
  • 8 replies
  • 1689 views

Are the renew subscription requiere that webhook respond within 1000 milliseconds because I'm getting a unreachable error? Maybe you should put more time because this depend on a lot of thing that we don't always have control. I think that 5000 should be enough for everyone. Or maybe we should be able to set "never expire"

8 replies

  • Known Participant
  • 105 replies
  • August 23, 2017
Have you setup an event filter for WebHook expiry events? 
/restapi/v1.0/subscription/~?threshold=XXX&interval=YYY

Using this event filter you can manage the threshold and the interval for the events and you can re-subscribe later. 

For more information on how to receive expiry events, please take a look at our 

QuickStart Guide for Subscription using Webhooks

  • Author
  • Participating Frequently
  • 8 replies
  • August 23, 2017
The issue is not about the expiry event but with the 1000 sec too short for us. So if the API try to renew the webhook, but got an "unreachable" error because 1000sec is over, I will get the same problem.

  • Author
  • Participating Frequently
  • 8 replies
  • August 23, 2017
So what I suggest is one of:  remove the need to renew subscription or raise the 1000ms limit at least

  • Author
  • Participating Frequently
  • 8 replies
  • August 26, 2017
I have do some test with some other API endpoint and your API, and a lot of time, this can take more than 1000 ms. So I think this is very very restrictive and should be raise. I never reach 3000ms, So I think this is enough. Sometimes, I reach a little bit over 2000.

  • 0 replies
  • August 27, 2017
The 1000ms requirement should be for general response, e.g. creating a webhook (verification) and events. It's interesting that you are only seeing this during subscription renewal. If this is the case, you can proactively renew the subscription since you know the expiration time. When you see a verification header you can have your server respond immediately without calling the other API endpoint.

We are looking into non-expiring webhooks but the above may be able to solve your situation now.

  • Author
  • Participating Frequently
  • 8 replies
  • August 27, 2017
This is what I already do. Using the renew endpoint to renew it before. But got this issue. But I think I have an idea why now. Will do some test and tell you if this work. Thanks for reply

  • Author
  • Participating Frequently
  • 8 replies
  • September 6, 2017
Finally. My test doesn't seem to give result. Always have the 
{
    "errorCode": "SUB-521",
    "message": "WebHook is not reachable",
    "errors": [
        {
            "errorCode": "SUB-521",
            "message": "WebHook is not reachable"
        }
    ]
}
error and this is exactly the same thing when I register the webhook the first time and this is not fast enough for ringcentral. Need to retry a lot of time until this work. But renewing make the webhook deleted if fail and I need to register it again...

  • Author
  • Participating Frequently
  • 8 replies
  • September 25, 2017
Any news on that?

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings