FAQ - Mobile devices - Provisioning

DECT Handset Provisioning — Feature Availability Notice

We are pleased to announce that remote provisioning has been implemented for our DECT handset portfolio, enabling automated configuration and deployment of handsets without the need for manual per-device setup.

Important Notice for Large-Scale Deployments

While DECT handset provisioning has been successfully validated in standard deployment scenarios, this feature has not yet undergone comprehensive testing in large-scale system environments. Customers operating installations with a high number of DECT handsets should exercise caution before deploying provisioning across their full infrastructure.

We strongly recommend the following precautions for large systems:

Perform provisioning in controlled, staged rollouts rather than initiating simultaneous provisioning across all devices.
Validate the provisioning process on a representative subset of handsets before proceeding with a full deployment.
Ensure adequate network capacity and system resources are available during the provisioning window.
Monitor system performance and provisioning success rates closely throughout the process.

We are actively working to extend our testing coverage to large-scale environments and will provide updated guidance as validation is completed. In the meantime, please contact our technical support team if you require assistance planning a safe provisioning strategy for your deployment.

Introduction

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

Supported by R700H / S700H / SL800H / SL850H, please make sure your handsets have the latest firmware version
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 allows to skip version value
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:

Link to one file for all handsets
Example: http://192.168.1.200/hsprov/provisioning.xml
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

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

Example: http://192.168.1.200/hsprov/provisioning.xml

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.

Assign handset to Provisioning schedule

There is a new column in the mobile devices table - "Provisioning"

Select your handset - Provisioning:

Disabled: Provisioning is not supported

Name of provisioning schedule 1

Name of provisioning schedule 2

FAQ

If you set the provisioning URL to an external server, by default the provisioning file is cached for 60 minutes. 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 (minute)

It has to be set on the DECT device/base 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

Check if Battery level high enough, must be 20% charged if out of charger and 5% if in charger
When using external server, does the firewall allow the DECT base to download the file
Version value is not changed, new file is not downloaded
Error in provisioning file
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.

Can I upload an Handset provisioning file via the DECT provisioning file

No, if you host the provisioning file on our DECT system, it must be uploaded via the web-interface.

How to create an Handset provisioning file?

Using the Gigaset Handset provisioning file generator tool
Find all parameter and create your own file: FAQ SL850H SL800H S700H R700H - Auto provisioning: Parameter list

Auto-provisioning

Assign provisioning window to handset

<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="e2">
<nvm>



<param name="hs.03b7b19e5c.HsProvisioningId" value="1"/>



</nvm >
</provisioning>

Provisioning window

<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="e2">
<nvm>

   <param name="HsProvisioning.1.DaysOfWeek" value="mon,tue,wed,thu,fri,sat,sun"/>
   <param name="HsProvisioning.1.Enabled" value="1"/>
   <param name="HsProvisioning.1.Name" value="HS provisioning"/>
   <param name="HsProvisioning.1.StartTime" value="11:04"/>
   <param name="HsProvisioning.1.Url" value="http://192.168.1.200/hsprov/provisioning.xml"/>
   <param name="HsProvisioning.1.Version" value="001"/>
   <param name="HsProvisioning.1.ForceProvisioning" value="1"/>

</nvm>
</provisioning>