Standardized Gigaset DECT Base Station Configuration

This article outlines the recommended approach for creating a "standard" configuration for Gigaset N530, N610, N670, and N870 DECT base stations, focusing on efficiency and best practices. It also highlights methods to avoid and explains the underlying reasons.

The goal of a standardized configuration is to pre-set essential parameters across multiple devices, including:

• Provider settings

• Phonebooks (Online Contacts)

• Telephony (VoIP) settings

• Network settings (e.g., VLAN)

Recommended Approach: Provisioning

Provisioning is the most efficient and reliable method for deploying standardized configurations. There are three primary ways to achieve this:

1. Via the Web GUI (XML File Upload): You can upload a provisioning XML file directly through the base station's web interface. This is suitable for smaller deployments or initial setup of individual devices.

2. Via a Custom Provisioning Server (XML File): For larger deployments, hosting your own provisioning server allows for centralized management and automatic configuration of devices upon connection to the network.

3. Via GRAPE (Gigaset Redirect and Provisioning Environment) Provisioning: GRAPE is Gigaset's dedicated redirection and provisioning service, offering a robust and scalable solution for managing a large fleet of devices, especially across different locations.

For detailed information on these topics, please refer to the following resources:

• FAQ - Auto provisioning

• FAQ - Auto provisioning: Parameters

What NOT to Do: Backup and Restore

It is crucially important that you do NOT configure a device manually and then distribute this configuration to other devices using the backup and restore function, except the original device is physically replaced and not active anymore.

Why Backup and Restore is Not Recommended: The PARI Explained

The main reason to avoid using the backup and restore function for standardized configurations is related to the PARI (Portable Access Rights Identifier).

The PARI is a unique identifier assigned to each Gigaset DECT base station. It plays a vital role in how DECT handsets identify and connect to base stations or DECT multi-cell networks. When a handset searches for a base station or DECT multi-cell network to connect to with or roam between, it uses the PARI to distinguish different base stations or DECT multi-cell networks.

If you use the backup and restore function, you will copy the original device's or DECT multi-cell network PARI to all other devices. This means multiple base stations or DECT multi-cell networks will end up with the exact same PARI.

The Consequences of Duplicate PARIs

When multiple single-cell base stations or DECT multi-cell networks are in close proximity, and they all share the same PARI, several issues can arise:

• Handset Registration Confusion: A handset might see multiple base stations with the identical PARI. Even if the handset is only registered to one specific base station, it may attempt to connect to another base station that has the same PARI but to which it is not actually registered.

• "Please Register" Error: In such scenarios, the handset will likely display "Please Register" on its display, even if it was previously registered. This happens because it's trying to connect to a base station that appears to be its registered one due to the matching PARI, but is in fact a different physical device or DECT multi-cell network where it lacks a valid registration.

• Interference and Instability: Duplicate PARIs can lead to unreliable connections, dropped calls, and general instability within your DECT environment, as handsets struggle to differentiate between base stations.

It is therefore EXTREMELY important that if there are multiple single-cell base stations or multiple DECT multi-cell networks in close proximity, the PARI MUST ALWAYS be different for each single-cell base station or DECT multi-cell network.

Provisioning ensures that each DECT-network (single- or multi-cell network) keeps the unique PARI given during production, preventing the issues associated with duplicate identifiers and ensuring a stable and reliable DECT environment.