I've been using multi interface juniper firewalls for a number of years and they are great, very flexible and the support never gives up on you til it's exactly what you want. Using pfsense for voip traffic allows me to leave the juniper to easily handle the rest without getting overly complicated. When I tried putting everything on one device, it was hell to pay. Splitting things up made the most sense in the long run.
On Tue, 13 Jul 2010 10:03:29 -0400, Michael Scheidell wrote: > something that doesn't interfere with sip traffic? can and will do QOS on > VOIP. > > pfsense seems to be 'ok' but as an open source package commercial support > is limited. > (and setting up 200 workstations, two DMZ's and 40 servers with 5 services > each is painful. seems like you need to make 40*2*5 entries in the > nat/portforward tables if you want 1 to one natting and support for an > average of 5 inbound and outbound services on each server, which all HAVE > to have its own public ip) > > > So: Commercial firewall, handle 10mb with 100mb bursts, at least three > interfaces. > > not specifically looking for something that is 'easy', just makes sense > from a ongoing support/moves and changes issue. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
