Vivox status 1058 (RTP Timeout) signals a failure of the voice audio stream, most commonly caused by network or firewall settings blocking UDP traffic. This article outlines the primary causes, including unstable connections and software conflicts, and provides a resolution guide. Key steps include verifying firewall rules against Vivox requirements, implementing a controlled retry strategy for dropped connections, and checking for service disruptions on the Unity Status page.
Symptoms:
The Vivox SDK status code VxErrorRtpTimeout (1058) occurs when the connection for voice audio data (the RTP stream) fails to establish or is interrupted. This is distinct from login or text channel connectivity and points specifically to a problem with the transmission of audio packets.
Note: In older SDKs, this error may be reported as status code 5020.
Cause:
This error can occur in several scenarios, ranging from common to rare:
-
Network and Firewall Restrictions This is the most frequent cause. The client is unable to send or receive UDP packets from the Vivox audio servers. This often manifests as a "Never RTP" timeout, where the connection is dropped after a fixed period (e.g., 15 seconds) because no audio data was ever exchanged. Common examples include:
- Corporate or local firewalls blocking the necessary UDP port ranges required by Vivox.
- Network Address Translation (NAT) devices or routers that are not configured to allow the required traffic.
- Asymmetrical network rules, where different policies are applied to different devices (e.g., PCs vs. consoles) on the same network.
- Unstable Network Connection If a user's internet connection is unstable or is lost entirely, an active RTP stream can be interrupted. This results in a "Lost RTP" timeout, where a previously working audio connection is dropped. Since the system has confirmed that a connection was recently active, it allows for a longer period of interruption before timing out compared to the "Never RTP" case.
- Vivox Server-Side Issues While less common, the issue can sometimes originate from the Vivox backend. RTP Timeouts can occur during some scheduled or emergency server maintenance, or as the result of a temporary service disruption, such as the sudden failure of an individual media server node. In these cases, the issue is not related to the user's local environment.
- Client-Side Software Conflicts Other software on the user's machine can interfere with the Vivox SDK's ability to access audio hardware or transmit data. For example, aggressively configured antivirus or security software might block the application from sending UDP traffic, leading to an RTP timeout.
Resolution:
The resolution for an RTP Timeout (1058) focuses on diagnosing and fixing issues with the audio data path. Follow these steps to identify and resolve the root cause.
-
1. Verify Network and Firewall Configuration This is the most common cause of 1058 errors. You must ensure that your network allows UDP traffic to and from Vivox servers on the required port ranges.
- Action: Review the official Vivox IP and port requirements and confirm with your network administrator or IT department that all necessary ports are open for outbound traffic. You can find the required ranges in this article: Vivox: What IPs and ports are required for Vivox to work?
- Tip: Pay close attention to asymmetrical rules. In a corporate environment, it's possible for firewall rules to be applied differently to PCs and consoles, even if they are on the same network.
-
2. Implement a Controlled Retry Strategy for Unstable Connections If the timeout is due to intermittent network instability (a "Lost RTP" timeout), automatically retrying the channel join is a valid strategy.
- Action: Before attempting to rejoin, first check for an active internet connection. If the connection is restored, you can implement a retry mechanism.
- Best Practice: Use an exponential backoff technique for automated retries (e.g., retry immediately, then after 5 seconds, then after 15 seconds) for a limited number of attempts to avoid flooding the server. Alternatively, provide a UI button for the user to initiate the retry manually.
-
3. Investigate Client-Side Software Conflicts Security software on the client machine can block the application's ability to send or receive audio data.
- Action: To diagnose this, temporarily disable antivirus or other security software and test the connection again.
- Solution: If disabling the software resolves the issue, add an exception or "allowlist" rule for your application to permit its network traffic.
-
4. Check for Vivox Service Disruptions If you have ruled out local network and software issues, the problem may be on the Vivox backend.
- Action: Check the official Unity Status page for any reported incidents related to Vivox services.
- Next Step: If no incidents are reported and the issue persists across multiple devices and networks, gather detailed logs and contact Unity Support for further investigation.