lync server networking guide v2.1

5/26/2018 Lync Server Networking Guide v2.1

1/133

Lync Server Networking Guide

Networking GuideNetwork Planning, Monitoring, and Troubleshooting with

Lync Server

Update Published:January 2014

Updated queries

Included a KHI spreadsheet for Lync 2013

Update uthors:Brandon Bernier, Kent il!er, "ndre# $nider%an and Jens rier &as%ussen

!riginally Published:'ay 2013

uthors:Ji!ar (ani, )rai! Hill, Jac* +i!ht, +ei hon!

"ontributors:Brandon Bernier, &o-ert Burnett, Jason )ollier, .aul )ulli%ore, (aniel Hernande/,

Ja%es Horn-y, (ae Jennin!s, Jonathan Le#is, Jens rier &as%ussen, Juha $aarinen, 'arc

$anders, Joel $is*o, ic* $%ith, "ndre# $nider%an, Ja%ie $tar*, "aron $teele, )onnie +elsh,

Kent il!er

#ditor:&andall (uBois

bstract:'icrosoft Lync $erer 2013 co%%unications soft#are is a realti%e unified

co%%unications application that ena-les peertopeer audio and ideo "56 callin!,

conferencin!, and colla-oration and relies on an opti%i/ed, relia-le net#or* infrastructure to

delier hi!hquality %edia sessions -et#een clients7 his !uide proides a %odel for %ana!in!

the net#or* infrastructure for Lync $erer 2013, consistin! of three phases8plannin!,%onitorin!, and trou-leshootin!7 hese phases can apply to ne# Lync $erer deploy%ents or to

e9istin! deploy%ents7 In ne# Lync $erer deploy%ents, your or!ani/ation %ust -e!in fro% the

plannin! phase7 In e9istin! deploy%ents, your or!ani/ation can start at the plannin! phase for

%a:or up!rades or for inte!ratin! ne# sites into the Lync $erer ecosyste%7 ;r!ani/ations #ith

e9istin! deploy%ents can also -e!in fro% the %onitorin! or trou-leshootin! phases, if you are

tryin! to achiee a healthy state7


2/133


his docu%ent is proided


3/133


"ontents

3


4/133


$% &ntroduction'icrosoft Lync $erer 2013 co%%unications soft#are is a realti%e unified co%%unications application

that ena-les peertopeer audio and ideo "56 callin!, conferencin!, and colla-oration and relies on an

opti%i/ed, relia-le net#or* infrastructure to delier hi!hquality %edia sessions -et#een clients7

his paper proides a %odel for %ana!in! the net#or* infrastructure for Lync $erer 2013, consistin! of

three phases@

.lannin!

'onitorin!

rou-leshootin!

hese phases can apply to ne# Lync $erer deploy%ents or to e9istin! deploy%ents7 In ne# Lync $erer

deploy%ents, your or!ani/ation %ust -e!in fro% theplanningphase7 In e9istin! deploy%ents, your

or!ani/ation can start at theplanningphase for %a:or up!rades or for inte!ratin! ne# sites into the Lync

2013 ecosyste%7 ;r!ani/ations #ith e9istin! deploy%ents can also -e!in fro% the monitoringor

troubleshootingphases, if you are tryin! to achiee a healthy state7

$%$ Support Materials

In addition to this +ord docu%ent, the 7/ip file you do#nloaded also contains the support files referred to

#ithin this docu%ent, includin! te9t files #ith the sa%ple queries, a spreadsheet #ith KHI infor%ation that

is referred to in section )727171 "ssert Auality, and a +indo#s .o#er$hell script

)reateKHI)ollection7ps16 to collect .erf'on infor%ation7

The 'ollowing 'iles are included in the %(ip 'ile:

Lync$ereret#or*in!Cuide27doc9 this docu%ent6

)*&s

Lync $erer 2010

)reateKHI)ollection7ps1

Lync$erer2010KeyHealthIndicators79ls9

Lync $erer 2013

)reateKHI)ollection7ps1

Lync$erer2013KeyHealthIndicators79ls9

+ueries

&D"('D 137t9t

Lync -$-

