Re: VoIP and Access vs. Trunk for PC+Phone Clients...

Never mind, someone pointed me to the voice VLAN section of switch config
guide to give me required answers. I had always thought voice VLAN was for
QoS primarily. I am relieved!

So easy an MCSE can do it. :-) LOL

On 6/7/10 9:48 PM, "John Lockie" <john.lockie_at_gmail.com> wrote:

> This question is for those of you studying for your voice, or who already
have
> your voice certification(s)...
>
> What is the standard practice with regards to switch interfaces when
> connecting PC to phone, and then phone to switch (phone is basically a
> switch)?
>
> You have 2 separate VLANs so is the switchport trunked? Or is there some
> method with voice VLAN to treat the interface more like an access interface
> (thus avoiding a plethora of trunk ports and spanning-tree ports, etc.)....
>
> I am working on a small multi-tenant voice job, non-Cisco phone, but Cisco
> 29609s at L2. Currently, I just trunk each interface, but this is not
ideal.
> I know NOTHING about voice VLAN. This network is ~25 clients, and we don9t
> have the luxury of dual ports for each office space (this is a mobile
office
> site).
>
> I have experience with Procurve, and it seems their implementation of dot1q
is
> actually better in this regard. =O
>
> Thanks,
> John

Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 07 2010 - 23:17:41 ART