On 10/7/2014 12:00 AM, [email protected] wrote:
Here is the log message form about:webrtc (https://mega.co.nz/#!4JMTyB4C!p_WyEbxc-dzItSYrpsw3sw76IgyFcO7TXCe0dKnK1G8) And I will try to capture it using Wireshark. Thanks. In addition, I did not see any log file under %TEMP%. So I only capture what I seen on my FF.
You can also run a Nightly Debug build with NSPR_LOG_MODULES=signaling:5,webrtc_trace:65535 WEBRTC_TRACE_FILE=some_file NSPR_LOG_FILE=some_other_file to get the internal logs. See https://wiki.mozilla.org/Media/WebRTC/Logging
The SDP you uploaded shows a number of issues, starting with audio and video both being on the same port (and the port being a number that's typically reserved - port 1). Even though your send is sendonly, we have to send RTCP reports to that port.
You specify H.264 and two payloads (126 and 97), but you do not provide a=fmtp: for either, and thus both will default to mode 0 packetization and a default profile-level-id. You should always provide a=ftmp for h.264 codecs with at minimum profile-level-id and packetization-mode (if not 0) specified.
Beyond that, I can't be sure what's wrong without more logs. My suggestion is to get the wireshark and look closely at the packets (using "Decode As ..." to force them to be seen as RTP) and the internal logs per above.
-- Randell Jesup, Mozilla _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
