Each system in the Small Community Network can include one IP Office Line where the SCN Resiliency Options is set to Supports Resiliency. The system to which the IP Office Line connects is then requested to provide fallback support for selected options for the local system.

• Note that both ends of the SCN trunk connection must be set to fallback.

• On the system requesting backup, the required SCN Resiliency Options are selected, indicating that it is requesting backup. A single system can only request backup from one other system.

• A system providing backup can provide backup for up to 7 other systems.

Resiliency is supported on Server Edition systems for Avaya 1600 and 9600 series H.323 phones. IP500 V2 systems also support 4600 and 5600 series phones. Resiliency is configured on Line | IP Office Line | Line under SCN Resiliency Options. The options supported are:

• Backs up my IP Phones

• Backs up my Hunt Groups

• Backs up my Voicemail

• Backs up my IP DECT Phones

Phone Resiliency

When Backs up my IP Phones is selected, the local system shares information about the registered phones and users on those phones with the other system. If the local system is no longer visible to the phones, the phones reregisters with the other system.

Failback Recovery If the setting System | Telephony | Telephony | Phone Failback is set to Automatic, and the phone’s primary gatekeeper has been up for more than 10 minutes, the system causes idle phones to perform a failback recovery to the original system.

Notes

• Fallback handover takes approximately 3 minutes. This ensure that fallback is not invoked when it is not required, for example when the local system is simply being rebooted to complete a non-mergeable configuration change.

• Fallback is only intended to provide basic call functionality while the cause of fallback occurring is investigated and resolved. If users make changes to their settings while in fallback, for example changing their DND mode, those changes will not apply after fallback.  

• If the fallback system is rebooted while it is providing fallback services, the fallback services are lost.

• Fallback features require that the IP devices local to each system are still able to route data to the fallback system when the local system is not available. This will typically require each system site to be using a separate data router from the system.

• When an IP Phone re-registers to a secondary IP Office on the failure of the primary control unit, the second system will allow it to operate indefinitely as a “guest”, but only until the system resets. Licenses will never be consumed for a guest IP phone.

• Remote hot desking users on H323 extensions are automatically logged out.