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

1-12
SBM Overview
SBM Role in a Microsoft UC&C Solution
Figure 1-5. Remote Peer-to-Peer Call
These basic steps occur when the branch user is the calling party:
1. The branch user’s Lync client contacts the SBM as its Front-End Server
(registrar). It uses SIP, a protocol for establishing communication ses-
sions. The client and SBM communicate on one of the following TCP
ports:
• TCP 5061 when TLS, which provides encryption, is used
• TCP 5060 when TLS is not used
Note If you have an existing Lync solution, you know that clients typically find the
Lync services using a DNS service record. When you add the SBM to the Lync
topology and assign users to its pool (as you will learn how to do in this guide),
the clients will automatically be directed to the SBM. You do not need to alter
the existing service records.
2. The SBM routes the call toward the correct location, drawing on routing
rules that the Conferencing Server (CS) Administrator defined for the
branch site and potentially for that particular user. Note that the SBM can
query Front-End servers at other sites to find the called party.