Library
Avaya Links
Avaya Support Site
Avaya Learning
Blogs
Videos & Podcasts
Knowledge base
Report Product bugs
English
Deutsch
English
Español (México)
Français
Français (Canada)
Italiano
Magyar
Nederlands
Polski
Português (Brasil)
Română
Русский
עברית
العربية
中文(简体)
中文(繁體)
日本語
한국어
AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Filter
No results found
Search suggestions:
Use fewer tags and filters.
Use different search terms.
Filters
Reset
Apply filter
Login
AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Filter
No results found
Search suggestions:
Use fewer tags and filters.
Use different search terms.
Filters
Reset
Apply filter
Library
Avaya Links
Avaya Support Site
Avaya Learning
Blogs
Videos & Podcasts
Knowledge base
Report Product bugs
English
Deutsch
English
Español (México)
Français
Français (Canada)
Italiano
Magyar
Nederlands
Polski
Português (Brasil)
Română
Русский
עברית
العربية
中文(简体)
中文(繁體)
日本語
한국어
Avaya Aura® Communication Manager Survivability Options
Table of Contents
Filter navigation by title
Type to filter navigation items by title
Collapse
Legal
Introduction
Purpose
Discontinued support for IP Server Interface (TN2312, commonly known as IPSI)
Intended audience
Change history
Survivability Overview
Survivable remote and core servers
Survivable remote server
Survivable core server
Primary search timer
Failover to a survivable core server
Processor Ethernet overview
Processor Ethernet functionality
Support for Processor Ethernet on a survivable core server
Processor Ethernet requirements
Optimal performance requirements
Survivable core server requirements
Survivable core server failover examples
Example one: Main servers fail
Example two: Network failure
Example three: A survivable remote server working in a survivable core server environment
Survivable Core Server design and planning
Survivable core server design strategy
Survivable core server terminology
Survivable core server prerequisites
Survivable core server worksheet
Server ID
Module Identification Number (MID)
Network port considerations
Main server and survivable core server differences
Trunking considerations
ISDN PRI non facility associated signaling
Guidelines for using ISDN PRI non facility associated signaling
E911
Inter-Gateway Alternate Routing
Personal Central Office Line
Separation of Bearer and Signaling
Data Networking
H.323 considerations when using survivable core server
Timing considerations
Primary Search Timer
Feature limitations during gateway outage
Feature considerations
Announcements
Attendant Console
Best Service Routing
Call Classification
Call Coverage
Call Vectoring
Centralized Attendant Service
Crisis Alert
CVLAN links
Dial Plan Transparency
Facility Busy Indication
Hunt Groups
Leave Word Calling
Music on Hold
Adjunct considerations
Call Detail Recording
Traditional Call Detail Recording
Survivable CDR
Call Management System
Extension to Cellular
Property Management System
Voice Mail
Voice Response System
Survivable Core Server installation
Survivable core server installation checklist
Installing a survivable core server
Checklist for installing survivable core server with existing server
Checklist for installing survivable core server with new servers
Survivable core server license files
License file for survivable servers
Station licenses for survivable servers
License files
Module IDs and Cluster IDs
System Identification numbers
MAC Address
Checking the license file
Feature Keywords
Verifying the license status
Server configuration worksheets
Network settings
Network configuration settings
Duplication parameters
Add Login
Survivable core server administration
Pre-requisites for administering a survivable core server on the main server
Survivable Processor screen
Administering page one of the Survivable Processor screen
Administering page two of Survivable Processor screen
Administering Page three of the Survivable Processor screen
Administering Page four of the Survivable Processor screen
Checking the administration on the main server
Translations
Verifying that the survivable core server has received the translations on the main server
Survivable core server conversions
Survivable core server conversion requirements
Converting the existing survivable core server to main server
Converting the existing server to survivable core server
Survivable core server management
Translations administration
Determining when the last translation is download from the main server
User enabled telephone features
Alarms
Update the main server
After a fall-back to the main server
Troubleshooting
Verifying the survivable core server translations
Verifying the survivable core server configuration
Registration
Survivable core server is not registered with the main server
Monitoring registration requests example
Survivable Core Server Acceptance Testing
Survivable core server acceptance testing
Testing transfer of control from main server to survivable core server
Testing transfer of control from survivable core server to main server
Verifying the acceptance criteria
Disabling a survivable core server from the main server
Verifying the acceptance criteria
Enabling a survivable core server from the main server
Verifying the acceptance criteria
Resources
Communication Manager documentation
Finding documents on the Avaya Support website
Accessing the port matrix document
Avaya Documentation Center navigation
Training
Viewing Avaya Mentor videos
Support
Using the Avaya InSite Knowledge Base
Glossary
CLID
Community
Main server
MID
MO
P
Preference
Priority value
Priority score
S
SAP
SSO
SVID
SVOR
Survivable Core Server
Survivable Remote Server
Home
Avaya Aura® Communication Manager Survivability Options
__references__
Unsupported platform
Unsupported platform
Share this page
On LinkedIn
On X
On Email
PDF Export Options
This Topic
Entire Document
Last Updated :
Jul 04, 2026
|
Calling and Messaging
Communication Manager
Reference Configuration
10.2.x
Table of Contents
Prolog information
Metadata
Keywords:
The following platforms are unsupported for all
Avaya
Aura®
Software-Only and Infrastructure as a Service (IaaS) deployment models:
Hypervisor: Microsoft Hyper-V
Cloud Platforms: Microsoft Azure, Google Cloud Platform (GCP), IBM Cloud
Send Feedback
In this article