<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=windows-1250">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body link=blue vlink=purple>
<div class=Section1>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>The only reason to route the voice
VLAN is if you need the phones to access the Internet and/or vice-versa. If you
only need to worry about the computers on the data VLAN accessing Trixbox's web
interface, I would suggest using the Ethernet VLAN capabilities of Linux. You
can create eth0.vlan1 for data on Trixbox, and have the "default"
vlan for the port on the switch be voice. Then, the voice VLAN goes nowhere but
to your PBX and the phones.<br>
<br>
The other option is to put in another NIC, one for the voice VLAN, the other
for the data VLAN. <br>
<br>
I've been pretty happy with the Linksys 24-port layer 2 switches (SRW224P).
They're running around $400 right now. If you really need layer3 support, I
would steer clear of the Netgear. I've had a lot of problems with them, and the
support was disappointing. But then again, I got a bunch that don't work that I
could sell you ;) </p>
</div>
<p class=MsoNormal> </p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'> </p>
<p><span style='color:#1F497D'>Ahh, interesting idea…if I understood
correctly, you’re basically using a layer 2 switch and trunking the voice
and data VLAN to the asterisk box and doing the routing and ACL work
there? Advantage is lower cost because you don’t need a layer 3
switch anymore and don’t have to learn a new CLI or other config method.?</span></p>
<p><span style='color:#1F497D'>Here’s a bit more information…the
client is a building owner who occupies the first floor and is renting out the
rest of the building. In addition to his own voice/data network (which
would be on separate VLANs) they want to offer the building tenants the ability
to use their PBX and internet connection. Due to a quirk in the service
providers SIP ALG all IP phones in the building must be on the same
network (VLAN) which I don’t see a problem with, but each tenant’s
data will be in a separate VLAN. I’m thinking I could trunk the
voice VLAN and all of the individual tenant data VLANs to the Trixbox to allow
them access to the web interface?</span></p>
<p><span style='color:#1F497D'>Any other ideas out there based on this scenario?</span></p>
<p><span style='color:#1F497D'> </span></p>
<p><span style='color:#1F497D'>Thanks again</span></p>
</div>
</body>
</html>
<BR>
<P><FONT size=2>No virus found in this outgoing message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.5.476 / Virus Database: 269.9.9/870 - Release Date: 6/26/2007 10:07 AM<BR>
</FONT> </P>