Dndpoint0(eice2010 117t9t

Dndpoint1syste%2010 117t9t

Dndpoint2&elay2010 117t9t

Dndpoint25.2010 117t9t

Dndpoint3ransport2010 117t9t

Last'ile0+ired2010 117t9t

4


5/133


Last'ile1+ireless2010 117t9t

.lant1"5')U'ediation2010 107t9t

.lant2'ediationCate#ay2010 137t9t

rend1"5')U'ediation2010 107t9t

rend2'ediationCate#ay2010 137t9t

rend3+ired2010 117t9t

rend4+ired.2.2010 107t9t

rendE;ther+ired2010 127t9t

rendF;ther+ireless2010 107t9t

rendG5.2010 117t9t

rendD9ternal2010 107t9t

rend+ireless2010 117t9t

rend10+ireless.2.2010 107t9t

rend11otal2010 107t9t

Lync -$.

Dndpoint0(eice 117t9t

Dndpoint1syste% 117t9t

Dndpoint2&elay 117t9t

Dndpoint25. 117t9t

Dndpoint3ransport 117t9t

Last'ile0+ired 117t9t

Last'ile1+ireless 117t9t

.lant1"5')U'ediation 107t9t

.lant2'ediationCate#ay 137t9t

rend1"5')U'ediation 107t9t

rend2'ediationCate#ay 137t9t

rend3+ired 117t9t

rend4+ired.2. 107t9t

rendE;ther+ired 127t9t

rendF;ther+ireless 107t9t

rendG5. 117t9t

rendD9ternal 107t9t

rend+ireless 117t9t

rend10+ireless.2. 107t9t

rend11otal 107t9t

E


6/133


$% Phase !verview

(urin! theplanningphase, your or!ani/ation %ust deter%ine the require%ents of deploy%ent either for

the entire or!ani/ation, or for specific sites #hen they are added7 his !uide assu%es that little or no Lync

$erer infrastructure e9ists to !enerate the data for pro:ections and for health and capacity assess%ents7

herefore, this phase !enerally inoles %odelin! the user require%ents and usin! tools to assess

capacity and health7 or e9a%ple, your or!ani/ation %ay decide that a site requires a certain a%ount of

-and#idth for Lync $erer oice and ideo traffic7 >ou %ay then choose to use Auality of $erice Ao$6data to help ensure adequate priority for this traffic7

(urin! the monitoringphase, your or!ani/ation %aintains the health of the deploy%ent, uses e9istin!

Lync $erer tele%etry #here possi-le, and fills the !aps -y usin! thirdparty tools7 he process inoles

identifyin! the ele%ents that need %onitorin!, and creatin! action plans for reactin! to alerts -ased on

*ey health indicators KHIs6 and net#or* quality ie#s7 If you find issues, the or!ani/ation enters the

troubleshootingphase7 ollo#in! the earlier e9a%ple fro% the plannin! phase, your or!ani/ation %ay

decide to use Lync $erer Auality of D9perience AoD6 data to help ensure that a sites net#or* health is

#ithin desi!nated tar!ets7 >ou %ay also decide to use thirdparty net#or* %ana!e%ent tools to help

ensure that Ao$ settin!s are continuously confi!ured to specification7

(urin! the troubleshootingphase, your or!ani/ation deter%ines the root causes of any issues arisin!

fro% %onitored entities or fro% enduser support escalations7 If appropriate %onitorin! solutions are inplace, your trou-leshootin! efforts #ill -e si!nificantly reduced7 )ontinuin! #ith the earlier e9a%ple, if

%ost of the core Lync $erer and net#or* infrastructure is correctly proisioned and %onitored, you can

start trou-leshootin! at the point closest to #here the issue is occurrin!, rather than fro% the core

infrastructure7 or e9a%ple, if a user co%plains a-out a poor audio e9perience, the trou-leshootin! #ill

start fro% the users endpoint7

"s these scenarios sho#, the plannin!, %onitorin!, and trou-leshootin! phases are strate!ies to deal #ith

the sa%e set of issues -y usin! the tools and data aaila-le at each respectie phase7 he infor%ation

contained in this !uide #ill apply to an or!ani/ation in any phase or scope of a Lync $erer deploy%ent7

inally, this !uide descri-es the pri%ary concept of -rea*in! do#n the Lync $erer deploy%ent and

net#or* infrastructure into managedand unmanagedspaces7 he %ana!ed space includes your entire

inside #ired net#or* and serer infrastructure7 he un%ana!ed space is the #ireless infrastructure andthe outside net#or* infrastructure7 (iidin! the deploy%ent and infrastructure into these t#o spaces

si!nificantly increases the clarity of your data and helps your or!ani/ation focus on #or*loads that #ill

hae a %easura-le i%pact on your users oice and ideo quality7 his is -ecause your users hae a

different e9pectation of quality if the call is placed on infrastructure that you o#n %ana!ed6 ersus

infrastructure that is partly under the control of so%e other entity un%ana!ed67 his is not to say that

#ireless users are left to their o#n deices to hae e9cellent Lync $erer e9periences7 "s #ith the

dependency -et#een the plannin!, %onitorin!, and trou-leshootin! phases, i%proin! oice quality in the

un%ana!ed space requires you to hae hi!h quality in the %ana!ed space7 +hether #ireless +ii6 is

considered %ana!ed or un%ana!ed space is up to your or!ani/ation7 he techniques to achiee a

healthy eniron%ent are different in the t#o spaces, as are the solutions7 his paper includes e9a%ples of

%ana!in! un%ana!ed call quality7

he follo#in! ta-le sho#s e9a%ples of Lync $erer call scenarios and their classification into the

%ana!ed and un%ana!ed spaces7

Lync Server "all Scenarios in Managed and Un/anaged Spaces

Scenario "lassi'ication

User calls fro% a hotel +ii connection Un%ana!ed

F


7/133


#o users call each other fro% their #ired des*top .)s inside the corporate fire#all 'ana!ed

User %a*es a .$ call fro% his #ired des*top .) inside the corporate fire#all 'ana!ed

User :oins a conference fro% her #ired des*top .) inside the corporate fire#all 'ana!ed

User on +ii calls another user Un%ana!ed

User fro% ho%e :oins a conference Un%ana!ed

G


8/133


% PlanningIn e9plorin! topics related to net#or* plannin!, t#o pri%ary questions #ill -e addressed@

Ho# does Lync $erer affect %y net#or*

Ho# does %y net#or* affect Lync $erer

he !oal of this net#or*in! !uide is not to teach you to -eco%e a Lync $erer e9pert, nor to teach you

ho# to -eco%e a net#or*in! e9pert7 &ather, this !uide descri-es areas related to enterprise data

net#or*in! that you should consider durin! the predeploy%ent plannin! phase of your Lync $erer

adoption7

"s a *ey area in any net#or*in! plannin! actiity related to -and#idth plannin!, #e inesti!ate the

e9ploratory questions that you should -e as*in! your or!ani/ation in order to %odel user -ehaior7 +e

also direct you to the pu-lic -and#idth calculator as a tool aaila-le for use, and to the default usa!e

%odels, defined in the -and#idth calculator, as startin! points7

In addition, #e descri-e ho# your e9istin! eniron%ent can affect the -ehaior of Lync $erer7 or

e9a%ple, topolo!y choices, %ultiple 'ultiprotocol La-el $#itchin! '.L$6 suppliers, or infrastructure

such as +" opti%i/ation deices, particularly if oerloo*ed durin! the plannin! process, can -eco%e

real challen!es as your deploy%ent eoles7

+e also discuss ho# to %a*e use of the 'icrosoft .artner )o%%unity in order to delier the Lync $erer

et#or* &eadiness assess%ent %ethodolo!y in your eniron%ent7 his %ethodolo!y quantitatiely

assesses your or!ani/ations a-ility to use Lync $erer -y #al*in! you throu!h the net#or* discoery,

usa!e %odelin!, traffic si%ulation, and analysis phases, durin! your en!a!e%ent7

et#or* plannin! for Lync $erer consists of the follo#in! areas@

et#or* assess%ent %ethodolo!y

o et#or* discoery

o 'odelin!personas

o Band#idth esti%ation

o raffic si%ulation

)all "d%ission )ontrol )")6

Auality of D9perience AoD6

Auality of $erice Ao$6

et#or* port usa!e

+ii scenarios

;perations

'iscellaneous plannin! questions

+e hi!hly reco%%end a net#or* assess%ent as a first step -efore deployin! Lync $erer7 " net#or*assess%ent proides you #ith insi!ht into the readiness of your net#or* infrastructure for supportin! an

e9cellent user e9perience, #hile usin! Lync $erer for realti%e co%%unications7 ;ur custo%ers often

as*, MIs %y net#or* infrastructure ready to support Lync $erer= ;ur approach helps to ans#er this

critical predeploy%ent question7 he net#or* assess%ent uses a proen %ethodolo!y to@

0iscoveryour eniron%ent7

Modelyour usa!e patterns and usa!e scenarios -y usin! infor%ation collected durin! discoery, #ith thehelp of the Lync Band#idth )alculator7


9/133


Si/ulatethe anticipated Lync $erer traffic olu%es -y usin! real %edia strea%s for a full seen days7

naly(ethe underlyin! net#or* infrastructure perfor%ance characteristics to deter%ine your readiness indeployin! Lync $erer7

he outco%e of the net#or* assess%ent ans#ers the question, ou %ay find that your +" lin* oerall usa!e is satisfactory, -ut that your fi9edsi/e priority

queue doesnt hae enou!h additional capacity to acco%%odate the additional proposed Lync $erer

traffic olu%es7 >ou should also collect the follo#in! %onitorin! data for analysis@

Band#idth usa!e oer the past three %onths

o "era!e -usy hour traffic

o .ea* -and#idth usa!e

et#or* issues oer the past 12 %onths

2.1.2 Network Impairments

he follo#in! topics descri-e different net#or* conditions that can affect Lync $erer traffic7

%$%%$ 1N !pti/i(ers

+" opti%i/ers orpacket shapers6 are typically used for %iti!atin! issues caused -y hi!h delays or lo#net#or* -and#idth7

+" opti%i/ation is a ter% !enerally used for deices that e%ploy different techniques to enhance data

transfer efficiency across +"s7 raditionally used opti%i/ation %ethods include cachin!, co%pression,

protocol su-stitution, different for%s of -and#idth throttlin!, and for#ard error correction D)67

Its critical for Lync $erer %edia traffic that all +" opti%i/ers are -ypassed, and that any outside

atte%pt to control Lync $erer %edia traffic is disa-led7 Its also i%portant to note that #ee seen +"


10/133


opti%i/ation deices #ith outdated fir%#aresoft#are cause pac*et loss in onedirection traffic, due to

hi!h ).U usa!e7

+hen esta-lishin! a %edia session, Lync $erer uses $ession (escription .rotocol $(.6 for settin! up

the initial codec -et#een endpoints7 (urin! the %edia session -et#een endpoints, realti%e transport

protocol &.6 is used for transferrin! the %edia strea%, and realti%e transport control protocol &).6

is used for controllin! %edia flo#7 he &). %onitors &. traffic7 his infor%ation is used, a%on! other

thin!s, to ne!otiate possi-le codec chan!es durin! the session7

Lync $erer includes a -and#idth %ana!e%ent %echanis%8call ad%ission control )")68that

deter%ines #hether to ena-le audioideo sessions, -ased on aaila-le net#or* capacity7 )") is a-le to

reroute call flo#s -y usin! the Internet or the .u-lic $#itched elephone et#or* .$6, if aaila-le7

In addition, +" opti%i/ers can cause net#or* delays -y inspectin!, queuin!, and -ufferin! pac*ets at

net#or* in!ress points7

%$%% 2irtual Private Network 32PN4

5irtual priate net#or*s 5.s6, specifically, splittunnel 5.s, are co%%only used for securin! e9ternal

connections #hen users are outside the corporate net#or*7 5.s technically e9tend an or!ani/ations

priate net#or* -y transferrin! encrypted traffic #ith tunnelin! protocols7

+hen users initiate a 5. connection, the traffic is sent throu!h the 5. tunnel7 his additional tunnelin!

layer affects Lync $erer traffic -y increasin! net#or* latency and :itter7 Dncryptin! and decryptin! Lync

$erer traffic can potentially de!rade a 5. concentrator, and can also affect the user e9perience7

"ll Lync $erer traffic is encrypted7 $I. si!nalin! uses ransport Layer $ecurity L$6 for clientserer

connections and all %edia traffic is encrypted -y usin! secure realti%e transfer protocol $&.67 Lync

traffic does not need an e9tra encryption layer throu!h a 5. tunnel, unless there is a specific need for

duallayer security7

Lync $erer uses the Interactie )onnectiity Dsta-lish%ent I)D6 protocol to proide different %edia

paths -et#een Lync $erer endpoints and serers7 Because an endpointinitiated %edia session is not

a#are of the receiin! endpoints location, I)D protocol helps -y proidin! a list of candidates -ased on

I. addresses and %edia ports and atte%ptin! to create %edia sessions -et#een the%7 here is a specific

candidate order, as follo#s, in #hich an I)D protocol tries to alidate the %edia path7 If a connection is

alidated, I)D protocol stops chec*in!, and the %edia session is opened@

17 User (ata!ra% .rotocol U(.6 local or host I. address7

27 U(. net#or* address translation "6 pu-lic I. address7

37 U(. relay throu!h pu-lic I. of Lync audioisual "56 Dd!e7

47 ransport )ontrol .rotocol ).6 relay throu!h pu-lic I. of Lync "5 Dd!e, if U(. is not

aaila-le7

)onsider the scenario #here -oth Lync users are located outside the corporate net#or*7 hey each hae

their o#n indiidual 5. tunnels, and so Lync $erer %edia traffic is affected t#ice -y the 5. oerhead7

10


11/133


Client VPN Solut ion

Client VPN Solut ion

External Firewall

User B

User A

Edge Server Pool

Internal Lync

Servers

Lync Users #5ternal to "orporate Network and 2PN !verhead

he solution is to use a splittunnel 5. #ith Lync $erer7 In a splittunnel 5. confi!uration, all I.

addresses that are used -y the Lync $erer eniron%ent are e9cluded, so that traffic to and fro% those

addresses is not included in the 5. tunnel7 >ou should also chec* the confi!uration for your 5.

solution a!ainst endor docu%entation7

%$%%. 6irewall Policies

Lync $erer uses a ariety of #or*loads8presence, instant %essa!in!, audio, ideo, application sharin!,

#e- conferencin!, and persistent chat7 hese #or*loads use %ultiple protocols $I., $(., $&., $&.),

.ersistent $hared ;-:ect 'odel .$;'6, I)D, and H.$67 'odern corporate net#or*s are e9tensiely

secured and se!%ented -y usin! fire#alls7 o %ini%i/e the i%pact of fire#alls on Lync $erer traffic,

%a*e sure that the perfor%ance of your deices and the protocol support of your f ir%#are and soft#are

are at the required leels7

Handlin! fire#all confi!uration for Lync $erer can -e challen!in!, and %isconfi!uration can cause issues

#ith Lync $erer traffic flo#s7 >ou can %ini%i/e this ris* -y properly plannin! port confi!uration and -y

docu%entin! it in detail7 or seeral useful tools that can help #ith f ire#all confi!uration, see M(eter%ineD9ternal "5 ire#all and .ort &equire%entsM at http@!o7%icrosoft7co%f#lin*pLin*IdN23F7

%$%%7 Sy//etric versus sy//etric Links

In a sy%%etric lin*, net#or* traffic is trans%itted out-ound and in-ound #ith an equal -and#idth rate7

)onersely, an asy%%etric lin* uses different -and#idth rates upstrea% and do#nstrea%7 he %ost

co%%on scenario for an asy%%etric di!ital su-scri-er line "($L6 is a hi!her -and#idth in-ound as

co%pared to out-ound7

"($L connections are not suita-le for a corporate net#or*, particularly #hen realti%e applications are

used7 If an "($L connection is the only option, re%e%-er that asy%%etric lin*s force Lync $erer

endpoints to use lo#er quality codecs, lo#er ideo resolution, and slo#er fra%e rates upstrea% than

do#nstrea%7 "lso, a Lync $erer deploy%ent that uses )") %ust ad:ust policies accordin! to the slo#erlin* speed7

%$%%8 Network Topology

Understandin! your net#or* topolo!y is essential #hen plannin! for Lync $erer7 Lync $erer uses the

follo#in! specific traffic call f lo#s@

11
http://go.microsoft.com/fwlink/p/?LinkId=299368http://go.microsoft.com/fwlink/p/?LinkId=299368


12/133


Peer8his traffic flo# uses a sitetosite connection in scenarios #here -oth participants are internalLync users7 If e9ternal or federated users are inoled, peertopeer connections are routed throu!hthe Internet connection7

"on'erencing8his traffic flo# is created -et#een the net#or*s site to a data center7

PSTN8his traffic flo# initiates fro% a Lync client to the .$7

he topolo!y of your corporate net#or* deter%ines ho# Lync $erer traffic flo#s influence -and#idthrequire%ents7 he t#o topolo!ies that follo# are e9a%ples of ho# different topolo!ies are affected -yLync $erer traffic flo#s7

he follo#in! fi!ure sho#s a corporate net#or* #ith t#o '.L$ carriers and a sin!le interconnection inone !eo!raphy7 Dery ti%e corporate users open a peertopeer %edia session oer to another'.L$, a net#or* interconnection is used7 here is a potential for net#or* delay or :itter #ith peertopeer traffic7

MPLSA MPLSB

"orporate Network with Two MPLS "arriers and a Single &nterconnection in !ne Geography

he follo#in! fi!ure sho#s a corporate net#or* #ith a hu-spo*e %i9ed #ith an '.L$ topolo!y7Dsti%atin! Lync $erer -and#idth is difficult -ecause hu- sites handle a lar!e part of traffic for spo*e

sites, -ut not all of it7

MPLS

"orporate Network with *ub9Spoke Mi5ed with MPLS Topology

12


13/133


2.1.3 Lync Devices

Lync $erer includes 'icrosoft Lync .hone Ddition co%%unications soft#are, #hich runs on qualifieddeices and proides traditional and adanced telephony features, inte!rated security, and%ana!ea-ility7 Lync $erer supports the follo#in! type of unified co%%unication U)6 phones@

(es* phones that are handset I., or U$B deices that are desi!ned to -e used -y e%ployees at theirdes*s7

)onferencin! deices that are handsfree I., or U$B phones that are desi!ned to -e used in %eetin!roo%s7

)o%%on area phones that are handset I. phones, desi!ned to -e used in shared areas7

