© 2006 Avaya Inc. All rights reserved. Network Small Community Network Network Small Community Network

Small Community Network (SCN) SCN can be enabled for IP Offices connected over IP lines. Up to 32 notes and 1000 users are supported.

SCN Example User name must be unique in a SCN Extensions must be unique in a SCN Huntgroup Name must be unique Hunt group users from multiple systems can be added VCM modules are required in all systems LAN LAN LAN System-Name: IP-Addr. LAN1 Extension: Huntgroup: London xxx MainLondon Frankfurt xxx MainFrankfurt Paris xxx MainParis

Small Community Network (SCN) System Frankfurt LAN Settings LAN1

Small Community Network (SCN) System Frankfurt LAN Settings LAN2

Small Community Network (SCN) IP lines must be set up accordingly.

Activate SCN on H323 Line Activate SCN by selecting IP Office SCN on the VoIP Settings tab.

Small Community Network (SCN) H323 Line to the connected IP Office Systems

Small Community Network (SCN) The IP routes must be programmed accordingly (here using the example of the IP Office 500 over LAN2).

Small Community Network (SCN) SCN wide HuntGroups.

Small Community Network (SCN) Hunt group users from multiple systems can be added.

Small Community Network (SCN) Hunt group users from multiple systems can be added.

SCN Star/Serial Layouts supported up to Release 4.2 = IP network, = IP Office H323 SCN Line. This are examples of star and serial layouts. These are the only types of layouts supported for Small Community Networks containing any pre-IP Office Release 5 systems.

SCN Mesh Layout supported with IP Office Release 5 The use of 'mesh' layouts connections is only supported for a Small Community Network of IP Office Release 5 systems. A mesh layout is one where there is more than one possible H323 SCN Line route between any two IP Offices. Mesh, star and serial layouts can be combined.

Resilient networks Large network, with 2 systems at the centre of the star providing backup routing. Medium sized network of peer systems. Direct calls are all point- point. You can now connect IP Office systems together in meshes, so that there is not a single system at the centre of a star. This makes calls across the network faster to establish, and SCN will continue to operate if the central system is inaccessible. You can connect your IP Office systems together any way you like.

Backup of a system that fails Backup can act as Alternate gatekeeper for Avaya IP Phones registered on the Primary. Will also provide DHCP. Backup can temporarily take over the Centralized voic function of the Primary. (requires appropriate VMPro licences on Backup) Backup can temporarily host any Distributed hunt groups which are homed on the Primary, distributing calls and providing announcements. (requires SCAN licence on Backup) Backup is otherwise a normal PBX on the SCN In an SCN, one IP Office can be assigned to backup another adjacent system. The backup kicks in when the failed system has been down for about 3 minutes, and there is corroborating evidence that the Primary is inaccessible. The backup will only work if it remains up while the failed system is down. It will not continue to act as backup if it is reset. It will not work over a power failure where both systems fail and only the backup recovers. Configure the H323 trunk between the systems to be Resilient SCN, and specify which features you want to back up. PrimaryBackup Resilient SCN

SCN - Fallback Activate it by selecting IP Office SCN - Fallback on the VoIP Settings tab.

Monitor Network view

Network visibility tool launched from SysMonitor Systems in the SCN Where the Voic servers are connected Connections which are down Types of PBX Calls over the SCN