<div><font size=2 color=navy face=Arial>
Not the answer, just a rant...<br><br>OCS 2007 R2 and earlier are unable to mark at the client. OCS 2010, aka Wave 14 will do this naively AFAIK but they may make the SIP signaling CS4 rather than CS3, RTAudio will be EF. So all that "you don't need QoS" statements from MSFT sales people will change as soon as that is released. Just like they call their implementation of QoS healing QoE. <br><br> </font></div>
<br><div><hr size=2 width="100%" align=center tabindex=-1>
<font face=Tahoma size=2>
<b>From</b>: cisco-voip-bounces@puck.nether.net <cisco-voip-bounces@puck.nether.net>
<br><b>To</b>: cisco-voip@puck.nether.net <cisco-voip@puck.nether.net>
<br><b>Sent</b>: Sun Apr 04 08:16:34 2010<br><b>Subject</b>: [cisco-voip] QoS and Microsoft OCS
<br></font><br></div>
<div>Just wondering if anyone has experience setting up QoS on a network in order to accomodate OCS? I would like to ensure that the OCS packets are tagged and prioritized according to the organization's QoS policy and wondering what ports, etc... I should look for in order to identify OCS traffic.</div>
<div> </div>
<div>Thanks!!</div>
<div>Gary</div>