Right, but since CoS only exists on the dot1q trunk frame, how could the PC even set any CoS value?
Jonathan On Wed, Jul 23, 2008 at 2:57 PM, Devildoc <[EMAIL PROTECTED]> wrote: > Your definition is reversed. The command "switchport priority extend cos 0" > does NOT allow the IP phone to reset the COS value received from the PC. > It's the opposite of that. That command is FOR the switch to reset the COS > value received from ANY device connected on the IP phone to a COS value of > 0. > > JD > >> Date: Wed, 23 Jul 2008 10:51:21 -0400 >> From: [EMAIL PROTECTED] >> To: ccie_voice@onlinestudylist.com >> Subject: [OSL | CCIE_Voice] Phone CoS Settings ? >> >> Hi Everyone, >> >> I see that the standard practice on a switchport is to configure >> "switchport priority extend cos 0" in order to allow the ip phone to >> reset the cos value received from the PC to 0. >> >> My question is how would a PC ever set a "CoS" value if the link >> between the ip phone and the PC is not an 802.1q trunk ? >> >> Can someone please help me understand this ? The only thing I can >> think of is that the PC would somehow have to support an 802.1q trunk >> to it, a trunk would have to be dynamically established between the >> phone and PC. And, then the user would have to manipulate the CoS >> value. Is this possible with a Cisco phone ? >> >> If this is the only case this would work then you would think that >> Cisco would document these pre-requisites. Perhaps I am confused. >> >> Please help ;-) >> >> Regards, >> >> Mike Brooks >> CCIE#16027 (R&S) > > > ________________________________ > Stay in touch when you're away with Windows Live Messenger. IM anytime > you're online.
