Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocket must heartbeat #68

Closed
tylerlong opened this issue Dec 1, 2023 · 1 comment · Fixed by #69
Closed

WebSocket must heartbeat #68

tylerlong opened this issue Dec 1, 2023 · 1 comment · Fixed by #69

Comments

@tylerlong
Copy link
Contributor

tylerlong commented Dec 1, 2023

There is idleTimeout, by default it's 30 minutes. If in 30 minutes there is no traffic, the connection will time out:

{
    "errorCode": "WSG-902",
    "message": "Idle timeout expired"
  }

WebSocket ping frame doesn't count as traffic, so you cannot rely on WebSocket library's auto-ping feature.

It's not a problem for apps with lots of traffic. But for app with not so much traffic, the notification will stop working after 30 minutes.

Refer to the implementation in C# https://github.com/ringcentral/RingCentral.Net/blob/master/RingCentral.Net.WebSocket/WebSocketExtension.cs#L90-L101

@tylerlong
Copy link
Contributor Author

I have fixed the issue for the Ruby SDK ringcentral/ringcentral-ruby@d07b09d...master

I am going to update the Python SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant