[cisco-voip] QoS and Microsoft OCS

[Kin Wai]

You will need to manually enable the tagging on the client/server OS. 

 

It’s somewhere in group policy under network, tried once long time ago on a WIN XP desktop and it does works. After that, it’s up to the customer to apply the policy on the whole domain. 

 

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Aaron Kent (aakent)
Sent: Sunday, April 04, 2010 8:36 PM
To: gary905775 at gmail.com; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] QoS and Microsoft OCS

 

Not the answer, just a rant...

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. 

 

  _____  

From: cisco-voip-bounces at puck.nether.net <cisco-voip-bounces at puck.nether.net> 
To: cisco-voip at puck.nether.net <cisco-voip at puck.nether.net> 
Sent: Sun Apr 04 08:16:34 2010
Subject: [cisco-voip] QoS and Microsoft OCS 

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.

 

Thanks!!

Gary

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100404/a97692c5/attachment.html>