%$%.%$ Power over #thernet 3Po#4

I. phones runnin! Lync .hone Ddition support .o#er oer Dthernet .oD67 o ta*e adanta!e of .oD, thes#itch %ust support .oD0273af or 0273at7

)onsider Lync oice resiliency carefully durin! net#or* plannin!7 If your deploy%ent includes I. phones,dont oerloo* the possi-ility of a po#er failure7 It is crucial that your .oD infrastructure %aintainsuninterrupted po#er7

%$%.% 2irtual LN 32LN4

5irtual L"s 5L"s6 #or* as -roadcast do%ains created -y s#itches7 5L"s are ery effectie foraddressin! space %ana!e%ent, particularly #hen you are deployin! a lar!e nu%-er of I. phones7here are t#o %ethods to delier 5L" infor%ation for I. phones@

Lin* Layer (iscoery .rotocol LL(.6

(yna%ic Host )onfi!uration .rotocol (H).6

"ll Lynccertified I. phones support Lin* Layer (iscoery .rotocol'edia Dndpoint (iscoery LL(.'D(67 o use LL(.'D(, the s#itch %ust support IDDD0271"B and "$II"10EG7 or e9a%ple,the LL(.'D( deliers 5L" I(, s#itch, and port infor%ation to I. phones7 In addition, the LL(.'D( can -e deployed for location loo*ups used -y D7117

he Lync .hone Ddition deices can also use (H). to o-tain a 5L" identifier7

2.1.4 Qualifie Network Devices

or a list of Lync qualified net#or* deices, see MInfrastructure qualified for 'icrosoft LyncM at

http@!o7%icrosoft7co%f#lin*pLin*IdN23FF7

% ModelingPersonas

he definition of a persona is the process of analy/in! e9istin! usa!e data, and then usin! this data to

calculate the potential load on a ne# syste%7 o fully e9plain the process, #e need to introduce so%e

ter%inolo!y that youll see in the Lync Band#idth )alculator7 or details, see MLync 2010 and 2013

Band#idth )alculatorM at http@!o7%icrosoft7co%f#lin*pLin*IdN301317

Usage scenariosdescri-e different #ays that users co%%unicate -y usin! Lync7 or instance, a peerto

peer audio call or a ideo conference are e9a%ples of usa!e scenarios7

" usage modelrepresents a collection of data associated #ith specific users, #hich can help you

custo%i/e and adapt a ne# syste% to your users specific needs7 or e9a%ple, the usa!e %odel that is

associated #ith pu-lic s#itched telephone net#or* .$6 callin! defines M'ediu%M users, or users in the

%ediu% usa!e cate!ory, as hain! a %a9i%u% of 10 percent concurrent calls to .$ at your

or!ani/ations -usiest ti%e7

13
http://go.microsoft.com/fwlink/p/?LinkId=299366http://go.microsoft.com/fwlink/p/?LinkId=299366http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=299366http://go.microsoft.com/fwlink/p/?LinkId=301391


14/133


"personais a lo!ical !roupin! of users -ased on the -ehaior that they e9hi-it #hen usin! a specific

functionality7 or e9a%ple, a !roup of users %ay hae M'ediu%M .$ callin! patterns, -ut


15/133


"dditionally, if an e9istin! dialin conferencin! proider proides audioconferencin! serices, you can

pro-a-ly access detailed usa!e reports used as part of the -illin! process7 his usa!e data is alua-le as

a tool to help you ad:ust personas and usa!e %odels for actual historical usa!e statistics re!ardin!

!eneral conferencin! -ehaior7

)ollect the follo#in! infor%ation@

)urrent location of the conference -rid!e in use7 "lthou!h this is not directly releant for the usa!e

%odelin!, youll need to *no# #hether the conferencin! %edia flo# patterns #ill -e chan!in! on thenet#or*7 Because conference traffic olu%es are si!nificant, chan!in! the location of the conference-rid!e can affect net#or* plannin! and desi!n7

'a9i%u% nu%-er of conferencin! ports used7

.ea* conferencin! usa!e in the last 12 %onths7

"era!e %a9i%u% nu%-er of concurrent conferences, includin! the nu%-er of participants #hen that%a9i%u% occurs7

"era!e %eetin! si/e7

"era!e %eetin! duration7

otal %inutes of conferencin! used per day and per %onth7

If aaila-le, ho# %any internal users ersus e9ternal users :oined the conference -rid!e7

>oull need si%ilar infor%ation for any ideo conferencin! syste%s in the infrastructure7 .ay specific

attention to the des*top ideo endpoints and codecs in use, and -e sure to as* these questions@

+hat is the %a9i%u% ideo resolution for e9ecutie ideo conferences@ H( or 5C"

+hat is the -ase ideo quality to -e used@ 5C" or )I

(o you plan to inte!rate #ith Lync

+hen definin! personas, the fe#er assu%ptions that you %a*e a-out the potential usa!e of the ne#

syste%, the %ore accurate your -and#idth and capacity calculations #ill -e7

he default persona definition should assu%e that users #ill use all Lync $erer %odalities #ith a 'ediu%

usa!e %odel7 Usin! this approach helps to ensure that you can turn off %odalities in your %odelin! toreduce traffic olu%es, rather than -ein! surprised -y an o%ission later in the process7

+e preiously descri-ed a persona as a lo!ical !roup of users #ho -ehae in a si%ilar %anner #hen

usin! a specific functionality7 he Lync Band#idth )alculator includes usa!e %odels for each of the

follo#in! usa!e scenarios@

'a9i%u% concurrency ofxP of the user -ase usin! instant %essa!in! and presence

'a9i%u% concurrency ofxP of the user -ase usin! peertopeer audio

'a9i%u% concurrency ofxP of the user -ase usin! peertopeer ideo

'a9i%u% concurrency ofxP of the user -ase usin! audio conferencin!

'a9i%u% concurrency ofxP of the user -ase usin! ideo conferencin!

'a9i%u% concurrency ofxP of the user -ase usin! des*top sharin!

'a9i%u% concurrency ofxP of the user -ase usin! .$ audio

'a9i%u% concurrency ofxP of the user -ase #or*in! re%otely

his usa!e %odel can then -e ad:usted, -ased on ho# you anticipate your users -ehain!, and on

historical usa!e statistics fro% e9istin! syste%s7

1E


16/133


>ou can use oerall usa!e %odelin! and user personas for future capacity plannin! in Lync $erer and

other infrastructures7 "fter youre in production, the data on syste% usa!e -eco%es aaila-le throu!h the

Lync $erer 'onitorin! and &eportin! feature7 >ou can then use this data to alidate the accuracy of your

ori!inal personas and -and#idth esti%ations, and to predict future require%ents7

%. ;andwidth #sti/ation

+hat is the potential i%pact of Lync $erer on your net#or*

Band#idth esti%ation is the *ey consideration #hen deployin! Lync $erer7 "ctually, net#or* esti%ation

#ould -e a %ore apt ter%, -ecause the co%%unication strea%s #ithin Lync $erer rely %ore on latency

and pac*et loss than they do on ra# aaila-le net#or* -and#idth7

o understand the role of net#or* esti%ation, you %ust also reco!ni/e the arious co%%unication flo#s

#ithin Lync $erer7 )oupled #ith theuser personas, you can then use this infor%ation #ithin the Lync

Band#idth )alculator to understand, per %odality, the olu%e of traffic that usin! Lync $erer #ill li*ely

!enerate7

he Lync Band#idth )alculator is continuously updated to reflect feed-ac* fro% internal testin! and also

fro% actual custo%erdeployed Lync pro:ects7 herefore, the latest ersion of this spreadsheet can -e

considered the %ost accurate ie# of net#or* -and#idth usa!e7 or details, see MLync 2010 and 2013

Band#idth )alculatorM at http@!o7%icrosoft7co%f#lin*pLin*IdN301317

or a !raphical oerie# of all the protocols in use #ithin Lync $erer, see@

M'icrosoft Lync $erer 2010 .rotocol +or*loads .osterM at http@!o7%icrosoft7co%f#lin*pLin*IdN23F07

M'icrosoft Lync $erer 2013 .rotocol +or*loads .osterM at http@!o7%icrosoft7co%f#lin*pLin*IdN32G47

2.3.1 !all "lows

+ithin any I.-ased unified co%%unications U)6 solution, there are certain characteristic callflo#

scenarios that affect traffic %odelin! results and traffic si%ulation7 $cenarios include peertopeer calls,

conference calls, and .$.BO calls7 Dach scenario has different %edia paths, and %ust -e %odeledand or si%ulated to deter%ine future load require%ents7 here are other callflo# scenarios #ithin the U)

solution8specifically, those of re%ote users or federated co%%unications7 he follo#in! scenarios focus

on plannin! for enterprise eniron%ents and %ana!ed net#or*s7 or details a-out these scenarios, see

MLync 2010 and 2013 Band#idth )alculatorM athttp@!o7%icrosoft7co%f#lin*pLin*IdN301317

%.%$%$ Peer9to9Peer Session

" peertopeer call is any co%%unication session -et#een t#o U) endpoints, usin! any %odality7

hese calls ori!inate and ter%inate on U) endpoints #ithin the corporate net#or*7

" peertopeer session is characteri/ed -y call control si!nalin! that is relayed centrally throu!h

the U) infrastructure, and the realti%e %edia is e9chan!ed directly -et#een the t#o endpoints7

%.%$% "on'erence Session

" conference call is a co%%unication session that ori!inates on a U) endpoint, and ter%inates

on the Lync $erer .ool -y default6 that hosts the audioideo "56 conferencin! serice7

(urin! a conference, %ultiple sessions #ill ter%inate on the "5 conferencin! serice7

he characteristic of a conference call consists of the %edia -ein! e9chan!ed -et#een the U)

endpoint and the "5 conferencin! serice7

1F
http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=299360http://go.microsoft.com/fwlink/p/?LinkId=299360http://go.microsoft.com/fwlink/p/?LinkId=327994http://go.microsoft.com/fwlink/p/?LinkId=327994http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=299360http://go.microsoft.com/fwlink/p/?LinkId=299360http://go.microsoft.com/fwlink/p/?LinkId=327994http://go.microsoft.com/fwlink/p/?LinkId=327994http://go.microsoft.com/fwlink/p/?LinkId=301391


17/133


%.%$%. PSTNMediation Server Session

+ithin the conte9t of a 'icrosoft U) syste%, a .$ call is any co%%unication session that

ori!inates on a U) endpoint and ter%inates on a Lync serer role called a 'ediation $erer for

on#ard relay to a .$ !ate#ay or a qualified I. .BO7 or net#or* plannin! purposes, you need

to understand the physical location of these Lync 'ediation $erers and !ate#ays7

In Lync $erer 2010, a ne# feature8media bypass8#as introduced that ena-les the Lync client

endpoint to -ypass a Lync 'ediation $erer7 his #ay, %edia traffic is sent directly to a qualified.$ !ate#ay or I. .BO7

%.%$%7 "ontent Sharing

(urin! Lync peertopeer and conference sessions, it is possi-le to share the entire des*top, or, %ore

efficiently, the indiidual application -ein! referenced7 +hen des*top or application sharin! is initiated,

Lync #ill use the &e%ote (es*top .rotocol &(.6 protocol -uilt into the host operatin! syste%7 his is a

). connection-ased protocol that resends pac*ets that are lost7

It is ery difficult to predict the effect of &(. on the net#or* -ecause, -y nature, it is a protocol

characteri/ed -y frequent -ursts, and it depends heaily on ho# often the shared des*top or application

i%a!e is updated7

$ee the follo#in! ta-le to esti%ate the ran!e of fi!ures for e9pected -and#idths7


18/133


"ll fi!ures are -ased around the industry standard of 20%s pac*eti/ation for U) applications,

#hich is E0 pac*ets per seconds7

Band#idth fi!ures include the protocol oerheads for I., U(., &., and $&.7 his is #hy the

'icrosoft -and#idth fi!ures for standard codecs are different fro% those quoted -y other 5oI.

suppliers, #ho only state the ra# codec fi!ure, and not the entire pac*et oerhead7 or 'icrosoft,

this fi!ure includes encryptin! all co%%unications7

i!ures in the follo#in! ta-le for audio -and#idths do not include a or#ard Drror )orrectionD)6 oerhead7 D) is a %iti!ation technique that is ena-led #hen the net#or* suffers

unusually hi!h pac*et loss7 he assu%ption is that, for plannin!, the net#or* ad%inistrator #ill

esti%ate traffic use #ithout %iti!ations7

or ideo, the default codec is the H72F4'.DC4 .art 10 "danced 5ideo )odin! standard,

coupled #ith its scala-le ideo codin! e9tensions for te%poral scala-ility7 o %aintain

interopera-ility #ith Lync 2010 or ;ffice )o%%unicator 200G &2 clients, the &5ideo codec is still

used for peertopeer calls -et#een Lync $erer 2013 and le!acy clients7 In conference sessions

#ith -oth Lync $erer 2013 and le!acy clients, the Lync $erer 2013 endpoint %ay encode the

ideo -y usin! -oth ideo codecs, and %ay send the H72F4 -it strea% to the Lync $erer 2013,

and send the &5ideo -it strea% to Lync 2010 or to ;ffice )o%%unicator 200G &2 clients7

(efault aspect ratio for Lync $erer 2013 has -een chan!ed to 1F@7 he 4@3 aspect ratio is stillsupported for #e-ca%s that dont allo# capture in 1F@ aspect ratio7

udio "odec ;andwidth

udio codec Scenarios Ma5i/u/ bandwidth

3)bps4

Typical bandwidth

3)bps4

