This topic describes HTTPS networking, which was introduced with Cisco Unity Connection version 10.x.
Increase scalability with HTTPS networking.
In Cisco Unity Connection version 10.x, legacy networking is supported to connect multiple Cisco Unity Connection servers in a network. However, we recommended that you deploy a new network using HTTPS networking. Legacy networking includes both intrasite (digital) and intersite networking. The legacy and HTTPS networking are not supported simultaneously in the same network.
The main objective of introducing HTTPS networking is to increase the scalability and security of Cisco Unity Connection deployments. The architecture of HTTPS networking is scalable both in terms of the number of Cisco Unity Connection locations and of the total directory size.
Each location within a network uses the HTTPS protocol to exchange directory information and the SMTP protocol to exchange voice messages with each other.
The locations in an HTTPS network are linked through an HTTPS link. HTTPS networking uses a hub-and-spoke topology that plays an important role in increasing the scalability of the directory size and the number of Cisco Unity Connection locations. A hub-and-spoke topology has two types of locations: the hub location and the spoke location. The Cisco Unity Connection location that has more than one HTTPS link is known as the hub location. The Cisco Unity Connection location that has only one HTTPS link is known as the spoke location. The figure shows a network of multiple Cisco Unity Connection locations joined by HTTPS links.
In a hub-and-spoke topology, all the directory information among the spokes is shared through the hub or hubs that connect the spokes. For example, in the figure, if spoke A needs to synchronize directory information with spoke E, the directory information will flow from spoke A to hub B, hub B to hub C, hub C to hub D, and then from hub D to spoke E.
You can connect a maximum of 25 Cisco Unity Connection locations in an HTTPS network.
A single HTTPS network system supports a single site, and each site can have a maximum of 25 nodes; however, multiple HTTPS network systems can be joined using VPIM.
VPIM Networking is supported only with Cisco Business Edition 6000/7000.
If you deploy VPIM in a Unity Connection networking site, each Cisco Unity Connection digital or HTTPS network must have one server defined as the bridgehead or site gateway. The bridgehead or site gateway is used to communicate with other digital or HTTP(S) networks. The Cisco Unity Connection global directory (the entire collection of local and replicated objects and object properties) is subject to certain size limits. However, it also generates a Cisco Unified RTMT alert so that the administrator can take appropriate action. Cisco Unity Connection version 10.x has separate limits on the number of users, the number of contacts, and the number of system distribution lists:
- 100,000 users
- 150,000 contacts
- 100,000 system distribution lists
- 25,000 users per system distribution list
- 1.5 million total list members across all system distribution lists
- 20 levels of nesting (where one system distribution list is included as a member of another list)