@Ashcor Usually, this happens during the night. At one point my suspicions was that it was due to inactivity. 3/4 of the time, its first thing in the morning that this problem is found.
However, I did have a spell about 9 months ago this was happening 3 times a day. This only lasted for about 2 weeks and went back to happening once a week.
I reached out to Tylnex and they were less than helpful.
I guess the thing that kind of confuses me is rebooting the PBX fixes it. I reboot the PBX mostly because its less disruptive to the network than rebooting the PFSense and the whole network goes down.
I just don’t know where to start, to start, troubleshooting this problem. I am looking to upgrade my PBX25 but I am not sure this would solve my problem. Really do not want to invest in another system and still have this problem.
Not a PF Sense user so can’t really help you with the how but I’d start analyzing the traffic/connections to the PFSense firewall when the problem occurs, noting the number/type of connections between the PBX and Firewall and then after the reboot of one or the other.
My guess is you’ll see a vast reduction in connections after the reboot.
The fact that rebooting either fixes the issue suggests it’s something between them and not anything outside (like your ISP). If it were an ISP problem I’d expect that only a firewall reboot would fix.
You might want to change the “Outbound NAT Mode” to “Manual Outbound NAT Rule Generation” on your pfSense router and let it run for a few days to see if it alleviates the problem that you’ve described.
That change should not impact much the way your router works otherwise, assuming that you are using a simple/basic configuration, with the possible exception that at some point you might need to add a line manually to force your router’s own outbound traffic to be NATted.
Have a couple of systems using iax2 trunks that would go offline on occasion
Different systems might lose trunk registration sometimes
the above would give all circuits busy
Clearing the router connection tracking cache would resolve the issue for me
Who is your trunk provider, guessing the trunk point of presence is offline. I’m guessing your firewall is port switching. But outbound calls should still work.
You could set your outbound NAT to static ports.
Under Firewall > NAT > outbound you can set your PBXs source IP to use static ports.
I don’t have a pfsense in front of me but it should help the trunk stay registered.