Hi Mark,

Regarding more debugging in Firefox - if you could run a debug version of
Nightly with env vars like these and capture the results it will give us
much more info to debug with:

export NSPR_LOG_FILE=/home/ehugg/tmp/nspr.log
export NSPR_LOG_MODULES=signaling:5
export R_LOG_LEVEL=9
export R_LOG_DESTINATION=stderr


the R_LOG ones are for the ICE code and the NSPR_ ones will give the
signaling info.

-EH



On Thu, Jul 25, 2013 at 9:11 AM, <[email protected]> wrote:

> 1.  FF 23.0, Chrome Canary M30 - Sorry Should have provided this.
> 2. I see some server reflexive candidates in Chrome.
>
> a=candidate:4260537832 1 udp 2113937151 172.17.30.226 63225 typ host
> generation 0
> a=candidate:4260537832 2 udp 2113937151 172.17.30.226 63225 typ host
> generation 0
> a=candidate:2092606300 1 udp 1845501695 209.43.1.201 59652 typ srflx raddr
> 172.17.30.226 rport 63225 generation 0
> a=candidate:2092606300 2 udp 1845501695 209.43.1.201 59652 typ srflx raddr
> 172.17.30.226 rport 63225 generation 0
> a=candidate:3010550040 1 tcp 1509957375 172.17.30.226 0 typ host
> generation 0
> a=candidate:3010550040 2 tcp 1509957375 172.17.30.226 0 typ host
> generation 0
>
> One thing I just noticed is that the DtlsSrtpKeyAgreement option seems to
> cause the same behavior with Chrome <--> Chrome.  Without it, FF doesn't
> accept a SDP from Chrome.  With it, Chrome no longer seems to work.  FF
> doesn't seem to work with or without it.
>
>
>
> On Thursday, July 25, 2013 11:26:22 AM UTC-4, Eric Rescorla wrote:
> > First, some introductory questions:
> >
> >
> >
> > 1. What version of Firefox are you on?
> >
> > 2. When you use Chrome, does it get TURN candidates (look for "relay" in
> >
> > the SDP).
> >
> >
> >
> > -Ekr
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Jul 25, 2013 at 7:29 AM, <[email protected]> wrote:
> >
> >
> >
> > > I'm trying to get WebRTC working in Firefox.   I have things working in
> >
> > > Chrome.  The project I am working on is implementing a SIP gateway,
> and it
> >
> > > is a little unique in that it treats each of the peers as an Offerer.
> >
> > >
> >
> > > The SDP's below are being exchanged between the peers.   I'm using the
> >
> > > Mozilla STUN server like the AppRTC demo.   When I try to do Chome
> <--> FF,
> >
> > > I get the same results.  The webrtc-internals in Chrome shows that the
> ICE
> >
> > > connection state never transitions past 'checking'.
> >
> > >
> >
> > > My application works fine with Chrome <--> Chrome.  When using FF, I
> see
> >
> > > no errors being traced in the console.
> >
> > >
> >
> > > Anyone have any ideas on what may be causing my issue?  Also, are there
> >
> > > any additional debugging tools in FF that I can use to try to diagnose
> the
> >
> > > issue?
> >
> > >
> >
> > > thanks.
> >
> > >
> >
> > > Offer:
> >
> > >
> >
> > > v=0
> >
> > > o=Mozilla-SIPUA-23.0 9508 0 IN IP4 0.0.0.0
> >
> > > s=SIP Call
> >
> > > t=0 0
> >
> > > a=ice-ufrag:2d72d8c1
> >
> > > a=ice-pwd:4bca6b6d87b277cd588b3f4ac5f71f3f
> >
> > > a=fingerprint:sha-256
> >
> > >
> 82:30:55:18:AA:C0:9E:4B:B4:45:E5:F6:F7:22:53:72:7B:73:B4:55:B3:40:C5:31:5E:19:B6:CD:CE:57:AB:9A
> >
> > > m=audio 49924 RTP/SAVPF 109 0 8 101
> >
> > > c=IN IP4 209.43.1.201
> >
> > > a=rtpmap:109 opus/48000/2
> >
> > > a=ptime:20
> >
> > > a=rtpmap:0 PCMU/8000
> >
> > > a=rtpmap:8 PCMA/8000
> >
> > > a=rtpmap:101 telephone-event/8000
> >
> > > a=fmtp:101 0-15
> >
> > > a=sendrecv
> >
> > > a=candidate:0 1 UDP 2111832319 172.17.30.226 64603 typ host
> >
> > > a=candidate:1 1 UDP 1692467199 209.43.1.201 49924 typ srflx raddr
> >
> > > 172.17.30.226 rport 64603
> >
> > > a=candidate:0 2 UDP 2111832318 172.17.30.226 64604 typ host
> >
> > > a=candidate:1 2 UDP 1692467198 209.43.1.201 7193 typ srflx raddr
> >
> > > 172.17.30.226 rport 64604
> >
> > > m=video 63409 RTP/SAVPF 120
> >
> > > c=IN IP4 209.43.1.201
> >
> > > a=rtpmap:120 VP8/90000
> >
> > > a=sendrecv
> >
> > > a=candidate:0 1 UDP 2111832319 172.17.30.226 64605 typ host
> >
> > > a=candidate:1 1 UDP 1692467199 209.43.1.201 63409 typ srflx raddr
> >
> > > 172.17.30.226 rport 64605
> >
> > > a=candidate:0 2 UDP 2111832318 172.17.30.226 64606 typ host
> >
> > > a=candidate:1 2 UDP 1692467198 209.43.1.201 17519 typ srflx raddr
> >
> > > 172.17.30.226 rport 64606
> >
> > > a=rtcp-fb:* nack
> >
> > > a=rtcp-fb:* ccm fir
> >
> > >
> >
> > > Answer:
> >
> > >
> >
> > > v=0
> >
> > > o=Mozilla-SIPUA-23.0 7906 0 IN IP4 0.0.0.0
> >
> > > s=SIP Call
> >
> > > t=0 0
> >
> > > a=ice-ufrag:2b41f466
> >
> > > a=ice-pwd:ef8a40ea309abe416476df5fa07d3bd4
> >
> > > a=fingerprint:sha-256
> >
> > >
> DC:9D:86:66:05:49:53:BE:5E:57:BC:41:F0:8D:BB:9F:D8:A1:26:A0:90:ED:5D:DE:1C:F8:86:0F:1C:1C:CE:81
> >
> > > m=audio 41641 RTP/SAVPF 109 0 8 101
> >
> > > c=IN IP4 209.43.1.201
> >
> > > a=rtpmap:109 opus/48000/2
> >
> > > a=ptime:20
> >
> > > a=rtpmap:0 PCMU/8000
> >
> > > a=rtpmap:8 PCMA/8000
> >
> > > a=rtpmap:101 telephone-event/8000
> >
> > > a=fmtp:101 0-15
> >
> > > a=sendrecv
> >
> > > a=candidate:0 1 UDP 2111832319 172.17.30.226 64609 typ host
> >
> > > a=candidate:1 1 UDP 1692467199 209.43.1.201 41641 typ srflx raddr
> >
> > > 172.17.30.226 rport 64609
> >
> > > a=candidate:0 2 UDP 2111832318 172.17.30.226 64610 typ host
> >
> > > a=candidate:1 2 UDP 1692467198 209.43.1.201 3613 typ srflx raddr
> >
> > > 172.17.30.226 rport 64610
> >
> > > m=video 5647 RTP/SAVPF 120
> >
> > > c=IN IP4 209.43.1.201
> >
> > > a=rtpmap:120 VP8/90000
> >
> > > a=sendrecv
> >
> > > a=candidate:0 1 UDP 2111832319 172.17.30.226 64611 typ host
> >
> > > a=candidate:1 1 UDP 1692467199 209.43.1.201 5647 typ srflx raddr
> >
> > > 172.17.30.226 rport 64611
> >
> > > a=candidate:0 2 UDP 2111832318 172.17.30.226 64612 typ host
> >
> > > a=candidate:1 2 UDP 1692467198 209.43.1.201 48757 typ srflx raddr
> >
> > > 172.17.30.226 rport 64612
> >
> > > a=rtcp-fb:* nack
> >
> > > a=rtcp-fb:* ccm fir
> >
> > >
> >
> > > _______________________________________________
> >
> > > 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
>
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media

Reply via email to