Call not hangup on external connection loss

[appbasehamburg]

Describe the bug An active call using the matrix-js-sdk (current stable version) is not hangup when an external source leads to a connection loss (e.g. browser reload).

To Reproduce Steps to reproduce the behavior:

1. Start a call between two matrix-js-sdk clients
2. Reload the browser tab of client a
3. Client b stays in the call state without any chance of knowing the connection is lost

Expected behavior After a short timeout the call should stop for client b.

Is there any configuration or documentation we missed?

[SimonBrandner]

I believe this is because the call should try to re-connect when the other client loses the connection. I believe there is some sort of a timeout, perhaps it's too short?

[appbasehamburg]

Thanks for the quick response, it's more like the other way around: If there is a timeout (we missed somehow) we want it to be shorter. In our case client a and b are in a call, client b reloads the browser / looses the connection somehow. Client a will never (or very late) be aware of the connection loss.

[SimonBrandner]

Agreed, made a mental typo, I meant too long :P