Hi All
I'm using rtpengine to in my implementation of webrtc.
In my client side browser I have used following code snippet to configure stun/turn servers to identify ice candidates and turn fall back.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
var pcConfig = {"iceServers": [ {'url': 'turn:52.6.57.126:3478?transport=tcp'}]}; peerConn = new PeerConnection(pcConfig);
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Am using rfc 5766 turn server http://code.google.com/p/rfc5766-turn-server/
As long as stun is working my webrtc flow works fine.
I wanted to know how rtpengine support the turn fallback, is there any configuration required in this case.
Regards Isuru
On 06/05/15 01:30 AM, Isuru Wijesinghe wrote:
Hi All
I'm using rtpengine to in my implementation of webrtc.
In my client side browser I have used following code snippet to configure stun/turn servers to identify ice candidates and turn fall back.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
var pcConfig = {"iceServers": [ {'url': 'turn:52.6.57.126:3478?transport=tcp'}] http://52.6.57.126:3478?transport=tcp'}]}; peerConn = new PeerConnection(pcConfig);
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Am using rfc 5766 turn server http://code.google.com/p/rfc5766-turn-server/
As long as stun is working my webrtc flow works fine.
I wanted to know how rtpengine support the turn fallback, is there any configuration required in this case.
RTP over TCP isn't supported quite yet, but it's being worked on and will be available in the near future.
Cheers
-
Isuru Wijesinghe -
Richard Fuchs