Disruptions in communication can occur when a user is removed from a channel or logged out in response to a prolonged network disruption. The expected behavior on platforms that support Automatic Connection Recovery in Vivox SDK versions 5.9.0 and later is that voice communication automatically recovers from brief disruptions or changes in network connectivity. For example, network connectivity will change when roaming between networks or when a user's network connection is unstable.
It is expected that the Vivox SDK will log out a user with the error code Automatic Reconnection Failure (10101) if a continuous disruption in connectivity lasts too long (more than 30 seconds by default). There are also circumstances under which the error code will be '0' (Success), indicating that the connection was lost, but the SDK never attempted to reconnect the user.
If users lose only voice audio but remain logged in due to an RTP Timeout, this might indicate that server settings need to be adjusted so that users are either cleanly logged out or fully reconnected. In practice, this manifests as a vx_evt_media_stream_updated event with state = session_media_disconnected and status_code = 1058 (RTP Timeout) or status_code = 1095 (Server RTP Timeout). Note that developers should also handle events that indicate a partial connection failure, which can sometimes occur after mobile app suspension.
If users consistently experience a logout after approximately 30 seconds, this might indicate that server settings need to be adjusted to ensure that the Vivox SDK will be able to properly monitor its connection to the internet.
If, after less than 30 seconds of network disconnectivity, users are logged out or experience a loss of voice without being logged out, a component of the server might need to be updated.
To request adjustments to server settings for any of the above or other help troubleshooting issues with automatic connection recovery, please reach out to your Unity representative.
Read more in the Automatic connection recovery Developer Guide topic.
For problems specific to Nintendo Switch, see the Nintendo Switch Developer Guide topic Network considerations.
Article is closed for comments.