My 2 cents: Focus on the _availability_ of individual services in your
design criteria.
We can expect file transfers and video streams to grab chunks of LAN and
WAN bandwidth. But there is no real benefit from running this traffic
through the 4801.
I suggest you consider this arrangement:
________
| Router |----IP Phone
| |----IP Phone ...
| |----Computer
| |----Computer ...
INTERNET---| |
| | __________
| |---| astlinux |
| | | box |
|________| |__________|
Let each unit do what it does best: The commercial router provides
Firewall, NAT and Layer-2 switching services, while the 4801 handles
call processing, voice mail, and transcoding.
Functional separation will isolate basic LAN/WAN data services from VoIP
service processing.
The router will shield your 4801 from WAN attacks.
And changes such as router replacement/upgrade and/or LAN expansion
(wired or wireless) will not impact your VoIP services.
Of course you will need to enable IAX [easy] and/or SIP/RTP [not so
easy] through the router in order to access VoIP service provider on the
WAN.
But if you find yourself having some trouble with VoIP quality across
the WAN link, you can address that issue at that time. (Often as not
could be issues on the WAN itself.)
If you then find that you really do need to run traffic
shaping/prioritization on your WAN interface, then you can consider how
best to do it. (Perhaps it will be time for a new router, anyway.)
Brian
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
REMEMBER: AstLinux mailing lists are moving soon:
http://sourceforge.net/mail/?group_id=170462
Please move any discussions ASAP!
