[Freeswitch-users] Firewall mysteriously starts blocking calls to port 5060

Brian : brians at iptel.co
Fri May 3 17:40:30 UTC 2019


Hi Chad, that's probably more of a question for the shorewall people..

Maybe there was some ids that thought blocked provider was a bad host for
some reason. Shorewall logs good place to start.

On Friday, May 3, 2019, Chad Phillips <chad at 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??
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20190503/9c3d04ea/attachment.html>


More information about the FreeSWITCH-users mailing list