In this document, we will show how to set & schedule firmware and configuration uploading to your intercom via TFTP. In our scenario, we will use the FREE software SolarWinds, but you can choose any TFTP server you like.
The configuration of the SolarWinds TFTP is pretty straightforward, you don't even need to do any special configuration and it will work right away.
But you can still make some further configuration:
- You can change the location of the root directory (from where the configuration and firmware will be uploaded)
- In the root directory, you can create folders for better organisation
- You can also improve the security with changing the transfer mode to send only and allow a specific IP range
For everything to work properly, you need to create a new inbound rule in your firewall:
Select a rule type "Port"
Select UDP protocol and specify a port 69
Once you create a rule, the TFTP server should be ready and the intercom should be able to connect successfully.
- First of all, you need to find the IP address of your PC, you can use a command line and type "ipconfig":
- After you successfully found out your IP address you have to fill it into the IP Intercom in this format: tftp://ip_address:69
If you've made folders in your root directory, you need to specify the correct location, otherwise, leave the "/" by default.
At this stage, you can also schedule, how often the intercom will check for any updates.
The intercom can check for updates:
To upload the firmware to the units, the file name needs to be in the correct format (check the formats below).
After you correctly re-name the file you need to save it to the correct directory (in our case C:\TFTP-Root\Firmware).
The latest firmware can be found on our site: https://www.2n.cz/en_GB/support/documents/firmware
|2N® IP Vario||hipv|
|2N® IP / LTE Verso||hipve||hipve-firmware.bin|
|2N® IP Solo||hipso||hipso-firmware.bin|
|2N® IP Base||hipba||hipba-firmware.bin|
|2N® IP Force||hipf||hipf-firmware.bin|
|2N® IP Safety||hipsf||hipsf-firmware.bin|
|2N® IP Video Kit||hipvk||hipvk-firmware.bin|
|2N® IP Audio Kit||hipak||hipak-firmware.bin|
|2N® SIP Speaker Horn||sassh||sassh-firmware.bin|
|2N® SIP Speaker||ss||ss-firmware.bin|
|2N® SIP Audio Converter||sac||sac-firmware.bin|
To upload the configuration to the units, the file name needs to be in the correct format (check the formats below).
After you correctly re-name the file you need to save it to the correct directory (in our case C:\TFTP-Root\Configuration).
The backup configuration file must be sourced from the device itself, here is how to make a back-up: https://2nwiki.2n.cz/pages/viewpage.action?pageId=65930568
If you want to have a specific configuration for one intercom you will have to substitute the "common" with a MAC address in this format: MODEL-XX-XX-XX-XX-XX-XX.xml
|2N® IP Vario||hipv|
|2N® IP / LTE Verso||hipve||hipve-common.xml|
|2N® IP Solo||hipso||hipso-common.xml|
|2N® IP Base||hipba||hipba-common.xml|
|2N® IP Force||hipf||hipf-common.xml|
|2N® IP Safety||hipsf||hipsf-common.xml|
|2N® IP Video Kit||hipvk||hipvk-common.xml|
|2N® IP Audio Kit||hipak||hipak-common.xml|
|2N® SIP Speaker Horn||sassh||sassh-common.xml|
|2N® SIP Speaker||ss||ss-common.xml|
|2N® SIP Audio Converter||sac||sac-common.xml|