Client side not using Xirsys Turn Servers

sweat....@gmail.com

unread,

Mar 12, 2016, 5:02:40 AM3/12/16

to kurento

Hello everyone not sure why but the configuration Xirsys is working but not using the turn servers. Any ideas? It only uses the stun server passed in the configuration client side:

var options = {
                            localVideo: $scope.localVideo,
                            mediaConstraints: constraints,
                            onicecandidate: window.localParticipant.onIceCandidate.bind(window.localParticipant),
                            configuration: "iceServers":[{"url":"stun:turn01.uswest.xirsys.com"},{"username":"a4786232-e833-11e5-9f3a-b1e3b1ec0622","url":"turn:turn01.uswest.xirsys.com:80?transport=udp","credential":"a47862be-e833-11e5-9123-12e1ac1c0311"},{"username":"a4786232-e833-11e5-9f3a-b1e3b1ec0622","url":"turn:turn01.uswest.xirsys.com:80?transport=tcp","credential":"a47862be-e833-11e5-9123-12e1ac1c0311"},{"username":"a4786232-e833-11e5-9f3a-b1e3b1ec0622","url":"turn:turn01.uswest.xirsys.com:3478?transport=udp","credential":"a47862be-e833-11e5-9123-12e1ac1c0311"},{"username":"a4786232-e833-11e5-9f3a-b1e3b1ec0622","url":"turn:turn01.uswest.xirsys.com:3478?transport=tcp","credential":"a47862be-e833-11e5-9123-12e1ac1c0311"}]
};

That is my configuration options when passing send only candidate.

Ivan Gracia

unread,

Mar 14, 2016, 1:25:07 PM3/14/16

to Kurento Public

No clue. Make sure you have access to that server. Please check the server here, but in my case it's giving back correct candidates.

Ivan Gracia

--
You received this message because you are subscribed to the Google Groups "kurento" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kurento+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Austin Sweat

unread,

Mar 14, 2016, 1:39:01 PM3/14/16

to kur...@googlegroups.com

Think its the cellular network blocking those ports or port types.

--
You received this message because you are subscribed to a topic in the Google Groups "kurento" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kurento/4fg2zSjztfQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kurento+u...@googlegroups.com.

Ivan Gracia

unread,

Mar 14, 2016, 1:42:12 PM3/14/16

to Kurento Public

Aaaaah that could perfectly be the case. It works well under wi-fi, I'd assume.

Ivan Gracia

Austin Sweat

unread,

Mar 14, 2016, 1:48:33 PM3/14/16

to kur...@googlegroups.com

Right, well from my research I found using TCP ports seems to be the best solution because they're blocking UDP to avoid torrenting.

Ivan Gracia

unread,

Mar 14, 2016, 1:50:13 PM3/14/16

to Kurento Public

Cool! Thanks for the feedback.

Ivan Gracia

AlohaTech

unread,

Jul 26, 2016, 6:32:24 AM7/26/16

to kurento, sweat....@gmail.com

Hello Guys,
Could you please tel me how do we secure our credentails on client side.
Currently I am passing configuration following way

    var options = {
                localVideo : video,
                onicecandidate: participant.onIceCandidate.bind(participant),
                configuration: {iceServers:[ {"username":"user","url":"turn:66.186.0.134","credential":"pass" }]}
            }

            participant.rtcPeer = new kurentoUtils.WebRtcPeer.WebRtcPeerSendonly(options,
                function(error) {
                    if (error) {
                        closeoutgoingScreen(msg.name);
                        return console.error(error);
                    }
                    this.generateOffer(participant.offerToReceiveVideo.bind(participant));
            });

it is working fine but I dn't want show my credentials to others.
So is there any way we can hide it or how do I convert into encrypted format?
Any suggestion would be appreciated.
Thank you

AlohaTech

unread,

Jul 26, 2016, 6:37:32 AM7/26/16

to kurento, sweat....@gmail.com

Also I searched "setTurnUrl" which is used on server side
after creating WebrtEndpoint. So is it correct way to set our turn url on server side using setTurnUrl.
Please correct me if I am wrong

Thank you

Ivan Gracia

unread,

Jul 26, 2016, 7:14:44 AM7/26/16

to Kurento Public, sweat....@gmail.com

How to pass the credentials in the client is something you'll need to check the RTCPeerConnection for. I guess you can use the token

RTCPeerConnection.peerIdentity value when providing the TURN url. You'll need to check with your TURN provider for the support of this feature.

Ivan Gracia

--

AlohaTech

unread,

Jul 26, 2016, 9:25:05 AM7/26/16

to kurento, sweat....@gmail.com

Thank Ivan. I will look into this and will update you later.

AlohaTech

unread,

Jul 27, 2016, 9:14:38 AM7/27/16

to kurento, sweat....@gmail.com

Hello Ivan,
Could you tell me how do we use this? OR
Is there any other way to secure our credentials on Client side?
How do we do this

"username":"a4786232-e833-11e5-9f3a-b1e3b1ec0622","url":"turn:turn01.uswest.xirsys.com:80?transport=udp","credential":"a47862be-e833-11e5-9123-12e1ac1c0311"

Ivan Gracia

unread,

Jul 28, 2016, 2:52:56 AM7/28/16

to Kurento Public, sweat....@gmail.com

Well, I've never done that, but it seems as easy as passing the token in the RTCPeerConnection configuration.

Ivan Gracia

Reply all

Reply to author

Forward