Installation and Operation Manual

ireset resets the device as soon it is idle
reset resets the device immediately
iresetn resets the device as soon it is idle
, only if a reset is required
resetn resets the device immediately, only if a reset is required
ser this is a no-op
TD 92579EN
10 April 2015 / Ver. N
Installation and Operation Manual
IP-DECT Base Station & IP-DECT Gateway (software version 7.2.X)
139
However, for new devices (that is, devices which have been reset to factory settings and
never had a successful download of a command file), the command file is retrieved every
minute (for up to 30 minutes). This is done so that a fresh device can quickly retrieve a site
depending standard configuration when it is installed.
When the command file is retrieved, the commands found in the file are executed in
sequence. Theoretically, all commands which can be typed in to a telnet session to the
device or which appear in a config file can be used in the command file. However, in most
cases, you will use config change commands and commands to the UP0/UP1 modules.
The command file is executed every time it is retrieved (depending on the poll interval).
However, in most cases, you don't want it to be executed each time, but only once. For
example, if you are about to deploy a certain configuration change to all IPBSs, then you
want this change to be done once per IPBS only. This can be achieved by the check
command:
mod cmd UP1 check <final-command> <serial>
The devices maintain an internal variable UPDATE/CHECK which is initially (or when the
device is reset to factory settings) empty. The check command will compare the <serial>
parameter with the UPDATE/CHECK variable. If it is equal, any further processing of the
command file is cancelled.
If it differs, the remainder of the file will be processed and, after the last command is
executed, the UPDATE/CHECK variable will be set to <serial> and the <final-command>
will be executed. The following commands are useful values for <final-command>:
Often, configuration changes shall be made only during certain times (e.g. non-working
hours). This can be achieved using the times command:
mod cmd UP1 times [/allow <hours>] [/initial <minutes>]
The times command will check the current time against <hours>. If it does not match this
restriction, any further processing of the command file is cancelled. <hours> is a comma
separated list of hours. Only those hours listed are considered valid times for execution of
the command file.
mod cmd UP1 times /allow 12,23,0,1,2,3,4
The command above allows command executions only between 12:00 and 12:59 and
23:00 and 4:59 local time (on a 24h clock). Note that if the device has no time set, all
command executions will be cancelled.
If the /initial parameter is set, the no commands will be executed within the first
<minutes> minutes after the device has been booted. This is done to avoid firmware
download and flashing when installing devices.
mod cmd UP1 times /allow 12,23,1,2,3,4 /initial 6
The command above suppresses any command file processing within the first six minutes
after each boot of the device. If /initial is set, new devices (or those that have been reset to
factory settings), the command file will be retrieved even if it normally would be