Skip to main content

I am testing Ring Central API to determine if it is a good fit for our company.

I am getting around 6 second second response times for subscription notifications in the development environment. Is this normal? Or is it because I am located in Australia?

I am listening for: /restapi/v1.0/account/~/presence

When I change my status, or start a call using the RC Phone app, it takes about 6 seconds before the event is triggered. I have tried using PubNub and WebHooks and get the same result. The code that I have is just subscribing to the event, then logging to console when triggered. I am using this API for nodejs: require('@ringcentral/subscriptions').Subscriptions

Yes it is normal. I observed the same delay (around 6 secs as you stated) on production environment for user presence status change.

So if I want to have a screen pop up for a user when they answer the phone (e.g. detect call answered, and lookup caller to bring up details on screen), they must wait for at least 6 seconds. Is there another way to get this to happen faster through the API? I saw that the desktop app can open an executable on incoming call, but it would mean that each user would need to be set up with this and if we would like to do other status change detections in the future, we would still have the delay.

Reply


Terms & ConditionsCookie settings