Snom Service Hub

Content

Page tree

On this Page, we will describe the Provisioning Proccess of the new DECT M9B & M9T Beacons of the Snom DECT M-Series.

Index:

Introduction

There is a special feature in the provisioning of our Beacon Gateway M9B. Due to technical issues, we had to take a special route to integrate the devices into your multi-cell.

In short, we set up a separate cloud provisioning service, where you upload once an excel sheet with the data of your beacons and enter a link to this special provisioning server in the WUI of a DECT base M900.
The concrete steps can be found in the now following step-by-step instructions.


Step by step guide

  1. Download and fill Excel file

    1. To make the task as easy as possible for you, we have prepared a sample file.

      To do so, visit the following URL: http://52.29.201.238:8080


    2. Depending on whether you want to use the M9B as a transmitter (Tx) or receiver (Rx) download the appropriate Excel file.

      An overview of the M9B can be found here, and an explanation of what the modes "Rx" and "Tx" mean can be found here.



    3. Now fill in the respective Excel table.
      1. Example Rx


      2. Example Tx


    4. In the following fold-out list you will find settings and syntax for the correct filling of the Excel table.

      If you want a mixed operation, i.e. you want to operate different M9B in Tx and Rx mode, you can simply add the desired columns to the Excel table.

      Please note that in order to ensure correct functioning of the cloud provisioning service, you must create three lines in the Excel file for each M9B device, which differ in the revision number. One line each with a 1, a 2 and a 3.

      ModeSettingDescription / Syntax
      Rx, Txc.IPEIIPEI number of the M9B
      Rx, Txc.revisionRevision of the current config. The config will only be applies, when a new revision is requested by the Base. To make sure - every time - a config will be requested and delivered we use revision 1,2,3 with the same configuration. The provisioning server automatically loops through those 3 provided revisions. 
      Rx, Txc.settingsVersion.majorDefault 1 - do not change 
      Rx, Txc.16 bitunsignedINTEGERDo not use this column, its for translation only.
      Rx, Txc.settingsVersion.minorDefault 1 - do not change 
      Rx, Txc.generalSettings.nameDo not change ! Uses "nameUNCHECKED"
      Rx, Txc.generalSettings.nameUNCHECKEDClear name of your M9B (max 12 characters) to be shown in the reports.
      Rx, Txc.generalSettings.alarmServerAddressNumber, e.g. 555, which is the identity number of the M9B
      Rx, Txc.generalSettings.beaconServerAddressNumber, e.g. 555, which is the identity number of the M9B. Should always be the same as "alarmServerAddress"
      Rx, Txc.rfSettings.antennaArraySelectionAntenna direction. Beam forming to look more to the RIGHT or LEFT or ACROSS (everywhere) 
      Rx, Txc.rfSettings.externalAntennaSelectionAntenna direction. Beam forming to look more to the RIGHT or LEFT or ACROSS (everywhere) 
      Rx, Txc.rfSettings.beaconOperationModeTX or RX mode
      Txc.rfSettings.txAttenuationSelectionDamping of the received signal in Algorithm 2 Mode.
      Txc.txModeSettings.txInterval.valueBeacon transmit (TX) Interval in seconds
      Rx, Txc.rxModeSettings.proximityAlgorithmChoose 4 as default.
      Txc.iBeaconSettings.uuidTX mode: iBeacon UUID sent from the M9B 
      Txc.iBeaconSettings.majorTX mode: iBeacon major version 16 bit value
      Txc.iBeaconSettings.minorTX mode: iBeacon minor version 16 bit value
      Rxc.rxModeSettings.proximityModein / out / both - in / out of range or both.

      The setting determines whether running in, running out or both is reported

      Rxc.rxModeSettings.sensitivitySetting

      TX mode: transmission power for the Beacon transmit.

      • Minimum - Very limited range,
      • Medium or Maximum range, used to cover a large area
      Rxc.rxModeSettings.cutoffThreshold.value

      Syntax:

      • -127 to zero
      • Value in dBm
      • Default -80
      Rxc.rxModeSettings.rxModeFilter.filterBeaconTypeDo not use. Future use
      Rxc.rxModeSettings.rxModeFilter.filterLength.valueDo not use. Future use
      Rxc.rxModeSettings.rxModeFilter.filterIdDo not use. Future use
      Rxc.rxModeSettings.statusUpdateInterval.valueSyntax:
      • 0 to 65535
      • Value in minutes
      • Zero (default) means off
      Rxc.rxModeSettings.statusUpdateRssiDiff.value

      Syntax:

      • 0 to 127
      • Value in dBm
      • Zero (default) means off
      Rxc.rxModeSettings.maxNumberTxDevices.valueDo not change
      Txc.altbeaconSettings.idTX mode: altBeacon UUID sent from the M9B 
      Txc.altbeaconSettings.mfgTX mode: altBeacon MFG sent from the M9B 

  2. Upload Excel file



    1. First you have to select the file, for this click on "Select file".
      The usual file selector will open.

    2. Then click on "Upload".

    3. Done. At this point you have now done everything.

  3. Copy the provisioning link into your WUI.



    1. In the web interface (WUI) of your M900, navigate to the "Management" menu item.

    2. And there copy the link from the cloud provisioning service into the "Configuration Server" field in the "Location Gateway" area.

    3. The "Auto Resync Time" specifies the time in the current time zone when the provisioning will be executed on each new day. In the example at 12:00h.

    4. "Auto Resync Max Delay" delays the start of the daily provisioning additionally by x seconds. 

    5. Then click on "save" at the bottom.

    6. Now be sure to restart the entire multicell. This will activate the daily provisioning on all bases.


You only ever need to repeat this process if you break up the multicell and set it up again, or you want to add more M9Bs or change the configuration from Rx to Tx.


Further Information


Related articles