1. Check microphone and camera permissions
Use the browser's site-permission controls to confirm that Chat256 can access the microphone and camera. If permission was previously denied, change the permission and reload the call page.
2. Update the browser
Calling depends on WebRTC support. Use a current version of a mainstream browser and avoid privacy extensions that block WebRTC APIs, WebSocket connections or required media permissions.
3. Test the network
Corporate, school and public Wi-Fi networks may restrict peer-to-peer traffic. Mobile networks can also use restrictive NAT. If direct connectivity cannot be established, TURN may be needed to relay the call.
4. No sound or one-way audio
Check the selected microphone and output device, browser permission, operating-system mute state and whether another application has exclusive control of the microphone. If only one participant has audio, check both sides independently.
5. Camera works but video does not arrive
Confirm camera permission and check whether another application is using the camera. A call can also establish successfully while a media track fails because of device or network constraints.
6. Calls connect on one network but not another
This pattern often indicates NAT or firewall differences. A properly configured TURN service can provide a relay route where direct ICE candidates are blocked. If the live service reports a relay error, retry on a different network and report the exact error to support.
Calling privacy reminder
WebRTC media is encrypted in transit, but network infrastructure can still see connection metadata. The person you call can also record the conversation independently of the transport encryption.