Specifications

Chapter 7 - Configuration File Download Configuration File Download Server
108
Mediatrix 4100
You must have a time server SNTP that is accessible and properly configured, or the automatic
configuration update feature may not work properly. It is assumed that you know how to configure
your SNTP server. If not, refer to your SNTP server’s documentation. You can also refer to “Chapter
14 - SNTP Settings” on page 157 for more details on how to configure the Mediatrix 4100 for a
SNTP server.
If a time range is specified, the unit will download the configuration files at a random time within the
interval specified.
The format should be one of the following:
hh[:mm[:ss]]
hh[:mm[:ss]] - hh[:mm[:ss]]
Where:
hh: Hours.
mm: Minutes.
ss: Seconds.
The configuration files are downloaded at the first occurrence of this value and thereafter with a
period defined by the configFileAutoUpdatePeriod variable. Let's say for instance the automatic unit
configuration update is set with the time of day at 14h00 and the update period at every 2 days.
• If the automatic update is enabled before 14h00, the first update will take place the
same day at 14h00, then the second update two days later at the same hour, and so
on.
• If the time range is set to '14:00 - 15:00' and the automatic unit configuration update is
enabled within those hours, the first update will take place the following day. This
means that a range of '00:00:00 - 23:59:59' will always take place the next day.
9. Set the configFileAutoUpdatePeriodicEnable variable to enable.
10. In the sysConfigMIB, set the sysConfigDownloadConfigFile variable to
automaticInitiateFileDownload.
The unit configuration is only updated if at least one parameter value defined in the downloaded
configuration files is different from the actual unit configuration.
If one of the telephones/faxes is off-hook, the Mediatrix 4100 will perform the update 5 minutes after
both ports are detected on-hook.
Error Handling
The following configuration file fetching service error sources are divided in three types depending on the
transfer protocol: common errors (Table 35), TFTP errors (Table 36) and HTTP errors (Table 37). The error
cause and the unit behaviour are also described.
Table 80: Configuration File Fetching Error Handling
Error Type Cause Behaviour
Common Error Handling
Invalid file format The file format is not valid. Send a syslog warning message including the
file location/name with the transfer server
address:
The fetched configuration file “XXX”,
from server “XXX”, has an invalid
format.
No recorded settings applied.
Empty file Committing an empty file. Send a syslog warning message including the
file location/name with the transfer server
address:
The fetched configuration file “XXX”,
from server “XXX”, is empty.