[wpseo_breadcrumb]
What you need to know:
Webex Calling now includes a dedicated cloud instance option based on the Cisco Unified Communications Manager architecture. Dedicated Instance (DI) is an add-on to Webex Calling that uses the services provided by the Webex platform to provide centralized administration and applicable cloud innovation that can be developed anywhere on the Webex platform to improve the calling experience. Dedicated Instance is compatible with older Cisco endpoints and essential business workflow integrations.
This guide provides information about Enhanced Survivability for Webex Calling Dedicated Instance.
Introduction
Should a customer’s network outage or a cloud outage prevent users at that site from connecting to Webex Calling Dedicated Instance, the Enhanced Survivability Node actively takes over the call routing responsibility. The Enhanced Survivability Node will process all Intra-site, PSTN, and Emergency calls for the users on that site during the outage.
The Enhanced Survivability Node is used when:
- There is a Customer Network outage – e.g., WAN or ISP outage.
- The Dedicated Instance Calling service is unavailable.
Overview
A Unified CM node deployed in the Customer’s data center connects to the Dedicated Instance Unified CM Cluster as an Enhanced Survivability Node.
During a survivability event, all the devices and third-party integrations that support the Enhanced Survivability Node will failover.
Key specifications for an Enhanced Survivability Node include:
- A maximum of 8 Enhanced Survivability Nodes can be deployed in a single Unified CM cluster.
- The round-trip time (RTT) between the Unified CM cluster in Dedicated Instance and the enhanced survivability node should be equal to or less than 200 milliseconds.
- A maximum of 7500 devices can be registered on the Enhanced Survivability Node during an event of Survivability.
- The feature is supported only on Edge or Partner Connect, cloud connectivity options.
The following table compares features between SRST and the Enhanced Survivability Node:
|
Call Scenarios |
SRST |
Enhanced Survivability Node |
|
Basic and Supplementary Calls (Inbound, Outbound, Hold/Resume) |
Yes |
Yes |
|
PSTN Calls |
Yes |
Yes |
|
Nomadic E911 Support |
Yes |
Yes |
|
EPIC CRM Integration |
No |
Yes |
|
CTI Integration |
No |
Yes |
|
SIP Integrations |
Yes |
Yes |
|
Paging Support (with CTI) |
No |
Yes |
Enhanced Survivability Node Prerequisites
Firewall, DNS, and proxy server settings must be completed before continuing with the enhanced survivability node installation and activation.
- The Customer’s Firewall should allow the mentioned ports for the Enhanced Survivability Node to reach the publisher deployed in the Dedicated Instance data center.
- The Customer’s Firewall must allow the below-mentioned ports for the Enhanced Survivability Node to reach the publisher deployed in the Dedicated Instance data center.
Note: *ESN: Enhanced Survivability Node.
List of ports to be allowed in the customer firewall
| Protocol | TCP/UDP | Source | Destination | Source Port | Destination Port | Direction | Purpose |
| SFTP | TCP | ESN | Unified CM | Greater than1023 | 22 | Bidirectional | Administration |
| SSH | TCP | CiscoMonitoring Tool | ESN | Greater than 1023 | 22 | >Unidirectional | Administration |
| NTP | UDP | ESN | Unified CM | Greater than1023 | 123 | Bidirectional | Clock sync to Publisher |
| SNMP | UDP | Cisco Monitoring Tool | ESN | Greater than1023 | 161 | Bidirectional | Monitoring |
| SNMP | UDP | ESN | Cisco Monitoring servers | Greater than1023 | 162 | Bidirectional | Monitoring |
| Monitoring | TCP | Cisco monitoring tool | ESN | Greater than 1023 | 443 | Bidirectional | Monitoring |
| Syslog | UDP | ESN | Cisco Monitoring servers | Greater than1023 | 514 | Bidirectional |
Monitoring
|
| Cisco AMC Service | TCP | ESN | Unified CM | Greater than1023 | 1090 | Bidirectional | Monitoring |
| Cisco AMC Service | TCP | ESN | Unified CM | Greater than1023 | 1099 | Bidirectional | Monitoring |
| Database Connection | TCP | ESN | Unified CM | Greater than1023 | 1500 | Bidirectional | Database Replication |
| Database Connection | TCP | ESN | Unified CM | Greater than1023 | 1501 | Bidirectional | Database Replication |
| Database Connection | TCP | ESN | Unified CM | Greater than1023 | 1510 | Bidirectional | Database Replication |
| Database Connection | TCP | ESN | Unified CM | Greater than1023 | 1511 | Bidirectional | Database Replication |
| Database Connection | TCP | ESN | Unified CM | Greater than1023 | 1515 | Bidirectional | Database Replication |
| Cisco Extended Functions DB Replication | TCP | ESN | Unified CM | Greater than1023 | 2551 | Bidirectional | Database Replication |
| Cisco Extended Functions DB Replication | TCP | ESN | Unified CM | Greater than1023 | 2552 | Bidirectional | Database Replication |
| RIS server | TCP | ESN | Unified CM | Greater than1023 | 2555 | Bidirectional | Monitoring |
| RIS client | TCP | ESN | Unified CM | Greater than1023 | 2556 | Bidirectional | Monitoring |
| CTI | TCP | ESN | Unified CM | Greater than1023 | 2748 | Bidirectional | Call Control |
| Trunk-based SIP service | TCP | ESN | Unified CM | Greater than1023 | 5060 | Bidirectional | SIP service |
| Trunk-based SIP service | TCP | ESN | Unified CM | Greater than1023 | 5061 | Bidirectional | SIP service |
| Database change notification | TCP | ESN | Unified CM | Greater than1023 | 8001 | Bidirectional | Database Replication |
| SDL | TCP | ESN | Unified CM | Greater than1023 | 8002 | Bidirectional | Call Control |
| SDL (CTI) | TCP | ESN | Unified CM | Greater than1023 | 8003 | Bidirectional | Call Control |
| Diagnosis | TCP | ESN | Unified CM | Greater than1023 | 8080 | Bidirectional | Monitoring |
| Cisco Control Centre between Nodes | TCP | ESN | Unified CM | Greater than1023 | 8443 | Bidirectional | Cisco Control Center between Nodes |
| Monitoring | TCP | Cisco Monitoring Tool | ESN | Greater than1023 | 8443 | Bidirectional | Monitoring |
| Intra Cluster Replication | TCP | ESN | Unified CM | Greater than1023 | 8500 | Bidirectional | Database Replication |
| Location Bandwidth Manager | TCP | ESN | Unified CM | Greater than1023 | 9004 | Bidirectional | Call Control |
| Secure Websocket | TCP | ESN | Unified CM | 9560 | n/a | Bidirectional | LPNS notification from DI cloud |
| Connectivity Validation | ICMP | ESN | Unified CM | n/a | n/a | - | Ping |
Permitted IPs in the Firewall
The following IP addresses need to be added to the Customer’s firewall for the Enhanced Survivability Nodes to communicate with the monitoring tools deployed in Dedicated Instance.
|
Dedicated Instance Region |
Subnet |
|
U.S |
69.168.17.0/24 |
|
EMEA |
178.215.138.0/24 |
|
EU |
178.215.131.0/24 |
|
APJC |
103.232.71.0/24 |
|
AUS |
178.215.128.0/24 |
Proxy Settings
The enhanced Survivability node has a module that needs to register to Cisco's telemetry cloud. This requires the node to reach the cloud over the Internet. For the same, there can be proxy servers used or not. There are three different options to configure the Enhanced Survivability Node to reach the Cisco Cloud:
If you do not have a proxy to reach the Internet, then the Enhanced Survivability Node can reach the Cisco Cloud directly without any proxy server
You configure the proxy server settings in the Enhanced Survivability Node.
You provide the proxy server details in the Control Hub Enhanced Survivability activation form, and we configure the proxy server details in the Enhanced Survivability Node during the activation.
If a proxy server is present on the customer’s site, then the following URLs need to be allowed in the Firewall > Proxy server and firewall:
|
URLs |
Purpose |
|
*.ucmgmt.cisco.com |
Control Hub |
|
*.webex.com |
Telemetry |
Visualization Specification
Enhanced Survivability for Webex Calling Dedicated Instance requires Unified CM version of v14 SU3 or above.
9951, 8861, 8961, and 7861 phone models display the survivability event text “Service Interruption. Few features may not be available currently” during the failover in the survivability event.
The following are the OVA specifications for the Enhanced Survivability Node:
| Supported Versions of VMware vSphere ESXi= 6.7, 7.0 U1 | ||||||
| Application | OVA Size | Virtual Machine Configuration Requirements | ||||
| vCPU | Physical CPU Base Frequency | vRAM | vDisk | vNIC | ||
| Enhanced Survivability Node | Medium | 2 | 2.50+ GHz | 8 GB | 1 x 110 GB | 1 (1GbE+) |
Note: Enable LPNS in the Dedicated Instance Unified CM cluster for your Apple iOS devices to get notifications during the survivability event.
Enable Enhanced Survivability
Once the Enhanced Survivability feature has been added to the subscription, you must enable the feature for a particular region in Control Hub, where the Enhanced Survivability Node will be deployed.
