Closed
Bug 929946
Opened 11 years ago
Closed 11 years ago
audio only webrtc
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 917980
People
(Reporter: frederic.luart, Unassigned)
Details
(Whiteboard: [webrtc])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36 Steps to reproduce: When Establishing an audio only call on WebRTC, audio stream are not routed, and voice can not be hearded. It is possible to reproduce the issue with demo on : https://apprtc.appspot.com/ by establishing a call and selecting "No video" on the device acceptation (both side). Actual results: No audio routing. On apprtc demo, call is not established : stay in "connecting" state. Expected results: Audio only call
Comment 1•11 years ago
|
||
I believe this is a bug in apprtc, though I can't find a bug on it right now (perhaps it was just discussed in #media on IRC)
Whiteboard: [webrtc]
I have done some more testings and it seems to be linked with the constraint on createOffer / createAnswer : {'OfferToReceiveAudio': true, 'OfferToReceiveVideo': true} If OfferToReceiveVideo is set to false, the audio call is OK. (OfferToReceiveVideo allows an application to indicate its preferences for receiving video when creating an offer)
Comment 3•11 years ago
|
||
This sounds similar to this bug - https://bugzilla.mozilla.org/show_bug.cgi?id=881236 We are not changing our ExpectedTracks after the negotiation so we wait forever for a track that's not coming.
Comment 4•11 years ago
|
||
I suspect it has ties in to the issue in Bug 917980 as well.
Comment 5•11 years ago
|
||
Yes seems like a duplicate of Bug 917980.
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•