We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
The text was updated successfully, but these errors were encountered:
I have fixed the issue for the Ruby SDK ringcentral/ringcentral-ruby@d07b09d...master
I am going to update the Python SDK.
Sorry, something went wrong.
Merge pull request #69 from tylerlong/master
0d79ad4
Add heartbeat feature to WebSocket, fix #68
Successfully merging a pull request may close this issue.
There is idleTimeout, by default it's 30 minutes. If in 30 minutes there is no traffic, the connection will time out:
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
The text was updated successfully, but these errors were encountered: