Rich Adamson wrote:
The only issue I see with that approach is that customers tend to buy
crap for firewalls without any knowledge/experience relative to nat
timeouts, etc. We've seen some that never timeout the nat entries (unless
the nat table becomes full), and others with very short duration timeouts.
Using the server-based qualify assumes you either know the nat table
timeout value, or, one must pick a very short duration qualify generating
wasteful traffic.
Wouldn't the same be true of the registration interval though? If you
need the NAT mapping to stay in effect, _something_ is going to have to
generate two-way traffic before it expires... I don't see how it matters
whether that is a registration or a qualify.
_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
