Datasheet

Cisco Preferred Architecture for
Midmarket Collaboration PAGE 24
Conferencing
Support for Multiple Call Processing Sites
Organizations may choose to implement more than one Cisco TelePresence Conductor cluster for any of the
following reasons:
Administrational separation This includes the need to keep users from different parts of the organization on
separate infrastructures or to have different departments operate different parts of the communications
infrastructure.
Geographic footprint Physical limitations such as excessive latency between endpoints and conferencing
resources could degrade the user experience (for example, US users might not have a productive collaborative
meeting if they use conferencing resources located in Europe).
Multiple Unified CM clusters If more than one Unified CM cluster is already deployed due to the previous
reasons, Cisco recommends also deploying multiple TelePresence Conductor clusters.
Deploy multiple TelePresence Conductor clusters along with local TelePresence Server resources (Figure 11). Implement
a global dial plan, as discussed in the Call Control section, to enable users to access conferences regardless of where the
TelePresence Conductor or TelePresence Server is located.
Figure 11. Multiple Call Processing Sites with Conferencing