25 Oct
2014
25 Oct
'14
5:35 a.m.
On 10/24/14 12:34, Marko Seidenglanz wrote:
Hello,
We want to use Kamailio (4.2) + RTPEngine (3.3) behind NAT.
Unfortunately the STUN Messages (Binding Requests) sent from remote peer
(Google Chrome ) do not arrive at RTPEngine host.
I think they get blocked by the firewall. RTPEngine itself does not send
any STUN Messages until it get's the first message from the remote peer
as Google Chrome has the "active" role in DTLS Agreement.
Is there a way to tell RTPEngine to open the ports for remote peer, so
that the messages arrive?
When RTPEngine is not behind NAT, everything works as expected.
Rtpengine is designed to be run on a host with a public address, or at
least a host that has direct communication with the clients that it's
supposed to serve. So no, there is no such function.
cheers