First off, let me point out that I am a user, not a developer. Secondly
you may want to tone down the attitude. Since many of the developers
volunteer, they won't bother taking on a bug that is a) limited in scope
b) having someone pester them about. that being said, the bug is NOT
exclusive to pfsense. While pfsense may be able to implement some
workarounds, this is ultimately an asterisks issue. You may have more
luck asking the asterisks community to fix it.
Yes, it works on some routers, but from what I was able to find the bug
is very narrow in scope, such as what someone already replied :
The triggers for this issue seem to be, specifically:
- PPPoE WAN interface
- dynamic WAN IP
- SIP service provider
Not having a PPoE WAN would fix this too. As for the idea of asterisks
on a dynamic address; the idea of having many services hosted on a
dynamic address is generally discouraged because of the extra complexity
and lack of reliability that comes with it. This is not specifically
about asterisks.
Now, back to the bug. From what I have read, this seems to be an issue
with the states table, which probably means that the WAN address is
changing and the states are not being update. I'm not sure why your ISP
would be changing your IP all the time. Most simply give you one when
you connect and you keep it until you are no longer connected. Without
knowing the exact problem, it would probably involve clearing the state
table every time the address changes and that may have other considerations.
On 9/26/2014 7:42 AM, Hannes Werner wrote:
are you saying that people with dynamic IP shouldn't use pfSense
behind an Asterisk service? I've had asterisk running behind Fritz-Box
for years without any trouble. I've seen the cheapest router being
able to handle this like the speedports. I can't believe pfSense is
unable to do this, but it doesn't matter a clear word would solve the
problem for all the time and you do not have to worry again about this
issue.
maybe you guys do better telling those users to change there router?
On Fri, Sep 26, 2014 at 1:33 PM, Chris Bagnall
<pfse...@lists.minotaur.cc> wrote:
On 26/9/14 12:06 pm, Giles Coochey wrote:
I can think of many reasons, why running a service such as Asterisk, on
an IP address that you have a temporary lease for (thus only have a
passing relationship with, before it is passed to someone else), would
be pretty bad practice.
I think Giles has put it far better than I did :-)
In short, Asterisk is temperamental with dynamic IPs _in general_, it's not
necessarily specific to pfSense (though I appreciate this bug report relates
specifically to pfSense).
I've seen the same symptoms with Asterisk servers behind Draytek routers,
for example - as with pfSense, it's usually solved with a state table reset.
Kind regards,
Chris
--
This email is made from 100% recycled electrons
_______________________________________________
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
