<div><div class="gmail_quote">On Sat, Jul 31, 2010 at 5:39 AM, Gary H <span dir="ltr"><<a href="mailto:ciscovoiper@gmail.com">ciscovoiper@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm using Dual-Mode on user interfaces and I didn't assign a vlan id so it is using the DEFAULT-VLAN. <br><br>I have voice traffic assigned with voice-vlan ##.<br><br>My trunk carries the voice traffic but the data get stuck somewhere. Does the Dual-Mode need to be assigned a vlan id so that it can be a tagged trunk port member because DEFAULT-VLAN no longer has the port available once it gets added to the voice vlan as a tagged port.<br>
</blockquote><div><br></div><div>Yes you should. Are you doing any inter-Vlan routing? Configure some data Vlan and trunk it to the interface and your problem will get resolved.</div><div><br></div><div>Thanks </div><div>
-Sujith</div></div></div>