On 5/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Jeff,
Assuming you are talking about T1 to internet and want to carry VoIP
in the tunnel, be careful. The main problem is that you must be able
to establish some kind of QOS through that tunnel. I am not sure
that you can prioritize traffic in the tunnel. If you can prioritize
prior to encryption, this could work out. You might have to add
another layer. The other folks on this list can help you with that.
As far as hardware requirements, for a T1, the needs are rather low
as indicated in previous postings. BTW, data is not data. jitter,
latency, echo and delay are significant factors for VoIP. For this
reason, you will want to make sure that encryption/decryption takes
place very fast. AES is a nice efficient method but I have not seen
that on pfSense yet. 3DES may be fine as long as you are not under
powered. I have done little testing in this area.
Park
On May 15, 2006, at 12:34 PM, Jeff Quinonez wrote:
> This is interesting, I'm about to pitch a pfSense solution to my
> boss for a new remote office. It will be a site to site VPN (T1)
> with VoIP traffic, possible 50 employees. He's a name brand kinda
> guy so he's thrown out Sonicwall and Cisco, I'm not a big fan of
> the PIX nor the cost that comes with it. Can someone recomend what
> kind of hardware I should purchase for this? RAM, CPU etc? Of
> course we'll have to see what our Nortel rep says about the VoIP,
> but hey data is data.
>
> Cheers.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
You're right, thanks for the info.
