[Freeswitch-users] Amazon EC2 Instances - Freeswitch
david.villasmil.work at gmail.com
Mon Jun 28 13:12:35 UTC 2021
You really need to look at your configuration and understand what’s
supposed to happen.
Sip signaling is not the same as RTP. I’m guessing you followed some
instructions to set it up. It probably instructed you to set the sip port
to 7870 at some point and you simply forgot.
Check both opensips at freeswitch’s config. If opensips is sending to
freeswitch on 7870 it can only be because it is configured to do so in
opensips somewhere, be it dispatcher or hard-coded in the config script,
and FS is configured yo listen on 7870 which is by no means a standard sip
port and wouldn’t be configured on FS by default. So you changed it at some
On Mon, 28 Jun 2021 at 13:02, HS <bullehs at gmail.com> wrote:
> Hi again.
> Thanks a lot for taking the time to respond. I thought port 7078 must be a
> default port or something and overlooked giving context. The pcap file
> shows the call coming from the correct IP address and port. However, the
> destination port (no matter what the IP) is always 7078. I am setup with
> one instance running Opensips in Amazon EC2 (using private IP in ACL) etc.
> Connects fine to Freeswitch on another instance (private IP). Call rings
> and is answered, but since the port is incorrect - I can't hear any audio.
> Additionally, I thought RTP would use ports from 16384 - 32768 range?
> Hope that helps a little.
> The FreeSWITCH project is sponsored by SignalWire https://signalwire.com
> Enhance your FreeSWITCH install with disruptive priced SMS and PSTN
> Build your next product on our scalable cloud platform.
> Join our online community to chat in real time
> Professional FreeSWITCH Services
> sales at freeswitch.com
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
email: david.villasmil.work at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeSWITCH-users