Cisco Unity Connection Network Design for Large Client: Valid Designs for 12 Locations

# Designing a Cisco Unity Connection Network: Valid Designs for 12 Locations

### Question

A collaboration engineer is designing a Cisco Unity Connection network for a large client running 10 x.

The client has 12 locations, each with their own Cisco Unity Connection cluster.

Which two designs are valid? (Choose two)

### Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

BE.

The scenario given in the question states that a collaboration engineer is designing a Cisco Unity Connection network for a large client running 10 x, which has 12 locations, each with their own Cisco Unity Connection cluster. The task is to choose two valid designs from the given options.

A. Full-Mesh Topology with HTTPS Networking: In this design, all the Unity Connection clusters would be connected to one another in a full-mesh topology using HTTPS networking. Each Unity Connection cluster would have direct connectivity with every other Unity Connection cluster, resulting in a fully connected network. While this design provides high resiliency and redundancy, it can be challenging to maintain as the number of clusters grows.

B. Six Clusters Each in Two Full-Mesh Unity Connection Digital Networks Connected with VPIM: This design involves dividing the 12 Unity Connection clusters into two groups of six clusters, which are then connected in a full-mesh topology using Unity Connection Digital Networking. The two networks would be connected using VPIM (Voice Profile for Internet Mail) to enable voicemail message exchange between them. This design provides high resiliency and redundancy and reduces the complexity of the network by dividing it into two smaller networks.

C. Hub-and-Spoke Topology with Unity Connection Digital Networking: In this design, a single central Unity Connection cluster would act as a hub, connected to the remaining 11 clusters in a spoke configuration using Unity Connection Digital Networking. This design provides centralized management and administration but can be a single point of failure.

D. A 10-Cluster Unity Connection Digital Network Connected to a 2-Cluster HTTPS Network: This design involves connecting 10 Unity Connection clusters using Unity Connection Digital Networking and the remaining two clusters using HTTPS networking. The design provides redundancy and resiliency while reducing the complexity of the network.

E. Hub-and-Spoke Topology with HTTPS Networking: Similar to option C, this design involves connecting all Unity Connection clusters in a hub-and-spoke topology, but using HTTPS networking instead of Unity Connection Digital Networking. This design provides centralized management and administration but can be a single point of failure.

F. Full-Mesh Topology with Unity Connection Digital Networking: This design involves connecting all Unity Connection clusters in a full-mesh topology using Unity Connection Digital Networking. Each Unity Connection cluster would have direct connectivity with every other Unity Connection cluster, resulting in a fully connected network. This design provides high resiliency and redundancy, but can be challenging to maintain as the number of clusters grows.

Based on the given options, the two valid designs are: B. Six Clusters Each in Two Full-Mesh Unity Connection Digital Networks Connected with VPIM, and F. Full-Mesh Topology with Unity Connection Digital Networking.

Both designs provide high resiliency and redundancy while minimizing complexity. Design B splits the clusters into two smaller networks connected with VPIM for message exchange, while Design F connects all the clusters in a fully connected network using Unity Connection Digital Networking.