Thanks Ross for the explanation.
Regards,
2015-10-13 23:37 GMT-03:00 Ross Finlayson :
> If you’re on the private side of a NAT, then you can’t run a RTSP server
> there and expect clients on the (public) Internet to be able to reach you.
> (You might be able to get this to work in some cases, b
If you’re on the private side of a NAT, then you can’t run a RTSP server there
and expect clients on the (public) Internet to be able to reach you. (You
might be able to get this to work in some cases, but there’s no guarantee.)
If your RTSP server is behind a NAT, then the only *reliable* way
Thanks Ross for your answer.
I am currently behind NAT as you mention. Couldn't I just use port
forwarding in order to have my server on a DMZ?
What I mean is this:
Public_IP:Port - FWD To -- Private_IP:Port
For each one of the ports mentioned above.
My clients would connect on the pub
> I have developed a RTSP server that serves unicast clients with a stream from
> a live source.
>
> I have based my development on the testOnDemandRTSPServer implementation.
>
> Over LAN everything works as expected. The problem I am having is that over
> the Internet I cannot use UDP as a tra
