Usage of static(dedicated) IP is preferred way for RTMPMiniServer. It allows send signal from publisher to studio by shortly way.
But LTE providers in many countries don’t offer static IP. For solve this issue we developed new feature – “ProxyAddon”. It does not required dedicated IP and port-forwarding manipulation.
Do this steps:
- run RTMPMiniServer and press START
- go to Tools/Proxy Add-on. It opens “Proxy Addon”.
- press “Connect” for get public address. Use this as RTMP URL.
What is cons and pros of usage proxy addon?
Cons – you don’t need dedicated IP and port-forwarding setup. It’s perfect for using for mobile studios.
Pros – this workflow has 3 participants: Publisher–> Proxy-server –> Studio
instead 2 participants for direct connection (Publisher–>Studio)
Where are located proxy servers and what’s about stable?
Now we are providing few public proxy node in Europe. But soon you can deploy proxy node on your server.
For example you can rent VPS from DigitalOcean or Scaleway or AWS and deploy proxy node. Many cloud providers allow hour-rate so you can turn on server only for event.
Our Studio in USA has dedicated IP and we happy with RTMPMiniServer. What is advantage of proxy addon we can get?
You can get advantage if your publisher in other country. Proxy node allows solve the “first mile” issue.
Example: your reporter located in Japan. Direct connection from reporter to your USA-studio may be unstable because international routing very depends on provider. So you can deploy proxy node on AWS (presented in Japan). In my opinion transfer between Japan AWS and USA more predictable because AWS use dedicated internet channel.
In other words: proxy node allows catch signal to stable environment and send to studio as soon as possible.