Show\Hide Navigation Manager: Small Community Networking
Up Down Back Forwards Print Feedback Synch Bookmark Search

Supported SCN Network Layouts

The IP Office systems within a Small Community network should only be connected using IP lines configured in a star and or serial layout. For each IP Office there should only be one possible IP Line route to any other IP Office even if that route is via intermediate IP Offices.

Note that we are referring to IP Line configured in the IP Office configurations. The actual IP network configuration, including IP routes in the IP Office configurations, can differ as per the customer network requirements.

The following are examples of supported star and serial layouts. Note that the maximum number of hops for user information transfers is 5.

scn networks okay

---- = IP network, | = IP Office IP Line.

The use of 'mesh' layouts connections is not supported. A mesh layout is one where there is more than one possible IP Line route between any two IP Offices. The following are examples of mesh layouts.

scn networks nokay

 

SCN Signalling
IP Office SCN uses a signalling similar to RIP is order to update each other of there presence. This traffic can be seen in the IP Office Monitor application as AVRIP packets. This traffic is is sent to port 50795 on which each IP Office system listens. Each IP Office in the SCN transmits an  update every 30 seconds. Additionally BLF updates are transmitted when applicable up to a maximum of every 0.5 seconds.  Typically the volume is less than 1Kbps per IP Office system.

 

 

Up Down Back Forwards Synch Print Feedback
© 2009 AVAYA
15-601011 Issue 22.zb.-
10:20, 25 June 2009
(scn_supported_scn_network_layouts.htm)

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners.

Last Modified: 03/06/2008