As Adam suggests, the problem appears to be that Chrome is not offering a DTLS-SRTP fingerprint. You need to set the DtlsSrtpKeyAgreement flag.
See: http://www.webrtc.org/interop Best, -Ekr On Sun, Jul 28, 2013 at 7:06 PM, Rob Manson <[email protected]> wrote: > Hey Eric, > > here you go. Shout if you need any other info. > > o=- 2738925626739154476 3 IN IP4 127.0.0.1 > s=- > t=0 0 > a=group:BUNDLE audio video > a=msid-semantic: WMS 5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoK > m=audio 38703 RTP/SAVPF 111 103 104 0 8 107 106 105 13 126 > c=IN IP4 120.158.143.205 > a=rtcp:38703 IN IP4 120.158.143.205 > a=candidate:2845767988 1 udp 2113937151 10.194.79.1 55430 typ host > generation 0 > a=candidate:2845767988 2 udp 2113937151 10.194.79.1 55430 typ host > generation 0 > a=candidate:328666875 1 udp 2113937151 172.20.10.2 42137 typ host > generation 0 > a=candidate:328666875 2 udp 2113937151 172.20.10.2 42137 typ host > generation 0 > a=candidate:3133702446 1 udp 1845501695 120.158.143.205 38703 typ srflx > raddr 172.20.10.2 rport 42137 generation 0 > a=candidate:3133702446 2 udp 1845501695 120.158.143.205 38703 typ srflx > raddr 172.20.10.2 rport 42137 generation 0 > a=candidate:12678881 1 udp 1845501695 120.158.143.205 41500 typ srflx > raddr 10.194.79.1 rport 55430 generation 0 > a=candidate:12678881 2 udp 1845501695 120.158.143.205 41500 typ srflx > raddr 10.194.79.1 rport 55430 generation 0 > a=candidate:3877438916 1 tcp 1509957375 10.194.79.1 0 typ host generation 0 > a=candidate:3877438916 2 tcp 1509957375 10.194.79.1 0 typ host generation 0 > a=candidate:1561653771 1 tcp 1509957375 172.20.10.2 0 typ host generation > 0 > a=candidate:1561653771 2 tcp 1509957375 172.20.10.2 0 typ host generation > 0 > a=ice-ufrag:E2hbRMG2uTrfTOGG > a=ice-pwd:1ToUWZN+**zmosFQ5NKRMMZpAw > a=ice-options:google-ice > a=extmap:1 urn:ietf:params:rtp-hdrext:**ssrc-audio-level > a=sendrecv > a=mid:audio > a=rtcp-mux > a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:iqLbGf04Kf+** > AYqol9X809bUrW0gKoRm28s8XyewL > a=rtpmap:111 opus/48000/2 > a=fmtp:111 minptime=10 > a=rtpmap:103 ISAC/16000 > a=rtpmap:104 ISAC/32000 > a=rtpmap:0 PCMU/8000 > a=rtpmap:8 PCMA/8000 > a=rtpmap:107 CN/48000 > a=rtpmap:106 CN/32000 > a=rtpmap:105 CN/16000 > a=rtpmap:13 CN/8000 > a=rtpmap:126 telephone-event/8000 > a=maxptime:60 > a=ssrc:2225430392 cname:XVx5MwI/mG7gpwKS > a=ssrc:2225430392 msid:**5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoK > 5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoKa0 > a=ssrc:2225430392 mslabel:**5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoK > a=ssrc:2225430392 label:**5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoKa0 > m=video 38703 RTP/SAVPF 100 116 117 > c=IN IP4 120.158.143.205 > a=rtcp:38703 IN IP4 120.158.143.205 > a=candidate:2845767988 1 udp 2113937151 10.194.79.1 55430 typ host > generation 0 > a=candidate:2845767988 2 udp 2113937151 10.194.79.1 55430 typ host > generation 0 > a=candidate:328666875 1 udp 2113937151 172.20.10.2 42137 typ host > generation 0 > a=candidate:328666875 2 udp 2113937151 172.20.10.2 42137 typ host > generation 0 > a=candidate:3133702446 1 udp 1845501695 120.158.143.205 38703 typ srflx > raddr 172.20.10.2 rport 42137 generation 0 > a=candidate:3133702446 2 udp 1845501695 120.158.143.205 38703 typ srflx > raddr 172.20.10.2 rport 42137 generation 0 > a=candidate:12678881 1 udp 1845501695 120.158.143.205 41500 typ srflx > raddr 10.194.79.1 rport 55430 generation 0 > a=candidate:12678881 2 udp 1845501695 120.158.143.205 41500 typ srflx > raddr 10.194.79.1 rport 55430 generation 0 > a=candidate:3877438916 1 tcp 1509957375 10.194.79.1 0 typ host generation 0 > a=candidate:3877438916 2 tcp 1509957375 10.194.79.1 0 typ host generation 0 > a=candidate:1561653771 1 tcp 1509957375 172.20.10.2 0 typ host generation > 0 > a=candidate:1561653771 2 tcp 1509957375 172.20.10.2 0 typ host generation > 0 > a=ice-ufrag:E2hbRMG2uTrfTOGG > a=ice-pwd:1ToUWZN+**zmosFQ5NKRMMZpAw > a=ice-options:google-ice > a=extmap:2 urn:ietf:params:rtp-hdrext:**toffset > a=sendrecv > a=mid:video > a=rtcp-mux > a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:iqLbGf04Kf+** > AYqol9X809bUrW0gKoRm28s8XyewL > a=rtpmap:100 VP8/90000 > a=rtcp-fb:100 ccm fir > a=rtcp-fb:100 nack > a=rtcp-fb:100 goog-remb > a=rtpmap:116 red/90000 > a=rtpmap:117 ulpfec/90000 > a=ssrc:2357739379 cname:XVx5MwI/mG7gpwKS > a=ssrc:2357739379 msid:**5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoK > 5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoKv0 > a=ssrc:2357739379 mslabel:**5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoK > a=ssrc:2357739379 label:**5AbKYRUGTe9roRp2Vb84bKnRtXNPW2**FQxmoKv0 > > roBman > > > > On 29/07/13 11:53, Eric Rescorla wrote: > >> Rob, could you attach the Chrome SDP please? >> >> -Ekr >> >> >> >> On Sun, Jul 28, 2013 at 4:37 AM, Rob Manson <[email protected] >> <mailto:[email protected]>> wrote: >> >> Thanks Adam...that would be awesome 8) >> >> I'm running a bunch of SDP mangling tests this week to see if I can >> isolate this further and learn more about the interop challenges so >> if I work out anything useful about this specific ERR I'll post it >> here. >> >> roBman >> >> >> >> On 28/07/13 18:49, Adam Roach wrote: >> >> To be clear, all of the "SDP Parsing Error" messages here are >> merely >> warnings, not failures. On a first examination of the code path >> that an >> get you to "Could not negotiate media lines; cause = ERR", I'm >> pretty >> sure the situation you ran into below was a DTLS negotiation >> failure. >> One of the things I plan to do is comb through everywhere we >> send back >> the rather obtuse "cause = ERR" and change it to be more >> illuminating. >> >> /a >> >> On 7/27/13 01:54, Ethan Hugg wrote: >> >> Hi Rob, >> >> Firefox and Chrome are not directly compatible. apprtc >> adapts them a bit >> to get them to work together. You can copy what they do >> from files like >> this: >> >> https://apprtc.appspot.com/js/**__adapter.js<https://apprtc.appspot.com/js/__adapter.js> >> >> <https://apprtc.appspot.com/**js/adapter.js<https://apprtc.appspot.com/js/adapter.js> >> > >> >> https://apprtc.appspot.com/js/**__main.js<https://apprtc.appspot.com/js/__main.js> >> >> >> <https://apprtc.appspot.com/**js/main.js<https://apprtc.appspot.com/js/main.js> >> > >> >> The bug for Bundle is here - >> >> https://bugzilla.mozilla.org/_**_show_bug.cgi?id=784491<https://bugzilla.mozilla.org/__show_bug.cgi?id=784491> >> >> >> <https://bugzilla.mozilla.org/**show_bug.cgi?id=784491<https://bugzilla.mozilla.org/show_bug.cgi?id=784491> >> > >> >> Though, how some of this should work exactly is still being >> discussed in >> the IETF standards groups MMUSIC and RTCWeb which meet next >> week in Berlin. >> >> -EH >> >> >> >> On Fri, Jul 26, 2013 at 3:55 PM, Rob >> Manson<[email protected] <mailto:[email protected]>> >> wrote: >> >> >> Hi, >> >> I couldn't see that anyone had raised this anywhere and >> it seems unrelated >> to this topic on discuss-webrtc >> https://groups.google.com/__** >> forum/#!topic/discuss-webrtc/_**_dLsbz6Xwxc0<https://groups.google.com/__forum/#!topic/discuss-webrtc/__dLsbz6Xwxc0> >> >> <https://groups.google.com/** >> forum/#!topic/discuss-webrtc/**dLsbz6Xwxc0<https://groups.google.com/forum/#!topic/discuss-webrtc/dLsbz6Xwxc0> >> > >> - so I >> thought I'd share the error message I'm receiving. >> >> If you'd like me to raise this as a bug please let me >> know...but thought >> it might be better first as just an informational post. >> >> So setting up a video call between the latest Chrome >> (28.0.1500.71 >> (Official Build 209842) ) and Firefox 22 & Nightly >> (25.0a1 (2013-07-25)) on >> Linux I get this SDP parsing error message in Firefox. >> >> "Could not negotiate media lines; cause = ERR | SDP >> Parsing Error: >> Warning: Group attribute type unsupported (BUNDLE). | >> SDP Parsing Error: >> Warning: Unrecognized attribute (msid-semantic) | SDP >> Parsing Error: >> Warning: Unrecognized attribute (ice-options) | SDP >> Parsing Error: Warning: >> Unrecognized attribute (extmap) | SDP Parsing Error: >> Warning: Numeric token >> for mid attribute not found | SDP Parsing Error: >> Warning: Invalid named >> events specified for fmtp attribute. | SDP Parsing >> Error: Warning: >> Unrecognized attribute (ssrc) | SDP Parsing Error: >> Warning: Unrecognized >> attribute (ssrc) | SDP Parsing Error: Warning: >> Unrecognized attribute >> (ssrc) | SDP Parsing Error: Warning: Unrecognized >> attribute (ssrc) | SDP >> Parsing Error: Warning: Unrecognized attribute >> (ice-options) | SDP Parsing >> Error: Warning: Unrecognized attribute (extmap) | SDP >> Parsing Error: >> Warning: Numeric token for mid attribute not found | SDP >> Parsing Error: >> Warning: Unrecognized attribute (ssrc) | SDP Parsing Error >> : Warning: Unrecognized attribute (ssrc) | SDP >> Parsing Error: Warning: >> Unrecognized attribute (ssrc) | SDP Parsing Error: >> Warning: Unrecognized >> attribute (ssrc) " >> >> However, in the exact same app I can setup a video call >> between two >> Firefox tabs or separate browsers so it's definitely >> working OK with >> Firefox SDP. >> >> If you'd like a full copy of the Chrome SDP and related >> signaling please >> let me know...but I'm sure you've got a good collection >> of this already 8) >> >> roBman >> ______________________________**___________________ >> >> dev-media mailing list >> [email protected] >> >> <mailto:dev-media@lists.**mozilla.org<[email protected]> >> > >> >> https://lists.mozilla.org/__**listinfo/dev-media<https://lists.mozilla.org/__listinfo/dev-media> >> >> <https://lists.mozilla.org/**listinfo/dev-media<https://lists.mozilla.org/listinfo/dev-media> >> > >> >> ______________________________**___________________ >> >> dev-media mailing list >> [email protected] <mailto:dev-media@lists.** >> mozilla.org <[email protected]>> >> >> https://lists.mozilla.org/__**listinfo/dev-media<https://lists.mozilla.org/__listinfo/dev-media> >> >> >> <https://lists.mozilla.org/**listinfo/dev-media<https://lists.mozilla.org/listinfo/dev-media> >> > >> >> >> >> -- >> Adam Roach >> Principal Platform Engineer >> [email protected] <mailto:[email protected]> >> +1 650 903 0800 x863 <tel:%2B1%20650%20903%200800%**20x863> >> >> ______________________________**___________________ >> >> dev-media mailing list >> [email protected] >> <mailto:dev-media@lists.**mozilla.org<[email protected]> >> > >> >> https://lists.mozilla.org/__**listinfo/dev-media<https://lists.mozilla.org/__listinfo/dev-media> >> >> <https://lists.mozilla.org/**listinfo/dev-media<https://lists.mozilla.org/listinfo/dev-media> >> > >> >> >> _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media

