Cisco WebEx Meetings Server Troubleshooting Guide for Version 2.5 and Earlier

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco WebEx Meetings Server Troubleshooting Guide for Version 2.5 and Earlier

Chapter Title

Disaster Recovery

Results

Updated:
October 24, 2014

Chapter: Disaster Recovery

Disaster Recovery

This section includes troubleshooting topics about disaster recovery.

Audio Conferencing Fails after Disaster Recovery is Performed on a Multi-data-Center System

Problem    On a secure teleconferencing system, your audio conferencing is not working after performing disaster recovery on a Multi-data Center (MDC) system.
Possible Cause    The Cisco Unified Call Manager (CUCM) SIP trunk configuration is not updated. Before you perform the disaster recovery procedure, the application point and load balance point SIP trunks are configured with X.509 SIP trunk security profiles. At your primary data center, your SIP trunks are configured with X.509 SIP trunk security profiles in that data center. At your secondary data center, the SIP trunks are configured with X.509 SIP trunk security profiles in that data center. Each SIP trunk security profile is indicated by its URL.
After disaster recovery, the restored secondary data center is assigned the SIP trunk security profile URL of the primary data center. This causes your audio conferencing features to fail. See the tables below for the required configurations for both data centers before disaster recovery.
Table 1 First Data Center Configuration Before Disaster Recovery
SIP Trunk SIP Trunk Security Profile: X.509 Subject Name
SIP trunk for a load balance point at the first data center Site URL for the first data center (FQDN format)
SIP trunk for an application point at the first data center Site URL for the first data center (FQDN format)
Table 2 Second Data Center Configuration Before Disaster Recovery
SIP Trunk SIP Trunk Security Profile: X.509 Subject Name
SIP trunk for a load balance point at the second data center Site URL for the second data center (FQDN format)
SIP trunk for an application point at the second data center Site URL for the second data center (FQDN format)
Launch CUCM and change the SIP trunk security profile for your secondary data center to the URL of the primary data center in the X.509 Subject field. See the table below for the required configuration of your secondary data center after disaster recovery. Refer to the "Using the Disaster Recovery Feature" section of the Cisco WebEx Meetings Server Administration Guide for more information on disaster recovery. Refer to the "Configuring Cisco Unified Communications Manager (CUCM)" section of the Cisco WebEx Meetings Center Planning Guide at http:/​/​www.cisco.com/​c/​en/​us/​support/​conferencing/​webex-meetings-server/​products-installation-and-configuration-guides-list.html for more information on configuring CUCM.
Table 3 Second Data Center Configuration After Disaster Recovery
SIP Trunk SIP Trunk Security Profile: X.509 Subject Name
SIP trunk for a load balance point at the second data center Site URL for the first data center (FQDN format)
SIP trunk for an application point at the second data center Site URL for the first data center (FQDN format)

Was this Document Helpful?

FeedbackFeedback

Contact Cisco