&"udio

+ide-and

.eertopeer, default codec F2 37

&"udio

arro#-and

.eertopeer, .$ 447 307

C7G22 (efault conferencin! codec 1007F 4F71

C7G22 $tereo .eertopeer, )onferencin! 1E G371

C7G11 .$ G F47$iren )onferencin! E27F 2E7E

Band#idth includes I. header, U(. header, &. header, and $&. headers7 he stereo ersion of the

C7G22 codec is used -y syste%s that are -ased on the Lync $erer 2013 'eetin! &oo% Ddition, #hich

ena-les stereo %icrophone capture so that listeners to can %ore easily distin!uish -et#een %ultiple

tal*ers in the %eetin! roo%7

%.%%$ 2ideo "odec ;andwidth

he required -and#idth depends on the resolution, quality, and fra%e rate7 or each resolution, there are

three -it rates@

Ma5i/u/ payload bit rate8Bit rate that a Lync $erer endpoint uses for resolution at the %a9i%u%fra%e rate supported for this resolution7 his alue ena-les the hi!hest quality and fra%e rate forideo7

Mini/u/ payload bit rate8Bit rate -elo# #hich a Lync $erer endpoint s#itches to the ne9t lo#erresolution7 o !uarantee a certain leel of resolution, the aaila-le ideo payload -it rate %ust not fall-elo# this %ini%u% -it rate for that resolution7 his alue ena-les you to deter%ine the lo#est aluepossi-le in cases #here the %a9i%u% -it rate is not aaila-le or practical7 or so%e users, a lo# -itrate ideo %i!ht -e considered an unaccepta-le ideo e9perience, so -e careful #hen you consider

1


19/133


applyin! these %ini%u% ideo payload -it rates7 or ideo scenes #ith little or no user %oe%ent,the actual -it rate %ay also te%porarily fall -elo# the %ini%u% -it rate7

Typical bit rate8Used #ith %ore than 100 users at site, as a %ore accurate #ay of %odellin! -and#idththan #ith usin! the %a9i%u% ideo -it rates7

%.%% 2ideo


20/133


he typical strea% -and#idth for panora%ic ideo is -ased on currently aaila-le deices that strea%

only up to F09144 panora%ic ideo7 "fter deices #ith 1207972 panora%ic ideo -eco%e aaila-le,

the typical strea% -and#idth is e9pected to increase7

%.%%. &/pact o' Multiple 2ideo Strea/s in Lync Server -$.

" feature in Lync $erer 2013 conferences displays up to fie si%ultaneous ideo strea%s, and potentially

a si9th, if the .anora%ic ideo option is used7 By default, the ideo strea%s sho# the current and past

four actie spea*ers, -ut this can -e chan!ed -y the user to select any fie feeds fro% #ithin the !allery

ie#, as sho#n in the follo#in! fi!ure7

Lync Server -$. "on'erence Gallery 2iew with 6ive Si/ultaneous 2ideo Strea/s

he fie lar!er #indo#s sho# the lie ideo feeds7 he %ediu% #indo# is a ideo preie# of the user,

and the pictures underneath are static i%a!es of other %eetin! attendees that can -e selected to -e one

of the fie ideo feeds7

2.3.2.3.1 Lync 'erver #anwit$

here is a alue in Lync $erer called the otal&eceie5ideoBit&ateK-, #hich, -y default, is set to

E0,000K-s or F72E'Bs67 +e reco%%end lo#erin! this alue to ,000K-s, #hich essentially li%its the

ideo traffic to a sin!le H( ideo strea%7 or details, see M)onfi!urin! 5ideo D9a%ple $cenariosM at

http@!o7%icrosoft7co%f#lin*pLin*IdN23F27

20
http://go.microsoft.com/fwlink/p/?LinkId=299362http://go.microsoft.com/fwlink/p/?LinkId=299362http://go.microsoft.com/fwlink/p/?LinkId=299362


21/133


%.%%7 udio "apacity Planning 'or PSTN

he follo#in! ta-le sho#s the net#or* -and#idth nu%-ers that indicate audio capacity plannin! for a

pu-lic s#itched telephone net#or* .$67

;andwidth 2alues 'or udio "apacity Planning 'or PSTN

Media codec Typical strea/ bandwidth 3)bps4 Ma5i/u/ strea/ bandwidth

C7G11 F47 G

&"udio arro#-and 307 447

he net#or* -and#idth nu%-ers in all precedin! ta-les represent one#ay traffic only, and include E

K-ps for &). traffic oerhead for each strea%7

or all -and#idth ta-les, the %a9i%u% -and#idth fi!ures should !enerally -e used in net#or* plannin!7

Lync $erer depends entirely on the underlyin! net#or* for the userperceied quality of its

co%%unications, particularly oice7 In addition, sites #ith fe#er than 100 users should al#ays use the

%a9i%u% fi!ures -ecause, statistically, the net#or* pea*s for Lync $erer occur %ore frequently7 or

sites #ith %ore than 100 users, the typical fi!ures can -e used7

2.3.3 #anwit$ (stimation for )eunant Links+e offer the follo#in! reco%%endations at a technical leel for esti%atin! -and#idth for redundant lin*s7

he econo%ics of your -usiness #ill typically deter%ine the leels of redundant lin*s that are required for

indiidual #or*loads #ithin the or!ani/ation7 .ro:ect #or* #ith custo%ers typically inoles the follo#in!

considerations@

'any custo%ers hae outsourced all their +" connections to a sin!le proider or a s%all !roup

for internationals6 that offers a serice leel a!ree%ent $L"6 for lin*s that %atch or e9ceed the-usiness require%ent for Lync $erer and oice6 serice aaila-ility7

Bac*up lin*s do e9ist, -ut #ith stricter call ad%ission control )")6 to reduce the nu%-er of

si%ultaneous connections that occur8for e9a%ple, a reduced serice7 he -ac*up lin*s also donot usually support any Ao$ settin!s, #hich are al%ost al#ays a cost option on +"

connections7 'any co%panies issue %o-ile phones or een s%artphones to their core *no#led!e #or*ers or

rely on M-rin! your o#n deices= B>;(s66, and also use these deices as -ac*up %echanis%sfor Lync $erer and oice6 serices7 his -eco%es %ore releant #ith Lync $erer 2013, #hichhas fully featured clients, includin! 5oI. and ideo that can run on %o-ile deices and operateacross %o-ile phone style data net#or*s for e9a%ple, 3C and 4C LD6-ased serices67

%7 Tra''ic Si/ulation

Understandin! ho# your net#or* perfor%s under real#orld traffic patterns is essential7 >our si%ulation

testin! should use fie -aseline net#or* characteristics that #ill quantify your net#or*s perfor%ance

under the anticipated traffic olu%e that your users #ill !enerate -y usin! Lync $erer7 >oue already

used the Lync Band#idth )alculator to esti%ate traffic olu%es -ased on usa!e %odels, and to create

personas that you %odified -y usin! real#orld data collected in your discoery conersations7 o#

youre ready to !enerate the olu%e of traffic in those si!nature %edia flo# scenarios8peer, conference,

and .$7

" si%ulation tool %ust -e a-le to !enerate traffic real &.&). traffic6, collect, and then !raph the

ariation in the fie -aseline net#or* characteristics for each call@

;ne#ay net#or* delay

"era!e :itter

21


22/133


'a9i%u% :itter

"era!e pac*et loss

Burst pac*et loss pea* consecutie pac*ets lost6

+hen si%ulatin! traffic, %a*e sure that you hae@

'odeled the a%ount of -and#idth required7

Identified sites for Lync $erer traffic si%ulation7)ollected Lync $erer realti%e scenarios to -e si%ulated7

2.4.1 'imulatin* (stimate +mount of #anwit$ )e,uire

"s you prepare to introduce Lync $erer realti%e serices to your or!ani/ations net#or* infrastructure, it

is crucial to accurately si%ulate and ealuate the anticipated load and the i%pact that Lync $erer

serices %ay hae in a !ien site or -et#een sites7

Den if youe already docu%ented and planned anticipated usa!e %odels and the associated a%ount of

-and#idth, unless your or!ani/ation can apply and si%ulate the anticipated load of Lync $erer realti%e

traffic on its net#or*, you #ont -e a-le to fully ealuate and erify the net#or*s a-ility to respond at pea*

ti%es of Lync $erer serices usa!e7

+hen perfor%in! a traffic si%ulation for alidatin! Lync $erer supporta-ility, the si%ulation itself needs to

-e focused on the anticipated a%ount of -and#idth required in support of Lync $erer %odalities to -e

