VoIP SIP dies until state table reset
-
Maybe you can find a hint here.
http://doc.pfsense.org/index.php?title=Special%3ASearch&search=voip&go= -
There's nothing new in those documents.
But since it's all UDP traffic I am considering changing the relevant rules to "state type" = none. I can keep a VoIP call up and without disruption through a state table reload.
-
Have you tried changing state table optimization ?
2. Set Conservative state table optimization - pf's default UDP timeouts are too low for some VoIP services. If your phones mostly work, but randomly disconnect, set "Firewall Optimization Options" to Conservative under System -> Advanced. Note this only works on 1.2.3-RC1 and newer as pf itself never increases UDP timeouts, our code changed to do this.
-
Yes I've tried all possible choices there.
For now the solution that is working is cron to reset state table I think 1x at 3:00 am and again 3:30 AM. It's a nasty dirty hack – but since I set it up I have not had any additional problems.
My next try would have been to disable states entirely for the VoIP traffic -- but if it's working fine now and I have no other issues with 2 daily state table resets I am going to leave it alone.
-
Hi joako,
Did you ever find a resolution to this issue. Since switching to pfSense, I've been experiencing exactly the same issue.
bd.
-
If your IP changes that will happen (unless you're running 2.0).
-
Hi joako,
Did you ever find a resolution to this issue. Since switching to pfSense, I've been experiencing exactly the same issue.
bd.
It's resolved but not how I would like it. Asterisk SIP peer becomes unreachable triggers an alert in nagios which clears pfSense state table. No complaints 620,000 calls later.
IP address is static for this route, but I do have a PPPOE dynamic WAN.
-
@cmb:
If your IP changes that will happen (unless you're running 2.0).
Could you please be more specific about 2.0 - are you talking about Gateway Monitoring feature?
It seems I have the same issue in 2.0-RC1, http://forum.pfsense.org/index.php/topic,34039.0.html
So, for some reasons this Gateway Monitoring feature is useless. Or misconfigured? -
I have seen this problem too with my IP changing and 2.0-RC1 not clearing out the states with the old IP, so of course my voip server cannot connect. I did notice that the gateway the IP changed on showed no downtime. Not sure if that "no downtime" was simply after the IP change or how the downtime is actually determined. I would think it should show sime kind of downtime during the IP change and take appropriate action with the state table. But then again…
-
If the ip changes gracefully e.g As a result of a routine dhcp renew I don't see why it should consider any downtime to have taken place.