851013 - Firefox nightly 22.0a1 send old STUN binding message to 23.21.150.121 when developing the webrtc

Status: RESOLVED WORKSFORME

(Core :: WebRTC, defect, P2)

Description

[george]

Attachment: STUN mesage.pcap

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:22.0) Gecko/20130307 Firefox/22.0
Build ID: 20130307030926

Steps to reproduce:

I use two laptops as two endpoint and one server for websoket and stun. I want to make video call between two endpoints.


Actual results:

Remote video didn't show on the page on the both endpoints, and they just get local video. From capturing packets, I found the firefox sent old STUN message to stun server which is different chrome (first sent STUN2 message). Here is some snippet of code
pc_config = {"iceServers": [{"url": "stun:135.252.135.1:3478"}]};
peerConn = new mozRTCPeerConnection(pc_config);
peerConn.onconnection = onSessionConnecting;
peerConn.onicecandidate = onIceCandidate;
peerConn.onaddstream = onRemoteStreamAdded;
peerConn.onremovestream = onRemoveStream;


Expected results:

It should show the remote real-time video.

Comment 1

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Would you mind looking in about:config and check your values for:

 - media.peerconnection.default_iceservers
 - media.peerconnection.use_document_iceservers

If you're not seeing these entries, you have an older Nightly, which might explain it.

Also, please let me know if you're seeing any errors or warnings in the WebConsole when your code-snippet runs.

23.21.150.121 is the default STUN server in Firefox, and is only supposed to be used if no stun server settings were detected, which is odd as your code snippet looks correct.

PS: tcpdump says "unknown file format" on your pcap file, so I wasn't able to read it.

Comment 2

[george]

