Neighboring The Local Vcs To Another Vcs Cluster - Cisco TelePresence Administrator's Manual

Calls between two endpoints registered to different peers in the cluster.
n
For example, Endpoint A is registered in the Default Subzone to Peer 1. Endpoint B is also registered in the
Default Subzone, but to Peer 2. When A calls B, the call route is shown on Peer 1 as Default Subzone ->
Cluster Subzone, and on Peer 2 as Cluster Subzone -> Default Subzone.
Calls received from outside the cluster by one peer, for an endpoint registered to another peer.
n
For example, we have a single VCS for the Branch Office, which is neighbored to a cluster of 4 VCSs at the
Head Office. A user in the Branch Office calls Endpoint A in the Head Office. Endpoint A is registered in the
Default Subzone to Peer 1. The call is received by Peer 2, as it has the lowest resource usage at that
moment. Peer 2 then searches for Endpoint A within the cluster's Local Zone, and finds that it is registered
to Peer 1. Peer 2 then forwards the call to Peer 1, which forwards it to Endpoint A. In this case, on Peer 2
the call route will be shown as Branch Office -> Default Subzone -> Cluster Subzone, and on Peer 1 as
Cluster Subzone -> Default Subzone.
Note that if Call routed mode is set to Optimal and the call is H.323, the call will not appear on Peer 2, and
on Peer 1 the route will be Branch Office > Default Subzone.

Neighboring the local VCS to another VCS cluster

You can neighbor your local VCS (or VCS cluster) to a remote VCS cluster; this remote cluster could be a
neighbor, traversal client, or traversal server to your local VCS. In this case, when a call is received on your
local VCS and is passed via the relevant zone to the remote cluster, it will be routed to whichever peer in that
neighboring cluster has the lowest resource usage. That peer will then forward the call as appropriate to one
of its:
locally registered endpoints (if the endpoint is registered to that peer)
n
peers (if the endpoint is registered to another peer in that cluster)
n
external zones (if the endpoint has been located elsewhere)
n
When configuring a connection to a remote cluster, you create a single zone and configure it with details of all
the peers in the cluster. Adding this information to the zone ensures that the call is passed to that cluster
regardless of the status of the individual peers.
You also need to enter the IP address of all peers in the remote cluster when the connection is via a
neighbor or traversal client zone. You do not do this for traversal server zones, as these connections are
not configured by specifying the remote system's IP address.
Note: systems that are configured as peers must not also be configured as neighbors to each other, and vice
versa.
Neighboring your clusters
To neighbor your local VCS (or VCS cluster) to a remote VCS cluster, you create a single zone to represent
the cluster and configure it with the details of all the peers in that cluster:
1. On your local VCS (or, if the local VCS is a cluster, on the master peer),
type. This zone will represent the connection to the cluster.
2. In the Location section, enter the IP address or FQDN of each peer in the remote cluster in the Peer 1 to
Peer 6 address fields.
Note that:
Cisco VCS Administrator Guide (X7.2)
Clustering and peers
create a zone of the appropriate
Page 158 of 498