SCN Fallback

IP Office 5.0 provides a number of features that allows IP Offices to provide fallback functions for each other. This operation requires the IP Offices to be running IP Office 5.0+.

Each IP Office in the SCN can include one H323 line where the Supplementary Services is set to RIP Office SCN - Fallback rather than IP Office SCN. The IP Office to which the H323 line connects can then be used to provide fallback support for selected options for the local IP Office.

•	Fallback handover takes approximately 3 minutes. This ensure that fallback is not invoked when it is not required, for example when the local IP Office is simply being power cycled 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 IP Office is rebooted while it is providing fallback services, the fallback services are lost.

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

Once a line is set to IP Office SCN - Fallback, the following options are available:

•

SCN Backup Options: Software level = 5.0+.
These options are only available on when the Supplementary Services option is set to IP Office - Fallback. The IP Office system to which the trunk connects must be an IP Office 5.0+ system. The intention of this feature is to attempt to maintain a minimal level of operation while problems with the local IP Office are resolved.

•	Backs up my IP Phones: Default = On. This option is used for Avaya 1600, 4600 and 5600 Series phones registered with the IP Office. When selected, it will share information about the registered phones and users on those phones with the other IP Office.

•	If the local IP Office is no longer visible to the phones, the phones will reregister with the other IP Office. The users who were currently on those phones will appear on the other IP Office as if they had hot desked.

•	Note that when the local IP Office is restored to the SCN, the phones will not automatically re-register with it. A phone reset via either a phone power cycle or using the IP Office System Status Application is required.

•	When phones have registered with the other IP Office, they will show an R on their display.

•

Backs up my Hunt Groups: Default = On.
When selected, any hunt groups the local IP Office is advertising to the SCN are advertised from the other IP Office when fallback is required. The trigger for this occurring is Avaya H323 phones registered with the local IP Office registering with the other IP Office, ie. Backs up my IP Phones above must also be enabled.

•	When used, the only hunt group members that will be available are as follows:

•	If the group was a distributed hunt group, those members who were remote members on other IP Office systems still visible within the SCN.

•	Any local members who have hot desked to another IP Office system still visible within the SCN.

•	When the local IP Office becomes visible to the other IP Office again, the groups will return to be advertised from the local IP Office.

•	Backs up my Voicemail: Default = On. This option can be used if the local IP Office is hosting the Voicemail Pro server being used by the SCN. If selected, when the local IP Office is no longer visible to the voicemail server, the other IP Office will act as host for the voicemail server.

•	This option requires the other IP Office to have licenses for the Voicemail Pro features that are required to operated during any fallback period.