Cisco Cisco TelePresence Video Communication Server Expressway
Configuring domains
It is best practice to keep the video endpoints in their own domain, and just have the FindMe users on the
“Lync gateway” VCS with the same domain as 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.
“Lync gateway” VCS with the same domain as 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 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.)
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.)
We strongly recommend that the user is created on the Lync Server first and signed in to at least once from a
Lync client. 5 to 10 minutes later the FindMe account can be created on the “Lync gateway” VCS when the
user is fully available on Lync Server.
Lync client. 5 to 10 minutes later the FindMe account can be created on the “Lync gateway” VCS when the
user is fully available on Lync Server.
B2BUA and Cisco AM GW integration
For full instructions about how to configure the Microsoft Lync B2BUA with a Cisco TelePresence Advanced
Media Gateway (Cisco AM GW), see Microsoft Lync 2010, VCS and Cisco AM GW Deployment Guide.
Media Gateway (Cisco AM GW), see Microsoft Lync 2010, VCS and Cisco AM GW Deployment Guide.
Previous versions of that document are also available for earlier, non-B2BUA VCS and Cisco AM GW
deployments.
deployments.
TEL URI handling for VCS to Lync calls
If an endpoint wants to dial a telephone number rather than selecting a user from a directory, the VCS Control
must format the telephone number appropriately for Lync to be able to look it up. Lync expects to see
telephone numbers (known as TEL: URIs) in the form: +<country code><full dialed number>
must format the telephone number appropriately for Lync to be able to look it up. Lync expects to see
telephone numbers (known as TEL: URIs) in the form: +<country code><full dialed number>
VCS Control can use transforms to appropriately format the telephone numbers. These transforms can either
be implemented globally using
be implemented globally using
Configuration > Dial plan > Transforms
or just for the Lync neighbor zone
or B2BUA neighbor zone by configuring the transform in the appropriate search rules.
For example, for 4 digit extension number dialing to be expanded to a full telephone number for a company in
the UK whose telephone number is 781xxx, an extension number 1008 would need to be expanded to
+441344781008. This can be implemented by configuring a transform as follows:
the UK whose telephone number is 781xxx, an extension number 1008 would need to be expanded to
+441344781008. This can be implemented by configuring a transform as follows:
Priority
80 (match in preference to the no transform needed rule - 80 is higher priority than 100)
Source
Any
Mode
Alias pattern match
Pattern type
Regex
Pattern string
(1…)@ciscotp\.com(.*)
Patter behavior
Replace
Replace string
+44134478\1;@ciscotp.com;user=phone\2
On successful match
Continue
Target Zone
To Microsoft Lync Server via B2BUA
Cisco TelePresence Microsoft Lync and Cisco VCS Deployment Guide (X8.2)
Page 78 of 80
Appendix 7: Additional information