<div>Obviously there is errors in the documentation because labbing it up proves otherwise. The following config worked great for me:</div> <div> </div> <div>interface fa0/1</div> <div>switchport trunk encap dot1q</div> <div>switchport mode trunk </div> <div>switchport trunk native vlan 5</div> <div>switchport voice vlan 90</div> <div> </div> <div>Although the voice vlan is not supported on interswitch trunks, it works great when the trunk is to a IP phone on a 3524XL. I did not have to enable trunking on the 3750s so, I have not labbed it up that way on a modern switch. Two people sent me that config on the forum one not including the <EM>switchport mode trunk. </EM>Without that statement on the 3524 the PC port worked but the phone never worked. Thanks Wes.</div> <div> </div> <div>Peter<BR><BR><B><I>Wes Sisk <wsisk@cisco.com></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px
solid">Truth = f(t)<BR><BR>Originally switches required the interface be configured as a trunk. This is the only way the switch would allow tagged packets over the interface. Later on switch code was changed to allow untagged data and tagged voice on a interface this was not defined as a trunk.<BR><BR>So most everyone is right, depending on which version of switch code you are on.<BR><BR>/Wes<BR><BR>Jonathan Charles wrote: <BLOCKQUOTE cite=mid5d093f9a0603310808s5efc2a8awd19d1fd1c80fcbd3@mail.gmail.com type="cite"><PRE wrap="">Wow. This is kind of surprising that so many voip engineers are making this mistake. The voice vlan is NOT supported (and does not work correctly) on ports configured as trunks. For the 3560: <A class=moz-txt-link-freetext href="http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/scg/swvoip.htm">http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/scg/swvoip.htm</A> "Voice VLAN is only
supported on access ports and not on trunk ports, even though the configuration is allowed." For the 3750: <A class=moz-txt-link-freetext href="http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/12225see/scg/swvoip.htm">http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/12225see/scg/swvoip.htm</A> "Voice VLAN is only supported on access ports and not on trunk ports, even though the configuration is allowed." While you may have gotten it to work, it is not consistent... Jonathan On 3/31/06, Rupp Christian <A class=moz-txt-link-rfc2396E href="mailto:Christian.Rupp@etavis.ch"><Christian.Rupp@etavis.ch></A> wrote: </PRE> <BLOCKQUOTE type="cite"><PRE wrap="">Hi Peter! We use this configuration that works: interface FastEthernet0/3 switchport trunk encapsulation dot1q switchport trunk native vlan yy switchport voice vlan xx ! Is the DHCP Server for the voice vlan the same like the PC vlan? Maybe you have to
configure a helper-address? Regards, Christian _______________________________________________ cisco-voip mailing list <A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> <A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A> </PRE></BLOCKQUOTE><PRE wrap=""><!----> _______________________________________________ cisco-voip mailing list <A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> <A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A> </PRE></BLOCKQUOTE>_______________________________________________<BR>cisco-voip mailing list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE><BR><p>
<hr size=1>Blab-away for as little as 1¢/min. Make <a href="http://us.rd.yahoo.com/mail_us/taglines/postman2/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"> PC-to-Phone Calls</a> using Yahoo! Messenger with Voice.