HP Survivable Branch Communication zl Module powered by Microsoft Lync Planning and Design Guide 2011-02

3-8
Ready the Data Center for an SBM Deployment
Add the Survivable Branch to the Lync Server Topology
4. You must now determine whether you also want to apply Media Bypass
to calls from the branch that are routed out a PSTN gateway at the central
site. Look at your bandwidth estimates for these calls. Does your WAN
connection provide enough bandwidth if the calls use the G.711 codec as
opposed to the RTAudio codec? Remember to take into account the fact
that other traffic will travel over the WAN link. The link needs to provide
enough bandwidth comfortably.
If you decide that the link provides sufficient bandwidth, define no
bandwidth constraints in the Lync Server Control Panel on the WAN
link between the branch and the central site. Media Bypass will apply
to all PSTN calls routed to the central site and through the SBM.
Otherwise, configure the bandwidth constraints. Only PSTN calls
from branch users that are routed through the SBM will use Media
Bypass.
If you have not already done so, enable Media Bypass based on region and site
configuration.
Create a CS Health Monitoring Pool
The SBM Setup Wizard includes a test that verifies that branch Lync users can
successfully place calls through the PSTN. To generate the test calls, the SBM
draws on the user accounts within its Health Monitoring pool.
You must create a pool for which the identity is the SBM’s FQDN. The pool
also contains the SIP usernames (sip:<sip name>) for two valid Lync users
within the SBM’s pool. Typically, you should specify user accounts specifically
created for the test, but you can use any accounts assigned to the SBM pool.
Note You must use the Lync Server Management Shell to create the Health Moni-
toring pool. The cmdlet is New-CsHealthMonitoringConfiguration.