Open Bug 975225 Opened 11 years ago Updated 2 years ago

ICE/TURN failure to punch hole on Verizon 4G via EasyTether (apprtc)

Categories

(Core :: WebRTC: Networking, defect, P5)

x86
macOS
defect

Tracking

()

People

(Reporter: jesup, Unassigned)

Details

(Whiteboard: [investigation])

Attachments

(1 file)

Attached file about:webrtc and logs
Mac OS/X 10.7/Nightly 30 <-> Windows 7/Aurora 29 Both on separate USB tethers to 4G Samsung Galaxy S4's via EasyTether Pro. (ok, unusual arrangement - but I'd made TokBox conference (6+ user) calls to their servers, hangouts, and Vidyo calls using this setup without any major problems). See the logs - It appears to have failed to select a candidate, perhaps due to 4G to 4G blocking on Verizon? But then why wouldn't TURN or TURN TCP work...? I believe the same problem exists for Chrome, as an earlier attempt to call someone in MV using apprtc also failed. Perhaps they're blocking TURN???
Seeing timeouts on relayed/relayed candidate pairs, but haven't had enough time to look deeply.
I have log files from the MV office from a similar call with Maire yesterday. Maire was on 4G with tethering. Neither FF nor Google Chrome worked. Only Vidyo worked. From a quick look I only see that no transport gets established. I assume Randel's log is more interesting, but I can upload my log from the other side if needed.
backlog: --- → webRTC+
Rank: 45
Priority: -- → P4
Whiteboard: [investigation]
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: