[Freeswitch-users] Firewall mysteriously starts blocking calls to port 5060
david.villasmil.work at gmail.com
Fri May 3 17:48:03 UTC 2019
I'd say this is a question for shorewall. But since you're here, is there
maybe some flood-prevention mechanism that would block it? Did you check
shorewall's log to try and find the reason it was blocked?
email: david.villasmil.work at gmail.com
On Fri, May 3, 2019 at 6:07 PM Chad Phillips <chad at apartmentlines.com>
> Recently I reconfigured my firewall (via Shorewall) to block all inbound
> traffic to port 5060, except for whitelisted IP addresses from my inbound
> DID providers. After setup, we ran tests and everything worked fine for all
> incoming calls across all providers.
> Then a few hours later, calls from one of our providers started being
> blocked. All calls from our other providers continued coming through fine.
> Upon restarting our firewall service, the blocked calls from the single
> provider started coming through again.
> Between our successful tests and the start of the issue, there were zero
> changes made to the server.
> So why would my firewall suddenly start blocking inbound traffic from a
> whitelisted IP that it was previously letting through??
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeSWITCH-users