Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 6 – B2BUA registration on “OCS/Lync gateway” VCSs
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.1
Page 92 of 104
useful when the called party wishes to return the call; the return call calls the FindMe ID resulting in all
endpoints relating to this FindMe and any MOC/Lync clients registered with this ID all ringing
simultaneously – rather than the return call being addressed directly to the single endpoint that made
the call.
endpoints relating to this FindMe and any MOC/Lync clients registered with this ID all ringing
simultaneously – rather than the return call being addressed directly to the single endpoint that made
the call.
Registered users with a cluster of Cisco VCSs
When the “OCS/Lync gateway” VCS is a cluster of Cisco VCSs, the shared domain FindMe users will
be shared across cluster peers (using an algorithmic distribution scheme). Each cluster peer will
register its FindMe users to OCS/Lync Server. When calls are made from OCS/Lync Server to the
VCS B2BUA, OCS/Lync Server will send the call to the VCS peer that registered that user – hence the
calls are statically load-shared across the VCS peers.
be shared across cluster peers (using an algorithmic distribution scheme). Each cluster peer will
register its FindMe users to OCS/Lync Server. When calls are made from OCS/Lync Server to the
VCS B2BUA, OCS/Lync Server will send the call to the VCS peer that registered that user – hence the
calls are statically load-shared across the VCS peers.
Configuring domains
It is best practice to keep the video endpoints in their own domain, and just have the FindMe users on
the “OCS/Lync gateway” VCS with the same domain as OCS/Lync Server. This avoids any confusion
as to what functionality will be received for each entity. When a call arrives for the FindMe user,
FindMe will forward calls appropriately to the defined endpoints, whichever domain they are in.
the “OCS/Lync gateway” VCS with the same domain as OCS/Lync Server. This avoids any confusion
as to what functionality will be received for each entity. When a call arrives for the FindMe user,
FindMe will forward calls appropriately to the defined endpoints, whichever domain they are in.
For example, when alice.parkes@ciscotp.com is called, the call will fork to the MOC/Lync client with
the same name, and also to alice.parkes.office@vc.ciscotp.com and
alice.parkes.external@ciscotp.com (assuming that these two devices are listed as primary devices in
Alice Parkes’ FindMe.)
the same name, and also to alice.parkes.office@vc.ciscotp.com and
alice.parkes.external@ciscotp.com (assuming that these two devices are listed as primary devices in
Alice Parkes’ FindMe.)
It is strongly recommended that the user is created on the OCS/Lync Server first and signed in to
at least once from a MOC/Lync client. 5 to 10 minutes later the FindMe account can be created
on the “OCS/Lync gateway” VCS once the user is fully available on OCS/Lync server.
at least once from a MOC/Lync client. 5 to 10 minutes later the FindMe account can be created
on the “OCS/Lync gateway” VCS once the user is fully available on OCS/Lync server.
If a cluster of VCSs is used for the “OCS/Lync gateway” then TMS is required to replicate FindMe
details across the cluster peers. See the relevant VCS cluster deployment guide for further details on
this.
details across the cluster peers. See the relevant VCS cluster deployment guide for further details on
this.