I filed a bug for this since it also happens on projectsquared.com:
https://bugzilla.mozilla.org/show_bug.cgi?id=1106874

-EH

On Tue, Dec 2, 2014 at 7:57 AM, Ethan Hugg <[email protected]> wrote:

>
> Could you go to about:webrtc after a failed test and send me the text from
> that page?  That will give us the information about the connection.  Thanks.
>
> -EH
>
>
> On Tue, Dec 2, 2014 at 4:45 AM, <[email protected]> wrote:
>
>> Hi,
>>
>> I posted an issue about using H264 stream on FF 33 before (
>> https://groups.google.com/forum/#!searchin/mozilla.dev.media/h264/mozilla.dev.media/Hbh3P1qGW9Y/Y4Ji2T6w6awJ),
>> and that's is solved by everyone's help! Thanks.
>> But.... when FF is upgraded to 34, this is happened again.. (OMG).
>>
>> So I come here again, and hope anyone can give me help~ thanks.
>> Here is my test environment:
>>
>>     My Device <---H264---> FF 34 (No video)
>>     My Device <---H264---> FF 33 (Has video)
>>
>> And here are offer and answer:
>>
>> Offer(FF to My Device)
>> v=0
>> o=Mozilla-SIPUA-34.0 14896 0 IN IP4 0.0.0.0
>> s=SIP Call
>> t=0 0
>> a=ice-ufrag:867d948c
>> a=ice-pwd:12e3c549e7c1aa5b62d19c5ba31d8a90
>> a=fingerprint:sha-256
>> B9:4B:EE:66:4F:B6:A6:FD:3E:78:43:36:9A:FE:E6:FD:B1:A4:50:82:B8:8C:A0:02:7E:E3:66:FC:66:57:99:B5
>> m=audio 9 RTP/SAVPF 109 9 0 8 101
>> c=IN IP4 0.0.0.0
>> a=rtpmap:109 opus/48000/2
>> a=ptime:20
>> a=rtpmap:9 G722/8000
>> a=rtpmap:0 PCMU/8000
>> a=rtpmap:8 PCMA/8000
>> a=rtpmap:101 telephone-event/8000
>> a=fmtp:101 0-15
>> a=sendrecv
>> a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
>> a=setup:actpass
>> a=rtcp-mux
>> m=video 9 RTP/SAVPF 120 126 97
>> c=IN IP4 0.0.0.0
>> a=rtpmap:120 VP8/90000
>> a=rtpmap:126 H264/90000
>> a=fmtp:126 profile-level-id=42e01f;packetization-mode=1
>> a=rtpmap:97 H264/90000
>> a=fmtp:97 profile-level-id=42e01f
>> a=recvonly
>> a=rtcp-fb:120 nack
>> a=rtcp-fb:120 nack pli
>> a=rtcp-fb:120 ccm fir
>> a=rtcp-fb:126 nack
>> a=rtcp-fb:126 nack pli
>> a=rtcp-fb:126 ccm fir
>> a=rtcp-fb:97 nack
>> a=rtcp-fb:97 nack pli
>> a=rtcp-fb:97 ccm fir
>> a=setup:actpass
>> a=rtcp-mux
>>
>> Answer(My Device to FF)
>> v=0
>> o=- 3637702335846616252 2 IN IP4 127.0.0.1
>> s=-
>> t=0 0
>> a=msid-semantic: WMS stream_label
>> m=audio 1 RTP/SAVPF 0 8 101
>> c=IN IP4 0.0.0.0
>> a=rtcp:1 IN IP4 0.0.0.0
>> a=ice-ufrag:dcIFiIhOR+fZHFY9
>> a=ice-pwd:mLqKK3C5It1/Z0L+SWWYrj+y
>> a=fingerprint:sha-1
>> 6C:FF:C0:2F:CA:C8:FD:44:88:DE:DB:2E:09:9D:1A:50:D8:B9:FD:D8
>> a=setup:active
>> a=mid:audio
>> a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
>> a=sendrecv
>> a=rtcp-mux
>> a=rtpmap:0 PCMU/8000
>> a=rtpmap:8 PCMA/8000
>> a=rtpmap:101 telephone-event/8000
>> a=ssrc:2594247746 cname:g07iau/woWmpLmF5
>> a=ssrc:2594247746 msid:stream_label audio_label
>> a=ssrc:2594247746 mslabel:stream_label
>> a=ssrc:2594247746 label:audio_label
>> m=video 1 RTP/SAVPF 126
>> c=IN IP4 0.0.0.0
>> a=rtcp:1 IN IP4 0.0.0.0
>> a=ice-ufrag:OVnd8UkxhD6jqb4W
>> a=ice-pwd:8bvK+cEwVy/UPE9f+Qv/LIJc
>> a=fingerprint:sha-1
>> 6C:FF:C0:2F:CA:C8:FD:44:88:DE:DB:2E:09:9D:1A:50:D8:B9:FD:D8
>> a=setup:active
>> a=mid:video
>> a=sendonly
>> a=rtcp-mux
>> a=rtpmap:126 H264/90000
>> a=rtcp-fb:126 ccm fir
>> a=rtcp-fb:126 nack
>> a=rtcp-fb:126 nack pli
>> a=ssrc:3920187810 cname:g07iau/woWmpLmF5
>> a=ssrc:3920187810 msid:stream_label video_label
>> a=ssrc:3920187810 mslabel:stream_label
>> a=ssrc:3920187810 label:video_label
>>
>> Has there any strange things that might cause this issue?
>> _______________________________________________
>> 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

Reply via email to