Dani
Member
Setup
In several cases, the first party's audio-only publish failed with the status info "Failed by ICE keep alive", although the first party had a good connection:
- WCS 5.3.498, Web SDK 2.0.286, WebRTC only.
- Keep-alive settings are the defaults: keep_alive.algorithm=HIGH_LEVEL, keep_alive.server_interval=5000, keep_alive.probes=10.
In several cases, the first party's audio-only publish failed with the status info "Failed by ICE keep alive", although the first party had a good connection:
- The video publish's RTT in getStats was 11 ms in one case and 16 ms in the other, with no packet loss. Video bitrate was 2.2-2.5 Mbps.
- Both had been publishing for over an hour.
- The Web SDK session (WebSocket) stayed ESTABLISHED.
- The selected ICE candidate pair was TCP (prflx)
- What exactly does the server check for "ICE keep alive" on a publish stream? Is it the STUN binding requests and responses on that stream's own ICE connection? Which timeout applies, and can it be configured?
- Is a low-bitrate audio-only stream (Opus) over TCP known to be more exposed to this? For example, could the browser send consent checks less often on that connection?
- Which server log or CDR field shows the last STUN activity for a stream, so we can see what happened before the failure?
- Is there a setting to make an audio-only stream more robust?