Open
Bug 1377823
Opened 7 years ago
Updated 2 years ago
Webrtc over TCP (STUN) not working on Firefox 54
Categories
(Core :: WebRTC: Signaling, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: kkaur, Unassigned)
Details
(Whiteboard: [bug on the server side - tracking only])
Attachments
(1 file)
8.60 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce: I am using wowza webrtc preview to stream recordings on media server. Initially I was using webrtc over udp but it got blocked on our network. Then I changed it to tcp. Actual results: Firefox still does not stream the recordings to media server whereas if I try on chrome, it does. Expected results: According to https://blog.mozilla.org/webrtc/active-ice-tcp-punch-firewalls-directly/, firefox 54 should be able to support ice tcp by default which is not happening in my case.
Updated•7 years ago
|
Group: firefox-core-security
Component: Untriaged → WebRTC
Product: Firefox → Core
Comment 1•7 years ago
|
||
Can you check if this is real?
Component: WebRTC → WebRTC: Signaling
Flags: needinfo?(drno)
Whiteboard: [needinfo 2017-07-05 drno]
Comment 2•7 years ago
|
||
I'm already in contact with Kulwinder via email. This is a problem on the Wowza media server side which hands out ICE TCP candidates which are missing the tcptype attribute parameter.
Flags: needinfo?(drno)
Updated•7 years ago
|
Whiteboard: [needinfo 2017-07-05 drno] → [bug on the server side - tracking only]
Updated•7 years ago
|
Rank: 59
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•