used, local to a !ien site7 his is i%portant -ecause, althou!h you %ust consider the potential -and#idth

associated #ith a particular codec fro% a capacity plannin! perspectie, its %ore i%portant to esti%ate

the a%ount of -and#idth required in total, !ien the potential %a9i%u% concurrent Lync $erer %odalities

and scenarios7 hese scenarios are discussed in the follo#in! sections7

%7%$%$ PP Scenarios

.eertopeer .2.6 scenarios consist of@

"udio

5ideo

(es*top sharin!

+e- colla-oration

%7%$% "on'erencing Scenarios

)onferencin! scenarios consist of@

"udio

5ideo

+e-

"nother *ey factor to identify #hen desi!nin! or perfor%in! traffic si%ulation scenarios is %odelin!anticipated usa!e, alon! #ith the associated -and#idth i%pact on a local site or -et#een sites7 or

details, see'odelin!.ersonasand Band#idth Dsti%ation7

In so%e cases, %odelin! can -e -ased on esti%ated !uesses for the e9pected usa!e leel or scenario for

a particular site7 "dditionally, -y usin! usa!e %odels as part of the actual traffic si%ulation process, you

can incorporate additional anticipated assu%ptions to deter%ine potential !aps7

22


23/133


he ne9t consideration@ #hat is the -est approach for properly assessin! and si%ulatin! Lync $erer

traffic, alon! #ith its potential i%pact in a !ien net#or* eniron%ent o deter%ine this, thin* a-out ho#

the anticipated Lync $erer traffic should -e si%ulated7 Be sure to include the ealuation and sa%plin!

periods required for representin! ho# the net#or* is a-le to respond and perfor%7

"s a -est practice, Lync $erer traffic si%ulation scenarios for a specific site should include@

&unnin! for a %ini%u% of one #ee*7

&unnin! 24 hours a day7

"s an additional part of this reco%%ended test profile, consider factorin! in the %a9i%u% anticipated

sessions, follo#in! the -and#idth calculator si/in! e9a%ple in the Matri5 0istributionta-, as follo#s@

Matri5 0istribution Tab in ;andwidth "alculator

" #elldesi!ned traffic si%ulation sa%plin! scenario ena-les you to@

(eter%ine if any con!estion patterns deelop #ithin the net#or* after Lync $erer realti%e serices areintroduced7

(eter%ine if the Ao$ policies in place are effectie and -ein! correctly applied7

Cau!e the net#or* response durin! certain periods of con!estion for e9a%ple, dropped pac*ets, delayand :itter effects, and so on67

2.4.2 Ientifyin* 'ites for Lync 'erver %raffic 'imulation

"fter you identify the scenarios to si%ulate traffic, coupled #ith the anticipated total -and#idth required,

youll need to deter%ine #hich sites or locations to use for a!ent place%ent to si%ulate Lync $erer

traffic7

>ou should al#ays place a si%ulation pro-e at the location #here your Lync )onferencin! serices

reside7 e9t, youll need to decide #hich re%ote locations +" sites6 youre !oin! to test7

>ou should cate!ori/e your locations, usually -ased on +" lin* speedtype, nu%-er of users in the site,

and !eo!raphic location7 Den enterprise custo%ers !enerally hae fe#er than F10 cate!ories of sites7

23


24/133


In practice, choose up to 20 sites to test, eenly distri-uted -et#een !eo!raphic re!ions7 Be sure to

choose a sa%ple fro% each cate!ory in each re!ion7 or e9a%ple, lets assu%e that your or!ani/ation

spans three re!ions "%ericas, Durope, the 'iddle Dast and "frica D'D"6 and "sia .acific ".")667

+ell also assu%e that your enterprise has si9 cate!ories of sites7 >ou #ould end up testin! #ith 1

re%ote locations -ecause youd !et a sa%plin! of 3 sites fro% each cate!ory split -et#een the re!ions7

inally, -e sure to ta*e a loo* at locationsre!ions #ith preious connectiity issues, or #here users hae

raised concerns a-out %edia quality issues7

2.4.3 Lync 'erver )eal-%ime 'cenarios to #e 'imulate

Up to this point, youe identified the usa!e scenarios, test cases, -and#idth esti%ation, and site

locations to -e ealuated7 >our final step is to deter%ine #hich Lync $erer realti%e scenarios should -e

considered as part of your traffic si%ulation testin! criteria7

or this effort, you should use the output of the Lync Band#idth )alculator7 he Band#idth )alculators

output identifies the follo#in! traffic olu%es on a site-ysite -asis@

.eer traffic should -e eenly distri-uted -et#een other re%ote location pro-es6

o "udio traffic olu%e

o 5ideo traffic olu%e

)onference traffic should -e -et#een the re%ote pro-e and the data center pro-e6


o 5ideo traffic olu%e

.$ traffic should -e -et#een the re%ote pro-e and the data center pro-e6


or details, see MLync 2010 and 2013 Band#idth )alculatorM athttp@!o7%icrosoft7co%f#lin*p

Lin*IdN301317

Cenerally, #e dont reco%%end si%ulatin! appsharin! traffic -ecause its ).-ased, typically un%ar*ed

for Ao$, and characteri/ed -y frequent -ursts7 he theoretical %odelin! actiities youe alreadyco%pleted, co%-ined #ith your historical %etrics, #ill help you deter%ine any potential ris*s7 If you feel

stron!ly a-out si%ulatin! appsharin! traffic, #e reco%%end usin! a ).-ased traffic si%ulation

pac*a!e7

2.4.4 )ecommene %ools for Lync 'erver %raffic 'imulation

here are %any tools aaila-le today on the %ar*et, and any of these tools can -e used #ith this

%ethodolo!y7 'a*e sure that the tool includes the follo#in! critical ele%ents@

"-ility to !enerate real &.&). traffic, for audio and ideo7

"-ility to centrally %ana!e the pro-es7

"-ility to %ar* traffic #ith Ao$ %ar*in!s7

"-ility to collect and !raphically present the fie -aseline net#or* characteristics %apped oer

ti%e7

Important Look for variations in those baseline characteristics over time# not simply a threshold

number that.s good or bad

$upport for all f ie -aseline characteristics@

24
http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391


25/133


o ;ne#ay net#or* delay

o "era!e :itter

o 'a9i%u% :itter

o "era!e pac*et loss

o Burst pac*et loss pea* consecutie pac*ets lost6

"dditional features in arious tools include the a-ility to !enerate auto%ated reports -ased on the

collection data, the a-ility to schedule tests, and the a-ility to fla! #hen Ao$ %ar*in!s are -ein! stripped7

2.4./ %raffic 'imulation #est 0ractices

In su%%ary, as you prepare to ealuate your net#or*s a!ainst pri%ary Lync $erer traffic si%ulation

scenarios, its i%portant to@

5erify site selection -ased on #here you anticipate Lync $erer realti%e serices to -e used7

(ecide on the leel of traffic distri-ution and allocation required for e9a%ple, flo#s and a%ount of trafficto si%ulate67

Kno# the *ey sites, and -and#idth in -et#een the%, for ho# Lync $erer traffic scenarios should -e -est

si%ulated7

Keep the list of sites to ealuate to 20 sites or fe#er7

est representatie sites that #ill use Lync $erer realti%e co%%unication serices7

ocus on potential #ea* points #ithin the net#or* for e9a%ple, areas #here -and#idth %ay -e thin67

(eter%ine potential pac*et loss and delay for connections that trael in -et#een continents7

Inquire a-out e9istin! or!ani/ational *no#led!e re!ardin! -ad quality, to deter%ine #here to perfor%traffic si%ulation scenarios7

)onsider site selection input other than technical factors for e9a%ple, the location of the )hiefInfor%ation ;fficers office67

)onsider traffic distri-ution and allocation -et#een sites7

.erfor% initial %odelin! #ith the MLync 2010 and 2013 Band#idth )alculatorM athttp@!o7%icrosoft7co%f#lin*pLin*IdN30131at the site leel for e9a%ple, in traffic fro% and to thesite6 to use as input for finali/in! the anticipated traffic si%ulation criteria7

%8 "all d/ission "ontrol 3""4

)all ad%ission control )")6 is an application layer %echanis% that deter%ines #hether there is

sufficient net#or* -and#idth to proide a hi!hquality e9perience for users #hen they place an audio call

or a ideo call throu!h the net#or*7 )") is solely confi!ured #ithin Lync $erer and does not *no#

enou!h a-out the underlyin! net#or* infrastructure to resere -and#idth, or to help ensure that

-and#idth is actually aaila-le outside of its o#n confi!ured alues7 Ho#eer, )") can ena-le you, as a

syste% ad%inistrator, to define potential net#or* capacity li%itations -et#een sites7 "dditionally, fro% a

user perspectie, )") proides a -etter e9perience -y re:ectin! or reroutin! a call and isually indicatin!the reason, rather than allo#in! a call to !o ahead #ith poor quality on the defined net#or* path7

In Lync $erer, call ad%ission control can -e confi!ured to define the %a9i%u% concurrent -and#idth to

-e used for realti%e audio and ideo %odalities7 )") can also -e confi!ured to define the %a9i%u%

-and#idth for a sin!le call of each %odality7 )") does not li%it the -and#idth of other traffic7 It cant

preent other data traffic, such as a lar!e file transfer or %usic strea%in!, fro% usin! all the net#or*

-and#idth7 )") also cant -e used to define the codec used -y a call7 Ho#eer, )") can -e confi!ured

to li%it the option of hi!her -and#idth for the call7

2E
http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391http://go.microsoft.com/fwlink/p/?LinkId=301391


26/133


"s an additional %easure to protect the necessary -and#idth, deploy Auality of $erice Ao$67 "s a -est

practice confi!uration, -e sure to coordinate )") -and#idth policies #ith Ao$ settin!s deployed to the

physical net#or*7

)all ad%ission control policies can -e defined -y usin! either the Lync $erer )ontrol .anel or the Lync

'ana!e%ent $hell7 he Lync $erer 'ana!e%ent $hell ena-les scriptin! of the confi!urations, #hich #e

reco%%end #ith %ultiple site specifications7 'onitorin! the usa!e of )") is aaila-le throu!h call detail

recordin! )(&6 data and Auality of D9perience AoD6 data in the 'onitorin! reports7 Be sure to use

%onitorin! functions to help ensure that )") polices are neither underproisioned nor oerproisioned for

specific sites7 )onfi!urin! )") alone does not proide opti%al -and#idth usa!e for sitetosite lin*sQ it

:ust protects real ti%e traffic fro% itself7

o confi!ure )") #ithin Lync $erer, it is ery i%portant to identify the I. su-nets that are assi!ned to

each site7 he I. su-nets specified durin! net#or* confi!uration on the serer %ust %atch the for%at

proided -y client co%puters to -e usa-le for the %edia -ypass feature of Lync $erer7 In other #ords,

the I. su-nets confi!ured in )") should %atch the su-nets proided -y (yna%ic Host )onfi!uration

.rotocol(H).6 serers or statically assi!ned to clients, rather than created for su%%ary purposes7

If the or!ani/ation proides %edia throu!h a irtual priate net#or* 5.6 connection, then the %edia

strea% and the si!nalin! strea% !o throu!h the 5., or -oth are routed throu!h the Internet7 Ho#eer,

