IP Office Technical Bulletin number 145
COMPAS ID 157236 Issue 2
Page 20 of 59
Server Edition Resiliency
IP Office resiliency can be divided into three distinct categories. The primary server
and secondary server can each support up-to 1000 users in resilient mode
Note: The Primary and Secondary servers can be co-located or can be on separate
locations to support Geo-Redundancy.
1.
Hardware Resiliency
o
RAID support
o
Dual PSU on Avaya sourced HP DL360G7
2.
Users and Application Resiliency
o
VoiceMail Pro server – P Backup in 1+1 redundant
active/passive configuration. Manual or auto failback control (auto is
new for R8.1)
o
IP Phones – 1:1 resilience to backup IP Office. Manual failback control
(Phone reset). Avaya 16xx/96xx H.323 phones only. Note Expansion
systems (gateways) cannot act as backup nodes for the Linux Servers
o
Hunt groups - 1:1 resilience to backup Server. Auto failback control
(device rediscovery – idle group)
o
Inter IP Office device links – Multi-Site Network (SCN) backup. Double
star. 1:1 resilience. Auto failback control (device rediscovery)
o
Inter IP Office device links – PSTN backup. M:N resilience via
Alternate Route Selection (ARS). Auto failback control (link availability)
o
Trunks – M: N resilience via ARS. Auto failback control (trunk
availability)
o
Incoming Call Routes – Incoming Call Routes are common to all
devices hence persist on user failover
3.
Trunk Resiliency
o
PSTN Back-up
By default resilience is setup between the Primary and Secondary server when it is
present. The secondary will backup the Voicemail, Hunt groups and users from the
Primary, and the Primary will backup the users from the Secondary.
Any IP phones on expansion systems are not backed up by default. Clicking on the
Resilience option in Server Edition manager will allow you to setup the IP phone
resilience options. Phones from each expansion system can be backed up by either
the primary or the secondary, it is not possible to split them between servers.