If freeswitch has no external (public) access, and you don’t have an rtpproxy/rtpengine, and you will be servicing clients on the public internet, the audio will no work. Your best bet for a simple setup is assign a public ip to freeswitch, allow all rtp port range (UDP) in and out of freeswitch, and set this public ip in external_rtp_ip. Everything else are the private IPs. On Sat, 5 Jun 2021 at 07:30, HS <bullehs@gmail.com> wrote:
Dear all,
I have been testing an Opensips + Freeswitch setup on the same instance on EC2. I did follow the guide here for IP setup: https://freeswitch.org/confluence/display/FREESWITCH/Amazon+EC2
However, for production, it seems better to have separate instances for Opensips and Freeswitch. (Or wrong?). What would be the following variables:
bind_server_ip external_rtp_ip external_sip_ip
Shall I use the Opensips external IP or Freeswitch (although Freeswitch will have no external access).
Thanks for the help. _________________________________________________________________________
The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform.
Join our online community to chat in real time https://signalwire.community
Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
-- Regards, David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337