{"wiki":"en","slug":"guide-system-autoprovisioning","markdown":"# Setting Up Auto-Provisioning\n\nThis setup guide describes how to set up and use auto-provisioning for the BEHNKE STATION.\n\nIn addition to manual setup via the web interface, the Behnke Station can also obtain its configuration automatically over the network. This method is called **auto-provisioning**. The Behnke Station contacts an **auto-provisioning server** at a set interval and checks whether a new or changed configuration, phone book, or firmware version has been provided there.\n\n%[NOTE_REQUIRES_BASIC_SETUP](NOTE_REQUIRES_BASIC_SETUP)%\n\n<!-- block: auto-provisionierung-aktivieren -->\n## 1. Enabling Auto-Provisioning\n\n%[BS_LOGIN_INFO](BS_LOGIN_INFO)%\n\n- Click the menu item %BS_MENU_SYSTEM% in the sidebar on the left\n- Navigate to the **Auto-Provisioning** section\n\n![Web interface, **Auto-Provisioning** section](uploads/227985b90a1f8fe8d82431d3546fc615/grafik.png)\n\n- Set the value of the **Provisioning** option to the desired interval\n- After activation, the Behnke Station contacts the configured auto-provisioning server according to the specified auto-provisioning interval\n\n<!-- block: url-des-auto-provisionierungs-servers -->\n## 2. URL of the Auto-Provisioning Server\n\nFor the Behnke Station to contact the auto-provisioning server, the URL of the server must be known.\n\nThe URL can be provided in two ways:\n\n- Manual configuration using the **URL** option in the **Auto-Provisioning** section\n- Automatic transmission by a **DHCP server**\n\nWhen using DHCP, the URL can be transmitted via the following DHCP options:\n\n- **DHCP option 66**\n- **DHCP option 43**\n\nThe DHCP server can provide the corresponding auto-provisioning URL based on the MAC address of the Behnke Station.\n\n> [!NOTE]\n> The exact structure of the URL is described in the help for the **URL** setting.\n\n<!-- block: konfigurationsdatei-bereitstellen -->\n## 3. Providing the Configuration File\n\nFor auto-provisioning, an existing configuration of a Behnke Station can be used as a basis.\n\nYou can find out how to export a corresponding configuration file here: see [Saving, Restoring, and Resetting the Configuration](Guide_System_ConfigActions).\n\nThe file is a text file and can be adapted as needed before it is provided on the auto-provisioning server.\n\n<!-- block: dateiname-der-konfigurationsdatei -->\n### 3.1 File Name of the Configuration File\n\nOn the auto-provisioning server, the configuration file must be saved under a name that is unique to the respective device.\n\nThe file name consists of the **MAC address of the Behnke Station without colons** and the file extension `.ini`.\n\nExample:\n\n```text\n001122AABBCC.ini\n```\nfor a Behnke Station with the MAC address:\n\n```\n00:11:22:AA:BB:CC\n```\n\nIf the Behnke Station finds a new or changed configuration file during auto-provisioning, it is downloaded and applied.\n\n> [!WARNING]\n> By default, the configuration provided via auto-provisioning completely replaces the existing configuration of the Behnke Station.\n\n<!-- block: zusatzkonfiguration -->\n## 4. Additional Configuration\n\nAlternatively, the configuration provided via auto-provisioning can be used as an **additional configuration**.\n\nIn this case, the existing local configuration is loaded first. Then the settings from the auto-provisioning file are applied on top of it.\n\nThe following applies:\n\n- Missing settings are added.\n- Existing settings are replaced by the values of the additional configuration.\n- The rest of the local configuration is retained.\n\nFor a configuration file to be recognized as an additional configuration, the first line of the file must read as follows:\n\n```text\nBEHNKE STATION INCLUDE CONFIGURATION FILE\n```\n> [!NOTE]\n> Phone book entries are an exception. If the additional configuration contains phone book entries, the existing phone book entries are discarded and replaced by the entries from the auto-provisioning file.\n\n<!-- block: telefonbuch-bereitstellen -->\n## 5. Providing the Phone Book\n\nThe phone book can be provided either as part of a configuration file or via a separate phone book file.\n\nA phone book file can be created, for example, using the export function in the **Phone Book** area.\n\nThe exported file is named:\n\n```text\nphonebook.txt\n```\nThe file is a text file and can be edited as needed.\n\nIt must also be saved on the auto-provisioning server under the name `phonebook.txt`.\n\nThis phone book file is then available to all Behnke Stations that use this auto-provisioning server.\n\nIf a Behnke Station finds a new or changed phone book file during auto-provisioning, it is imported.\n\n> [!WARNING]\n> When a phone book file is imported, the existing phone book is completely replaced by the new phone book.\n\n<!-- block: telefonbuch-synchronisation-mit-ldap -->\n## 6. Phone Book Synchronization with LDAP\n\nIf the phone book of the Behnke Station is synchronized via an LDAP server, a configuration file additionally transmitted via auto-provisioning should be provided as an additional configuration without phone book entries.\n\n> [!NOTE]\n> When phone book synchronization via LDAP is enabled, no separate phone book file can be transmitted via auto-provisioning.\n\n<!-- block: firmware-ueber-auto-provisionierung-aktualisiere -->\n## 7. Updating Firmware via Auto-Provisioning\n\nAuto-provisioning can also be used to provide a new firmware version for the Behnke Station and install it automatically.\n\nTo do this, the following files must be provided on the auto-provisioning server:\n\n- the matching firmware file for the respective hardware platform\n- a file named `firmware.txt`\n\nThe file `firmware.txt` contains the firmware version that the Behnke Station is to install.\n\nFor example, if firmware version `%LATEST_VERSION%` is to be installed, the file `firmware.txt` must have the following content:\n\n```text\n%LATEST_VERSION%\n```\nDuring each auto-provisioning run, the Behnke Station checks the version specified in `firmware.txt` and compares it with the currently installed firmware version.\n\nIf the specified version differs from the installed version, the Behnke Station downloads the corresponding firmware file from the auto-provisioning server and then performs the firmware update.\n\n> [!NOTE]\n> The provided firmware must be suitable for the hardware platform of the respective Behnke Station and named accordingly (`firmware-%LATEST_VERSION%.bin` for P1 and `P2-firmware-%LATEST_VERSION%.bin` for P2)\n\n<!-- block: faq -->\n## 8. FAQ\n\n%[NO_CONTENT](NO_CONTENT)%\n","lastModified":"2026-10-14T13:47:15+02:00"}