Seamless Communication with Automatic Reconnection
When the internet connection drops momentarily, the call doesn't end — the connection is automatically re-established in the background, and most of the time you won't even notice.
Mobile networks fluctuate, Wi-Fi drops for a moment, a user enters an elevator — in real life, connections are not perfect. Bitenta manages this without losing the call: the browser's ICE connection status is continuously monitored. When the connection status falls to “disconnected” or “failed”, the call isn't terminated; after a short wait, the WebRTC ICE negotiation is restarted (restartIce) and a new network path is found. This is attempted up to 3 times in the background until the connection is restored; once connected, the attempt counter resets. Neither the representative nor the visitor needs to press a single button — everything is automatic and happens within seconds.
Drop → recovery → resume
Disconnection Detection
The ICE connection status is continuously monitored; failed/disconnected states are detected instantly.
ICE Restart
After a ≈1 second wait, restartIce is initiated to negotiate a new network path.
Call Continues
The connection is restored within up to 3 attempts; the counter resets, and the call continues.
The mechanism that keeps the call alive
Detection, recovery and retry — all automatic.
Drop detection
The WebRTC ICE connection state is continuously monitored. When the state becomes “disconnected” or “failed”, the outage is noticed instantly.
Recovery with ICE restart
After a short wait (≈1 s), if the problem persists, restartIce is called; a new network path is negotiated and the call continues.
Up to 3 attempts
It retries in the background up to 3 times until the connection returns. On a successful connection the retry counter resets.
Resilient to network changes
Even when switching from Wi-Fi to mobile data, a new path is found; the session stays DTLS-SRTP encrypted and the call does not drop.
What you gain with auto reconnect
Up to 3 Attempts
The system retries in the background until the connection is restored; the counter resets upon successful connection.
Resilient to Network Changes
When switching from Wi-Fi to mobile data, ICE restart finds a new path and the call doesn't drop.
Within Seconds
During brief disconnections, the user often doesn't notice the interruption.
No Intervention Required
Neither the representative nor the visitor needs to press any buttons; detection and recovery are fully automatic.
Status Monitoring Included
Alerts when connection quality deteriorates; reconnection kicks in if it worsens.
Encrypted Session Protected
The DTLS-SRTP encrypted, secure session continues during reconnection.
Frequently asked questions
Does the call end when the internet drops momentarily?
No. The connection status is continuously monitored; when a disconnection is detected, the call isn't terminated, and the system attempts to re-establish the connection in the background.
How does reconnection work?
When the browser's ICE connection status is “failed” or “disconnected”, after a short wait (≈1 second), the WebRTC ICE negotiation is restarted (restartIce). This finds a new network path and continues the call.
How many attempts are made?
The system retries up to 3 times in the background until the connection is restored. Once connected, the attempt counter resets; if all 3 attempts fail, the call is safely terminated.
Will my call drop if I switch from Wi-Fi to mobile data?
No. When the network changes, ICE restart finds a new path and the call continues from where it left off — the user often doesn't notice the interruption.
Do I need to do anything to reconnect?
No. Neither the representative nor the visitor needs to press any buttons; detection and recovery are fully automatic.
How long does recovery take?
Usually within seconds. During brief disconnections, the call flow continues almost uninterrupted.