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.0
Page 91 of 104
Appendix 6 – B2BUA registration on
“OCS/Lync gateway” VCSs
“OCS/Lync gateway” VCSs
The B2BUA registration function allows personal video endpoints to appear in a similar manner to an
endpoint registered directly to OCS/Lync Server with the same credentials as an existing OCS/Lync
user, but still maintain the benefits of having the endpoint register to the Cisco VCS which is designed
to support video calling.
endpoint registered directly to OCS/Lync Server with the same credentials as an existing OCS/Lync
user, but still maintain the benefits of having the endpoint register to the Cisco VCS which is designed
to support video calling.
The B2BUA registration function also means that the user credentials are no longer needed on each
individual video endpoint. This is possible because the Cisco VCS B2BUA is configured as a trusted
host to OCS/Lync Server. This simplifies the long term endpoint management since passwords do not
need to be regularly updated on the video endpoints.
individual video endpoint. This is possible because the Cisco VCS B2BUA is configured as a trusted
host to OCS/Lync Server. This simplifies the long term endpoint management since passwords do not
need to be regularly updated on the video endpoints.
What does “Register FindMe users as clients” in
OCS/Lync do?
OCS/Lync do?
When enabled, FindMe users that are in the shared domain with OCS/Lync are registered to
OCS/Lync Server so that they appear like MOC/Lync clients.
This means that if a MOC/Lync client registers to OCS/Lync Server, and a FindMe user is registered
as that same user to OCS/Lync Server, when the user is called by another MOC/Lync client, the call
will be forked to both the registered MOC/Lync client and also to the VCS’s FindMe. This means that
MOC/Lync clients and all video endpoints configured as primary devices in the FindMe will ring when
called at the MOC/Lync client address.
Without registering the shared domain FindMe user, OCS/Lync Server will not fork the call to Cisco
VCS, but:
OCS/Lync Server so that they appear like MOC/Lync clients.
This means that if a MOC/Lync client registers to OCS/Lync Server, and a FindMe user is registered
as that same user to OCS/Lync Server, when the user is called by another MOC/Lync client, the call
will be forked to both the registered MOC/Lync client and also to the VCS’s FindMe. This means that
MOC/Lync clients and all video endpoints configured as primary devices in the FindMe will ring when
called at the MOC/Lync client address.
Without registering the shared domain FindMe user, OCS/Lync Server will not fork the call to Cisco
VCS, but:
if a MOC/Lync client is registered with the called address then just that MOC/Lync client will ring.
if there is no MOC/Lync client registered but there is a static domain route to the Cisco VCS for
that domain the call will be routed to Cisco VCS to handle.
that domain the call will be routed to Cisco VCS to handle.
if there is no MOC/Lync client registered and there is no static domain route for this call then the
call will just fail.
call will just fail.
Note that OCS/Lync Server only allows FindMe users to register if the FindMe ID being registered is a
valid user in the OCS/Lync Active Directory (in the same way that MOC/Lync clients can only register
if they have a valid account enabled in the OCS/Lync AD).
valid user in the OCS/Lync Active Directory (in the same way that MOC/Lync clients can only register
if they have a valid account enabled in the OCS/Lync AD).
Registering FindMe users also allows the presence of these users to be provided to OCS/Lync
Server and for ‘in-call’ as well as ‘available’ and ‘off-line’ status to be provided.
•
Server and for ‘in-call’ as well as ‘available’ and ‘off-line’ status to be provided.
•
Endpoint devices and FindMe entries that are not registered to OCS/Lync Server can only
communicate ‘available’ and ‘off-line’ status to OCS/Lync server.
communicate ‘available’ and ‘off-line’ status to OCS/Lync server.
Note that the “OCS/Lync gateway” VCS (or VCSs) must host the presence server for the domain
shared with OCS/Lync (ciscotp.com) in order for presence to be provided to OCS/Lync Server.
shared with OCS/Lync (ciscotp.com) in order for presence to be provided to OCS/Lync Server.
The “OCS/Lync gateway” VCS must also host the presence server for the domain of the video network
(vc.ciscotp.com). This is because presence of a FindMe entry can only be provided if the presence
status of the device(s) in the active location of the FindMe entry are hosted on the “OCS/Lync
gateway” VCS.
(vc.ciscotp.com). This is because presence of a FindMe entry can only be provided if the presence
status of the device(s) in the active location of the FindMe entry are hosted on the “OCS/Lync
gateway” VCS.
If FindMe entries contain multiple devices in the active location, VCS will aggregate the presence of
those devices whose presence is hosted on the “OCS/Lync gateway” VCS and present the
appropriate overall presence status.
those devices whose presence is hosted on the “OCS/Lync gateway” VCS and present the
appropriate overall presence status.
Use of FindMe also allows any endpoint that is referred to in the FindMe to take on the caller ID of that
FindMe entry. This means that whichever video endpoint makes the call, the receiving MOC/Lync
client and video endpoints will see the call as having come from the FindMe ID. This is especially
FindMe entry. This means that whichever video endpoint makes the call, the receiving MOC/Lync
client and video endpoints will see the call as having come from the FindMe ID. This is especially