Problems Kurento on mobile

73 views
Skip to first unread message

jose...@gmail.com

unread,
Sep 11, 2018, 2:13:18 AM9/11/18
to kurento
Hi everybody, I have a problem running WebRTC client (Kurento) with Chrome installed on Android terminal. 
If the video chat is accessed via Wi-Fi / Ethernet, the video chat is viewed correctly. If it is done through Movistar 4G connection, the video cannot be seen. But, through a 4G connection if the service provider is Yoigo, the video looks correct.
I have read in forums that the problem may be in the service provider, which disconnects connections from WebSockests because they are long-term connections. may I solve this problem, and keep using Movistar? Maybe changing port?? Talking with Movistar itself?? Or I must change the provider

I have another question referring firewalls, I see that working through a firewall I couldn’t see the video and audio, due the firewall restriction, but I can see websites and youtube for example. My question is, may I use another port? I mean, if I publish kurento on port 80 instead of port 8888, could I avoid cutting firewalls?

Thanks

allo...@meeting-in.com

unread,
Sep 11, 2018, 7:11:49 AM9/11/18
to kurento
Is a common problem, please if somebody knows how to solve and works on Movistar or Vodafone, or any other operator, it will be more than appreciate.

thnks
ALL

jose...@gmail.com

unread,
Sep 12, 2018, 5:42:30 AM9/12/18
to kurento
I have detect data ips of my mobile with What is my IP:

LOCAL IP Mobile with Whatis My IP : ---- LOCAL IP MOBILE ------ 
PUBLIC IP Mobile with Whatis My IP : ---- PUBLIC IP MOBILE ------ 

This is my log messages on IceCandidate with my 4g connection(Orange):

Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:764647650 1 udp 2122260223 ---- LOCAL IP MOBILE ------  48071 typ host generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'audio',
     sdpMLineIndex: 0 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:764647650 1 udp 2122260223 ---- LOCAL IP MOBILE ------  41645 typ host generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'video',
     sdpMLineIndex: 1 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:1662018578 1 tcp 1518280447 ---- LOCAL IP MOBILE ------  9 typ host tcptype active generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'audio',
     sdpMLineIndex: 0 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:1662018578 1 tcp 1518280447 ---- LOCAL IP MOBILE ------  9 typ host tcptype active generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'video',
     sdpMLineIndex: 1 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:1146738467 1 udp 1686052607 ---- PUBLIC IP MOBILE ------ 22585 typ srflx raddr ---- LOCAL IP MOBILE ------ rport 41645 generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'video',
     sdpMLineIndex: 1 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:1146738467 1 udp 1686052607 ---- PUBLIC IP MOBILE ------ 39411 typ srflx raddr ---- LOCAL IP MOBILE ------ rport 48071 generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'audio',
     sdpMLineIndex: 0 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:1146738467 1 udp 1686052607 ---- PUBLIC IP MOBILE ------ 26018 typ srflx raddr ---- LOCAL IP MOBILE ------ rport 48071 generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'audio',
     sdpMLineIndex: 0 } }
Connection 11 received message  { id: 'onIceCandidate',
  candidate:
   { candidate: 'candidate:1146738467 1 udp 1686052607 ---- PUBLIC IP MOBILE ------ 43020 typ srflx raddr ---- LOCAL IP MOBILE ------ rport 41645 generation 0 ufrag TxSW network-id 1 network-cost 900',
     sdpMid: 'video',
     sdpMLineIndex: 1 } }
 
All candidates looks correct but i cannot view the video chat. There are only udp ports, but if i try to connect with yoigo, tpc ports are used too. 

Thanks for all



El martes, 11 de septiembre de 2018, 8:13:18 (UTC+2), jose...@gmail.com escribió:

jose...@gmail.com

unread,
Sep 12, 2018, 5:50:06 AM9/12/18
to kurento
I use a turn server installed by me and a stun server in 77.72.174.164:3478, listed in kurento docummnetation.

Thanks for all

El martes, 11 de septiembre de 2018, 8:13:18 (UTC+2), jose...@gmail.com escribió:

jose...@gmail.com

unread,
Sep 14, 2018, 5:56:32 AM9/14/18
to kurento

I have solved the problem. The problem was that the TCP ports were not open in the rules of the Amanzon instanace where I installed the kurento media server. It could only be accessed through UDP, so only the Yoigo operator could connect (Yoigo does not seem to block UDP communications). Opening the TPC ports in the instance, from the other operators (Orange and Simyo) has been able to see the video chat.

If I force kurento to have only TCP communications, the kurento server stopped working after one hour. Are there problems in Kurento with TCP communications? In UDP communications so far had not had problems.

Thanks for all


El martes, 11 de septiembre de 2018, 8:13:18 (UTC+2), jose...@gmail.com escribió:
Reply all
Reply to author
Forward
0 new messages