Page History

Align

align	right

Image Added

Section

Column

width	90%

titleColor

Panel

#F85404	titleBGColor	#F0F0F0
title	Introduction	Valid 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.An Gigaset repeater can be used with the N610, repeater support is done in 2 steps. For now, in step 1 the repeater is supported in transparent mode.

Repeater functionality:

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

Step 1, transparent mode:

DECT Connection is unencrypted
Activation via provisioning

Step 2, upcoming:

Register repeater using existing known repeater registration procedure
Web-interface setting
encrypted connection

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

Section

Panel

titleColor	#F85404
titleBGColor	#F0F0F0
title	Auto-provisioning

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

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

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

Info

title	How to use provisioning file to enable transparent repeater operation:

Provisioning is not atomic!
Wildcard-provisioning

does not automatically synchronize settings for all 'ConfirmedBaseStations'!

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:

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

Reboot is needed after successful provisioning to get this synchronized.

Code Block

language	xml
title	Provisioning template

<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="e2">
    <nvm>
 
        <!-- Provisioning file for N610:
        deactivate enhanced DECT settings,
        that are not supported by a transparent repeater -->
  
        <!-- Since V2.50.0 defaults local base of ARI-Class A (N610) to 0,-->
        <!-- repeater-support needs to swap RPN of local base to 1!-->
        <!-- ATTENTION: DO NOT apply this provisioning xml to Nx70 system!!!-->
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" />
<!-- The following  provisioning command could apply to 'all'base stations of cingle cell system,-->
    ======================================================================== -->

<!-- butMAC MUSTaddress NOTin apply to ALL base stations of Nx70 system,-->
    
    <!-- Wildcard provisioning is not immediately synchronized to table of ConfirmedBaseStations!!! -->
    <!-- So please replace wildcard '@' by mac address of your N610, or reboot the base after successful provisioning. -->
    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" />
      
	    <!-- Encryption Off ======================================================================== -->
        <param name="DmGlobal.0.DECTCipherDisable" value="1" />
		
	    <!-- enhanced Encryption Off , for consistency -->
        <param name="DmGlobal.0.DECTEnhancedEncryption" value="0" />

	    <!-- Cf 0=off=Base confirms to Cs, advanced bearer setup decision by handset not affected ;-( until Domino/0x87=On 8Segments-->
        <param name="DmGlobal.0.DECTCfSettings" value="0x00" />
		
	    <!-- DECTBlindslots 0x0aaa for even slots; 0x0fff for all slots -->
        <param name="DmGlobal.0.DECTBlindslots" value="0x0aaa" />
        
	    <!-- wideband off : handset needs 40s asynchrony (by reboot) to learn this!!! --<param name="DmGlobal.0.WidebandEnabled" value="0" />
        <param name="DmGlobal.0.WidebandEnabledDECTDSAA2" value="0" />
		
    </nvm>
</provisioning>

Examples of provisioning files

Provisioning file to activate the Repeater support (Above example)

Section

name

Panel

titleColor	#F85404
titleBGColor	#F0F0F0
title	Connect 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

Attachments

preview

false

upload

false

old

false

patterns

*.xml

sortBy

Section

Panel

titleColor	#F85404
titleBGColor	#F0F0F0
title	How 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.

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

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

Image Modified

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'.

Section

Panel

titleColor	#F85404
titleBGColor	#F0F0F0
title	PARI of Class A needed

Several handset implemented rules ( sometimes just tuning, sometimes hard requirements ),
need DECT PARI of class A ( starting with '0' ), to best interop with repeaters, expecially of the rather old generation.
Image RemovedSome very early samples were equipped with PARI of class B starting with '1'.
Please return such sample back to headquarter for replacement by correct sample.

Page tree

Versions Compared

Old Version 22

New Version Current

Key

Examples of provisioning files

Provisioning file to activate the Repeater support (Above example)

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