5.5.5 Auto Provisioning

The 2N IP intercoms help you update firmware and configuration manually, or automatically from a storage on a TFTP/HTTP server selected by you according to predefined rules. 

You can configure the TFTP and HTTP server address manually. The 2N IP intercoms support automatic identification of the local DHCP server address (Option 66).

Firmware

Use the Firmware tab to set automatic firmware download from a server defined by you. The intercom compares the server file with its current firmware file periodically and, if the server file is later, automatically updates firmware and gets restarted (approx. 30 s). Hence, we recommend you to update when the intercom traffic is very low (at night, e.g.).


2N IP intercom expects the following files:

  1. MODEL-firmware.bin – intercom firmware
  2. MODEL-common.xml – common configuration for all intercoms of one model
  3. MODEL-MACADDR.xml – specific configuration for one intercom

MODEL in the filename specifies the intercom model:

  1. hipv – 2N® IP Vario
  2. hipf – 2N® IP Force
  3. hipsf – 2N® IP Safety
  4. hipak – 2N®  IP Audio Kit
  5. hipvk – 2N® IP Video Kit
  6. hipve – 2N® IP Verso
  7. hipso – 2N® IP Solo
  8. hipba – 2N® IP Base
  9. sac – 2N® SIP Audio Converter
  10. sassh – 2N® SIP Speaker Horn 
  11. ss – 2N® SIP Speaker

MACADDR is the MAC address of the intercom in the 00-00-00-00-00-00 format. Find the MAC address on the intercom production plate or in the Intercom Status tab via the web interface.

Example:

2N® IP Vario with MAC address 00-87-12-AA-00-11 downloads the following files from the TFTP server:

    • hipv-firmware.bin
    • hipv-common.xml
    • hipv-00-87-12-aa-00-11.xml

Configuration

Use the Configuration tab to set automatic configuration download from the server defined by you. The intercom periodically downloads a file from the server and gets reconfigured without getting restarted. 

Note

  • A few seconds' interruption of the display function occurs in the display-equipped 2N® IP Vario models during reconfiguration. Therefore, we recommend you to update when the intercom traffic is very low (at night, e.g.).

List of Parameters

  • Firmware update enabled – enable automatic firmware/configuration updating from the TFTP/HTTP server.

  • Address Retrieval Mode – select whether the TFTP/HTTP server address shall be entered manually or a value retrieved automatically from the DHCP server using Option 66 shall be used.
  • Server Address – enter the TFTP (tftp://ip_address), HTTP (http://ip_address) or HTTPS (https://ip_address) server address manually.
  • DHCP (Option 66/150) Address – check the server address retrieved via the DHCP Option 66 or 150.
  • File Path – set the firmware/configuration filename directory or prefix on the server. The intercom expects the XhipY_firmware.bin, XhipY-common.xml and XhipY-MACADDR.xml files, where X is the prefix specified herein and Y specifies the intercom model.
  • Use Authentication  enable authentication for HTTP server access.
  • Username  enter the user name for server authentication.
  • Password  enter the password for server authentication.
  • Trusted Certificate – set the set of CA certificates for validation of the ACS public certificate.
  • User Certificate – specify the user certificate and private key to validate the intercom right to communicate with the ACS.

  • At Boot Time – enable check and, if possible, update execution upon every intercom start.
  • Update Period – set the update period: hourly, daily, weekly and monthly.
  • Update At – set the update time in the HH:MM format for periodical updating at a low-traffic time. The parameter is not applied if the update period is set to a value shorter than 1 day.
  • Next Update At – set the next update time.

 

  • Last Update At  last update time.
  • Update Result  last update result. The following options are available:

Result Description
Invalid server address The server address is invalid.
Unsupported protocol The protocol is not supported. HTTP(s) and TFTP are supported only.
Invalid file path The provisioning file location is invalid.
DHCP option 66 failed The server address loading via DHCP Option 66 or 150 has failed.
Invalid domain name The server domain name is invalid due to wrong configuration or unavailability of the DNS server.
Server not found The requested HTTP/TFTP server fails to reply.
Authentication failed The HTTP credentials are invalid.
File not found The file has not been found on the server.
Request waiting in queue... The provisioning request is queuing...
In progress... Update is in progress.
File is invalid The file to be downloaded is corrupted or of a wrong type.
Firmware is up to date The firmware update attempt reveals that the latest firmware version has been loaded.
Update Succeeded The configuration/firmware update has been successful. With firmware update, the device will be restarted in a few seconds.

Internal error

An unspecified error occurred during file download.

My2N / TR069

Use this tab to enable and configure remote intercom management via the TR-069 protocol. TR-069 helps you reliably configure intercom parameters, update and back up configuration and/or upgrade device firmware.

The TR-069 protocol is utilised by the My2N cloud service. Make sure that TR-069 is enabled and Active profile set to My2N to make your intercom log in to My2N periodically for configuration.

This function helps you connect the intercom to your ACS (Auto Configuration Server). In this case, the connection to My2N will be disabled in the intercom.

  • My2N / TR069 Enabled – enable connection to My2N or another ACS server. 

  • Active Profile – select one of the pre-defined profiles (ACS), or choose a setting of your own and configure the ACS connection manually.
  • Next Synchronisation in – display the time period in which the intercom shall contact a remote ACS.
  • Connection Status – display the current ACS connection state or error state description if necessary.
  • Communication Status Detail – server communication error code or HTTP status code.
  • Connection test – test the TR069 connection according to the set profile, see the Active profile. The test result is displayed in the Connection status.

  • My2N ID – unique identifier of the company created via the My2N portal.
  • My2N Security Code – display the full application activating code.

  • ACS Server Address – set the ACS address in the following format: ipaddress[: port], 192.168.1.1:7547, for example.
  • Username – set the user name for intercom authentication while connecting to the ACS server.
  • Password – set the user password for intercom authentication while connecting to the ACS server.
  • Trusted Certificate – set the set of CA certificates for validation of the ACS public certificate. Choose one of three sets, see the Certificates subsection. If none is selected, the ACS public certificate is not validated.
  • User Certificate – specify the user certificate and private key to validate the intercom right to communicate with the ACS. Choose one of three sets, refer to the Certificates subsection.
  • Periodic Inform Enabled – enable periodical logging of the intercom to the ACS.
  • Periodic Inform Interval – set the interval of periodical logging of the intercom to the ACS if enabled by the Periodic Inform Enabled parameter.