<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2050303069;
mso-list-type:hybrid;
mso-list-template-ids:-1044889054 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple>
<br>
<div class=WordSection1><p style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>can my 10 pilot lync moc clients do p2p or p2m desktop video sessions with rt audio and rt video codecs with out going via ccm cluster or with out the help of ccm at all.<o:p></o:p></p><p><span style='color:#0070C0'>Yes, between themselves but not between a Cisco endpoint and a MOC endpoint.<o:p></o:p></span></p><p style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>just like ccm's sccp end points which will have a dn # , should my lync moc clients too need to have dn # or lync moc can audio & video call each other via their sip addresses or user names ?<o:p></o:p></p><p><span style='color:#0070C0'>You will configure each user for ‘Enterprise Voice’ and assign a tel URI which is their telephone number. Normally, this is an E164 number (i.e. tel:+12125551212)<o:p></o:p></span></p><p>3.from qos perspective , what tcp & udp ports should i have to mark and classify for rt audio or rt video signalling and payloads ? from my very limited understanding on lync so far , moc clients when they talk to lync server via sip , they do open up peer to peer sort of 1024 to 65534 sort of huge port range. which i gather , can we locked in to smaller range via in-band signalling. so as you can see here , i am totally confused on best possible qos templates to protect and give some sort of priority (perhaps IP Prec 2 or AF21) lync desktop video p2p and p2p sessions. <o:p></o:p></p><p><span style='color:#0070C0'>Out of the box, Lync clients use 1024-65535 for audio or video. This can be adjusted, search around technet for QoS settings. <o:p></o:p></span></p><p><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>i do gather that , lync do offer cac , similar to ccm. if that is the case , how much bw shall i have to configure for 2 x desktop video sessions ?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#0070C0'>2 desktop video sessions at CIF will be around 512kbps. You also need to factor in audio though, don’t think your 512k pipe will handle this well.<o:p></o:p></span></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>5. lastly , i was just checking nbar class maps on my is router and i spotted match protocol rtp audio and rtp video and rtp payload , but nbar match options does not offer rt audio or rt video to cover microsoft lync protocol matching. so , i am just wondering , are they both same or not. if they are not same , then perhaps , the bets i could do it is match tcp and udp port ranges of rt audio and rt video traffic streams.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='color:#0070C0'>Your best bet is to configure Lync to use different port ranges for audio and video and classify and mark on the edge switches.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Tony Edwards<br><b>Sent:</b> Tuesday, May 10, 2011 6:17 AM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> [cisco-voip] lync moc desktop p2p & p2m video calls , conferencing<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p>hi guys,<o:p></o:p></p><p>can some one please guide me on the below queries?<o:p></o:p></p><p>i am planning to run a pilot with a lync2010 server with 10 odd lync moc clients on 10 user windows7 computers with an aim to <br>turn on a desktop video p2p and p2m ( conference) streams both with in lan environment as well as between 2 x wan site , separated by a 512k frame relay pipe.<o:p></o:p></p><p>in isolation i do have a ccm running with 10 sites with 100 sccp end points and lync platform will be totally separate to begin with while i trial desktop to desktop video.<o:p></o:p></p><p>so that being the aim , i am not sure on how to address following 4 aspects.<o:p></o:p></p><p>1. can my 10 pilot lync moc clients do p2p or p2m desktop video sessions with rt audio and rt video codecs with out going via ccm cluster or with out the help of ccm at all.<o:p></o:p></p><p>2. just like ccm's sccp end points which will have a dn # , should my lync moc clients too need to have dn # or lync moc can audio & video call each other via their sip addresses or user names ?<o:p></o:p></p><p>3.from qos perspective , what tcp & udp ports should i have to mark and classify for rt audio or rt video signalling and payloads ? from my very limited understanding on lync so far , moc clients when they talk to lync server via sip , they do open up peer to peer sort of 1024 to 65534 sort of huge port range. which i gather , can we locked in to smaller range via in-band signalling. so as you can see here , i am totally confused on best possible qos templates to protect and give some sort of priority (perhaps IP Prec 2 or AF21) lync desktop video p2p and p2p sessions. <o:p></o:p></p><div><p class=MsoNormal>4. i do gather that , lync do offer cac , similar to ccm. if that is the case , how much bw shall i have to configure for 2 x desktop video sessions ?<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>5. lastly , i was just checking nbar class maps on my is router and i spotted match protocol rtp audio and rtp video and rtp payload , but nbar match options does not offer rt audio or rt video to cover microsoft lync protocol matching. so , i am just wondering , are they both same or not. if they are not same , then perhaps , the bets i could do it is match tcp and udp port ranges of rt audio and rt video traffic streams.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>thank you a lot.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>tony<o:p></o:p></p></div></div>
<BR>
<BR>
<table border=0 cellspacing=0 cellpadding=0><tr><td><A href="www.dimensiondata.com"><IMG border="0" style="border:0;" alt="dimension data" src="cid:111051114365201701@service106.mimecast.com" ></A></td></tr></table>
<br>
<P></P><hr size=1></P>
<P><STRONG><font size="2"><font color="#808080">
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</P></STRONG>
<font color=white>itevomcid</font>
</body></html>