Versions Compared

Old Version 3

changes.mady.by.user Max Schwab (Unlicensed)

Saved on

compared with

New Version 4

changes.mady.by.user Max Schwab (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This guide will explain how to convert the backup file (.xml) from a T1E1 module equipped device to a E1 module equipped device.

Be invited to use our free support and a support worker will assist you with this. If you want to do it yourself, the following procedure is for you.

Overview

We offer two ISDN PRI module types each with 1 or 2 ports
(depending on the age, the product name may vary)

  • 1 Port

    • BNMO-1PRI / BNMO-1T1E1 /  bf1t1e1 (which offers both E1 and T1 technology with 1 port)

    • BNMO-1E1 / BNMO-1E1-M (which offers only E1 technology with 1 port)

  • 2 Ports

    • BNMO-2PRI / BNMO-2T1E1 /  bf2t1e1 (which offers both E1 and T1 technology with 2 ports)

    • BNMO-2E1 / BNMO-2E1-M (which offers only E1 technology with 2 ports)

Why convert the configuration?

In the case that you have a backup of a configuration that was created on a PRI/T1E1 module and you need to use the configuration file in a gateway with a pure PRI/E1 module, the configurations are not compatible out of the box.

This is because the PRI/T1E1 module offers more configuration options than a pure PRI/E1 module, because the module can provide both technologies T1 and E1.

Info

If you try to import a backup from a T1E1 configuration to a device with E1 equipped:

The message “Hardware has changed” will appear and a factory reset is required. Additionally you need to reconfigure the device manually.

To avoid the reconfiguration process, this guide will show you how to convert and manipulate the .XML backup file correctly.

Whats different between the two?

The “PSTN → ISDN PRI” configuration options are the exact same between the two module types.
The “PSTN → Hardware” settings will differ, because the PRI/T1E1 offers a bit more flexibilities.

Info

The backup files are simple XML text files that can be edited with any text-editor. It contains key-value pairs for each configuration setting.

Important here is the hardware.conf file and it’s usually the first one in the XML file. We assume the module is seated on the first slot (lif0 → line interface 0)

Go through these steps and edit the XML file as follows:

On the device with the T1E1 module:
→ Download the Backup under Management → Backup and Restore

Original Config Backup.xml (T1E1)

Code Block
languagehtml
<?xml version="1.0"?>
<beroNetProvisioning>
	<Config>
		<File>
			<Name>hardware.conf</Name>
			<Contents>
[lif0]
type=bf2t1e1
master=1
clock=255
interface_type=hdlc,hdlc
termination=te,te
protocol=e1,e1
sigchan=16,16
country=de,de
coding=,

          </Contents>
		</File>
		
		[ ... ]

  1. set “type” to new module name (bf1E1 or bf2E1)

  2. “master” should stay the same

  3. set “clock” to the same value as “master”

  4. if “clock” was set to 255, add “crystal_clock=1,1”

  5. duplicate “termination” and rename to ntteSW and ntteHW respectively

  6. remove “interface_type“, “protocol”, “sigchan”, “country” and “coding”

  7. add the following extra configuration options as the default options. Feel free to adjust these settings to your liking

, these are the defaults

  1. :

Code Block
languagexml
permanentl1=0,0
crlen=
cidlen=
crc=1,1

New Config Backup.xml (E1)

Code Block
languagexml
<?xml version="1.0"?>
<beroNetProvisioning>
	<Config>
		<File>
			<Name>hardware.conf</Name>
			<Contents>
[lif0]
type=bf2E1
master=1
clock=1
ntteSW=te,te
ntteHW=te,te
permanentl1=0,0
crlen=
cidlen=
crc=1,1
crystal_clock=1,1
ptp=1,1
          </Contents>
		</File>
		
		[ ... ]

→ Save the XML file

On the device with the pure E1 module:
→ Restore the Backup under Management → Backup and Restore

After that press the red activate and wait for the device to reboot and apply the configuration

If everything worked, the module is detected correctly and the settings are applied correctly. No new hardware was found and everything works as expected.