On 26/09/2014 11:58, Chris Bagnall 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.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.
The bug itself seems to be a genuine problem, the way the bug is put forward doesn't do much for motivating its resolution.
-- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7584 634135 http://www.netsecspec.co.uk [email protected] -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7584 634135 http://www.coochey.net http://www.netsecspec.co.uk [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
