I'm trying to establish the webrtc connection between the browser and docker container with Janus gateway with the video room plugin.
Everything works fine when I create the RTCPeerConnection from the browser with permissions to media not set or denied.
However, I experience problems when I try to connect with Janus from the browser with media permissions already granted before the connection was created. In this case, the connection state is failed. I can see in the janus (in docker container) that the remote candidates are not present there.
I can see in the webrtc console that for all pairs, there are STUN request setnt but no responses received
Related
Well I am studying about Web-RTC from its official documentation. I need to integrate live streaming in my website but after seeing this and studying about all its documentation. I only learn about streaming on locally like on same browser and same page. But this is not what i want. I want to start stream from my admin panel(This part has been completed) and broadcast that stream whoever has access to my website whatever the website is and whatever device. Whoever open my website if i m streaming then he should see that and if some of u have worked on live streaming then u should tell me. It will be a great help for me. All i did until now is to make a connection between two peers on same page. Now i want to make global peer to peer connection
I have done this implementation using simple-peer. Basically a wrapper for webRTC.
As soon as a new user connects a new webrtc connection should be made between the receiver and the caller. The receiver is firstly initialized and then sends a message to the sender to start the connection. This first connection is all done by your own server you should write.
Here is a working example. And here is the demo. Any connected devices will be automatically connected to the call. Multiple users supported. You'll find all the webrtc code in /public/js/main.js
You have to do signaling which mean that you have to exchange the PEER CONNECTIONS over the server and which required you to build a server page and client page so both of you can exchange the peer connection.
here is the complete procedure of exchanging the peer connection over the server.
find the heading
RTCPeerConnection plus servers
https://www.html5rocks.com/en/tutorials/webrtc/basics/
I had agora rtc integrated in my website few months back and it was running smoothly until recently when the remote video is not being seen, and upon checking in the console, there is an error that says
Agora-SDK [ERROR]: [866CE]None Ice Candidate not allowed.
Agora has provided the reason and solution to this problem in this documentation,
Reason:
When establishing a WebRTC connection, the SDK fails to find any ICE (Interactive Connectivity Establishment) candidate.
NOTE: A candidate contains the IP address and port information for connecting to a remote device.
Solution:
The type of candidates used for connection depends on whether you have enabled cloud proxy or not. Choose one of the following solutions accordingly.
If you have enabled cloud proxy, the SDK gets relay candidates from a TURN server. Check whether you have whitelisted the IP addresses and ports that Agora provides for cloud proxy, and ensure that the local client can connect to the TURN server.
If you have not enabled cloud proxy, the SDK gets host candidates from the local device. In this case, the error is usually caused by the security settings of the local device.
Check whether the browser has any plugins that disable WebRTC.
Ensure that you have enabled UDP in the system firewall, and added the specified domains and ports to the whitelist.
I have successfully run the "one2one-call" Kurento tutorial using a Windows KMS server, but am unable to see remote video when one of the peers is on a different network.
I have two laptops (one for each peer). One of these laptops is also running the Windows KMS server and the Application server.
I have also enabled port forwarding so that both peers can navigate to the web browser using the public IP and port number.
This works when both laptops are connected to the same network; but when I connect one of the laptops to another network, the remote video is no longer displayed. I can view the UI, register and attempt a call, additionally, when attempting the call, a notification does pop up on the remote peer and both peers get the popup requesting permission to access the microphone and camera, but no remote video. Each peer is only able to see their own image.
Would appreciate any information.
Did you configure STUN and TURN in KMS config file? (WebRtcEndpoint.conf.ini)
Try adding STUN server to config file. You can use google's STUN server.
stunServerAddress=74.125.143.127
stunServerPort=19302
If adding STUN to config did not work, you need TURN. If either of these networks have restrictive firewalls you will need to set up TURN server and add it to KMS configuration.
turnURL=USER:PASS#YOUR_MACHINE_PUBLIC_IP:<PORT>
You will also need to modify JavaScript for browser to use TURN.
For the reference: http://doc-kurento.readthedocs.io/en/stable/installation_guide.html#stun-and-turn-servers
I created an Azure Container Registre some days ago, and now it's impossible to login to this registry with docker login command. I always get this error message:
Error response from daemon: Get https://XXXXXXXXX.azurecr.io/v2/: dial tcp: lookup XXXXXXXXX.azurecr.io on [::1]:53: read udp [::1]:52627->[::1]:53: read: connection refused
Docker client may throw such error when it is unable to connect to the local Docker daemon properly. So, Restart/Reinstall-Docker should mostly fix that.
I made an app that connect to server to get some info
I use HTTPAdapter to send a post request
It runs successfully with preview on my browser
I've check that tha adapter and code has no bug
but it failed when I run it on my virtual device(3G network)
Request timeout for [http://172.16.100.106:10080/WistronAppProject/apps/services/api/WistronApp/android/query]
why i can't send request with different ip domain ?
it has to run in the same network?
there is some other problem?
The device must be able to connect to the same network Worklight Server is in.
If your server does not have a PUBLIC IP address, meaning it is running for example in your office network that is not available outside, then your device MUST be connected to the same office network via WiFi. If you connect via 3G, it will not be able to find the Worklight Server and connect to it.