Versions Compared

Old Version 4

changes.mady.by.user Baremans, Eric

Saved on

compared with

New Version Current

changes.mady.by.user Bakker, Bas

Saved on

Key

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

Image Added

Image Added

Image Added

Image Added

Section
Column
width90%
titleColor
Panel
#F85404titleBGColor#F0F0F0
titleIntroductionValid for N610 but not supported by N670 / N870 / N870E. Software 2.53 or higher is needed.

If in a business environment more DECT coverage is needed, the best solution is to create an (Mini) multicell solution. A multicell offers more reliability, stability and parallel calls then a repeater solution.

If in some cases, a repeater solution is enough, the N610 supports unencrypted repeaters.

Repeater functionality:The N610 supports

  • Up to 6 repeaters in star arrangement
  • Connection is unencrypted
  • 2 narrowband calls in extended DECT range
  • Activation via provisioning

Planned is:

  • Web-interface setting
  • encrypted connection

N670 and N870 does do not support repeaters, for the N670/N870 (mini) multi-cell is available. 

Section
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleAuto-provisioning

Following provisioning file does apply RPN=1 to all base stations of a system. In singlecell system, to the one and only local base.

(warning) DO NOT apply following provisioning file to any N670/N870/N870E.

Info
titleHow to use provisioning file to enable transparent repeater operation:
  • Provisioning is not atomic!
  • Wildcard-provisioning even more is not atomic!
  • Some settings depend on the other!

So the fully safe procedure to apply this provisioning file is to apply the provisioning twice:

  1. It is recommended to save a backup before applying the following provisioning step.
  2. Upload this provisioning file via web-ui.
  3. "Start auto configuration", should be successful, confirm by OK!
  4. Repeat step 3 - "Start auto configuration", should be successful, confirm by OK!
  5. Reboot the device. 



Code Block
languagexmliconfalse
titleProvisioning template
<?xml version="1.0" encoding="UTF-8"?>


<provisioning version="1.1" productID="e2">

<nvm>


    <nvm>
 
        <!--
Provisioning file for N610: deactivate enhanced DECT settings, that are not supported by a transparent repeater -->
<!-- Encryption Off -->
<param name="DmGlobal.0.DECTCipherDisable" value="1" />
<!-- enhanced Encryption Off , for consistency -->
<param 
 ATTENTION: DO NOT apply this provisioning xml to N670/N870 system!!! It will break your N670/N870 system-->

<!-- Provisioning is not atomic! ===========================================
 Provisioning is not atomic!
 Wildcard-provisioning even more is not atomic!
 Some settings depend on the other!
 So the fully safe procedure to apply this provisioning file is to apply the provisioning twice:
 1. Upload this provisioning file via web-ui.
 2. "Start auto configuration", should be successful, confirm by OK!
 3. "Start auto configuration", should be successful, confirm by OK!
 4. Reboot the device.
-->
        <param name="dm.local.LocalBaseRpn" value="1"/>
        <param name="ConfirmedBaseStations.@.ucRpnIndex" value="0x1" />
<!-- ======================================================================== -->

<!-- MAC address in lower case, without ':' separator =======================
If you want to prevent wildcard provisioning, 
you need to give the MAC address of the local base,
without ':' separators and in lower case letters:
        <param name="dm.local.LocalBaseRpn" value="1"/>
        <param name="ConfirmedBaseStations.0x589ec6123456.ucRpnIndex" value="0x1" />
======================================================================== -->
        <param name="DmGlobal.0.
DECTEnhancedEncryption
DECTCipherDisable" value="
0
1"
/><!-- Cf 0=off=Base confirms to Cs, advanced bearer setup decision by handset not affected ;-( until Domino/Stromberg 0x87=On8Segments-->
<param 
 />
        <param name="DmGlobal.0.DECTEnhancedEncryption" value="0" />
        <param name="DmGlobal.0.DECTCfSettings" value="0x00"
/>
<!-- wideband off : handset needs 40s asynchronity (by reboot) to learn this!!! -->
<param 
 />
        <param name="DmGlobal.0.DECTBlindslots" value="0x0aaa" />
        <param name="DmGlobal.0.WidebandEnabled" value="0"
/>
<!-- DECTBlindslots 0x0aaa for even slots; 0x0fff for all slots -->
<param 
 />
        <param name="DmGlobal.0.
DECTBlindslots
DECTDSAA2" value="
0x0aaa
0" />

		
    </nvm>

</provisioning>

Examples of provisioning files

Section
Panel
titleColor#F85404
titleBGColor#F0F0F0
titlePARIConnect the repeater

When the above is done, the next step is to connect the repeater.

  • Open the web-interface of the N610.
  • Go to SETTINGS - Mobile devices - Registration Centre and click on Start now
  • Set the repeater in registration mode FAQ Repeater - Registration
  • All is successful when on the repeater, the left LED is constantly green
Section
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleHow to check in Web-UI and with handset MMI?

DECT Settings → DECT Encryption, early Encryption and re-keying is disabled to support transparent repeater operation.

Image Added

Telephony → Audio → Wideband Support must stay deactivated to support transparent repeater operation:

Image Added


With handset you could check the RPN in the RFP-Scan procedure

Image Added


If repeater support is deactivated RPN ends with '0' or '8'.

If repeater support is activated RPN ends with '1' or '9'.

Repeater might show up in RFP-scanning with RPN ending with '2..7' or 'a..f'

Using first manual generated N610 the repeater was not working.

The issue was caused due to wrong PARI.

Image Removed

Check if your PARI starts with "0" like above. With the sample, the PARI started with "1".

The PARI needs to be changed to solve the problem.