call ad%ission control is not enforced for re%ote users #here the net#or* traffic flo#s throu!h the

Internet7 Because the %edia traffic is traersin! the Internet, #hich is not %ana!ed -y Lync $erer, )")

cannot -e applied7 )") chec*s are perfor%ed on the portion of the call le! that flo#s throu!h the

or!ani/ations net#or*7

2./.1 Multiple !all +mission !ontrol 'ystems

Because realti%e co%%unications syste% lifecycles ary, its li*ely that %ultiple realti%e

co%%unications syste%s #ill -e operatin! at the sa%e ti%e on the enterprise net#or*7 his could -e due

to specific %odalities -ein! controlled -y one co%%unications syste%, or -y other specific islands of

technolo!y -ein! aaila-le in certain re!ions, or throu!h coe9istence or %i!ration7 "t these ti%es, %ultiple

)") %echanis%s are aaila-le throu!h the indiidual syste%s7 hese %echanis%s are separate fro%

each other, so its i%portant to alidate %odelin! profiles and -and#idth esti%ation for potential use7

$pecifically, for )"), youll need to %a*e allo#ances for traffic fro% %ultiple syste%s across +" lin*s,

and youll need to use consistent, re!ular %onitorin! to facilitate necessary ad:ust%ents in any specified

alues7

In this scenario, call ad%ission control is used to protect Lync $erer realti%e traffic and other syste%srealti%e traffic fro% interferin! #ith each other in the conte9t of the underlyin! net#or* topolo!y, andAuality of $erice Ao$6 %ar*in!7 o illustrate the point, i%a!ine your oice Ao$ queue as a lar!e pipe,#ith t#o s%aller pipes #ithin the lar!er pipe7 he Lync $erer )")8one of the s%all pipes8#ould li%itthe olu%e of the Lync $erer traffic in the oice queue, and the other syste%s )")8the other s%allpipe8#ould need to li%it the olu%e of its traffic in the oice queue7 o help ensure that -oth syste%scoe9ist #ithout affectin! each other, deter%ine the appropriate si/e of )") li%its and of queues -efore

deploy%ent, and alidate these data re!ularly as part of operational e9cellence%> +uality o' Service 3+oS4

Auality of $erice Ao$6 is the %echanis% that ena-les classification, %ar*in!, and prioriti/ation of traffic

on the net#or*7

Ao$ helps to !uarantee the -and#idth aaila-le for confi!ured traffic flo#s7 "s a -est practice, youll need

to coordinate )") -and#idth policies #ith Ao$ settin!s deployed to the physical net#or*7

2F


27/133


Ao$ classification enco%passes %any different types of net#or* traffic, #ith port-ased and protocol

-ased traffic as the %ost co%%on classification %ethods7 >ou can also confi!ure your net#or*

infrastructure to trust ($). %ar*in!s on net#or* traffic that it receies fro% the endpoint7

Lync $erer 2013 ena-les -oth defined port ran!es and ($). %ar*in!7 o help ensure the -est user

e9perience, you should confi!ure Lync $erer 2013 to %ar* all traffic for trans%ission onto the net#or*7

" !ood startin! point #ould -e to confi!ure all oice realti%e traffic to use (iff$erer )ode .oint 4F, #ith

ideo confi!ured for 347 )onfi!ure $I. $i!nallin! traffic to use 247 'ar* other %odalities accordin! to-usiness require%ents7 Because these are only reco%%endations, %a*e sure that youre usin! the

%ar*in!s that hae -een a!reed upon as part of your enterprises e9istin! Ao$ strate!y7

.ay attention to the Ao$ policies i%ple%ented on e9istin! s#itch infrastructures to help ensure that client

($). %ar*in!s are not stripped, or reset7

)onfi!ure Ao$ endtoend, and erify that the Ao$ %ar*in!s in place throu!hout the net#or* are

le!iti%ate to aoid any confi!uration issues on the s#itch infrastructure7 ;ther#ise, this %is%atch could

cause re%ar*in! of pac*ets to a less than opti%al alue, #hich could cause the% to %iss priority queuin!

confi!ured on the net#or*7

%? Network Port Usage

+hen usin! net#or* ports, -e sure that youe co%pleted the follo#in! plannin! require%ents@

)onfi!urin! %anual port scenarios7

Auality of $erice Ao$67

'ana!in! -and#idth7

.lace%ent of internal fire#alls7

'ini%u% nu%-er of ports for #or*loads at scale7

Dffect of %anual port ran!e assi!n%ent on $&. co%%unications7

)onfi!urin! %anual ports for the Lync client7

)onfi!urin! port ran!es for your )onferencin! $erer, "pplication $erer, and 'ediation $erer75erifyin! %anual port confi!uration on the client side7

5erifyin! a unified co%%unications U)6 port ran!e that is ena-led for Lync clients7

5erifyin! %anual port confi!uration on the serer side7

.rioriti/in! traffic for realti%e co%%unications7

2..1 Manual 0ort !onfi*uration 'cenarios

+ith enterprise deploy%ents for Lync $erer 2013, one of the %ost co%%on questions fro% custo%ers is@

MIs it possi-le to assi!n a dedicated nu%-er and ran!e of ports per Lync $erer %odality= and


28/133


Internal fire#all place%ent

2..2 Quality of 'ervice Qo' for Moality %ypes

o support an or!ani/ation Ao$ policy that can differentiate -et#een realti%e co%%unication %odality

types, #e reco%%end that you allocate a separate and dedicated ran!e for each Lync $erer %odality

for e9a%ple, oice, ideo, or application sharin!67 (ependin! on the port ran!e assi!ned, the Ao$ policy

in place inspects the traffic and desi!nates priority, -ased on the processin! prioriti/ation classifications in

place for a particular net#or* deice7

2..3 #anwit$ Mana*ement

"s a co%ple%ent to a Ao$ policy already in place, so%e or!ani/ations %ay #ant to add traffic

%ana!e%ent policies for allocatin! a %a9i%u% a%ount of -and#idth per Lync $erer %odality type7 In

this case, the policy is confi!ured to allocate -and#idth -ased on ho# the affected net#or* deice is

confi!ured7

2..4 Internal "irewall 0lacement

$ecurityconscious or!ani/ations often hae a re!ulatory or co%pliance require%ent that %andates

placin! an internal f ire#all -et#een clienttoclient and clienttoserer co%%unications, for %ana!e%entand %onitorin! capa-ilities7 In %any cases, -ecause a fire#all is li%ited -y the I. address assi!ned to the

interfaces routin! traffic, the list of ports aaila-le to support a ran!e of co%%unication scenarios is fro%

1024 to FEE3E7 "s a result, so%e or!ani/ations %ay need to allocate the %ini%u% nu%-er of ports

required, due to the ).I. port allocation li%itations for routin! Lync $erer 2013 clienttoclient and

clienttoserer traffic7

Note /ecause this scenario is not officially supported by Lync Server '()* deployment# the capabilities of

Microsoft for providing assistance# if re&uired# will be best"effort 0f the issues can.t be resolved# you may

be asked to temporarily remove the firewall# in order to move to a supported scenario to find a solution

2../ Minimum Num&er of 0orts for orkloas at 'cale

o support a dedicated nu%-er of port ran!es per Lync $erer %odality so that you can proide the%ini%u% nu%-er of ports needed per serer and per client to ena-le all #or*loads at scale, you %ust first

allocate a ran!e of ports to -e unique per %odality, as sho#n in the follo#in! ta-le7

llocation o' Port


29/133


in ter%s of the precedin! ta-le, you could hae Lync clients confi!ured to use ports 42000 throu!h 4201

for application sharin! scenarios67 ;r you could hae Lync $erer confi!ured, -y default, to the follo#in!

set of ports instead@ 4003 throu!h 41E1 for application sharin! scenarios67

he ran!e of client ports assi!ned does not need to represent a su-set of the ports used -y Lync $erer

itself7 he %ain difference is that Lync $erer needs a -roader ran!e or ports aaila-le to -est support the

ran!e of clients required at scale7

Note +e recommend that you make your client port ranges a subset of your server port ranges

o assi!n the port ran!es sho#n in the precedin! ta-le to your !lo-al collection of conferencin!

confi!uration settin!s, use the follo#in! Lync $erer 'ana!e%ent $hell c%dlet@

Set-CsConferencingConfiguration -Identity global -ClientAudioPort 50020-ClientAudioPortRange 20 -ClientVideoPort 58000 -ClientVideoPortRange 20-ClientAppSharingPort 2000 -ClientAppSharingPortRange 20 -Client!ile"ransferPort 2020 -Client!ile"ransferPortRange 20

2..5 !onfi*urin* Manual 0orts for t$e Lync !lient

By default, the Lync client applications #ill use any port -et#een 1024 and FEE3E #hen i%ple%entin! the

follo#in! realti%e co%%unication %odalities@

5oice

5ideo

"pplication %edia6 sharin!

+e- colla-oration

ile transfer

If you %ust %anually assi!n and specify a ran!e of ports8#hich #e reco%%end, if you plan on

i%ple%entin! Ao$8you %ust first ena-le client %edia port ran!es7 (o this -y runnin! the follo#in!

+indo#s .o#er$hell c%dlet@

Set-CsConferencingConfiguration -Client#ediaPortRange$nabled %"rue

o %anually assi!n dedicated port ran!es for the arious traffic types audio, ideo, %edia, applicationsharin!, and file transfer6 to a series of unique port ran!es, run the follo#in! +indo#s .o#er$hell c%dlet@

Set-CsConferencingConfiguration

Note %he preceding cmdlet enables client media port ranges for the global collection of conferencingconfiguration settings $owever# these settings can also be applied at a Lync site scope and7or the servicescope 3for the 5onferencing Server service only4 levels %o enable client media port ranges for a specificsite or server# specify the identity of that site or server when running the'et-!s!onferencin*!onfi*urationcmdlet6

Set-CsConferencingConfiguration -Identity &site'CentralSite(&-Client#ediaPortRange$nabled %"rue

By default, if no %anual %edia port ran!e throu!h conference confi!uration settin!s6 has -een defined,

define the follo#in! property alues@

Media Port


30/133


)lient5ideo.ort&an!e 40

)lient"pp$harin!.ort E3E0

)lient"pp$harin!.ort&an!e 40

)lientileransfer.ort E3E0

)lientransfer.ort&an!e 40

ro% the preious results, the follo#in! property set is confi!ured as alse -y default@

Client#ediaPortRange$nabled

+hen this property is set to alse, Lync clients can use any ran!e of User (ata!ra% .rotocol U(.6 or

). ports aaila-le fro% a ran!e of 1024 throu!h FEE3E #hen esta-lishin! Lync %edia co%%unications7

2.. !onfi*urin* 0ort )an*es for +pplication6 !onferencin*6 anMeiation 'ervers

By default, the Lync 2013 "pplication, )onferencin!, and 'ediation $erers use any port -et#een 1024

and FEE3E #hen i%ple%entin! the follo#in! realti%e co%%unication %odalities@

5oice

5ideo

"pplication %edia6 sharin!

+e- colla-oration

o erify that the e9istin! port ran!es for your )onferencin!, "pplication, and 'ediation serers are

