Behavior after a session timeout?
Hi. I'm trying ristreceiver and ristsender between Windows computers. I got this session timeout after a few hours but I have a question: after a session timeout, should RIST automatically reconnect?
Ristreceiver Log:
1733070519.041236|0.0|[INFO] {"flow_cumulative_stats":{"flow_id":1051551442,"received":1893451,"recovered":1903,"lost":0}}
1733070519.041348|2599016427584.0|[INFO] ************** Session Timeout after 2s of no data, deleting flow with id 1051551442 ***************
1733070519.041429|2599016427584.0|[INFO] Triggering data output thread termination
1733070519.048059|2599016427584.0|[INFO] Data output thread shutting down
1733070519.048338|2599016427584.0|[INFO] Resetting peer states
1733070519.048440|2599016427584.0|[INFO] Free flow peer list
1733070519.048536|2599016427584.0|[INFO] Deleting missing queue elements
1733070519.048616|2599016427584.0|[INFO] Deleting output buffer data
1733070519.048692|2599016427584.0|[INFO] Freeing data fifo queue
1733070519.049149|2599016427584.0|[INFO] Deleting flow
1733070521.373914|0.0|[INFO] Connection Status changed for Peer 2599015462432, new status is 1, peer connected count is 0`
Activity
Yes, session timeouts will stop stats printout as the flow is considered dead. However, the peer is still trying to connect and will automatically do so when the other side appears again (assuming it is on the same port). I just verified this with latest master. If you want sniff traffic after a session timeout and you can see that the rist internal communication messages are still being sent
It just happened. It has been running for a few hours without being able to reconnect. The traffic in wireshark shows udp packets on the destination ports. On the rist-sender side, I don't register that same traffic. Probably if I run rist-receiver on the same ip:port, it will reconnect as a new connection.
Edited by ManuelI started a new connection from another instance of rist-receiver on the same computer. The connection is successful but I am not receiving RTP data. I restarted the RTP encoder from the rist-sender side (thinking that might be the problem) and got no improvement.
2024-12-11 17:37:50 1733949470.768076|0.0|[INFO] Peer has been peer_connected_count, sending oob/api message: auth,172.17.0.1:49870,0.0.0.0:10899
2024-12-11 17:37:50 1733949470.768103|0.139689972858896|[INFO] Enabling reverse keepalive for peer 16
2024-12-11 17:37:50 1733949470.768173|0.139689972858896|[INFO] New keepalive received. MAC: 80:e8:2c:f3:dd:4f X: 0 R: 0 B: 1 A: 0 P: 0 E: 1 L: 0: N: 1 D: 1 T: 0 V: 0: J: 1 F: 0
2024-12-11 17:37:50 1733949470.768190|0.139689972858896|[INFO] New reverse RTCP peer connecting, peer_id 16, ports 32769 <- 1969
2024-12-11 17:37:50 1733949470.768196|0.139689972858896|[INFO] Successfully Authenticated peer 16
2024-12-11 17:37:50 1733949470.768201|0.139689972858896|[INFO] Peer 16 receiver name is now: pc-m
2024-12-11 17:37:50 1733949470.768205|0.139689972858896|[INFO] Peer 16 receiver with name pc-m reconnected
2024-12-11 17:37:50 1733949470.768208|0.0|[INFO] Connection Status changed for Peer 139689717702928, new status is 0, peer connected count is 1
2024-12-11 17:37:50 1733949470.894840|0.0|[INFO] {"sender-stats":{"peer":{"flow_id":3984866880,"id":16,"cname":"pc-m","type":"data","stats":{"quality":100,"sent":9,"received":7,"retransmitted":0,"bandwidth":5724,"retry_bandwidth":0,"bandwidth_skipped":0,"bloat_skipped":0,"retransmit_skipped":0,"rtt":31.4662692402526,"avg_rtt":8.3082836550315751,"retry_buffer_size":1,"cooldown_time":0}}}}
2024-12-11 17:37:50
2024-12-11 17:37:51 1733949471.893580|0.0|[INFO] {"sender-stats":{"peer":{"flow_id":3984866880,"id":16,"cname":"pc-m","type":"data","stats":{"quality":100,"sent":19,"received":20,"retransmitted":0,"bandwidth":10662,"retry_bandwidth":0,"bandwidth_skipped":0,"bloat_skipped":0,"retransmit_skipped":0,"rtt":31.277759060779744,"avg_rtt":21.42656814941768,"retry_buffer_size":1,"cooldown_time":0}}}}
2024-12-11 17:37:51
2024-12-11 17:37:52 1733949472.892110|0.0|[INFO] {"sender-stats":{"peer":{"flow_id":3984866880,"id":16,"cname":"pc-m","type":"data","stats":{"quality":100,"sent":20,"received":20,"retransmitted":0,"bandwidth":12190,"retry_bandwidth":0,"bandwidth_skipped":0,"bloat_skipped":0,"retransmit_skipped":0,"rtt":26.85573882174182,"avg_rtt":23.125864674862463,"retry_buffer_size":1,"cooldown_time":0}}}}
