Using WebSocket Heartbeats
Description
This API is used to keep the established WebSocket message stream alive. If the meeting server does not receive a heartbeat request within 180 seconds, it closes the WebSocket connection. It is recommended that a heartbeat request be sent every minute.
Parameter |
Type |
Description |
---|---|---|
action |
String |
"HeartBeat" |
sequence |
String |
Timestamp when a message is generated, in milliseconds. |
Example WebSocket Heartbeat Request
{ "sequence": "000000000000000001611993655770", "action": "HeartBeat" }
Parameter |
Type |
Description |
---|---|---|
action |
String |
"HeartBeat" |
sequence |
String |
Timestamp when a message is generated, in milliseconds. The value is the same as sequence in the heartbeat request. |
Example WebSocket Heartbeat Response
{ "sequence": "000000000000000001611993655770", "action": "HeartBeat" }
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot