I'm sure more people are with dynamic WAN IPs and facing this problem. The issue #1629 is showing this clearly. If at least there would be a report saying "we are not going to fix it" than all of those could decide to use or not to use pfsense.
On Fri, Sep 26, 2014 at 12:58 PM, Chris Bagnall <[email protected]> wrote: > On 26/9/14 11:43 am, Hannes Werner wrote: >> >> I wonder what the reason for not getting >> https://redmine.pfsense.org/issues/1629 fixed? >> Many gave up waiting for this, but it seems there must be a proper >> reason for it. May I ask what the problem is not being able to use >> pfSense with Asterisk? > > > Worth mentioning here that many of us are using Asterisk behind pfSense > without any issue at all. > > The triggers for this issue seem to be, specifically: > - PPPoE WAN interface > - dynamic WAN IP > - SIP service provider > > We (one of my $dayjobs is a VoIP service provider) have dozens of clients > using Asterisk with PPPoE WAN without any problem, but they're all using > static WAN IPs provided by the ISP(s) in question. > > Kind regards, > > Chris > -- > This email is made from 100% recycled electrons > _______________________________________________ > List mailing list > [email protected] > https://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
