innovaphone wiki - User contributions [en]

User:Gijsbert Zijlstra

2019-06-04T11:13:32Z

Gijsbert Zijlstra:

'''Gijsbert Zijlstra
'''

Support Manager

'''Lydis b.v.'''

Jool-Hulstraat 16

NL – 1327 HA Almere

The Netherlands

Tel: +31 (0) 36 20 20 120

Mobile: +31 (0) 6 820 19 802

Fax: +31 (0) 36 20 20 129

E-mail: [mailto:g.zijlstra@lydis.nl g.zijlstra@lydis.nl]

Web: [https://www.lydis.nl www.lydis.nl]

Skype: gijsbertzijlstra

User:Gijsbert Zijlstra

2017-10-03T08:22:50Z

Gijsbert Zijlstra:

'''Gijsbert Zijlstra
'''

Support Manager

'''Lydis b.v.'''

Antennestraat 33

NL – 1322 AH Almere

The Netherlands

Tel: +31 (0) 36 20 20 120

Mobile: +31 (0) 6 820 19 802

Fax: +31 (0) 36 20 20 129

E-mail: [mailto:g.zijlstra@lydis.nl g.zijlstra@lydis.nl]

Web: [https://www.lydis.nl www.lydis.nl]

Skype: gijsbertzijlstra

Reference8:Configuration/General/HTTP-Server

2010-05-03T07:40:39Z

Gijsbert Zijlstra:

The internal HTTP server allows web access to the device.

== Configuration ==

{|
|valign=top nowrap=true|'''Force HTTPS:'''
|Allow only HTTPS sessions. HTTP requests are redirected to HTTPS requests. On the first request after enabling this feature some browsers may not accept redirection of the XSL file, in this case the reload button of the browser helps. 
When you still get the message in the browser that the page can't be found, check if the TLS 1.0 support is enabled in the browser.
|-
|valign=top nowrap=true|'''Disable HTTP basic authentication:'''
|For HTTP basic and digest authentication is supported by the device. With basic authentication the password is transmitted as clear text, which is a security risk if the someone can listen to this coummunication. Digest authentication only transmits a hash code of the password which is of no use for a listener. To avoid the vulnerability of the basic authentication it can be disabled, but some applications may not support the digest authentication, which in turn do not work anymore if basic authentication is disabled.
|-
|valign=top nowrap=true|'''Password protect all HTTP pages:'''
|Apart from the start page Configuration/General/Info, all areas of the user interface are password protected. If this checkmark is set all pages are password protected. This option disables also login to the system using the 'Name' and the 'Password' configured in the PBX User object, so only logins with device administrator accounts are possible.
|-
|valign=top nowrap=true|'''Port:'''
|As default port 80 is used for HTTP. With this field it can be changed to any other value (e.g. 8080).
For disabling HTTP in general - so that only HTTPS is allowed - set the Port to 0
|-
|valign=top nowrap=true|'''HTTPS-Port:'''
|As default port is 443 is used for HTTPS. With this field it can be changed to any other value.
|-
|valign=top nowrap=true|'''External style sheet:'''
|If you want to personalize the appearance of the web interface you can specify the location of an external style sheet (CSS). If empty, the built-in style sheet of the box is used.
|-
|valign=top nowrap=true|'''Allowed stations:'''
|Access to the device can be restricted to a particular network (for example, 192.168.0.0 / 255.255.0.0) or to a particular host (for example, 192.168.0.23 / 255.255.255.255).
|-
|valign=top nowrap=true|'''Public compact flash access:'''
|Access to the compact flash generally needs authentication ( user and password ). If parts of the compact flash shall be accessed without authentication a list with the path and the access rights ( read or write ) can be configured. The access rights of the first match of the list is used. If the ''Path'' ends with a slash ('/'), then the whole sub-tree is affected. Example: If the compact flash drive is used for a update script in the directory <code>script</code> and the backups are stored in a directory <code>backup</code> the configuration could be <code>/drive/cf0/script/</code> ''read'' and <code>/drive/cf0/backup/</code> ''write''.
|}

== Status ==

All active HTTP sessions are displayed under the Active HTTP sessions section. The table shows for each session the clients IP address, the most recently accessed URL and the number of HTTP requests served on the session.

For example: From 172.16.1.49 To /HTTP0/info.xml No 22.

Reference:Update Server

2008-03-03T13:57:06Z

Gijsbert Zijlstra: /* Example */

== Configuration of the Update-Server ==
It is possible to update the firmware and configuration of a large number of innovaphone devices in a distributed environment by automated means.

This is done by storing the configuration and firmware information on a standard Web server, which in turn is called up the individual devices.

There are two modules in the device which work in tandem. The first is known as "UP0" and acutally executes the upload and download of configuration information as well as the download of updated firmware. UP0 is controlled by commands as detailed below.
The second module is known as "UP1". It serves to poll a given website for changed configuration information. If certain conditions are met, UP1 will issue commands to UP1 to perform the requested updates.

=== System requirements ===
* One or more Web server(s) accessible by the devices.
* The Web servers tested were MS IIS and the Apache server. It should, however, also work with all other common Web servers.
* For best results, the Web server should be able to manage a large number of simultaneous HTTP sessions. MS Personal Web Server, for example, is not a suitable Web server, since it manages a maximum of 10 simultaneous HTTP sessions.

=== Installation ===
To be able to transfer device configurations onto the Webserver, the latter must allow HTTP PUT requests. All other functions require HTTP GET authorisation.

Since all HTTP requests are executed unauthenticated, the Web server must allow anonymous reading and possibly also anonymous writing.

To allow HTTP PUT commands on a MS IIS, the read and write check box must be enabled in the configuration of the relevant virtual directory.

=== Configuration ===
Detailed information on how the URL parameter of the update server is configured on the innovaphone devices may be found in the chapter entitled "[[Reference:Configuration/General/Update|Configuration/General/Update]]".

Note here that the URL parameter must point precisely to the location of the file with the contained maintenance commands. It is also to be noted that this URL (just like all other URLs used by innovaphone devices) does not support host names. Therefore, a valid IP address always has to specified.

If the URL happens to end with a ‘/’, then a standard file name based on the product description is used. If, for example, the URL is <nowiki>http://1.2.3.4/configs/</nowiki> , then it is extended in the case of an IP1200 as follows: <nowiki>http://1.2.3.4/configs/update-ip1200.htm</nowiki> . The product name is specified in the first line in chapter "[[Reference:Configuration/General/Info|Configuration/General/Info]]". The file extension is irrelevant here. The extension *.txt or *.htm or no file extension at all is possible. In relation to URL specifications, note that some Web servers differentiate between upper case and lower case letters.

=== Running maintenance ===
The update file is immediately read and also immediately executed. After a device restart, the update server is automatically queried periodically in accordance with the interval set.

When the maintenance file has been successfully received, it is executed sequentially. Theoretically, all commands that can be transmitted to the device in a Telnet session or that occur in a configuration file can be used in the maintenance file.

=== Maintenance commands ===
Additional commands implemented specially for the update server are available.
The maintenance file is executed every time (depending on the interval set), as soon as it is received.

==== Check command ====
In most cases, however, the maintenance file should be executed not every time as soon as it is received, but once only. Assuming that a secure configuration is to be loaded onto several devices, then it is best if this is done from one device. This can be achieved with the check command:

'''mod cmd UP1 check <final-command> <serial>'''

innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/CHECK. The check command compares the content of <serial> with the UPDATE/CHECK variable. If both match, all further processes of the maintenance file are terminated.

If they differ, the remaining processes are executed. When the last process has been executed, the UPDATE/CHECK variable is overwritten with the content of <serial>, and the content of <final-command> is executed. The following commands are usable content for <final-command>
* ireset: Resets the device as soon as it is not being actively used.
* reset: Resets the device immediately.
* iresetn: Resets the device as soon as it is not being actively used and a reset is required.
* resetn: Resets the device immediately if a reset is required.
* ser: no-op

==== Time command ====
Often it is preferred to perform such changes at particular times (for example, at night when no work is being done). This can be achieved with the times command:

'''mod cmd UP1 time [/allow <hours>]'''

The time command compares the current time with the content of <hours>. <hours> is a comma-separated list of specified hours, within which execution of the maintenance file is possible. If the content of <hours> with the restriction does not match, all further processes are terminated. The following hours are considered valid times, within which execution of the maintenance file makes sense.

'''mod cmd UP1 time /allow 12,22,23,0,1,2,3,4'''

With this command, execution of the maintenance file is allowed from 12:00 to 12:59 hrs and from 22:00 to 04:59 hrs. If the device does not have a time, all processes are terminated.

'''mod cmd UP1 time [/allow <hours>] [/initial <minutes>]'''

If the /initial parameter is set, no further commands are executed within the specified number of minutes <minutes>, once the device has been reset. This was implemented to avoid a firmware download and the overwriting of Flash memory during device installation.

'''mod cmd UP1 time /allow 12,22,23,0,1,2,3,4 /initial 6'''

With this specification, all processes of the maintenance file are suppressed within the first six minutes and within the valid times specified in the /allow parameter after every device restart. If the /initial parameter was set, new devices (or devices that were reset with the standard settings) can, after a restart, receive the maintenance file within the number of minutes specified in the /initial parameter, even if they lie outside the valid times as specified in the /allow parameter. This allows new devices to receive a current standard configuration quickly.

==== Prot command ====
To initiate a firmware update, the following command can be executed:

'''mod cmd UP0 prot <url> <final-command> <built-serial>'''

This command downloads new firmware (if available) from the specified URL onto the device. Finally, the <final-command> is executed.
innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/PROT. The prot command compares the content of <build-serial> with the UPDATE/PROT variable. If both match, no firmware is downloaded. If the UPDATE/PROT variable is not set (new devices or after a device restart), the content of <build-serial> is compared with the built number of the current firmware. Once the firmware has been successfully downloaded, the UPDATE/PROT variable is overwritten with the content of <build-serial> . Note that the <build-serial> parameter is not compared with the firmware version currently loaded. It is the responsibility of the administrator to keep this standard.

If the <url> parameter ends with a slash (‘/’), a standard firmware file name is appended to the URL depending on the product description (for example, IP1200.bin for an IP DECT system).

'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ip1200.bin ireset 04-5656</nowiki>'''

The command 
'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ ireset 04-5656</nowiki>'''

determines whether the firmware version 04-5656 was already installed. If this is not the case, the current firmware is downloaded from the address 192.168.0.10/firm/ip1200.bin, the UPDATE/PROT internal variable is overwritten with 04-5656 and, finally, the device is reset as soon at it is not being actively used.

==== Boot command ====
With the boot command, the boot code is updated and this is done in the same way as with the prot command.

'''mod cmd UP0 boot <url> <final-command> <built-serial>'''

The command 
'''mod cmd UP0 boot <nowiki>http://192.168.0.10/firm/ ireset 205</nowiki>'''

determines whether the boot code version 205 was already installed. If this is not the case, the current boot code is downloaded from the address 192.168.0.10/firm/boot1200.bin, the UPDATE/BOOT internal variable is overwritten with the version number of the downloaded boot code (205) and, finally, the device is reset as soon as it is not being actively used.

==== Bmc command (only for DECT devices)====
With the bmc command, the DECT radio code ( aka burst mode controller firmware or BMC code ) is updated and this is done in the same way as with the prot command.

'''mod cmd UP0 bmc <url> <final-command> <built-serial>'''

The command 
'''mod cmd UP0 bmc <nowiki>http://192.168.0.10/firm/ ireset PCS04fd</nowiki>'''

determines whether the DECT radio code PCS04fd was already installed. If this is not the case, the current DECT radio code is downloaded from the address 192.168.0.10/firm/ccfp1200.bin, the UPDATE/BMC internal variable is overwritten with PCS04fd and, finally, the device is reset as soon at it is not being actively used.
==== SCFG command ====
If the UP0 interface is being used, then the device configuration can be stored on a Web server.

'''mod cmd UP0 scfg ''<url>'''''

This command instructs the device to upload its current configuration to the ''<url>''. This can be achieved with the HTTP PUT command. The url must be writable. The following constants can be used in the url:

{|
! style="background-color:#DCDCDC;"| Sequence !! style="background-color:#DCDCDC;"| Replaces !! style="background-color:#DCDCDC;"| Example
|-
| #F || kernel build number || 08-12345
|-
| #B || boot code build number || 401
|-
| #H || hardware build || 102
|-
| #h || Device hardware number || IP1200-03-0d-f0
|-
| #m || MAC address of the device || 00-90-33-03-0d-f0
|-
| #d || Current date and time || 20051010-170130
|-
| #b''n'' || rolling backup index || 3
|-
| #i || (one of) the local ip-address || 192.168.0.1
|}

The rolling backup number loops over 0 .. ''n''-1 for each backup.

==== CFG command ====
A configuration file may be loaded using the

'''mod cmd cfg <url> <final-command> <serial>'''

command. The file will be read, all configuration commands in there executed and a final '''config write''' appended. Please note that no activation will be done implicitly. Thus, you will likely either use '''reset''' as <final-command> or use '''ser''' and have a '''config activate''' and '''iresetn''' follow.

=== Example ===
A Web server exists at the address 192.168.0.10 with a subdirectory called configs. In this directory, there are two further subdirectories, in which the current firmware files for all innovaphone devices are stored.
Clients provide the DHCP server with the option #215 as <nowiki>http://192.168.0.10/configs/</nowiki>. In this directory, there is a file update-ip1200.htm , which processes the following lines:

mod cmd UP1 times /allow 23,0,1,2,3,4 /initial 6
mod cmd UP0 scfg http://192.168.0.10/configs/saved/#h.txt
mod cmd UP0 prot http://192.168.0.10/configs/04-5679 ser 04-5679
mod cmd UP1 check ser 20040330-01
config change PHONECFG0 /coder G729A,60, /lang eng /protect
config change PHONEAPP0 /f4-10 BellOff /f4-v0 %1BE /f5-10 BellOn /f5-v0 %1BF
config write
config activate
iresetn

This example demonstrates how the configuration of a device is stored on a Web server; all IP1200 devices are then instructed to load/update the firware version 04-5679 in the time period 23:00 hrs to 04:59 hrs. New devices are updated after a restart and after the specified six minutes have elapsed. The devices are configured so that they use the G729 codec with a frame size of 60ms, the language setting is English and the configuration is write-protected. Therefore, only an administrator with appropriate authorisation can change this file. In addition, two standard functions were programmed for the device.

There is also the file update-ip3000.htm, which reads the following two lines:
mod cmd UP1 time /allow 23,0,1,2,3,4
mod cmd UP0 prot http://192.168.0.10/configs/04-5679 /ser 04-5679

IP3000 devices are updated to firmware version 04-5679 in the time period 23:00 hrs to 04:59 hrs.

====Using an innovaphone box as web server====
Any box with a CF slot and a CF card installed can serve as web server platform to read update scripts, firmware files, configuration files or to save configurations from V6 SR1 on.

====Asynchronous operation====
The commands prot boot bmc and cfg run asyncronous. The status of the current upload command can be shown with the status command

'''mod cmd UP0 status'''

In most cases a syncronous operation is preferred, in this case the /sync option can be used:

'''mod cmd UP0 /sync prot''' ...

Reference:Update Server

2008-03-03T13:53:34Z

Gijsbert Zijlstra: /* Example */

Reference:Update Server

2008-03-03T13:41:12Z

Gijsbert Zijlstra: /* Boot command */

== Configuration of the Update-Server ==
It is possible to update the firmware and configuration of a large number of innovaphone devices in a distributed environment by automated means.

This is done by storing the configuration and firmware information on a standard Web server, which in turn is called up the individual devices.

There are two modules in the device which work in tandem. The first is known as "UP0" and acutally executes the upload and download of configuration information as well as the download of updated firmware. UP0 is controlled by commands as detailed below.
The second module is known as "UP1". It serves to poll a given website for changed configuration information. If certain conditions are met, UP1 will issue commands to UP1 to perform the requested updates.

=== System requirements ===
* One or more Web server(s) accessible by the devices.
* The Web servers tested were MS IIS and the Apache server. It should, however, also work with all other common Web servers.
* For best results, the Web server should be able to manage a large number of simultaneous HTTP sessions. MS Personal Web Server, for example, is not a suitable Web server, since it manages a maximum of 10 simultaneous HTTP sessions.

=== Installation ===
To be able to transfer device configurations onto the Webserver, the latter must allow HTTP PUT requests. All other functions require HTTP GET authorisation.

Since all HTTP requests are executed unauthenticated, the Web server must allow anonymous reading and possibly also anonymous writing.

To allow HTTP PUT commands on a MS IIS, the read and write check box must be enabled in the configuration of the relevant virtual directory.

=== Configuration ===
Detailed information on how the URL parameter of the update server is configured on the innovaphone devices may be found in the chapter entitled "[[Reference:Configuration/General/Update|Configuration/General/Update]]".

Note here that the URL parameter must point precisely to the location of the file with the contained maintenance commands. It is also to be noted that this URL (just like all other URLs used by innovaphone devices) does not support host names. Therefore, a valid IP address always has to specified.

If the URL happens to end with a ‘/’, then a standard file name based on the product description is used. If, for example, the URL is <nowiki>http://1.2.3.4/configs/</nowiki> , then it is extended in the case of an IP1200 as follows: <nowiki>http://1.2.3.4/configs/update-ip1200.htm</nowiki> . The product name is specified in the first line in chapter "[[Reference:Configuration/General/Info|Configuration/General/Info]]". The file extension is irrelevant here. The extension *.txt or *.htm or no file extension at all is possible. In relation to URL specifications, note that some Web servers differentiate between upper case and lower case letters.

=== Running maintenance ===
The update file is immediately read and also immediately executed. After a device restart, the update server is automatically queried periodically in accordance with the interval set.

When the maintenance file has been successfully received, it is executed sequentially. Theoretically, all commands that can be transmitted to the device in a Telnet session or that occur in a configuration file can be used in the maintenance file.

=== Maintenance commands ===
Additional commands implemented specially for the update server are available.
The maintenance file is executed every time (depending on the interval set), as soon as it is received.

==== Check command ====
In most cases, however, the maintenance file should be executed not every time as soon as it is received, but once only. Assuming that a secure configuration is to be loaded onto several devices, then it is best if this is done from one device. This can be achieved with the check command:

'''mod cmd UP1 check <final-command> <serial>'''

innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/CHECK. The check command compares the content of <serial> with the UPDATE/CHECK variable. If both match, all further processes of the maintenance file are terminated.

If they differ, the remaining processes are executed. When the last process has been executed, the UPDATE/CHECK variable is overwritten with the content of <serial>, and the content of <final-command> is executed. The following commands are usable content for <final-command>
* ireset: Resets the device as soon as it is not being actively used.
* reset: Resets the device immediately.
* iresetn: Resets the device as soon as it is not being actively used and a reset is required.
* resetn: Resets the device immediately if a reset is required.
* ser: no-op

==== Time command ====
Often it is preferred to perform such changes at particular times (for example, at night when no work is being done). This can be achieved with the times command:

'''mod cmd UP1 time [/allow <hours>]'''

The time command compares the current time with the content of <hours>. <hours> is a comma-separated list of specified hours, within which execution of the maintenance file is possible. If the content of <hours> with the restriction does not match, all further processes are terminated. The following hours are considered valid times, within which execution of the maintenance file makes sense.

'''mod cmd UP1 time /allow 12,22,23,0,1,2,3,4'''

With this command, execution of the maintenance file is allowed from 12:00 to 12:59 hrs and from 22:00 to 04:59 hrs. If the device does not have a time, all processes are terminated.

'''mod cmd UP1 time [/allow <hours>] [/initial <minutes>]'''

If the /initial parameter is set, no further commands are executed within the specified number of minutes <minutes>, once the device has been reset. This was implemented to avoid a firmware download and the overwriting of Flash memory during device installation.

'''mod cmd UP1 time /allow 12,22,23,0,1,2,3,4 /initial 6'''

With this specification, all processes of the maintenance file are suppressed within the first six minutes and within the valid times specified in the /allow parameter after every device restart. If the /initial parameter was set, new devices (or devices that were reset with the standard settings) can, after a restart, receive the maintenance file within the number of minutes specified in the /initial parameter, even if they lie outside the valid times as specified in the /allow parameter. This allows new devices to receive a current standard configuration quickly.

==== Prot command ====
To initiate a firmware update, the following command can be executed:

'''mod cmd UP0 prot <url> <final-command> <built-serial>'''

This command downloads new firmware (if available) from the specified URL onto the device. Finally, the <final-command> is executed.
innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/PROT. The prot command compares the content of <build-serial> with the UPDATE/PROT variable. If both match, no firmware is downloaded. If the UPDATE/PROT variable is not set (new devices or after a device restart), the content of <build-serial> is compared with the built number of the current firmware. Once the firmware has been successfully downloaded, the UPDATE/PROT variable is overwritten with the content of <build-serial> . Note that the <build-serial> parameter is not compared with the firmware version currently loaded. It is the responsibility of the administrator to keep this standard.

If the <url> parameter ends with a slash (‘/’), a standard firmware file name is appended to the URL depending on the product description (for example, IP1200.bin for an IP DECT system).

'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ip1200.bin ireset 04-5656</nowiki>'''

The command 
'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ ireset 04-5656</nowiki>'''

determines whether the firmware version 04-5656 was already installed. If this is not the case, the current firmware is downloaded from the address 192.168.0.10/firm/ip1200.bin, the UPDATE/PROT internal variable is overwritten with 04-5656 and, finally, the device is reset as soon at it is not being actively used.

==== Boot command ====
With the boot command, the boot code is updated and this is done in the same way as with the prot command.

'''mod cmd UP0 boot <url> <final-command> <built-serial>'''

The command 
'''mod cmd UP0 boot <nowiki>http://192.168.0.10/firm/ ireset 205</nowiki>'''

determines whether the boot code version 205 was already installed. If this is not the case, the current boot code is downloaded from the address 192.168.0.10/firm/boot1200.bin, the UPDATE/BOOT internal variable is overwritten with the version number of the downloaded boot code (205) and, finally, the device is reset as soon as it is not being actively used.

==== Bmc command (only for DECT devices)====
With the bmc command, the DECT radio code ( aka burst mode controller firmware or BMC code ) is updated and this is done in the same way as with the prot command.

'''mod cmd UP0 bmc <url> <final-command> <built-serial>'''

The command 
'''mod cmd UP0 bmc <nowiki>http://192.168.0.10/firm/ ireset PCS04fd</nowiki>'''

determines whether the DECT radio code PCS04fd was already installed. If this is not the case, the current DECT radio code is downloaded from the address 192.168.0.10/firm/ccfp1200.bin, the UPDATE/BMC internal variable is overwritten with PCS04fd and, finally, the device is reset as soon at it is not being actively used.
==== SCFG command ====
If the UP0 interface is being used, then the device configuration can be stored on a Web server.

'''mod cmd UP0 scfg ''<url>'''''

This command instructs the device to upload its current configuration to the ''<url>''. This can be achieved with the HTTP PUT command. The url must be writable. The following constants can be used in the url:

{|
! style="background-color:#DCDCDC;"| Sequence !! style="background-color:#DCDCDC;"| Replaces !! style="background-color:#DCDCDC;"| Example
|-
| #F || kernel build number || 08-12345
|-
| #B || boot code build number || 401
|-
| #H || hardware build || 102
|-
| #h || Device hardware number || IP1200-03-0d-f0
|-
| #m || MAC address of the device || 00-90-33-03-0d-f0
|-
| #d || Current date and time || 20051010-170130
|-
| #b''n'' || rolling backup index || 3
|-
| #i || (one of) the local ip-address || 192.168.0.1
|}

The rolling backup number loops over 0 .. ''n''-1 for each backup.

==== CFG command ====
A configuration file may be loaded using the

'''mod cmd cfg <url> <final-command> <serial>'''

command. The file will be read, all configuration commands in there executed and a final '''config write''' appended. Please note that no activation will be done implicitly. Thus, you will likely either use '''reset''' as <final-command> or use '''ser''' and have a '''config activate''' and '''iresetn''' follow.

=== Example ===
A Web server exists at the address 192.168.0.10 with a subdirectory called configs. In this directory, there are two further subdirectories, in which the current firmware files for all innovaphone devices are stored.
Clients provide the DHCP server with the option #215 as <nowiki>http://192.168.0.10/configs/</nowiki>. In this directory, there is a file update-ip1200.htm , which processes the following lines:

mod cmd UP1 times /allow 23,0,1,2,3,4 /initial 6
mod cmd UP0 scfg http://192.168.0.10/configs/saved/#h.txt
mod cmd UP0 prot http://192.168.0.10/configs/04-5679 ser 04-5679
mod cmd UP1 check ser 20040330-01
config change PHONECFG0 /coder G729A,60, /lang eng /protect
config change PHONEAPP0 /f4-10 BellOff /f4-v0 %1BE /f5-10 BellOn /f5-v0 %1BF
config write
config activate
iresetn

There is also the file update-ip3000.htm, which reads the following two lines:
mod cmd UP1 time /allow 23,0,1,2,3,4
mod cmd UP0 prot http://192.168.0.10/configs/04-5679 /ser 04-5679

This example demonstrates how the configuration of a device is stored on a Web server; all IP1200 devices are then instructed to load/update the firware version 04-5679 in the time period 23:00 hrs to 04:59 hrs. New devices are updated after a restart and after the specified six minutes have elapsed. The devices are configured so that they use the G729 codec with a frame size of 60ms, the language setting is English and the configuration is write-protected. Therefore, only an administrator with appropriate authorisation can change this file. In addition, two standard functions were programmed for the device.

IP3000 devices are updated to firmware version 04-5679 in the time period 23:00 hrs to 04:59 hrs.

====Using an innovaphone box as web server====
Any box with a CF slot and a CF card installed can serve as web server platform to read update scripts, firmware files, configuration files or to save configurations from V6 SR1 on.

====Asynchronous operation====
The commands prot boot bmc and cfg run asyncronous. The status of the current upload command can be shown with the status command

'''mod cmd UP0 status'''

In most cases a syncronous operation is preferred, in this case the /sync option can be used:

'''mod cmd UP0 /sync prot''' ...

Reference:Update Server

2007-10-23T11:34:44Z

Gijsbert Zijlstra: /* Bmc command */

It is possible to update the firmware and configuration of a large number of innovaphone devices in a distributed environment by automated means.

This is done by storing the configuration and firmware information on a standard Web server, which in turn is called up the individual devices.

There are two modules in the device which work in tandem. The first is known as "UP0" and acutally executes the upload and download of configuration information as well as the download of updated firmware. UP0 is controlled by commands as detailed below.
The second module is known as "UP1". It serves to poll a given website for changed configuration information. If certain conditions are met, UP1 will issue commands to UP0 to perform the requested updates.

== System requirements ==
* One or more Web server(s) accessible by the devices. It is also possible to use an innovaphone device with a CF card as an update server.
* The Web servers tested were MS IIS and the Apache server. It should, however, also work with all other common Web servers.
* For best results, the Web server should be able to manage a large number of simultaneous HTTP sessions. MS Personal Web Server, for example, is not a suitable Web server, since it manages a maximum of 10 simultaneous HTTP sessions.

== Installation ==
To be able to transfer device configurations onto the Webserver, the latter must allow HTTP PUT requests. All other functions require HTTP GET authorisation.

Since all HTTP requests are executed unauthenticated, the Web server must allow anonymous reading and possibly also anonymous writing.

To allow HTTP PUT commands on a MS IIS, the read and write check box must be enabled in the configuration of the relevant virtual directory.

== Configuration ==
Detailed information on how the URL parameter of the update server is configured on the innovaphone devices may be found in the chapter entitled "[[Reference:Configuration/General/Update|Configuration/General/Update]]".

Note here that the URL parameter must point precisely to the location of the file with the contained maintenance commands. It is also to be noted that this URL (just like all other URLs used by innovaphone devices) does not support host names. Therefore, a valid IP address always has to specified.

If the URL happens to end with a ‘/’, then a standard file name based on the product description is used. If, for example, the URL is <nowiki>http://1.2.3.4/configs/</nowiki> , then it is extended in the case of an IP1200 as follows: <nowiki>http://1.2.3.4/configs/update-ip1200.htm</nowiki> . The product name is specified in the first line in chapter "[[Reference:Configuration/General/Info|Configuration/General/Info]]". The file extension is irrelevant here. The extension *.txt or *.htm or no file extension at all is possible.
When you discover problems that the update isn't working and the update screen in the GUI is presenting "failed 404" then check if the file name, for example "update-ip1200" does have the extension *.htm.

In relation to URL specifications, note that some Web servers differentiate between upper case and lower case letters.

== Running maintenance ==
The update file is immediately read and also immediately executed. After a device restart, the update server is automatically queried periodically in accordance with the interval set.

When the maintenance file has been successfully received, it is executed sequentially. Theoretically, all commands that can be transmitted to the device in a Telnet session or that occur in a configuration file can be used in the maintenance file.

== Maintenance commands ==
Additional commands implemented specially for the update server are available.
The maintenance file is executed every time (depending on the interval set), as soon as it is received.

=== Check command ===
In most cases, however, the maintenance file should be executed not every time as soon as it is received, but once only. Assuming that a secure configuration is to be loaded onto several devices, then it is best if this is done from one device. This can be achieved with the check command:

'''mod cmd UP1 check <final-command> <serial>'''

innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/CHECK. The check command compares the content of <serial> with the UPDATE/CHECK variable. If both match, all further processes of the maintenance file are terminated.

If they differ, the remaining processes are executed. When the last process has been executed, the UPDATE/CHECK variable is overwritten with the content of <serial>, and the content of <final-command> is executed. The following commands are usable content for <final-command>
* ireset: Resets the device as soon as it is not being actively used.
* reset: Resets the device immediately.
* iresetn: Resets the device as soon as it is not being actively used and a reset is required.
* resetn: Resets the device immediately if a reset is required.
* ser: Is a global variable and not a function.

=== Times command ===
Often it is preferred to perform such changes at particular times (for example, at night when no work is being done). This can be achieved with the times command:

'''mod cmd UP1 times [/allow <hours>]'''

The times command compares the current time with the content of <hours>. <hours> is a comma-separated list of hours, within which execution of the maintenance file is allowed. If the current time does not match <hours>, all further processing of the maintenance file is suppressed. The command line

'''mod cmd UP1 times /allow 12,22,23,0,1,2,3,4'''

allows execution of the maintenance file from 12:00 to 12:59 hrs and from 22:00 to 04:59 hrs. Note that if the device has no time set (yet), all commands following the times command will be ignored.

'''mod cmd UP1 times [/allow <hours>] [/initial <minutes>]'''

The /initial parameter prevents execution of the maintanance file within <minutes> minutes after the device has been booted. Further the /initial parameter forces the execution of the maintanance file for new devices when <minutes> minutes have been passed, even if the current time then does not match the times specified in the /allow parameter. Thus the /initial parameter avoids firmware download and overwriting of flash memory during device installation and forces new devices to receive a current standard configuration quickly. The command line

'''mod cmd UP1 times /allow 12,22,23,0,1,2,3,4 /initial 6'''

will suppress execution of the maintenance file within the first six minutes after each boot of the device. If a new device (or a device that has been reset to factory defaults) (re)reads the maintenance file therafter it will ignore the restrictions of the /allow parameter and execute the maintenance file.

=== Prot command ===
To initiate a firmware update, the following command can be executed:

'''mod cmd UP0 prot <url> <final-command> <build-serial>'''

This command downloads new firmware (if available) from the specified URL onto the device. Finally, the <final-command> is executed.
innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/PROT. The prot command compares the content of <build-serial> with the UPDATE/PROT variable. If both match, no firmware is downloaded. If the UPDATE/PROT variable is not set (new devices or after a device restart), the content of <build-serial> is compared with the build number of the current firmware. Once the firmware has been successfully downloaded, the UPDATE/PROT variable is overwritten with the content of <build-serial> . Note that the <build-serial> parameter is not compared with the firmware version currently loaded. It is the responsibility of the administrator to keep this standard.

If the <url> parameter ends with a slash (‘/’), a standard firmware file name is appended to the URL depending on the product description (for example, IP1200.bin for an IP DECT system).

'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ip1200.bin ireset 04-5656</nowiki>'''

The command 
'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ ireset 04-5656</nowiki>'''

determines whether the firmware version 04-5656 was already installed. If this is not the case, the current firmware is downloaded from the address 192.168.0.10/firm/ip1200.bin, the UPDATE/PROT internal variable is overwritten with 04-5656 and, finally, the device is reset as soon at it is not being actively used.

=== Boot command ===
With the boot command, the boot code is updated and this is done in the same way as with the prot command.

'''mod cmd UP0 boot <url> <final-command> <build-serial>'''

The command 
'''mod cmd UP0 boot <nowiki>http://192.168.0.10/firm/ ireset 205</nowiki>'''

determines whether the boot code version 205 was already installed. If this is not the case, the current boot code is downloaded from the address 192.168.0.10/firm/bootip1200.bin, the UPDATE/BOOT internal variable is overwritten with 205 and, finally, the device is reset as soon as it is not being actively used.

=== Bmc command ===
The bmc command allows you to update the ''burst mode controller' firmware (a.k.a. ''radio-code'') and this is done in the same way as with the prot command.

'''mod cmd UP0 bmc <url> <final-command> <build-serial>'''

The command 
'''mod cmd UP0 bmc <nowiki>http://192.168.0.10/firm/ ireset 4711</nowiki>'''

determines whether the bmc code version 4711 was already installed. If this is not the case, the current bmc code is downloaded from the address 192.168.0.10/firm/ccfp1200.bin, the UPDATE/BMC internal variable is overwritten with 4711 and, finally, the device is reset as soon as it is not being actively used.

Please note that this should work for IP600 and IP1200 and for version 5 and 6, but not for IP1500. Of course, it does only work for DECT devices anyway.

=== SCFG command ===
If the UP0 interface is being used, then the device configuration can be stored on a Web server.

'''mod cmd UP0 scfg <url>'''

This command instructs the device to upload its current configuration to the <url>. This can be achieved with the HTTP PUT command. The url must be writable. The following constants can be used in the url:

{|
! style="background-color:#DCDCDC;"| Sequence !! style="background-color:#DCDCDC;"| Replaces !! style="background-color:#DCDCDC;"| Example
|-
| '''#d''' || Current date and time || 20051010-170130
|-
| '''#m''' || MAC address of the device || 00-90-33-03-0d-f0
|-
| '''#h''' || Device hardware number || IP1200-03-0d-f0
|-
| '''#b'''''N'' || Backup number (cycling from 1 to ''N'') ''N'' defaults to 10 || 1 .. ''N''
|-
| '''#F''' || current Firmware || 07-6060001
|-
| '''#B''' || current boot code (no year) || 307
|-
| '''#H''' || current hardware build || 101
|}

Note: #b is implemented in version 6.00 SR1, #F/#B/#H are implemented in version 6.00 SR1-hotfix-1

== Example ==
A Web server exists at the address 192.168.0.10 with a subdirectory called configs. In this directory, there are two further subdirectories, in which the current firmware files for all innovaphone devices are stored.
Clients provide the DHCP server with the option #215 as <nowiki>http://192.168.0.10/configs/</nowiki>. In this directory, there is a file update-ip1200.htm , which processes the following lines:

mod cmd UP1 times /allow 23,0,1,2,3,4 /initial 6
mod cmd UP0 scfg <nowiki>http://192.168.0.10/configs/saved/#h.txt</nowiki>
mod cmd UP0 prot <nowiki>http://192.168.0.10/configs/04-5679</nowiki> /ser 04-5679
mod cmd UP1 check ser 20040330-01
config change PHONECFG0 /coder G729A,60, /lang eng /protect
config change PHONEAPP0 /f4-10 BellOff /f4-v0 %1BE /f5-10 BellOn /f5-v0 %1BF
config write
config activate
iresetn

There is also the file update-ip3000.htm, which reads the following two lines:
mod cmd UP1 times /allow 23,0,1,2,3,4
mod cmd UP0 prot <nowiki>http://192.168.0.10/configs/04-5679</nowiki> /ser 04-5679

This example demonstrates how the configuration of a device is stored on a Web server; all IP1200 devices are then instructed to load/update the firware version 04-5679 in the time period 23:00 hrs to 04:59 hrs. New devices are updated after a restart and after the specified six minutes have elapsed. The devices are configured so that they use the G729 codec with a frame size of 60ms, the language setting is English and the configuration is write-protected. Therefore, only an administrator with appropriate authorisation can change this file. In addition, two standard functions were programmed for the device.

IP3000 devices are updated to firmware version 04-5679 in the time period 23:00 hrs to 04:59 hrs.

[[Category:Concept|{{PAGENAME}}]]

Howto:Convert wave files in to G7xx coder files

2007-09-17T13:54:30Z

Gijsbert Zijlstra: /* V6 SR1 note */

The HTTP interface allows to play sound files delivered from a web server. This is used mostly for music on hold or waiting queue announcements. These files need to be in a specific format, not standard wave file. Here is how to convert a standard wave file into this format.

==Applies To==
This information applies to

* All innovaphone gateways (IP202, IP302,IP305 ,IP800, IP3000, IP6000)

Version 5.0 and later.

==More Information==

===Problem Details===
To avoid just-in-time format conversion and/or encoding, sound files played via the HTTP interface must be present as coder-specific raw sound stream data files. To use a standard wave file, it must be converted into G711/G723/G729 format first. Also, if you want to provide a specific sound file for calls with different coders, you must provide a single version of such file for each coder in question. To create G723, G729, G711a or G711u files, you will need standard 8kHz, 16bit, mono wave files.

At the [http://download.innovaphone.com/ice/6.00/ download site] you will find the softcod.exe in the tools folder. This is a command line utility which will convert such a wave file to the required coder files.

To convert a wave file announcement.wav, call at command line:
softcod announcement.wav

Softcode will create announcement.g723, announcement.g729, announcement.g711a and announcement.g711u.

Due to licensing issues, the conversion process requires access to an innovaphone gateway. The tool will thus ask for a valid gatekeeper/pbx alias. Note that the tool must be able to register with this alias. Therefore, you cannot use an account which is currently in use. As the tool will not ask for a password, you cannot use an account which is password protected.

===Installation===
There is no install available or required. Simply call softcod.exe from the command line.

===Known Problems===
The tool will locate the gatekeeper/pbx using gatekeeper discovery. Note that this currently will not work on multi-homed hosts, that is, hosts with more than one (virtual or physical) network interface. Most available wave file tools will not create wave files in the proper format (as defined above). In order for softcod.exe to work, you have to make sure the input wave file is in the proper format. Depending on the tool you are using, you may need to change the files audio properties. Also, you may use Windows™ standard audiorecorder application (sndrec32.exe) to convert a wave file in to the proper format (use File/Properties/Convert).

== V6 SR1 note ==
Starting from V6 Sr1 it is possible to run the sound files via the Cf cardslot (no etxternal web server needed) please refer to the related articles below.

Also it is then possible to automaticly convert the wav files into g7xx on the built-in compact flash card.

8khz, 16bit, mono *.wav files can be copied to webdav-mountable '''\\''x.x.x.x''\drive\CX0''', in order to convert to *.g711a, *.g711u, *.g729.
Please use the the '''Internet Explorer''' to open the directory on the CF.
Go with '''Internet Explorer''' to '''"Administration, Diagnostics, CF"''' and choose the option '''"Browse CF Content (Explorer, IE only)"'''. In the Internet Explorer the line '''\\''x.x.x.x''\drive\CF0''' is appearing.
Change in the URL '''CF0''' to '''CX0'''. The URL is then looking like '''\\''x.x.x.x''\drive\CX0'''.

Use now drag&drop to copy the wav file to the directory on the Compact Flash card.

[[Image:How_to_convert_wave_files_in_to_G7xx_coder_files_for_the_HTTP_interface_1.PNG]]

After a succesfull conversion, you should have a similar file structure on your CF card.

However, please be patient - a 2.5MB file (2.5min audio content) takes on an ip800 ~15min to be converted into a *.g729 file.

== Related Articles ==

[http://download.innovaphone.com/ice/6.00/ Download softcode (icluded into Tools Package)]

[[Howto:Installing_the_voicemail/music_on_hold_on_a_compact_flash_card]]

[[Howto:General_information_for_compact_flash_cards]]

[[Howto:Convert wave files to G7xxx with softcode]]

[[Category:Howto|{{PAGENAME}}]]

User:Gijsbert Zijlstra

2007-08-14T13:18:21Z

Gijsbert Zijlstra:

'''Gijsbert Zijlstra
'''

Technical Research & Support Manager

'''Tiptel b.v.'''

Camerastraat 2

NL – 1322 BC Almere

The Netherlands

Tel: +31 (0) 36 53 66 650

Mobile: +31 (0) 6 212 969 34

Fax: +31 (0) 36 54 65 296

E-mail: [mailto:g.zijlstra@tiptel.nl g.zijlstra@tiptel.nl]

Web: [http://www.tiptel.nl www.tiptel.nl]

Skype: gijsbertzijlstra

User:Gijsbert Zijlstra

2007-08-14T12:53:01Z

Gijsbert Zijlstra: New page: '''Gijsbert Zijlstra ''' Technical Research & Support Manager Tiptel b.v. Camerastraat 2 NL – 1322 BC Almere The Netherlands Tel: +31 (0) 36 53 66 650 Mobile: +31 (0) 6 212...

'''Gijsbert Zijlstra
'''

Technical Research & Support Manager

Tiptel b.v.

Camerastraat 2

NL – 1322 BC Almere

The Netherlands

Tel: +31 (0) 36 53 66 650

Mobile: +31 (0) 6 212 969 34

Fax: +31 (0) 36 54 65 296

E-mail: g.zijlstra@tiptel.nl

Web: [www.tiptel.nl]

Skype: gijsbertzijlstra

Reference:Update Server

2007-05-08T12:27:02Z

Gijsbert Zijlstra: /* Configuration */

It is possible to update the firmware and configuration of a large number of innovaphone devices in a distributed environment by automated means.

This is done by storing the configuration and firmware information on a standard Web server, which in turn is called up the individual devices.

There are two modules in the device which work in tandem. The first is known as "UP0" and acutally executes the upload and download of configuration information as well as the download of updated firmware. UP0 is controlled by commands as detailed below.
The second module is known as "UP1". It serves to poll a given website for changed configuration information. If certain conditions are met, UP1 will issue commands to UP1 to perform the requested updates.

== System requirements ==

* One or more Web server(s) accessible by the devices.
* The Web servers tested were MS IIS and the Apache server. It should, however, also work with all other common Web servers.
* For best results, the Web server should be able to manage a large number of simultaneous HTTP sessions. MS Personal Web Server, for example, is not a suitable Web server, since it manages a maximum of 10 simultaneous HTTP sessions.

== Installation ==

To be able to transfer device configurations onto the Webserver, the latter must allow HTTP PUT requests. All other functions require HTTP GET authorisation.

Since all HTTP requests are executed unauthenticated, the Web server must allow anonymous reading and possibly also anonymous writing.

To allow HTTP PUT commands on a MS IIS, the read and write check box must be enabled in the configuration of the relevant virtual directory.

== Configuration ==

Detailed information on how the URL parameter of the update server is configured on the innovaphone devices may be found in the chapter entitled "[[General_Update|Configuration/General/Update]]".

Note here that the URL parameter must point precisely to the location of the file with the contained maintenance commands. It is also to be noted that this URL (just like all other URLs used by innovaphone devices) does not support host names. Therefore, a valid IP address always has to specified.

If the URL happens to end with a ‘/’, then a standard file name based on the product description is used. If, for example, the URL is <nowiki>http://1.2.3.4/configs/</nowiki> , then it is extended in the case of an IP1200 as follows: <nowiki>http://1.2.3.4/configs/update-ip1200.htm</nowiki> . The product name is specified in the first line in chapter "[[General_Info|Configuration/General/Info]]". The file extension is irrelevant here. The extension *.txt or *.htm or no file extension at all is possible.
When you discover problems that the update isn't working and the update screen in the GUI is presenting "failed 404" then check if the file name, for example "update-ip1200" does have the extension *.htm.

In relation to URL specifications, note that some Web servers differentiate between upper case and lower case letters.

== Running maintenance ==

The update file is immediately read and also immediately executed. After a device restart, the update server is automatically queried periodically in accordance with the interval set.

When the maintenance file has been successfully received, it is executed sequentially. Theoretically, all commands that can be transmitted to the device in a Telnet session or that occur in a configuration file can be used in the maintenance file.

== Maintenance commands ==

Additional commands implemented specially for the update server are available.
The maintenance file is executed every time (depending on the interval set), as soon as it is received.

=== Check command ===

In most cases, however, the maintenance file should be executed not every time as soon as it is received, but once only. Assuming that a secure configuration is to be loaded onto several devices, then it is best if this is done from one device. This can be achieved with the check command:

'''mod cmd UP1 check <final-command> <serial>'''

innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/CHECK. The check command compares the content of <serial> with the UPDATE/CHECK variable. If both match, all further processes of the maintenance file are terminated.

If they differ, the remaining processes are executed. When the last process has been executed, the UPDATE/CHECK variable is overwritten with the content of <serial>, and the content of <final-command> is executed. The following commands are usable content for <final-command>
* ireset: Resets the device as soon as it is not being actively used.
* reset: Resets the device immediately.
* iresetn: Resets the device as soon as it is not being actively used and a reset is required.
* resetn: Resets the device immediately if a reset is required.
* ser: Is a global variable and not a function.

=== Time command ===

Often it is preferred to perform such changes at particular times (for example, at night when no work is being done). This can be achieved with the times command:

'''mod cmd UP1 time [/allow <hours>]'''

The time command compares the current time with the content of <hours>. <hours> is a comma-separated list of specified hours, within which execution of the maintenance file is possible. If the content of <hours> with the restriction does not match, all further processes are terminated. The following hours are considered valid times, within which execution of the maintenance file makes sense.

'''mod cmd UP1 time /allow 12,22,23,0,1,2,3,4'''

With this command, execution of the maintenance file is allowed from 12:00 to 12:59 hrs and from 22:00 to 04:59 hrs. If the device does not have a time, all processes are terminated.

'''mod cmd UP1 time [/allow <hours>] [/initial <minutes>]'''

If the /initial parameter is set, no further commands are executed within the specified number of minutes <minutes>, once the device has been reset. This was implemented to avoid a firmware download and the overwriting of Flash memory during device installation.

'''mod cmd UP1 time /allow 12,22,23,0,1,2,3,4 /initial 6'''

With this specification, all processes of the maintenance file are suppressed within the first six minutes and within the valid times specified in the /allow parameter after every device restart. If the /initial parameter was set, new devices (or devices that were reset with the standard settings) can, after a restart, receive the maintenance file within the number of minutes specified in the /initial parameter, even if they lie outside the valid times as specified in the /allow parameter. This allows new devices to receive a current standard configuration quickly.

=== Prot command ===

To initiate a firmware update, the following command can be executed:

'''mod cmd UP0 prot <url> <final-command> <built-serial>'''

This command downloads new firmware (if available) from the specified URL onto the device. Finally, the <final-command> is executed.
innovaphone devices have an internal variable that is initially empty (or empty if the device was reset with the standard settings) called UPDATE/PROT. The prot command compares the content of <build-serial> with the UPDATE/PROT variable. If both match, no firmware is downloaded. If the UPDATE/PROT variable is not set (new devices or after a device restart), the content of <build-serial> is compared with the built number of the current firmware. Once the firmware has been successfully downloaded, the UPDATE/PROT variable is overwritten with the content of <build-serial> . Note that the <build-serial> parameter is not compared with the firmware version currently loaded. It is the responsibility of the administrator to keep this standard.

If the <url> parameter ends with a slash (‘/’), a standard firmware file name is appended to the URL depending on the product description (for example, IP1200.bin for an IP DECT system).

'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ip1200.bin ireset 04-5656</nowiki>'''

The command 
'''mod cmd UP0 prot <nowiki>http://192.168.0.10/firm/ ireset 04-5656</nowiki>'''

determines whether the firmware version 04-5656 was already installed. If this is not the case, the current firmware is downloaded from the address 192.168.0.10/firm/ip1200.bin, the UPDATE/PROT internal variable is overwritten with 04-5656 and, finally, the device is reset as soon at it is not being actively used.

=== Boot command ===

With the boot command, the boot code is updated and this is done in the same way as with the prot command.

'''mod cmd UP0 boot <url> <final-command> <built-serial>'''

The command 
'''mod cmd UP0 boot <nowiki>http://192.168.0.10/firm/ ireset 205</nowiki>'''

determines whether the boot code version 205 was already installed. If this is not the case, the current boot code is downloaded from the address 192.168.0.10/firm/bootip1200.bin, the UPDATE/BOOT internal variable is overwritten with the version number of the downloaded boot code (205) and, finally, the device is reset as soon as it is not being actively used.

=== SCFG command ===

If the UP0 interface is being used, then the device configuration can be stored on a Web server.

'''mod cmd UP0 scfg <url>'''

This command instructs the device to upload its current configuration to the <url>. This can be achieved with the HTTP PUT command. The url must be writable. The following constants can be used in the url:

{|
! style="background-color:#DCDCDC;"| Sequence !! style="background-color:#DCDCDC;"| Replaces !! style="background-color:#DCDCDC;"| Example
|-
| #d || Current date and time || 20051010-170130
|-
| #m || MAC address of the device || 00-90-33-03-0d-f0
|-
| #h || Device hardware number || IP1200-03-0d-f0
|-
| #bN || Backup number (cycling from 1 to N) N defaults to 10 ||
|}

Note: #b is implemented in version 6.00 SR1

== Example ==

A Web server exists at the address 192.168.0.10 with a subdirectory called configs. In this directory, there are two further subdirectories, in which the current firmware files for all innovaphone devices are stored.
Clients provide the DHCP server with the option #215 as <nowiki>http://192.168.0.10/configs/</nowiki>. In this directory, there is a file update-ip1200.htm , which processes the following lines:

mod cmd UP1 times /allow 23,0,1,2,3,4 /initial 6
mod cmd UP0 scfg <nowiki>http://192.168.0.10/configs/saved/#h.txt</nowiki>
mod cmd UP0 prot <nowiki>http://192.168.0.10/configs/04-5679</nowiki> /ser 04-5679
mod cmd UP1 check ser 20040330-01
config change PHONECFG0 /coder G729A,60, /lang eng /protect
config change PHONEAPP0 /f4-10 BellOff /f4-v0 %1BE /f5-10 BellOn /f5-v0 %1BF
config write
config activate
iresetn

There is also the file update-ip3000.htm, which reads the following two lines:
mod cmd UP1 time /allow 23,0,1,2,3,4
mod cmd UP0 prot <nowiki>http://192.168.0.10/configs/04-5679</nowiki> /ser 04-5679

This example demonstrates how the configuration of a device is stored on a Web server; all IP1200 devices are then instructed to load/update the firware version 04-5679 in the time period 23:00 hrs to 04:59 hrs. New devices are updated after a restart and after the specified six minutes have elapsed. The devices are configured so that they use the G729 codec with a frame size of 60ms, the language setting is English and the configuration is write-protected. Therefore, only an administrator with appropriate authorisation can change this file. In addition, two standard functions were programmed for the device.

IP3000 devices are updated to firmware version 04-5679 in the time period 23:00 hrs to 04:59 hrs.

[[Category:Concept|{{PAGENAME}}]]