Global IP Office Technical Tip
130: Pushing Configurations to Multiple Units in a SCN Environment
*Release Date: 9 May 2006
It has come to the attention of Avaya that the practice of building a configuration on one
unit and then modifying that configuration to fit other locations in the same Small
Community Network (SCN) is being used in the field.
After creating a configuration, ensure each system in the SCN has a unique
configuration by opening the configuration offline and changing:
• User names and numbers
• System Name
• IP Addresses
• Group names and numbers
• License key server and voicemail server addresses
• Ensure that meshed network topologies are not used with SCN
Failure to follow the above rules can cause unpredictable network behaviour. The only
resolution to this is to default all configurations affected and reprogram.