Closed
Bug 1042345
Opened 11 years ago
Closed 11 years ago
Problems with DNS resolution for ice configuration on B2G
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1042873
blocking-b2g | 2.0+ |
People
(Reporter: drno, Unassigned)
References
Details
(Whiteboard: ft:loop)
B2G does not support STUN servers with DNS names, but only with IP addresses.
Comment 1•11 years ago
|
||
[Blocking Requested - why for this release]:
Nominating to 2.0, as without this fix, Loop FxOS calls are not going to work when located in different networks.
blocking-b2g: --- → 2.0?
Whiteboard: ft:loop
Reporter | ||
Comment 2•11 years ago
|
||
Sorry misunderstood how nICEr is doing DNS resolution.
No longer depends on: 933102
Comment 3•11 years ago
|
||
Shell - Can you find out if this can be worked around on the server-side with Tokbox?
Flags: needinfo?(sescalante)
Comment 4•11 years ago
|
||
It can. I've asked TokBox to make that change ASAP. They are preparing a change -- first to their QA system to verify it fixes this issue.
Flags: needinfo?(sescalante)
Comment 5•11 years ago
|
||
As Byron indicates, this is not a lack of DNS resolution but most likely instead
a byte ordering issue in the resolution system:
ICE(PC:272899921727 (id=4 url=http://mozilla.github.io/webrtc-landing/stun_test.html)): resolved candidate srflx(IP4:31.133.149.56:45999/UDP|stun.l.google.com:19302). addr=IP4:173.194.78.127:26187/UDP
Comment 6•11 years ago
|
||
(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #4)
> It can. I've asked TokBox to make that change ASAP. They are preparing a
> change -- first to their QA system to verify it fixes this issue.
Okay. Thanks for the clarification.
Maria - Given that this can fixed via a server-side workaround for Loop, are you okay with triage deciding to unblock this?
Flags: needinfo?(oteo)
Reporter | ||
Updated•11 years ago
|
Summary: B2G missing DNS resolution for ice configuration → Problems with DNS resolution for ice configuration on B2G
Comment 7•11 years ago
|
||
Byron has found the problem. I suggest we just wait instead of doing a workaround.
Updated•11 years ago
|
Flags: needinfo?(oteo)
Comment 8•11 years ago
|
||
(In reply to Eric Rescorla (:ekr) from comment #7)
> Byron has found the problem. I suggest we just wait instead of doing a
> workaround.
Okay - blocking on this basis then. We'll fix this directly in the platform. If there's concern with this, feel free to renominate.
blocking-b2g: 2.0? → 2.0+
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•