Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
42 Views

Having issue in Chrome to Firefox invitation in Intel CS WebRTC JS SDK

Hi,

I had deploy Intel CS for WebRTC. I created one Peer Server as per provided documentation and hosted js sdk p2p sample in another hosted server.

Issue: I am able to make ICe connection by sending invitation from Firefox to Chrome. Video share, messages working well.

But when I send Invitation from Chrome to firefox then its not working. Ice connection get failed. And I am not able to share video or messages etc. Same issue with Internet Explorer too.

1. Test Environment
Network status: Wired LAN via lease line 6 MBPS network
Server machine information : Ubuntu 14.04.4 LTS, Azure - 2vcpu, 7GB RAM, Bandwidth Unlimited, Server version - PeerServer, Server Configuration - All Defaults. Stun and Turn are also installed on same Peer Server Machine.
Client machine information : Windows 7, Core I7, 8GB, Chrome Version 52.0.2743.82 m Latest, rest default
Test topology : two users only in two different browser on same client machine
 
2. Test Steps
a. I had hosted js sdk p2p sample application in my another server which is on Azure. Application url : http://enterprise-dev2.georama.com/p2p/peercall.html

b. Open http://enterprise-dev2.georama.com/p2p/peercall.html in Chrome browser. Login by 101 id.

c. Open http://enterprise-dev2.georama.com/p2p/peercall.html in Firefox browser. Login by 102 id.

d. Now Invite 102 from Chrome.

e. Invitation is accepted. But Ice connection failed.

3. Chrome Console log :

adapter.js:146 This appears to be Chrome

woogeen.sdk.js:8 DEBUG: Query string: clientType=Web&clientVersion=3.1&token=101

woogeen.sdk.js:8 INFO: Connected to websocket server.

woogeen.sdk.js:8 DEBUG: Authentication passed. User ID: 101

woogeen.sdk.js:8 DEBUG: Send invitation to 102

peercall.html:85 Invite success.

woogeen.sdk.js:8 INFO: Received woogeen message.

woogeen.sdk.js:8 DEBUG: Received chat accepted.

woogeen.sdk.js:8 DEBUG: Draining pending streams.

woogeen.sdk.js:8 DEBUG: Peer connection is ready for draining pending streams.

woogeen.sdk.js:8 DEBUG: Signaling state changed: have-local-offer

woogeen.sdk.js:8 DEBUG: Set local descripiton successfully.

woogeen.sdk.js:8 INFO: Received woogeen message.

woogeen.sdk.js:8 DEBUG: S->C: {"type":"answer","sdp":"v=0\r\no=mozilla...THIS_IS_SDPARTA-47.0.1 1246555333179353951 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0 0\r\na=fingerprint:sha-256 71:AB:FD:AF:FF:B5:B9:FA:38:C5:29:F6:A2:00:53:AF:91:81:00:D4:0B:D7:AF:C0:2A:B3:FF:AA:49:B2:C3:74\r\na=ice-options:trickle\r\na=msid-semantic:WMS *\r\nm=audio 0 UDP/TLS/RTP/SAVPF 0\r\nc=IN IP4 0.0.0.0\r\na=inactive\r\na=rtpmap:0 PCMU/8000\r\nm=video 0 UDP/TLS/RTP/SAVPF 120\r\nb=AS:500\r\nc=IN IP4 0.0.0.0\r\na=inactive\r\na=rtpmap:120 VP8/90000\r\n"}

woogeen.sdk.js:8 DEBUG: About to set remote description. Signaling state: have-local-offer

woogeen.sdk.js:8 DEBUG: Set remote descripiton successfully.

woogeen.sdk.js:8 DEBUG: Draining pendding messages.

woogeen.sdk.js:8 DEBUG: Signaling state changed: stable

woogeen.sdk.js:8 DEBUG: Draining pending streams.

woogeen.sdk.js:8 DEBUG: Peer connection is ready for draining pending streams.

woogeen.sdk.js:8 DEBUG: Ice connection state changed. State: checking

woogeen.sdk.js:8 DEBUG: Ice connection state changed. State: failed

Thanks!

Tags (2)
0 Kudos
3 Replies
Highlighted
Beginner
42 Views

Please help me for above reported issue ASAP.

Thanks

0 Kudos
Highlighted
Beginner
42 Views

Its working in Chrome, IE 10/11 and with Android device. Only problem is with firefox which is not compatible with P2P Server as it mentioned to work with only Chrome and IE 10/11.

I feel, while working on P2P, use only latest Chrome and IE 10/11.

Thanks

0 Kudos
Highlighted
42 Views

Hi Parveen,

Firefox is not supported currently in P2P mode. The coming v3.2 release will have this feature.

Thanks!

0 Kudos