> On Sep 28, 2017, at 21:36, Michael Froman <[email protected]> wrote: > > Hello, > > The RTP logger only logs the packet header, not the payload. The first step > would be to go to the about:webrtc page, and click the ‘Save Page’ button. > The best option would be to open a bug and attach that file to the new bug. > Please let us know the bug number.
Michael is right that the RTP logger on purpose over writes the biggest part of the payload with zeros. So zero’s in the result of logger do not tell you anything about any decoding errors. But the first few bytes after the RTP header do get logged to allow you to peak into the payload. So you should in Wireshark see after the RTP header the Opus header. The Opus payload will be mostly zeros. Best Nils > Thank you! > Michael. > >> On Sep 28, 2017, at 8:29 AM, [email protected] wrote: >> >> I'm trying to create an audio mixing server using Janus, but every packet >> the client receives is having all data after the packet header completely >> discarded by firefox with no message explaining why. I've tried enabling >> logging using the about:webrtc and about:networking pages, but nothing is >> ever written to the WebRTC.log file, so I've been using MOZ_LOG instead with >> the following modules >> "sync,timestamp,rtplogger:5,webrtc_trace:5,MediaManager:5,MediaStream:5,MediaStreamGraph:5,MediaEncoder:5,TrackEncoder:5". >> >> When looking through the log file I noticed the rtplogger in the socket >> thread outputs each packet's contents and everything after the header is >> always straight zeros. At the same time I captured those packets in >> wireshark and the packet data is showing up just fine. I assumed firefox was >> encountering an error when decoding the opus stream in the packet, but I set >> up the server to write each packet to an ogg file before sending them out to >> the clients and I was able to play back that file without any issues, so the >> encoded audio doesn't seem to be malformed. The only other possible cause I >> can think of is improper settings for the client's opus decoder, but all the >> settings for the server's encoder match up with the remote SDP description, >> so the client's decoder should be properly configured to decode the audio. >> >> I have been testing using Firefox Developer Edition v57.0b2 (64 bit). Any >> assistance would be greatly appreciated and if there's any more information >> I can provide please let me know. >> _______________________________________________ >> dev-media mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-media > > _______________________________________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-media
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
