I am new to FreePBX and have been setting up a new system.
I am not positive where to find out why voipfirewalld is using so much CPU.
I’ve tried rebooting the system and the CPU is still high.
Is there a certain log I can look through to find out why the CPU is so high?
I did update back to the latest, 13.0.57.1, to see if I can track down the problem.
The most recent lines in /tmp/firewall.log show this. Just looks like the FreePBX server and SIP provider:
1539104278: /sbin/iptables -w5 -W10000 -A fpbx-rtp -p udp -m udp --dport 10000:20000 -j ACCEPT
1539104278: /sbin/iptables -w5 -W10000 -A fpbx-rtp -p udp -m udp --dport 4000:4999 -j ACCEPT
1539104278: /sbin/ip6tables -w5 -W10000 -A fpbxsignalling -p udp -m udp --dport 5160 -j MARK --set-xmark 0x1/0xffffffff
1539104278: /sbin/ip6tables -w5 -W10000 -A fpbxsignalling -p udp -m udp --dport 5060 -j MARK --set-xmark 0x1/0xffffffff
1539104278: /sbin/iptables -w5 -W10000 -A fpbxsignalling -p udp -m udp --dport 5160 -j MARK --set-xmark 0x1/0xffffffff
1539104278: /sbin/iptables -w5 -W10000 -A fpbxsignalling -p udp -m udp --dport 5060 -j MARK --set-xmark 0x1/0xffffffff
1539104278: /sbin/iptables -w5 -W10000 -A fpbxsmarthosts -s 444.333.222.111/32 -m mark --mark 0x1/0x1 -j ACCEPT
1539104278: /sbin/iptables -w5 -W10000 -A fpbxregistrations -s 111.222.333.444/32 -j fpbxknownreg
1539104278: /sbin/iptables -w5 -W10000 -A fpbxregistrations -s 444.333.222.111/32 -j fpbxknownreg
1539104278: /sbin/ip6tables -w5 -W10000 -A fpbxhosts -s ::1/128 -j zone-trusted
1539104278: /sbin/iptables -w5 -W10000 -A fpbxhosts -s 111.222.333.444/32 -j zone-trusted
1539104278: /sbin/iptables -w5 -W10000 -A fpbxhosts -s 127.0.0.1/32 -j zone-trusted
1539104278: /sbin/ip6tables -w5 -W10000 -R fpbxlogdrop 1 -j DROP
1539104278: /sbin/iptables -w5 -W10000 -R fpbxlogdrop 1 -j DROP
1539104278: /sbin/ip6tables -w5 -W10000 -A fpbxinterfaces -i eth0 -j zone-external
1539104278: /sbin/iptables -w5 -W10000 -A fpbxinterfaces -i eth0 -j zone-external
1539104278: /sbin/iptables -w5 -W10000 -t nat -A masq-output -o eth0 -j MARK --set-xmark 0x2/0x2