Hello,

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?

Regards,

David Villasmil
phone: +34669448337


On Fri, May 3, 2019 at 6:07 PM Chad Phillips <chad@apartmentlines.com> wrote:
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 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