Engineering guides / Realtime communication and P2P engineering
By Arte Soft engineering · 24 October 2026
NAT traversal consulting: diagnose why direct connections fail
A failed direct connection is not automatically an application signaling bug. NAT traversal work needs evidence from both peers, including candidate gathering, the selected path and the moment connectivity stopped making progress.
Define the failed connection precisely
Record whether neither peer connects, only one direction of media works or a call succeeds only through relay. Note the platforms, network types and sequence used to start the session. A broad statement such as “mobile data does not work” can conceal several unrelated defects. Preserve enough timing and session identity to compare a failed attempt with a successful one under the same conditions.
Inspect the ICE lifecycle
Check which local candidates were gathered, which remote candidates arrived and whether they were applied to the correct session generation. Late candidates from a previous attempt can create misleading logs. Review completion and timeout handling rather than assuming that no selected pair means no candidate existed. The outcome should identify where progress stopped, not merely repeat a browser’s final connection status.
Test relay reachability separately
A fallback service can be configured but unreachable from the network that needs it most. Verify credentials, expiry behavior and the transport options actually deployed. Compare forced-relay tests with normal candidate selection. This isolates relay problems from direct-path limitations. A relay that works in the developer’s environment is not proof that its addresses, certificates or ports are usable from a restrictive customer network.
Use network labels carefully
Home broadband, enterprise Wi-Fi and carrier networks contain many configurations. Do not infer an exact NAT behavior from a marketing name or a public IP address alone. Use observed connectivity checks and controlled comparisons. Test IPv4 and IPv6 conditions when relevant, and distinguish an application regression from a network policy that deliberately blocks the required traffic. Some constraints require a fallback rather than a cleverer direct connection attempt.
Deliver an evidence-based repair plan
The audit should provide sanitized traces from both endpoints, a candidate-path summary and experiments ranked by likely value. Proposed fixes may involve signaling order, ICE restart handling, relay configuration or timeout policy. Measure setup success and time to usable media after the change. Avoid publishing a universal direct-connection percentage from a small convenience sample that does not represent your users.
Traversal evidence checklist
- Preserve sanitized candidate information from both peers and relate it to a specific attempt rather than combining several retries.
- Test the relay path independently, including the configured credential lifetime and the network that originally failed.
- Write down which observed result supports each conclusion, separating a confirmed signaling defect from a suspected restriction that still needs a controlled experiment.
Set a supportable completion boundary
A traversal engagement can establish and verify a relay fallback for the tested environments without promising direct connectivity everywhere. Wonek is relevant communication engineering R&D context, while Wonek communication work remains an engineering R&D reference. Bring affected network examples and permission to run synthetic calls. Acceptance should name the tested combinations, diagnostic visibility and remaining exclusions so your support team can distinguish a known limitation from a new regression.
Relevant Arte Soft work
Wonek — communication engineering R&D, not a shipped or audited messaging product is our own product or engineering project. It provides context for the work we discuss here; it is not a claim of identical results for every client deployment.
Sources and further reading
Need help with NAT traversal diagnostic audit?
Send the current app, system or brief, the behaviour you need and your constraints. We can agree a discovery, implementation or repair scope with concrete acceptance criteria.
Discuss this with Arte Soft