I have to manually reset states after WAN down to allow Asterisk to re-register.

aventrax

Same problem here (pfSense 2.1.4)

WAN DHCP, static IP. My pbx does not register the trunks until I reset the state table, even with the "State Killing on Gateway Failure" option is de-selected.

I'm not able to do replicate the problem, so after any change I have to wait (days) to see if something different is happening… :(

charliem

It's clear to me that this is not a high priority to be fixed with the 2.1.x series. As a work-around for 2.1.x, look at my post here:
https://forum.pfsense.org/index.php?topic=70418.msg387457#msg387457 and re-apply the patch that's in the link.

Upgrading to 2.2 alpha has solved the problem for me, so you could consider that option as well.

aventrax

@charliem:

It's clear to me that this is not a high priority to be fixed with the 2.1.x series. As a work-around for 2.1.x, look at my post here:
https://forum.pfsense.org/index.php?topic=70418.msg387457#msg387457 and re-apply the patch that's in the link.

Upgrading to 2.2 alpha has solved the problem for me, so you could consider that option as well.

On 2.1.4 the commit that you suggest is not working.
I applied the commit 19d723d2af5e8392d372720ef97b5b83336ec9e1 and it changed the filter.inc.

I will update you on my next gateway down event :)

aventrax

It is working like a charm =)

streetfighter12

Still the same Problem on 2.3.3 for me.

I have to do the following to fix it for me (found it some years ago on the pfsense forum):

cd /usr/local/sbin
vi voip-wan-wipe

#!/bin/sh
sleep 30
pfctl -F state

chmod 755 voip-wan-wipe

vi ppp-linkup and add before exit 0:

/usr/local/sbin/voip-wan-wipe &

Works for me like a charm.

–

But my question is: Is there any better way to do it in the actual release of pfsense?

agbloomfield

I think I'm having the same issue with a flaky DSL modem – but registering a SIP trunk with Grandstream PBX (which is an Asterisk flavor).

I'm not sure that I understood the previous (last) reply: write the script and then call it as the last line in ppp-reconnect? Does that work for a DHCP WAN connection too? It's confusing to me that this is the only location (out of 16) that has this problem.

Thanks!