(In reply to Jan-Ivar Bruaroey [:jib] from comment #1)
> Would you mind looking in about:config and check your values for:
> 
>  - media.peerconnection.default_iceservers
>  - media.peerconnection.use_document_iceservers
> 
> If you're not seeing these entries, you have an older Nightly, which might
> explain it.
> 
> Also, please let me know if you're seeing any errors or warnings in the
> WebConsole when your code-snippet runs.
> 
> 23.21.150.121 is the default STUN server in Firefox, and is only supposed to
> be used if no stun server settings were detected, which is odd as your code
> snippet looks correct.
> 
> PS: tcpdump says "unknown file format" on your pcap file, so I wasn't able
> to read it.

I have both entries.
media.peerconnection.default_iceservers  [{"url": "stun:135.252.135.1:3478"}]
media.peerconnection.use_document_iceservers  true
135.252.135.1 is my stun server. I also use the 23.21.150.121, it didn't work too.

Below is the SDP info between both endpoints.

send local sdp info to peer:{"type":"offer","sdp":"v=0\r\no=Mozilla-SIPUA 17188 0 IN IP4 0.0.0.0\r\ns=SIP Call\r\nt=0 0\r\na=ice-ufrag:651184e6\r\na=ice-pwd:c698faa3b9f7597a45f005e2d4226f6b\r\na=fingerprint:sha-256 7A:FE:00:BF:96:71:6D:9D:9E:7B:E8:DE:84:7A:24:C7:6D:2C:0F:C9:9B:66:EE:8F:00:53:FA:D8:DE:6A:EA:E6\r\nm=audio 2428 RTP/SAVPF 109 0 8 101\r\nc=IN IP4 135.252.33.50\r\na=rtpmap:109 opus/48000/2\r\na=ptime:20\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.50 2428 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.50 2429 typ host\r\nm=video 2430 RTP/SAVPF 120\r\nc=IN IP4 135.252.33.50\r\na=rtpmap:120 VP8/90000\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.50 2430 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.50 2431 typ host\r\nm=application 2432 SCTP/DTLS 5000 \r\nc=IN IP4 135.252.33.50\r\na=fmtp:5000 protocol=webrtc-datachannel;streams=16\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.50 2432 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.50 2433 typ host\r\n"}

incomingSignalingMessage Peer SDP:
{"type":"answer","sdp":"v=0\r\no=Mozilla-SIPUA 13777 0 IN IP4 0.0.0.0\r\ns=SIP Call\r\nt=0 0\r\na=ice-ufrag:bc61d7e4\r\na=ice-pwd:6eef85eb16a6832e5a82d73afdc4a5fc\r\na=fingerprint:sha-256 80:8E:F7:C7:A2:C1:35:18:8B:50:43:D6:64:49:99:E9:C7:FA:26:B3:1E:F6:A8:CD:3C:84:BB:73:43:92:9E:7D\r\nm=audio 1194 RTP/SAVPF 109 101\r\nc=IN IP4 135.252.33.103\r\na=rtpmap:109 opus/48000/2\r\na=ptime:20\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.103 1194 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.103 1195 typ host\r\nm=video 1196 RTP/SAVPF 120\r\nc=IN IP4 135.252.33.103\r\na=rtpmap:120 VP8/90000\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.103 1196 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.103 1197 typ host\r\nm=application 1198 SCTP/DTLS 5001 \r\nc=IN IP4 135.252.33.103\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.103 1198 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.103 1199 typ host\r\n"}

The only wrong place is the ready state of peerconnection is undefined which is addresses in the bug 825560.

Comment 3

[george]

I use wireshark to capture the packets, and I think tcpdump should have opened it, you can try it using wiewshark. Ans in case the attactment is really bad, I will attach one again.

Comment 4

[george]

Attachment: STUN error message

Comment 5

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Comment on attachment 724824 [details]
STUN mesage.pcap

Tcpdump recognized the new attachment, so I obsoleted the previous one.

I'm a little confused about what specific bug you are reporting. From the subject I thought you were seeing usage of the built-in STUN server in spite of providing your own STUN details, so I thought I could help. But it sounds like that's not it.

I'm not sure how to diagnose your problem of it not working end to end. Have you tried http://mozilla.github.com/webrtc-landing and does that work? If you could find a known-good case that works for you and compare it against the problems you're experiencing, and narrow down what the difference is that is causing it to not work, that would help a lot in establishing the bug.

Comment 6

[george]

I tried "Multi-person video chat via mozRTCPeerConnection for Nightly" on the link http://mozilla.github.com/webrtc-landing using two laptop, but it is strange there is no online user for my test, is it the reason I was in the intranet?
I have checked the code with the example on the site you provided, the API and its usage is the same with mine. Now I want to know why the Firefox send STUN, rather than STUN2 which is sent by Chrome? In my code, I saw peerConn.addIceCandidate is not called, I think because it can't collect the candidate.
Below is the output from the console:
******************************************************************
incomingSignalingMessage Peer SDP:
{"type":"offer","sdp":"v=0\r\no=Mozilla-SIPUA-23.0a1 3204 0 IN IP4 0.0.0.0\r\ns=SIP Call\r\nt=0 0\r\na=ice-ufrag:b075b42e\r\na=ice-pwd:80cc501365f633238e5ad45a7ab790e1\r\na=fingerprint:sha-256 2D:F2:B1:0B:2C:F5:6C:EF:DE:81:0F:F1:DC:5D:A9:EE:9C:01:57:71:D2:6B:B9:47:94:4E:0A:26:6F:37:CD:92\r\nm=audio 2844 RTP/SAVPF 109 0 8 101\r\nc=IN IP4 135.252.33.103\r\na=rtpmap:109 opus/48000/2\r\na=ptime:20\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.103 2844 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.103 2845 typ host\r\nm=video 2846 RTP/SAVPF 120\r\nc=IN IP4 135.252.33.103\r\na=rtpmap:120 VP8/90000\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.103 2846 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.103 2847 typ host\r\n"}

receive remote stream:
{"stream":{},"type":"video"}

receive offer, send answer

send local sdp info to peer:{"type":"answer","sdp":"v=0\r\no=Mozilla-SIPUA-23.0a1 6926 0 IN IP4 0.0.0.0\r\ns=SIP Call\r\nt=0 0\r\na=ice-ufrag:a14856f0\r\na=ice-pwd:9df29424456cd3c70777dd0d98940afe\r\na=fingerprint:sha-256 9F:2B:11:0B:8B:73:8D:16:B7:6D:CD:E1:6A:D3:2C:A9:4E:33:96:9F:84:ED:7D:C7:ED:43:92:BE:73:4E:DA:25\r\nm=audio 4041 RTP/SAVPF 109 101\r\nc=IN IP4 135.252.33.50\r\na=rtpmap:109 opus/48000/2\r\na=ptime:20\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.50 4041 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.50 4042 typ host\r\nm=video 4043 RTP/SAVPF 120\r\nc=IN IP4 135.252.33.50\r\na=rtpmap:120 VP8/90000\r\na=sendrecv\r\na=candidate:0 1 UDP 2111832319 135.252.33.50 4043 typ host\r\na=candidate:0 2 UDP 2111832318 135.252.33.50 4044 typ host\r\n"}
*******************************************************************
Looking forward to your suggestion.

Thanks

Comment 7

[george]

And must it run on the Win7? Now it run on the XP.

Comment 8

[george]

Attachment: From capturing packets, it seems there are a lots of RTP packets from remote end. I attached them for you.

Comment 9

[Nils Ohlmeier [:drno]]

Based on the age of the bug I'm guessing this can be safely closed.