Closed
Bug 1215073
Opened 10 years ago
Closed 10 years ago
WebRTC - Unable to hear any audio during a Firefox (audio) to Chrome (audio/video) connection
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: leticia.choo, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
Steps to reproduce:
Tested in apprtc.appspot.com.
1. Start Chrome 45 and join a room in apprtc (User A)
2. Start Firefox 42.0b6 and join the room in apprtc (User B)
3. Wait for connection.
4. Attempt to hear audio on both Firefox and Chrome.
Additional information:
User A - Chrome 46.0.2454.101 (64-bit) Mac OSX Yosemite 10.10.3
User B - Firefox 42.0b6 Mac OSX Yosemite 10.10.3.
User B is tested with Firefox 40.0.3 as well and on Windows 10 platform.
Actual results:
Chrome - No audio received from Firefox
Firefox - Could hear audio from Chrome
Expected results:
Chrome - Should be able to hear audio from Firefox
Firefox - Still be able to hear audio from Chrome
Updated•10 years ago
|
Component: Untriaged → WebRTC: Audio/Video
Product: Firefox → Core
Comment 1•10 years ago
|
||
Tried with Chrome 47 talking to Firefox 44 - works perfectly.
Please capture the info for the peerconnection in about:webrtc and attach it.
I assume these are on two different machines, not the same one?
Do you hear audio in Firefox -> Firefox calls?
Do you hear audio with firefox on https://mozilla.github.io/webrtc-landing/gum_test.html if you select audio or audio/video?
If you can, try running with NSPR_LOG_MODULES=signaling:4,timestamp and NSPR_LOG_FILE=some_log_file and upload that as well. Thanks
Flags: needinfo?(leticia.choo)
| Reporter | ||
Comment 2•10 years ago
|
||
Hi Randell,
Yes they are two different machines. I'll test again with Chrome 47 and get back to you
Flags: needinfo?(leticia.choo)
Comment 3•10 years ago
|
||
Could you retest this with the release versions of Chrome and Firefox? thanks
Flags: needinfo?(leticia.choo)
| Reporter | ||
Comment 4•10 years ago
|
||
Hi,
Apologies for the late reply.
It seems like Chrome has responded the issue on their end:
https://code.google.com/p/chromium/issues/detail?id=534859
Thank you
Flags: needinfo?(leticia.choo)
| Reporter | ||
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•