confi!ured as e9pected, run the follo#in! Lync $erer 'ana!e%ent $hell c%dlets@

)et-CsSer*ice -ConferencingSer*er + Select-,bect Identity. AudioPortStart.AudioPortCount. VideoPortStart. VideoPortCount. AppSharingPortStart.AppSharingPortCount

)et-CsSer*ice -ApplicationSer*er + Select-,bect Identity. AudioPortStart.AudioPortCount

)et-CsSer*ice -#ediationSer*er + Select-,bect Identity. AudioPortStart.AudioPortCount

he follo#in! ta-le lists the default port ran!es assi!ned to Lync $erer 2013@

0e'ault Port


31/133


"s the precedin! ta-le sho#s, for each %odality listed8audio, ideo, and application sharin!8t#o

separate property alues are assi!ned@ the port start and the port count7 he port start alue indicates the

first port fro% the ran!e assi!ned that should -e used for that specific %odality7

or e9a%ple, #hen you are usin! an audio port co%%unication scenario, if the defined audio port start is

equal to E0,000, this %eans that the first port that is used for audio traffic #ill -e port E0,0007 If the audio

port count is set to 20, this %eans that only 20 ports #ill -e allocated as audio call scenarios7

Note /ecause ports from an assigned range are used for a specific modality# the range of ports used fora specific modality scenario will be contiguous 2or example# >(#(((# >(#(() through >(#()< indicates up

to '( continuous audio sessions that the Lync client will be able to participate in and support

+hen confi!urin! %anual port ran!es for Lync $erer roles, %a*e sure that@

"udio port settin!s are identical across your )onferencin!, "pplication, and 'ediation $erers7

.ort ran!es assi!ned per %odality do not oerlap7

or e9a%ple, in reference to the precedin! ta-le, port ran!es assi!ned are identical across all serer

types7 "dditionally, fro% the default confi!uration@

he startin! audio port is set to port 4,1E2 for each serer type, and the total nu%-er of ports reseredfor audio in each serer is also an identical nu%-er@ ,347

he ports set aside for application sharin! start at port 4, 1E27

o preent port ran!es fro% oerlappin!, you can confi!ure application sharin! to start at port 40,03 and

still hae a port count of ,34 ports assi!ned7 "s a result, Lync serers #ill use ports 40,03 throu!h port

4,1E1 #ith no oerlap in the ran!e of ports assi!ned to audio scenarios, and #ith audio port

co%%unications startin! on port 4,1E27

o %odify the port alues for application sharin! on a sin!le )onferencin! $erer, run a Lync $erer

'ana!e%ent $hell c%dlet si%ilar to this@

Set-CsConferenceSer*er -Identity ConferencingSer*er'ste(-ls-00(/contoso/co-AppSharingPortStart 0801 -AppSharingPortCount 818

If you #ant to %a*e these chan!es on all your )onferencin! $erers, run this c%dlet instead@

)et-CsSer*ice -ConferencingSer*er + !or$ach-,bect Set-CsConferencingSer*er-Identity %3/Identity -AppSharingPortStart 0801 -AppSharingPortCount 8184

"fter chan!in! port settin!s, stop and then restart each serice that is affected -y the chan!es7

It is not %andatory that your )onferencin!, "pplication, and 'ediation $erers share the sa%e port

ran!e7 he only require%ent is that you set aside unique port ran!es on all your serers7 Ho#eer,

ad%inistration is typically easier if you use the sa%e set of ports on all your serers7

2..7 !onfi*urin* Deicate 0ort )an*es for (*e 'ervers

By default, a Lync 2013 Dd!e $erer is confi!ured #ith the follo#in! port ran!e assi!n%ents in the

correspondin! realti%e co%%unication %odalities7

Lync Server -$. Port


32/133


o confi!ure an Dd!e $erer to use these ran!e of port alues per %odality as sho#n in the precedin!

ta-le, run the follo#in! c%dlet in Lync $erer 'ana!e%ent $hell@

Set-Cs$dgeSer*er -Identity $dgeSer*er'st(-edge-00(/contoso/co-#ediaCounicationPortStart 0801 -#ediaCounicationPortCount 210

If its required to si%ultaneously confi!ure all the Dd!e $erers in your or!ani/ation, you can run thefollo#in! Lync $erer 'ana!e%ent $hell c%dlet this is an e9a%ple6@

)et-CsSer*ice -$dgeSer*er + !or$ach-,bect Set-Cs$dgeSer*er -Identity%3/Identity -#ediaCounicationPortStart 0801 -#ediaCounicationPortCount2104

"fter you set %edia port ran!es, you can erify the current port settin!s for your Dd!e $erers -y runnin!

the follo#in! Lync $erer 'ana!e%ent $hell c%dlet@

)et-CsSer*ice -$dgeSer*er + Select-,bect Identity.#ediaCounicationPortStart. #ediaCounicationPortCount

2..8 9erifyin* Manual 0ort !onfi*uration : !lient 'ie

"fter you set the ran!e of %edia ports fro% a Lync client policy perspectie, you can erify that the

allocated %edia port ran!es defined are -ein! used -y the Lync client per %odality, as e9pected7 (o this

-y first e9itin! 'icrosoft ;ffice )o%%unicator, and then relaunchin! it, to %a*e sure that the update

%edia port confi!uration assi!ned is proisioned and receied -y the Lync client, accordin!ly7

"fter successfully lo!!in! in to the Lync 2010 client, open the Lync client trace lo!s LyncUcc"pi

07Ucc"pilo!6, #hich are !enerally located in the follo#in! path@

)@RUsersRSPUserna%ePTR"pp(ataRLocalR'icrosoftR;fficeR1E70RLyncRracin!RLyncUcc"pi07Ucc"pilo!

2..1; 9erifyin* t$e

utility7 or details, see M'icrosoft Lync $erer 2013 (e-u!!in! oolsM at http@!o7%icrosoft7co%f#lin*p

Lin*IdN3013376 $earch for the indicated settin!s as illustrated in this e9a%ple6 to help ensure that

youe set the appropriate port ran!es per %odality, as part of the client lo!in and in-and policy proision

process7

2..11!onfi*ure


33/133


.orts E0,000 thru E0,01 "ssi!ned to oice scenarios@

o Suc'in"udio.ortT8----Suc'in"udio.ortT

o Suc'a9"udio.ortT8--$@Suc'a9"udio.ortT

.orts E0,020 thru E0,03 "ssi!ned to ideo scenarios@

o Suc'in5ideo.ortT8---Suc'in5ideo.ortT

o Suc'a95ideo.ortT8--.@Suc'a95ideo.ortT

.orts E0,040 thru E0,0E "ssi!ned to application sharin! scenarios@

o Suc'in"pp$harin!.ortT8--7-Suc'in"pp$harin!.ortT

o Suc'a9"pp$harin!.ortT8--8@Suc'a9"pp$harin!.ortT

.orts E0,040 thru E0,0E "ssi!ned to file transfer scenarios@

o Suc'inileransfer.ortT8--7-Suc'inileransfer.ortT

o Suc'a9ileransfer.ortT8--8@Suc'a9ileransfer.ortT

2..12 9erifyin* Manual 0ort !onfi*uration : 'erver 'ie

he ne9t step, fro% a serer perspectie, is to %a*e sure that the appropriate port nu%-er and %edia

ran!e per %odality are confi!ured, -ased on runnin! the follo#in! +indo#s .o#er$hell c%dlets, and

dependin! on the Lync $erer 2013 role type@

Lync $erer 2013 "pplication $erer@

)et-CsSer*ice -ApplicationSer*er + Select-,bect Identity.AudioPortStart. AudioPortCount

Lync $erer 2013 )onferencin! $erer@

)et-CsSer*ice -ConferencingSer*er + Select-,bect Identity.AudioPortStart. AudioPortCount. VideoPortStart. VideoPortCount.AppSharingPortStart. AppSharingPortCount

Lync $erer 2013 'ediation $erer@

)et-CsSer*ice -#ediationSer*er + Select-,bect Identity.AudioPortStart. AudioPortCount

Lync $erer 2013 Dd!e $erer@

)et-CsSer*ice -$dgeSer*er + Select-,bect Identity.#ediaCounicationPortStart. #ediaCounicationPortCount

2..13 %raffic 0rioriti>ation for )eal-%ime !ommunications

By default, #heneer the follo#in! co%%unication scenarios are initiated, the Lync client atte%pts to

esta-lish realti%e co%%unications &)6 throu!h the follo#in! lo!ic@

If no %edia port ran!e confi!uration is ena-led default confi!uration6@

o Use a U(. dyna%ic ran!e of ports fro% 1024FEE3E

o Use a ). dyna%ic ran!e of ports fro% 1024FEE3E

o ). 443

If a %anual %edia port ran!e confi!uration is ena-led@

33


34/133


o Use a U(. dyna%ic ran!e of ports fro% 1024FEE3E

o Use a ). dyna%ic ran!e of ports fro% 1024FEE3E

o ). 443

Note ,n escalation of a peer"to"peer call to a conference triggers a temporary doubling of the ports in

use

o su%%ari/e the preious t#o scenarios@ By default, the client atte%pts to esta-lish a set of U(. portsfor %edia co%%unications7 If connectiity throu!h U(. is not possi-le, the client atte%pts to esta-lish

co%%unication throu!h a set of ). ports7 If neither U(. nor ). co%%unications are possi-le throu!h

a set of allocated ports, the client #ill retreat to :ust ). 443, as a less opti%al scenario7

%A 1i96i Scenarios

Lync $erer 2013 is the only ersion that has -een fully tested in +ii eniron%ents, and therefore is the

only ersion that is fully supported for +ii7 his does not %ean that older ersions #ill not #or*, -ut that

Lync $erer 2013 is the only released ersion that has -een fully tested7

2.7.1 #ack*roun

he nu%-er of deices used -y *no#led!e #or*ers is !ro#in!7 In the past, a *no#led!e #or*er #ouldhae #or*ed on a des*top co%puter, or perhaps a laptop7 In al%ost all cases, this #ould hae -een

throu!h #ired net#or* connections7

oday at 'icrosoft, for e9a%ple, %any offices hae no structured net#or* ca-lin! to des* areas7 he

aera!e 'icrosoft e%ployee has at least three unified co%%unications U)6 deices, #ith at least t#o of

the% +indo#s .hone and +indo#s & ta-let6 hain! no &J4E soc*et, as required for -ein! #ired

into the net#or*7 $i%ilarly, the %a:ority of custo%ers #ith #ho% 'icrosoft #or*s no# require a scala-le

and sta-le +ii platfor% for their #or* and personal lies7

ro% the perspectie of require%ents, runnin! realti%e co%%unications &)6 %edia oer +ii is no

different fro% runnin! &) oer a #ired connection7 In !eneral, any net#or* infrastructure, includin! +i

i, %ust -e a-le to %eet the *ey perfor%ance indicators re!ardin! net#or* characteristics7 hese

indicators, or alues, are releant een #hen %o-ile +ii connections roa% -et#een #ireless access

points +".s6 durin! periods of #ireless interference7

2.7.2 $at Is i-"i?

here are three types of +ii eniron%ents@

#nterprise 1i96i8'ultiple -ase stations that are essentially du%- and controlled -y central +iicontrollers7

