Has anyone noticed a major uptick in the number of remote mobile softphones having their public IPs blocked by the responsive firewall? This used to be a bigger problem, but has been pretty solid for a while now. However, starting on Monday, across multiple instances (though I believe all were running FreePBX 17) a number of mobile apps started getting blocked (both Sangoma Talk and Groundwire apps).
The apps are utilizing the push servers, which themselves weren’t getting blocked, but when they would register to try to dial out, or to switch over to take a call after receiving a push notif, the phone’s IP would get blocked by the responsive firewall. Unless I’m missing something, I don’t think this is due to a FreePBX module update. I haven’t been able to verify this fully, but I think so far all of the users who experienced this are running Android. I do see a Groundwire update from July 9, but Sangoma Talk hasn’t been updated since January 12. I also haven’t been able to capture sip during when this occurred, but I’m hoping to do that if this continues happening.
I do see this in the firewall log on one of the instances. I’m wondering if my custom responsive firewall rules (trying to relax them slightly) are not working properly?
iptables v1.8.9 (nf_tables): RULE_REPLACE failed (Invalid argument): rule in chain fpbxratelimit
Has anyone else been experiencing this?