Dropped Calls - 3CX & FlowRoute with PFSense FireWall
Whitey436 last edited by
I am having a random issue when running a 3CX soft PBX using FlowRoute as my SIP trunk provider.
When connected on a call on average about 15-30 minutes into the call, it will drop the call. This when on for a few months and I finally changed the network design such that the 3CX server is now not flowing through the PFSense but rather directly to the public connection.
I have been running this config for a week now and have had no dropped calls. I would very much prefer to run all traffic though the PF F/W but cannot afford the aggravation of having to deal with dropped calls.
Does anyone have any ideas on what might be causing this behavior?
marvosa last edited by
Reading other posts, it sounds like it might be a state timeout issue. It's been suggested that switching the Firewall Optimization Options (System-> Advanced-> Firewall and NAT tab) to "conservative" may help. Apparently typing "pfctl -st" in the console shows you the timings.
Below are the normal values. The fact that the "tcp.closing" timing matches up with your 15 min. disconnect issue is probably not a coincidence :
[2.2.6-RELEASE][firstname.lastname@example.org]/: pfctl -st tcp.first 120s tcp.opening 30s tcp.established 86400s tcp.closing 900s tcp.finwait 45s tcp.closed 90s tcp.tsdiff 30s udp.first 60s udp.single 30s udp.multiple 60s icmp.first 20s icmp.error 10s other.first 60s other.single 30s other.multiple 60s frag 30s interval 10s adaptive.start 481800 states adaptive.end 963600 states src.track 0s
Here are the conservative timings:
[2.2.6-RELEASE][email@example.com]/: pfctl -st tcp.first 3600s tcp.opening 900s tcp.established 432000s tcp.closing 3600s tcp.finwait 600s tcp.closed 180s tcp.tsdiff 60s udp.first 300s udp.single 150s udp.multiple 900s icmp.first 20s icmp.error 10s other.first 60s other.single 30s other.multiple 60s frag 30s interval 10s adaptive.start 481800 states adaptive.end 963600 states src.track 0s