XML Backup & Provisioning File

Introduction

Starting from Firmware 16.XX the beroNet Gateways and Cards have a single XML file for the functions:

  • Backup
  • Restore
  • Provisioning

In older firmwares the backup consisted of a .tar.gz package of several configuration files. These files are still the same, but encoded into a simple XML file. 

This method allows it to handle provisioning more easy, because a single request provides the whole gateway configuration. 

File Format

The file is structured as follows:

<?xml version="1.0"?>
<beroNetProvisioning>
    <Config>
        <Update>[yes|no]</Update>
        <File>
            <Name>FILENAME</Name>
            <Contents>
FILE-CONTENTS
            </Contents>
        </File>
    </Config>
    <Firmware>
        <Install>[yes|no]</Install>
        <Filename>FIRMWARE.[tar.gz|fw]</Filename>
		<Url>https://second-provisioning-server.url/ANOTHER-FIRMWARE.[tar.gz|fw]</Url>
    </Firmware>
</beroNetProvisioning>

As you can see the XML-Format is simply mostly a container for configuration files with a <name> and a <content> tag. There are some special tags:

  • <update>  - defines if the file should be used in a device that receives it via provisioning.
  • <Firmware> - defines a firmware that can be installed and if this firmware should be installed

Please Note:

The <Url> flag in the <Firmware> section is optional and only available since the 21.03 firmware. It offers the possibility to download the firmware to a second webserver using https://second-provisioning-server.url/ANOTHER-FIRMWARE.[tar.gz|fw] as Provisioning-URL. When set, it replaces the <Filename> flag. (HTTP of HTTPS protocol can be used).


All current config-files for the 16.XX firmware are:

filedescriptionmandatory?
hardware.confhardware and module related settings, like TE/NT and Synchronization Port for ISDN Portsalways mandatory
isgw.analogcontains the port groups and the group configuration for analog ports (FXS/FXO)only if analog module present, otherwise emtpy
isgw.cascontains CAS groups and their configurations (T1 module)only if T1 module is present and set into CAS mode
isgw.causescontains the ISDN causes to SIP response code mapalways mandatory
isgw.confcontains general configuration settings like logging and pcm bridgingalways mandatory
isgw.cptcall progress table for mapping SIP STATUS responses to ISDN STATUS Messagesmandatory but can be empty most times
isgw.dialplanDialplan which connects the technologies and contains number rewriting rulesalways mandatory
isgw.gsmcontains GSM groups and their settings (GSM Module)only if gsm module present, otherwise empty
isgw.isdncontains the ISDN BRI and PRI groups and their settingsonly if ISDN module present, otherwise empty
isgw.sipcontains the SIP Accounts and their configurationsonly if SIP is used, general part should be provided always
isgw.tdmcontains the tdm timeslot configurationalways mandatory and depending on module combination, should be configured manually and then stored for each combination
misc.confcontains several system related settings like network, snmp and cloudalways mandatory
network.aclcontains the firewall rulesalways mandatory

If you need scheduled remote assistance, you can request our on-demand support services: https://www.beronet.com/support