We are seeking an experienced Korento server developer. You will be responsible for assisting our AWS team in trouble shooting a Kurento data channels/ports issue that we're having with UDP and TCP.
You must have considerable experience with the following:
Kurento
Coturn
webRTC
Issues and Questions to answer::
Question1:
Does Kurento media server needs to be public in order to work?
We tried 3 tests as below.
1. Kurento and Turn - All TCP and UDP ports open - Its working
2. Kurento: TCP open only to Application server and Turn: open to public - Stream not working
3. Both open to Application only - Not working
Basically, it works only if all the ports of Kurento server are open. But We want to secure the kurento server by allowing it only to the Application server, app would pass the data to kurento server.
Question2:
Having few issues with kurento server configuration on AWS
We see connectivity issue with the TURN server when we put the Media server ina private subnet behind a NAT gateway.
Our AWS stack is web application node with Nginx ( in public subnet) which talks to the
kurento media server ( in private subnet behind a NAT which is in a public subnet)
its a one to many peer to peer connection based application.
1)We had both TURN server resides on the same kurento media server.
2)We installed the TURN server on a separate node within the public subnet.
hence we have a webapp (node), kurentomedia node(2), Turn node(3).
We still see the same issue with data not able to stream with the kurento in private subnet.
Appreciate if you can let us know.
question 3) Does kurento media server has to be public ?
Are there any instances where in users have been able to media server in a private subnet?
question 4 )if the kurento media server has to be public then what are some of the ways we can secure the media server as most of the ports would be remain open.
About the recuiterMember since May 20, 2018 Sanjeev Yadav
from Saint-Denis, Reunion