Peer Server working only in computers in the same network

[Ahmed_N_]

Hi,

I installed Peer server v3.2.1 on Ubuntu 14.04 LTS instance published in AWS.

Then I run the P2P sample in Javascript SDK from two different computers.

If the two computers are in the same wireless network -> It works just fine and the two browsers are connected successfully. but if they are not in the same network -> they login successfully, but when I invite the other side I got Ice connection state changed. State: failed

This is the log in case of failing (the machine logged as apple and the other one logged as wind):

DEBUG: Query string: clientType=Web&clientVersion=3.2.1&token=apple
INFO: Connected to websocket server.
DEBUG: Authentication passed. User ID: apple
INFO: Received woogeen message.
DEBUG: S->C: {"type":"offer","sdp":"v=0\r\no=- 3093287351609602721 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE audio video data\r\na=msid-semantic: WMS\r\nm=audio 9 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126\r\nc=IN IP4 0.0.0.0\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:xzdb\r\na=ice-pwd:ND1hvRqTLMSYoMHZYmy99ZrM\r\na=fingerprint:sha-256 76:30:F4:E4:55:F9:07:A3:6B:22:16:2E:F8:16:EB:57:72:E2:F4:B9:D9:B1:63:0C:E7:BF:88:5B:E0:E9:E0:C4\r\na=setup:actpass\r\na=mid:audio\r\na=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level\r\na=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\r\na=recvonly\r\na=rtcp-mux\r\na=rtpmap:111 opus/48000/2\r\na=rtcp-fb:111 transport-cc\r\na=fmtp:111 minptime=10;useinbandfec=1\r\na=rtpmap:103 isac/16000\r\na=rtpmap:104 isac/32000\r\na=rtpmap:9 G722/8000\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:106 cn/32000\r\na=rtpmap:105 cn/16000\r\na=rtpmap:13 cn/8000\r\na=rtpmap:126 telephone-event/8000\r\nm=video 9 UDP/TLS/RTP/SAVPF 100 101 107 116 117 96 97 99 98\r\nb=AS:500\r\nc=IN IP4 0.0.0.0\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:xzdb\r\na=ice-pwd:ND1hvRqTLMSYoMHZYmy99ZrM\r\na=fingerprint:sha-256 76:30:F4:E4:55:F9:07:A3:6B:22:16:2E:F8:16:EB:57:72:E2:F4:B9:D9:B1:63:0C:E7:BF:88:5B:E0:E9:E0:C4\r\na=setup:actpass\r\na=mid:video\r\na=extmap:2 urn:ietf:params:rtp-hdrext:toffset\r\na=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\r\na=extmap:4 urn:3gpp:video-orientation\r\na=extmap:6 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay\r\na=recvonly\r\na=rtcp-mux\r\na=rtcp-rsize\r\na=rtpmap:100 VP8/90000\r\na=rtcp-fb:100 ccm fir\r\na=rtcp-fb:100 nack\r\na=rtcp-fb:100 nack pli\r\na=rtcp-fb:100 goog-remb\r\na=rtcp-fb:100 transport-cc\r\na=rtpmap:101 VP9/90000\r\na=rtcp-fb:101 ccm fir\r\na=rtcp-fb:101 nack\r\na=rtcp-fb:101 nack pli\r\na=rtcp-fb:101 goog-remb\r\na=rtcp-fb:101 transport-cc\r\na=rtpmap:107 H264/90000\r\na=rtcp-fb:107 ccm fir\r\na=rtcp-fb:107 nack\r\na=rtcp-fb:107 nack pli\r\na=rtcp-fb:107 goog-remb\r\na=rtcp-fb:107 transport-cc\r\na=fmtp:107 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f\r\na=rtpmap:116 red/90000\r\na=rtpmap:117 ulpfec/90000\r\na=rtpmap:96 rtx/90000\r\na=fmtp:96 apt=100\r\na=rtpmap:97 rtx/90000\r\na=fmtp:97 apt=101\r\na=rtpmap:99 rtx/90000\r\na=fmtp:99 apt=107\r\na=rtpmap:98 rtx/90000\r\na=fmtp:98 apt=116\r\nm=application 9 DTLS/SCTP 5000\r\nc=IN IP4 0.0.0.0\r\na=ice-ufrag:xzdb\r\na=ice-pwd:ND1hvRqTLMSYoMHZYmy99ZrM\r\na=fingerprint:sha-256 76:30:F4:E4:55:F9:07:A3:6B:22:16:2E:F8:16:EB:57:72:E2:F4:B9:D9:B1:63:0C:E7:BF:88:5B:E0:E9:E0:C4\r\na=setup:actpass\r\na=mid:data\r\na=sctpmap:5000 webrtc-datachannel 1024\r\n"}
DEBUG: About to set remote description. Signaling state: stable
INFO: Received woogeen message.
DEBUG: S->C: {"type":"candidates","candidate":"candidate:704553097 1 udp 2113937151 192.168.1.3 53336 typ host generation 0 ufrag xzdb network-cost 50","sdpMid":"audio","sdpMLineIndex":0}
DEBUG: On remote ice candidate from peer wind
DEBUG: Add remote ice candidates.
INFO: Received woogeen message.
DEBUG: S->C: {"type":"candidates","candidate":"candidate:704553097 2 udp 2113937150 192.168.1.3 53338 typ host generation 0 ufrag xzdb network-cost 50","sdpMid":"audio","sdpMLineIndex":0}
DEBUG: On remote ice candidate from peer wind
DEBUG: Add remote ice candidates.
DEBUG: Draining pending streams.
DEBUG: Peer connection is ready for draining pending streams.
DEBUG: Add ice candidate success.
DEBUG: Signaling state changed: have-remote-offer
INFO: Received woogeen message.
DEBUG: S->C: {"type":"candidates","candidate":"candidate:704553097 1 udp 2113937151 192.168.1.3 53340 typ host generation 0 ufrag xzdb network-cost 50","sdpMid":"data","sdpMLineIndex":2}
DEBUG: On remote ice candidate from peer wind
DEBUG: Add remote ice candidates.
INFO: Received woogeen message.
DEBUG: S->C: {"type":"candidates","candidate":"candidate:704553097 1 udp 2113937151 192.168.1.3 53342 typ host generation 0 ufrag xzdb network-cost 50","sdpMid":"video","sdpMLineIndex":1}
DEBUG: On remote ice candidate from peer wind
DEBUG: Add remote ice candidates.
DEBUG: Add ice candidate success.
DEBUG: Signaling state changed: stable
DEBUG: Draining pending streams.
DEBUG: Peer connection is ready for draining pending streams.
DEBUG: Ice connection state changed. State: checking
DEBUG: Set local description successfully.
DEBUG: Sent answer.
INFO: Received woogeen message.
DEBUG: S->C: {"type":"candidates","candidate":"candidate:704553097 2 udp 2113937150 192.168.1.3 53344 typ host generation 0 ufrag xzdb network-cost 50","sdpMid":"video","sdpMLineIndex":1}
DEBUG: On remote ice candidate from peer wind
DEBUG: Add remote ice candidates.
DEBUG: Add ice candidate success.
DEBUG: Ice connection state changed. State: failed

Any Help would be appreciated!

[Jianjun_Z_Intel]

Hi Ahmed,

If two clients are in different networks, a STUN/TURN server may be required.

[dandy__kiven]

Where can I configure peerserver-release-4.2.1 P2P service to point to the server address?