Member Junction
    Preparing search index...

    Variable REALTIME_RESUMPTION_RECOVERY_WINDOW_MSConst

    REALTIME_RESUMPTION_RECOVERY_WINDOW_MS: 45000 = 45_000

    Default time a reconnect keeps trying after the connection is gone: from the start of the cycle for a lost connection, and from the end of the old connection (the provider limit, or the end a goAway announced) for a planned move, whose old connection keeps the call going until then. 45 s outlasts the outages a call should survive (Wi-Fi roaming, a VPN reconnect, a short tunnel: the #6462 smoke's 10 s cut ended the call under the old 4 s schedule), yet is short enough that the user is not left on "Resuming" for an outage that is not ending.

    The window only stops new attempts: one already running finishes on its own timeouts (up to REALTIME_RESUMPTION_PREPARE_TIMEOUT_MS plus REALTIME_RESUMPTION_ATTEMPT_TIMEOUT_MS, 30 s by default), and the listed schedule (REALTIME_RESUMPTION_RETRY_DELAYS_MS) always runs in full. So with the defaults a lost connection can stay on "Resuming" for up to about 94 s (three attempts that each time out after 30 s, plus the 1 s and 3 s waits), and a planned move's cycle can run until about 75 s after its old connection ends. A close the provider meant (not a network loss) is retried the same way: closes are not classified.