Servers close sockets consistent with keep-alive spec, regardless of client sending KEEP_ALIVE_RESPs

Realtime Media Streams
1

Using my development keys, I’ve been able to successfully stream media but only for ~60 seconds. (I’ve previously reported here that any media connections would not stream data using development keys in the handshake request signature, but this appears to be resolved.) This seems consistent with the behavior for not responding to KEEP_ALIVE_REQ messages as described by the RTMS docs.

I immediately respond to KEEP_ALIVE_REQ messages with KEEP_ALIVE_RESP messages from my client’s handshake and media server connections. I ensure that the timestamp is in millis from epoch and that the timestamp is after the server clock timestamp sent from the KEEP_ALIVE_REQ. e.g.:

{"msg_type":13,"timestamp":1750963565521}

To be completely sure, I am also responding to WebSocket pings with pongs.

Key context: I am not using any SDK; my organization is building an RTMS client in Ruby.

Thanks for your help!

2

@davej ,

The timestamp which you should sent back should be the exact timestamp in msg.timestamp