search

l7mp / stunner

A Kubernetes media gateway for WebRTC. Contact: info@l7mp.io
https://l7mp.io
MIT License
737 stars 56 forks source link

No timeout for inactive peers? #107

Closed kenaniah closed 11 months ago

kenaniah commented 11 months ago

We have a situation in which some of the peers do not signal their disconnection (and STUNner does not appear to be handling UDP timeouts). Downstream, our application is unable to detect these disconnections (since its connection to STUNner is still live).

Is there a way to detect and/or configure peer disconnections & timeouts?

rg0now commented 11 months ago

STUNner is in fact a glorified proxy, so timeouts may refer to connections to clients or peers. The client-side connection is always TURN so RFC8856 applies: allocations last for 10 minutes by default without being refreshed, but clients can request a custom allocation lifetime in Allocate or Refresh requests. If you want your TURN clients to time out fast request a small lifetime, STUNner will respect such requests (provided your TURN client lib supports setting custom timeouts, I guess most JavaScript WebRTC stacks won't). The peer-side connection is always plain UDP and STUNner uses the default idle UDP timeout of the platform, which can be anything from 30 seconds to several minutes.

kenaniah commented 11 months ago

Perfect. Thanks for the info and the links!