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:

file	description	mandatory?

file	description	mandatory?
hardware.conf	hardware and module related settings, like TE/NT and Synchronization Port for ISDN Ports	always mandatory
isgw.analog	contains the port groups and the group configuration for analog ports (FXS/FXO)	only if analog module present, otherwise emtpy
isgw.cas	contains CAS groups and their configurations (T1 module)	only if T1 module is present and set into CAS mode
isgw.causes	contains the ISDN causes to SIP response code map	always mandatory
isgw.conf	contains general configuration settings like logging and pcm bridging	always mandatory
isgw.cpt	call progress table for mapping SIP STATUS responses to ISDN STATUS Messages	mandatory but can be empty most times
isgw.dialplan	Dialplan which connects the technologies and contains number rewriting rules	always mandatory
isgw.gsm	contains GSM groups and their settings (GSM Module)	only if gsm module present, otherwise empty
isgw.isdn	contains the ISDN BRI and PRI groups and their settings	only if ISDN module present, otherwise empty
isgw.sip	contains the SIP Accounts and their configurations	only if SIP is used, general part should be provided always
isgw.tdm	contains the tdm timeslot configuration	always mandatory and depending on module combination, should be configured manually and then stored for each combination
misc.conf	contains several system related settings like network, snmp and cloud	always mandatory
network.acl	contains the firewall rules	always mandatory

XML Backup & Provisioning File

Introduction

File Format