You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction


From software 2.68 or higher we have implemented auto-provisioning of our DECT handsets.

  • Supported by R700H / S700H / SL800H / SL850H
  • Handset must be 20% charged if out of charger and 5% if in charger
  • Provisioning URL to external server
    • URL to one file for all handsets
    • URL contains placeholder %IPUI, each handsets has it's own provisioning file
    • Nested profiles is supported
  • Our DECT system can host one provisioning file for all handsets
  • Up to 2 provisioning schedules can be created
  • Version value supported to allow only download of newer files
  • Force download supported
  • By default, the provisioning file is cached for 1 hour by the DECT system
  • The DECT base station, the handset is connected to, will download the provisioning file
  • The handset will try 2 times to download the file in case the download failed, then it will stop

Provisioning schedule


You can create 2 Provisioning schedules

Provisioning schedule - Edit

Activate: Enable/Disable the provisioning schedule

Name: Provide the name of the provisioning schedule, you can later see this in the handset table

Start time: The time that the provisioning needs to be started

Planned schedule: Select the days the provisioning needs to be started

URL to provisioning file:

Upload provisioning file: Allows you to upload one provisioning file for all Handsets that are assigned to this Provisioning schedule.

Version: Press the Refresh button to add the current date/time stamp. Only when the date/time stamp is newer, the provisioning file will be downloaded. As DECT channels have limited capacity, this make sure that only resources are used when newer provisioning files are available.

Force update: In case you want that always the provisioning file is downloaded then enable Force update or if Version = empty.

Provisioning URL to external server


You can use an external server that hosts the provisioning files.

Link to one file for all handsets

Link to for each handset a separate file

Example: http://192.168.1.200/hsprov/%IPUI.xml

The device will replace %IPUI by it's own IPUI

Example: http://192.168.1.200/hsprov/03b7b19e5c.xml  (MAC address is lower case)

Provisioning file hosted by our DECT system


We allow to upload one provisioning file per Provisioning window.

As our DECT system can have up to 20.000 handsets, we do not offer a web-interface to manage so many provisioning files for all handsets. 

You need to  use an external server if you want to have for each handset an own provisioning file.

FAQ


Can the caching time be changed ?

Yes, the caching time of the provisioning file can be changed via the following SSH command.

We recommend to do this only during testing phase.

cli-config set mcmad.suota_cache_time_limit=60

Lowest value = 1

It has to be set on the device where your handset is connected

How to check the provisioning URL in the handset

Open the handset menu <Center key>

*#provurl#  or *#7768875#

Can I upload more then 1 provisioning file ?

No, we offer the possibility to host one provisioning file per provisioning schedule. 

As our DECT system can have up to 20.000 handsets, we do not offer a web-interface to manage so many provisioning files for all handsets. 

You need to  use an external server .

Provisioning is not working

  1. Check if Battery level high enough, must be 20% charged if out of charger and 5% if in charger
  2. When using external server, does the firewall allow the DECT base to download the file
  3. Version value is not changed, new file is not downloaded
  4. Error in provisioning file
  5. File is changed but as caching is set to 1 hour, the old file is still used

Can I start from one provisioning file for all and then for each handset an own file?

Yes, this is called nested profiles: FAQ SL850H / SL800H / S700H / R700H - Auto provisioning: Nested profiles

The first file can be hosted by our DECT system, the handset specific files must be hosted by the external server.

  • No labels