*o/e 1i96i8;ften only a sin!le -ase station, occasionally #ith repeaters7

Public 1i96i8;ften sin!le access points #ith a ariety of authentication %echanis%s7

Dnterprise +ii runs in three %odes@

$tandard data transfer oer +ii7

&ealti%e co%%unications &)6 traffic fro% a static endpoint oer +ii7

&) traffic fro% a roa%in! endpoint oer +ii, traffic :u%ps -et#een +".s7

he follo#in! sections focus on the net#or* i%pact of enterprise +ii net#or*s #ith &) traffic,includin! specific factors that co%prise the enterprise +ii infrastructure7 or details a-out +ii #ithLync $erer 2010 or Lync $erer 2013, includin! reco%%endations for ho%e and pu-lic +ii scenarios,see MLync $erer 2010@ (elierin! Lync &eali%e )o%%unications oer +iiM at

34


35/133


http@!o7%icrosoft7co%f#lin*pLin*IdN23G0and MLync 2013@ (elierin! Lync 2013 &eali%e)o%%unications oer +iiM at http@!o7%icrosoft7co%f#lin*pLin*IdN23G17

%A%%$ 1ireless Standards

he oldest #ireless standard is 02711a, #hich used the E CH/ -and for trans%issions7 hese days, it is

rarely used inside, or een outside, an or!ani/ation7 he ne9t standard, 02711-, uses con!ested 274

CH/, and quic*ly -eca%e the default +ii standard7 hese standards #ere -oth launched in 17

By 2003, 02711! had appeared, -rin!in! 02711a data rates E4 '-ps6 to the 274 CH/ -and, #hich #as

preiously li%ited to 11'-ps7

In 200, the current default standard of 02711n -eca%e ratified7 his ena-les data rates of up to F00

'-ps, and increases the ran!e of the #ireless si!nal oer earlier standards7 02711n #or*s in -oth the

274 CH/ and E CH/ -ands7 he hi!h speed and coera!e up!rades #ere possi-le due to the

i%ple%entation of %ultiple inputoutput 'I';6 antennas that ena-led the sa%e total po#er output to

spread across %ultiple antennas, increasin! frequency efficiency, and, therefore, also increasin! -it rate

and coera!e7

%A%% 1i96i Multi/edia 31MM4

+ii 'ulti%edia +''6 is a +ii "lliance initiatie that proides -asic Auality of $erice Ao$6 features

to 01711 net#or*s, in a si%ilar #ay that (ifferentiated $erices )ode .oint($).6 %ar*in!s #or* #ith

#ired net#or*s7

+''capa-le #ireless access points translate ($). %ar*in!s into the equialent +'' ta! alue7

Ho#eer, %any #ireless %anufacturers do not rely on this %ethod7 Instead, they identify the traffic

strea%s used -y Lync $erer and carry out pac*et prioriti/ation -ased on this identification7

Lync $erer supports four classes of Ao$ ia +'' for +ii7 he %ost critical class is audio traffic,

#hich has the hi!hest priority7 or details a-out all the supported classes, see M(elierin! Lync 2013

&eali%e )o%%unications oer +iiM at http@!o7%icrosoft7co%f#lin*pLin*IdN23G17

%A%%. 1P Planning

he density and trans%ission po#er of the #ireless access points +".s6 is crucial to the success of a+ii eniron%ent supported -y Lync $erer7 "s preiously descri-ed, realti%e co%%unications &)6

traffic places !reater de%ands on the net#or* co%pared to standard data traffic7 $pecifically, &) traffic

needs a stron!er si!nal than plain data7 " receie si!nal stren!th &$$6 of less than FE dB% and a si!nal

tonoise ratio $&6 of under 30 dB is required to help ensure a consistently stron! Lync $erer

e9perience across #ireless net#or*s7

Its also i%portant to consider ho# e%ployees use the #ireless net#or*, and in #hat densities7 +hen

plannin! +". locations, for e9a%ple, its i%portant to not oerloo* lar!e %eetin! roo%s7

'any %anufacturers also support a de!ree of auto%atic coera!e and hard#are failure healin!7 hese

%ethods are -ased on intelli!ent al!orith%s that detect the presence of nei!h-orin! +".s and local

sources of interference7 hey can -oost trans%ission po#er to oerco%e interference or a local +".

failure, or dial -ac* trans%ission po#er to ena-le %ore +".s to coer a hi!hdensity +ii area7

2.7.3 i-"i !ertification for Lync 'erver

I9ia has -een selected -y 'icrosoft as the official test house to qualify Lync $erer a!ainst +ii

infrastructure ele%ents, such as -ase stations, and also client deices7 ;ne of the core areas tested is

#hether 'icrosoft partners +ii +'' Ao$6 settin!s #or* as e9pected8specifically, #ith the encrypted

applications flo#s that Lync $erer uses7

3E
http://go.microsoft.com/fwlink/p/?LinkId=299370http://go.microsoft.com/fwlink/p/?LinkId=299370http://go.microsoft.com/fwlink/p/?LinkId=299371http://go.microsoft.com/fwlink/p/?LinkId=299371http://go.microsoft.com/fwlink/p/?LinkId=299371http://go.microsoft.com/fwlink/p/?LinkId=299370http://go.microsoft.com/fwlink/p/?LinkId=299371http://go.microsoft.com/fwlink/p/?LinkId=299371


36/133


he testin! pro!ra% itself consists of a 200V pa!e docu%ent that descri-es a #ide ran!e of testin!

scenarios7 his lar!e test suite helps to ensure that Lync $erer traffic is treated appropriately -y the

#ireless eniron%ent, #ithout co%pro%isin! perfor%ance or security7

or a list of certified +ii equip%ent, see MInfrastructure qualified for 'icrosoft LyncM at

http@!o7%icrosoft7co%f#lin*pLin*IdN23FF7

2.7.4 i-"i !$allen*es an )ecommenations

+ii challen!es and reco%%endations include latency, +". confi!uration, and location trac*in!7

%A%7%$ 1P "on'iguration

he Lync $erer #hite papers, MLync $erer 2010@ (elierin! Lync &eali%e )o%%unications oer +i

iM at http@!o7%icrosoft7co%f#lin*pLin*IdN23G0and MLync 2013@ (elierin! Lync 2013 &eali%e

)o%%unications oer +iiM at http@!o7%icrosoft7co%f#lin*pLin*IdN23G1, address

reco%%endations and e9planations re!ardin! +i, #ith hi!hli!hts as follo#s@

'a*e sure that the density of the +". reflects #here +ii deices #ill connect fro%7

.articularly, chec* that theres sufficient density for lar!e %eetin! areas7

(isa-le 02711-7 his standard is 14 years old and uses a frequency that 02711n can use %uch

%ore effectiely7 he %a9i%u% speed that 02711- deices reach is 11'-ps7 02711n can do

300'-ps #ith the sa%e frequency ran!e7

(efault support to 02711n only7 'ore efficient use of the frequencies aaila-le in -oth radio

stac*s 274 W E CH/6, and -etter coera!e than older standards7

Dna-le +'' Ao$6 on the #ireless and #ired infrastructure -ecause the -ac*haul #ired net#or*

%ust also support the Ao$ %ar*in! not :ust the +ii +".s67

'a*e sure that the +". supports -oth radio stac*s 274 W E CH/6, and that clients are steered

to#ard a -and#idth of E CH/7 his allo#s for !reater +". density and has less interference fro%

other radio deices that operate in the 274 CH/ -and8for e9a%ple, (i!ital Dnhanced )ordless

eleco%%unications (D)6 phones, %icro#aes, #ireless *ey-oards, #ireless !a%in!

controllers, and Bluetooth deices7

2.7./ Ne=t 'teps

here are three options for you, as a net#or* ad%inistrator, to help you understand your or!ani/ations

#ireless infrastructure and to deter%ine if up!rades are needed7 he options escalate in price@

$i%ple +ii scan

$pectru% scan

+ii assess%ent

%A%8%$ Si/ple 1i96i Scan

here are %any tools that analy/e the local #ireless eniron%ent and proide a list of all the +ii access

points and the +ii net#or* types that they support7

;ne of the -etter e9a%ples@ " free tool, In$$I(er, fro% 'etaCee*7

he follo#in! fi!ure sho#s a si%ple scan #ith the In$$I(er, ta*en fro% a ho%e location8a s%all illa!e

in the United Kin!do% UK67 he scan sho#s a fairly -usy 274 CH/ spectru% #ith nothin! -ein! used in

the E CH/ spectru%7 It also sho#s the +ii type, encryption, and %anufacturer, co%plete #ith channel

3F
http://go.microsoft.com/fwlink/p/?LinkId=299366http://go.microsoft.com/fwlink/p/?LinkId=299366http://go.microsoft.com/fwlink/p/?LinkId=299370http://go.microsoft.com/fwlink/p/?LinkId=299370http://go.microsoft.com/fwlink/p/?LinkId=299371http://www.metageek.net/http://go.microsoft.com/fwlink/p/?LinkId=299366http://go.microsoft.com/fwlink/p/?LinkId=299370http://go.microsoft.com/fwlink/p/?LinkId=299371http://www.metageek.net/


37/133


usa!e, to indicate ho# con!ested the air#aes are7 his infor%ation helps in plannin! an i%proed +ii

serice7 In this e9a%ple, a %oe to the E CH/ spectru% #ould -rin! o-ious adanta!es7

he fi!ure also sho#s that the +". for the hi!hli!hted +ii net#or* )ore6 is usin! 02711n, co%plete

#ith 'I';, -ecause t#o +ii channels are -ein! used to !ie a %a9i%u% connection speed of 300

'-s7

Si/ple 1i96i Scan Using &nSS&0er Tool 'ro/ MetaGeek

%A%8% Spectru/ Scan

e9t, youll need to chec* for #ireless interference, includin! non+ii radio deices7 Because specialist

hard#are is required to analy/e the spectru%, costs are typically inoled7 In the follo#in! fi!ure, aspectru% scan that uses the )hanaly/er fro% 'etaCee* sho#s an e9pected spi*e in -and#idth usa!e

around channel 1 in the 274 CH/ spectru%, #hich corresponds to the core net#or* in the precedin!

fi!ure7 he spi*es in the 1013 channel ran!e are li*ely fro% cordless phones, #ireless *ey-oards, and

%ouse deices in the icinity7 he use of Bluetooth and cordless headsets can hae a si!nificant i%pact

on +ii, leadin! to poor audio quality7

3G


38/133


Spectru/ Scan Using "hanaly(er 'ro/ MetaGeek

%A%8%. 1i96i ssess/ent

he third option8a full assess%ent proided -y a #ireless assess%ent professional, includin! a for%al

reportrequires the lar!est financial inest%ent, -ut this option is also he %ost co%prehensie one,

addressin! eerythin! fro% the client deice driers to the +". desi!n, includin! heat %aps for oice and

ideo coera!e throu!hout custo%ers offices7 If youre thin*in! of hain! a +ii assess%ent carried out

on your #ireless infrastructure, consider the follo#in! areas@

.reassess%ent questionnai

lync server networking guide v2.1

Documents

ntroductionicrosoft

erer ecosyste

ith e9istin

e unifiedco

unications soft

hese phases

ith khi infor

ord docu