peerjs

Pop up state directly from coldstart

↘锁芯ラ 提交于 2019-12-12 10:53:01
问题 I've built a Cordova app using the ionic framework. It is build using Peer JS and i need the app to open a state from cold start quickly whenever my peer receives an incoming call, kind of like the phone app opens the incoming call activity when we receive a call. Currently I'm using ionic push notifications to open the state on click of the notification but that takes too long and loads from the splash screen onwards. Is there a way to kind of pop open my state containing the receive call

Custom PeerJs Server giving ERR_CONNECTION_TIMED_OUT

久未见 提交于 2019-12-11 07:33:34
问题 So I installed peerjs server on my digitalocean hosting using following command. npm install peer peerjs --port 9000 --key peerjs After running above command the putty gave following print: Started PeerServer on ::, port: 9000, path: / (v. 0.2.8) Following is my index.html code: <!DOCTYPE html> <html> <head> <title>Peer JS Testing</title> <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/peerjs/0.3.13

iceConnectionState is disconnected (when used over the internet)

谁说我不能喝 提交于 2019-12-06 09:43:30
问题 This question has been asked before, but I have not found an answer yet. I'm basically having the same problem as described here and here. I'm trying to set up a webRTC connection using PeerJS. It works flawlessly in LAN but I can't get it to work over the internet. I'm using coturn as TURN server, but so far this has not solved the problem.The Chromium console prints out the following: PeerJS: Added ICE candidate for: client1 peer.js:1476 PeerJS: Set remoteDescription: ANSWER for: client1

How can I receive data with a peerJS peer to peer connection?

白昼怎懂夜的黑 提交于 2019-12-06 04:17:52
I'm trying to connect two peers using peerJS. I am pretty much just following through their "Getting Started" but I am still struggling. Below is the code that I have gotten so far. <body> <script src="http://cdn.peerjs.com/0.3/peer.min.js"></script> <script> var conn; var peer = new Peer({key: 'lwjd5qra8257b9'}); peer.on('open', function(id){ console.log('My peer ID is:' + id); document.getElementById('peerIdDisplay').innerHTML = '<b>My peer ID is: </b><font color="red">' + id + '</font>'; }); function ConnectToPeer() { var peerId = document.getElementById("peerIdTxtBox").value; console.log

Chrome won't play WebAudio getUserMedia via WebRTC/Peer.js

青春壹個敷衍的年華 提交于 2019-12-04 01:59:17
问题 I want to make a simple audio only stream over WebRTC, using Peer.js. I'm running the simple PeerServer locally. The following works perfectly fine in Firefox 30, but I can't get it to work in Chrome 35 . I would expect there was something wrong with the PeerJS setup, but Chrome -> Firefox works perfectly fine, while Chrome -> Chrome seems to send the stream, but won't play over speakers. Setting up getUserMedia Note: uncommenting those lines below will let me hear the loopback in Chrome and

WebRTC with PeerJS: iceConnectionState Disconnected?

强颜欢笑 提交于 2019-12-02 03:37:18
问题 I have a node app in each of my machines running this example on localhost with a PeerServer key that I made. When I try initiating a call between the two, the connection is established (as in, the receiver says it got a call from the sender). However, the Media Streams are also initiated (black boxes show up in the video divs), and then the connection stops because "iceConnectionState is disconnected". What could be causing this problem? Is it some sort of configuration issue? I'm using two

WebRTC with PeerJS: iceConnectionState Disconnected?

﹥>﹥吖頭↗ 提交于 2019-12-02 02:21:46
I have a node app in each of my machines running this example on localhost with a PeerServer key that I made. When I try initiating a call between the two, the connection is established (as in, the receiver says it got a call from the sender). However, the Media Streams are also initiated (black boxes show up in the video divs), and then the connection stops because "iceConnectionState is disconnected". What could be causing this problem? Is it some sort of configuration issue? I'm using two Macs running Yosemite. 来源: https://stackoverflow.com/questions/31750312/webrtc-with-peerjs

Chrome won't play WebAudio getUserMedia via WebRTC/Peer.js

流过昼夜 提交于 2019-12-01 10:48:41
I want to make a simple audio only stream over WebRTC, using Peer.js . I'm running the simple PeerServer locally. The following works perfectly fine in Firefox 30, but I can't get it to work in Chrome 35 . I would expect there was something wrong with the PeerJS setup, but Chrome -> Firefox works perfectly fine, while Chrome -> Chrome seems to send the stream, but won't play over speakers. Setting up getUserMedia Note: uncommenting those lines below will let me hear the loopback in Chrome and Firefox. navigator.getUserMedia = (navigator.getUserMedia || navigator.webkitGetUserMedia || navigator

peerjs/webrtc iceConnectionState failed

梦想与她 提交于 2019-12-01 06:25:25
I've been trying to figure this out for a while. I'm trying to establish a simple connection using peerjs. I can connect successfully to the peer with id USER_ID . However, they are unable unable to connect to me. I receive the following log when they try to connect. iceConnectionState is changed to failed eventually and no data can be recieved. The application is using the peerjs cloud server I'm using the latest version of Chrome. They have tried using latest versions of Chrome and Firefox They have switched off any firewalls Have even tried the peerjs chat example and it fails with the same

peerjs/webrtc iceConnectionState failed

旧时模样 提交于 2019-12-01 04:35:27
问题 I've been trying to figure this out for a while. I'm trying to establish a simple connection using peerjs. I can connect successfully to the peer with id USER_ID . However, they are unable unable to connect to me. I receive the following log when they try to connect. iceConnectionState is changed to failed eventually and no data can be recieved. The application is using the peerjs cloud server I'm using the latest version of Chrome. They have tried using latest versions of Chrome and Firefox