Mike's PBX Cookbook

Small Community Network

IP Office systems linked by IP trunks can enable voice networking to form a Small Community Network (SCN). Within an SCN the separate IP Office systems 'learn' each other's extension numbers and user names. This allows extension calls between systems and support for a range of internal call features. Note that short codes still need to be built on each system for trunk calls (eg, dial-9).

Capacity:
  • Maximum Number of Systems: 32
  • Maximum Number of Users: 1000
  • Maximum H.323 Line Hops Between Systems: 5
Pre-requisites:
  • A star, serial or mesh data network between sites
  • IP500 Voice Networking licenses on all systems
  • Appropriate VCM channels in all systems

SCN is supported between IP Office systems with the same major software level, or one level of difference in major software level.
Within a SCN using differing levels of software, network features will be based on the lowest level of software within the network.
It is recommended that all systems within a Small Community Network are upgraded to the same level where possible. ip500v2_lan.png

Use WAN/LAN2 for IP phones and the SCN; LAN/LAN1 is for local maintenance.
Note, all IP Office's and SCN trunks should be on the same (LAN2) interface.

Setup a VoIP Line from System A to System B

1Make sure all names and extension numbers are unique within the multi-site network.

2Right-click Line, and select NewIP Office Line. buildscn1.png

3Select the Line tab and set the following:

buildscn2.png

4Click the VoIP Settings tab.

buildscn3.png

5Select System ➤ Voicemail.

buildscn4.png

6Save the configuration and reboot System A.

Setup the VoIP Line from System B to System A

1Repeat the steps to create an IP Office Line to System A.

2Save the configuration and reboot System B.

3Make test calls between extensions on the different systems.

Manager

SCN discovery must be enabled in the Manager in order to find and load each SCN member configuration.

Call Routing

SCN automagically takes care of routing only extensions. Short codes are still required to send other call types (eg, trunk) to another system. The short code Line Group ID will be the Outgoing Group ID assigned to the IP Office Line connected to the tandem system.
Note that a local extension number will override a conflicting short code, though ideally any dialing conflicts should be resolved.
Ensure that Line ➤ "Allow direct media path" is unchecked if the network topology doesn't support it, eg, with multiple sites.

Source: Avaya documentation