This message was deleted.

Hi, would you have any detail about the issues you are having?

We are basically in the same situation, we always have some trouble with egress

@few-night-99427 can you share what issues you are experiencing? and with what type of Egress?

@dry-elephant-14928 we are trying to use track egress with websocket streaming, but it always fails for us (after 40-50 sec). There’s some communication about it here: https://github.com/livekit/egress/issues/210 There’s a test project mentioned in the comments which is a skeleton of our setup, with that it is easily reproducible, but in production, with deployed components, the result is the same. We also have another similar websocket solution using the same websocket endpoint in our system, which works well so we do not think that the problem is with our code. cc: @dazzling-ghost-11795

@few-night-99427 The issue above should be resolved (we are waiting for confirmation before closing it). The timeout previously was due to the lack of ping/pong messages on the websocket. So when audio track is muted, there aren't any communications over the socket. That could cause the TCP connection to get dropped by the intermediary routers/NAT devices.

@dry-elephant-14928 yesterday i tested this, my audio track was not muted, i was also speaking, but the error still happened

@few-night-99427 could you file an issue for this? it sounds different from the above. if you could include repro steps, we will give it a try

we are seeing disconnection of websocket stream, on audio track mute. Currently video has moved on lower priority for us, so didnt raise it

@dry-elephant-14928 sorry for the late reply, here is the issue: https://github.com/livekit/egress/issues/410