0% found this document useful (0 votes)
120 views122 pages

Gigaset N870 IP PRO - Multicell System - en - INT

Uploaded by

fredon quentin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
120 views122 pages

Gigaset N870 IP PRO - Multicell System - en - INT

Uploaded by

fredon quentin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 122

Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / cover_front_admin.

fm / 11/7/18

pro

Gigaset N870 IP PRO


Multicell System
Installation, configuration and operation
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminIVZ.fm / 11/7/18

Content

Content
N870 IP PRO Multicell System – Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Planning your DECT wireless network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
N870 IP PRO – overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Package content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preparing to use the telephone system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Mounting the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing the Integrator (large installation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Defining the device role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operation hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Light emitting diodes (LED) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Resetting base stations to factory settings via power procedure . . . . . . . . . . . . . . . . . . . . . . . . 18
Emergency reset to factory settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The web configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Network administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IP and VLAN settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
DECT manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DECT manager administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DECT manager registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
DECT manager synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Base stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Base stations administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Base station synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Provider and PBX profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring provider or PBX profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Mobile devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Mobile devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Handset Registration Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Template Module, Version 1.2, 11.09.2018,

Telephony settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
General VoIP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Audio quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Call settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
XSI services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Online directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Corporate online directories (LDAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Online directories in XML format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Online directories – XSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminIVZ.fm / 11/7/18

Content

Online services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
System settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Web configurator access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Provisioning and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Save and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
DECT settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Diagnostics and troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Status information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Base station events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
System log and SNMP manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Using a handset connected to an N870 IP PRO base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Making calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Accepting calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Conversation with three participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Message indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Using directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Using the network mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
LDAP directory – configuration example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Access to the LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Display on the handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Service (Customer Care) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Authorisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Template Module, Version 1.2, 11.09.2018

Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Contact with liquid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

3
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / introduction.fm / 12/4/18

N870 IP PRO Multicell System – Introduction

N870 IP PRO Multicell System – Introduction


N870 IP PRO is a DECT multicell system for connecting DECT base stations to a VoIP PBX. It
combines the options of IP telephony with the use of DECT telephones.
Components
The following illustration shows the components of the N870 IP PRO Multicell System and the
way the system is embedded in the IP telephone environment:

Configuration N870 IP PRO N870 IP PRO IP telephones


via web DECT integrator DECT manager
interface (virtual machine)

LAN

N870 IP PRO
DECT base
stations

PBX

DECT (VoIP, ISDN, analogue)


Handover & roaming

Handsets

• DECT integrator
Central management and configuration unit of the DECT multicell system.
The DECT integrator
• Integrates multiple DECT managers to one roaming domain
• Contains the central DECT subscriber database
• Provides a web user interface for subscriber configuration
Template Module, Version 1.2, 11.09.2018,

• Provides access to the configuration for all DECT managers and the base station synchro-
nisation hierarchy
In small and medium installations the integrator and DECT manager are located on the same
device. For large installations the integrator will be provided as a virtual machine
(¢ page 14).

4
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / introduction.fm / 12/4/18

N870 IP PRO Multicell System – Introduction

• N870 IP PRO DECT manager


Management unit for a group of base stations. At least one DECT manager must be used for
each installation.
The DECT manager
• Manages bases station synchronisation within the clusters
• Provides application gateway between SIP signalling and DECT signalling
• Controls the media path from PBX to relevant base stations
Configuring DECT managers page 28
• N870 IP PRO DECT base stations
• Provide cell site DECT functions
• Provide media processing from handset directly towards PBX
• Provide connection channels for the handsets, the number depends on various factors
such as the approved bandwidth and the device role
Configuring the base stations page 37
• Handsets (mobile devices)
• Per DECT manager up to 250 handsets can be connected. To allow inter-DECT-manager
roaming, the regular load of handsets planned to be attached to one DECT manager
should be lower (approx. 80 %).
60 DECT calls could be made simultaneously for VoIP calls, network directory sessions
and info center sessions. For information on handset functions in relation to Gigaset base
stations, visit wiki.gigasetpro.com.
• Subscribers can accept or initiate calls in all DECT cells with their handset (Roaming), and
can also switch between the DECT cells during a call (Handover). A handover is only
possible if cells are synchronised.
Configuring handsets page 57
Detailed information about approved Gigaset handsets can be found in the relevant user
guide. These are provided on the Internet at wiki.gigasetpro.com.
• PBX (Private Branch Exchange)
You need to connect your DECT telephone system to an IP PBX or Provider with VoIP
(SIP)connections, e.g.,
• On premise PBX
• Hosted PBX
• Cloud PBX
• VoIP Provider
The PBX
Template Module, Version 1.2, 11.09.2018

• Establishes the connection to a public telephone network


• Enables central management of telephone connections, directories, network mailboxes

5
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / introduction.fm / 12/4/18

N870 IP PRO Multicell System – Introduction

• Forming clusters
A cluster defines a set of base stations of a DECT manager that shall synchronise in order to
perform handover, roaming and overload balancing.
Handover means to switch a handsets DECT connection to a new base station during a call.
Roaming means to connect a handset in idle mode via a new base.
Overload balancing is the process to setup a DECT connection (for a call or other adminis-
trative or customer purpose) not at the current base station, which is fully loaded with active
DECT or media connections, but via a neighbour base station, which has free resources to
setup/accept the new DECT connection.
While handover and roaming is possible between base stations of different DECT managers,
overload balancing is only possible inside the area of one DECT manager.
Handover and overload balancing can only be provided by synchronised base stations. In
some cases, not all base stations connected to one DECT manager can be synchronised for
location specific reasons. To organize synchronisation just within a subset of base stations
connected to one DECT manager, you can form clusters, within a DECT manager.
A DECT manager can offer multiple clusters with base stations synchronised within the
cluster, but not synchronised along different clusters.
In multiple DECT manager installations, cross-cluster synchronisation is possible via DECT
manager synchronisation ( page 34).
Template Module, Version 1.2, 11.09.2018,

6
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / introduction.fm / 12/4/18

N870 IP PRO Multicell System – Introduction

Deployments
The N870 IP PRO Multicell System deployment can be delivered in different stages of expan-
sions.

Small Medium Large – XXL


Embedded INT + DM device Embedded INT + DM device
with activated without DECT base station Virtualised integrator
DECT base station

INT DM DM DM DM
DM 1 2 ..... 10 100

INT BS BS BS BS BS BS BS BS BS
DM . . . 2 .... 10 1 2 ..... 60 1 60 ..... 600 6000
BS 1

1 2 ... 50 1 2 ... 250 1 2 3 ... 20,000


.......... .......... ..........

INT = Integrator, DM = DECT manager, BS = base station

Small Medium Large


Base stations Up to 10 Up to 60 Up to 6,000
BS functionality can be acti- Up to 60 per DM
vated on the Integrator/DM
device.
Handsets Up to 50 Up to 250 per DM * Up to 20,000
DECT manager Up to 100
Integrator and DECT manager on the same device
Integrator Virtual machine
* In case of a multi-DECT manager roaming installation, calculate some headroom for roaming visitor hand-
sets. They cannot be load-balanced to other DECT managers.

Information on how to migrate from a small or medium configuration with one single
DECT manager to a multiple DECT manager system ¢ page 96.
Template Module, Version 1.2, 11.09.2018

7
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / introduction.fm / 12/4/18

N870 IP PRO Multicell System – Introduction

Number of parallel calls depending of device role

Base 10
Base + DECT manager 8
Base + DECT manager + Integrator 5

Number of parallel calls per base station depending on the bandwidth: page 54

Planning your DECT wireless network


Careful planning of your DECT wireless network is the prerequisite for successful operation of
the N870 IP PRO Multicell System with good call quality and adequate call options for all
subscribers in all the buildings and areas belonging to the PBX. When deciding how many base
stations are needed, and where these should be positioned, both the requirements for the
capacity of the PBX and its wireless coverage, as well as many ambient conditions, must be taken
into consideration.
The "N870 IP PRO - Site Planning and Measurement Guide" will make it easier for you to plan your
multicell DECT network, explain the necessary preparatory work for the installation and describe
how to carry out measurements in order to find the best positions for your base stations. Please
read these instructions before starting installation.
We also offer the N720 IP PRO Site Planning Kit (Site Planning Kit) to help you measure the wire-
less coverage and signal quality on your DECT network. Information about setting up and using
the Gigaset measuring equipment can also be found in the "N870 IP PRO -Site Planning and
Measurement Guide".
Template Module, Version 1.2, 11.09.2018,

8
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / introduction.fm / 12/4/18

N870 IP PRO Multicell System – Introduction

N870 IP PRO – overview

Front

Device button
Set the device role; reset the device
¢ page 15

LED displays
Operation status of the device
¢ page 17

Top

LAN and power cable slot


Connecting the device ¢ page 12

Rear
Template Module, Version 1.2, 11.09.2018

Wall mounting slots


Wall mounting ¢ page 16

9
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

First steps

Package content
• One N870 IP PRO
It can be used as DECT management system or as
base station
• Security leaflet

The N870 IP PRO devices are powered by Power over Ethernet (PoE). If you do not use
an Ethernet switch with PoE functionality and require a power adapter to connect to
the mains power supply, you can order this as an accessory ( page 116).

Preparing to use the telephone system


To use the telephone system the following steps must be performed:
1 Perform DECT measurement and site planning
During the planning phase of your DECT network you should have created
an installation plan for the DECT managers and base stations.
"Site Planning and Measurement Guide"
2 Connect the devices to the local network ¢ page 13
3 In small and media installations:
Configure one device as Integrator/DECT manager ¢ page 15
In large installations:
Set-up the virtual machine for the Integrator ¢ page 14
Configure the DECT manager stations and register them on the Integrator ¢ page 15
4 Mount the devices at the planned locations ¢ page 16
Note: For each location please note down the MAC address of the device you
are going to install.
5 Configure the local network settings via web configurator ¢ page 25
Template Module, Version 1.2, 11.09.2018,

You need a PC connected to the local network, so that you can configure
your telephone system via the web configurator.
6 Perform a firmware update ¢ page 84
7 In case of a multi-DECT manager installation, register the DECT managers at ¢ page 28
the Integrator

10
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

8 Register the base stations at the DECT manager ¢ page 37


Note: The base stations will go offline for the duration of firmware update.
Further configuration of base stations (step 9) could be done via the Inte-
grator Web-UI (and database). But the base stations cannot learn new
settings, until they have finished their offline status in case of a firmware
update.
9 Configure the base station synchronization ¢ page 42
10 Configure VoIP PBX or provider ¢ page 50
11 Register handsets and perform handset configuration ¢ page 57
All the handsets to be used for making calls over the N870 IP PRO must be
registered at the telephone system. Any handset must get assigned an indi-
vidual SIP account at the SIP PBX. When registering, the handset is perma-
nently assigned a VoIP connection as the receive and send connection.
Create a backup to save your configuration ¢ page 87
If you want to migrate from a small or medium configuration with one single DECT
manager to a multiple DECT manager system, please read the "Migration" chapter
first (¢ page 96).

Whenever there are new or improved functions for your Gigaset device, firmware
updates are made available for you to download to your DECT managers and your
base stations. If this results in operational changes when using your phone, a new
version of this user guide or the necessary amendments will be published on the
Internet at
wiki.gigasetpro.com
Select the product to open the relevant product page for your base, where you will
find a link to the user guides.
Select the product to open the relevant product page for your base, where you will
find a link to the user guides.
To find out which version of the Integrator/DECT manager firmware is currently
loaded, see ¢ page 84 and/or page 90.
Template Module, Version 1.2, 11.09.2018

11
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

Mounting the device


Read the "N870 IP PRO - Site Planning and Measurement Guide" before you start
installing the devices.
• When installing the base stations, please take into account the technical conditions for posi-
tioning and the installation guidelines, which are described in the "N870 IP PRO - Site Plan-
ning and Measurement Guide".
• Install the base stations at the positions you determined when planning or measuring your
DECT wireless network.
• The N870 IP PRO device acting as Integrator/DECT manager can be installed anywhere
within the range of the local network. It does not need to be installed in the coverage area of
the DECT wireless network. Exception: the device comprising the DECT manager also acts as
base station.
• The N870 IP PRO devices are intended for wall mounting (¢ page 16).

• The devices are designed for use in dry rooms with a temperature range of +5°C
to +45°C.
• Never expose the devices to heat sources, direct sunlight or other electrical
appliances.
• Protect your device from moisture, dust, corrosive liquids and fumes.
Template Module, Version 1.2, 11.09.2018,

12
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

Connecting to the LAN


DECT manager and base stations must be connected to the same Ethernet or virtual
LAN sharing a common broadcast domain.
If you intend to use DECT-LAN synchronisation, please consider the requirements
mentioned in section "LAN-based synchronisation" (¢ page 43).
You can connect the devices to your local network via a router, switch, or hub. A VoIP PBX is
required for Internet telephony. This must be accessible via the local network and must have
network access (to the Internet and/or the analogue or ISDN telephone network), because DECT
manager and base stations do not offer any NAT-traversal support. NAT-traversal support of a
PBX or providers might not provide unlimited support for a multicell system with SIP (DECT
manager) and media (base station) traffic transferred via different hosts. Otherwise it will only be
possible to make calls within the LAN.
You also need a PC connected to the local network, so that you can configure your telephone
system via the web configurator.
For each device to be connected to the local network an Ethernet cable is required.

2 3

¤ Pull up the upper part of the housing and fold it forwards 1 .


¤ Insert a plug from an Ethernet cable into the LAN connection socket at the top of the
device 2 .
¤ Insert the second Ethernet cable plug into a LAN socket for your local network or on the PoE
switch 3 .
¤ Close the flap.
Template Module, Version 1.2, 11.09.2018

13
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

Data protection notice


Once the device is connected to the Internet, it automatically contacts the Gigaset
support server to make it easier for you to configure the devices and to enable
communication with Internet services.
For this purpose, the system sends the following information when it is started and
then every five hours:
• Serial number/item number
• MAC address
• IP address on the LAN/its port numbers
• Device name
• Software version
The following data is transmitted once every day.
• Number of registered handsets
• Information for each handset: DECT identifier (IPUI), device type, user name and
display name
On the support server, this information is linked to the existing device-specific infor-
mation:
• System-related/device-specific passwords

Connecting the power supply


Your N870 IP PRO is supplied with sufficient power via PoE (Power over Ethernet) if the
device is connected to an Ethernet switch with PoE functionality (PoE class
IEEE802.3af). In this case, you do not need to connect the device to the mains power
supply.

Installing the Integrator (large installation)


The virtual integrator appliance could be offered as
• *.zip archive consisting of one *.vmx file specifying the virtual machine configuration and
some virtual disk images (*.vmdk) for this virtual machine
or
• single *.ova file, into which the VM configuration and the virtual disk-images files are
compiled.
Template Module, Version 1.2, 11.09.2018,

The virtual integrator is designed for and tested with VM Spehre ESXi (Versions 5.5, 6.0 and 6.5).
With its low requirements, the virtual integrator appliance might be supported by many other
hypervisor solutions, which are not mentioned here.

14
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

Defining the device role


On delivery all N870 IP PRO devices are configured as base station. To set up the DECT multicell
system at least one device must be configured as DECT manager. Detailed information on device
roles: ¢ page 4.
You use the device button on the front side to change the role of the device. The following
settings are possible:
• Base station,
• Base station and DECT manager with dynamic IP settings (large installation),
• Integrator/DECT manager with dynamic IP address (small/medium installation),
• Integrator/DECT manager with fixed IP settings (small/medium installation).
¤ Press the device button for at least 10 seconds until all LEDs switch off. Release the button
. . . the device is now in programming mode.
¤ Select the device role by pressing the device button.
Integrator/DECT manager with dynamic IP settings:
¤ Short press the device button until both LEDs light blue. . . . The
IP address will be assigned by a DHCP server in your network.
Integrator/DECT manager with fixed IP settings:
¤ Short press the device button until the right LED lights blue. . . .
The following IP settings are set:
IP address: 192.168.143.1
Subnet mask: 255.255.0.0
Base station:
¤ Short press the device button until the right LED lights green.

Base station and DECT manager:


¤ Short press the device button until the left LED lights blue and
the right LED lights green.
Once the desired role is selected:
¤ Press the device button at least three seconds but less than 10 seconds . . . the previously
selected role is assigned to the device . . . the device is reset and rebooted.

When changing the device role the system is reset to factory setting. This means,
that existing configuration and user data will be lost.
Template Module, Version 1.2, 11.09.2018

If you change the role of a device that has been acting as Integrator, you should save
the configuration previously (¢ page 87).
If you intend to reset the role from base to base/DECT manager:
Before you switch the device role, previously delete the base at any other system
where it was registered before. Otherwise problems may occur because the device
might be bound to two concurrent systems.

15
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

First steps

Wall mounting
N870 IP PRO is intended for wall mounting. After connecting the LAN cable and setting the
device role you can place it to the destined location.

max. ø 8 mm
max. 3 mm
max. ø 4 mm
110 mm

Fix the device to the wall with two screws:


¤ Drill holes with the vertical spacing of 110 mm.
¤ Affix wall plugs and secure the screws. Let the screws
protrude by approx. four mm.
¤ Hang the device on the screws.
Template Module, Version 1.2, 11.09.2018,

16
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

Operation hints

Operation hints

Light emitting diodes (LED)


Depending on the device role the LEDs on the front side show different operational states. The
LEDs can have three different colours (red, blue, green) or can be off.

DECT manager and base stations


LED 1 (left) LED 2 (right) Description
0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s

Power off

Device is booting

Firmware update in progress

No connection to LAN or
no IP address available/assigned

Connecting to DECT manager or


no connection to DECT manager

Base station operational states


LED 1 (left) LED 2 (right) Description
0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s

Successful connection to DM,


synchronising

Synchronised, DECT ready

Synchronised, DECT traffic

Synchronised, DECT overload

DECT manager (without DECT)


Template Module, Version 1.2, 11.09.2018

LED 1 (left) LED 2 (right) Description


0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s

No DECT base inside active

System traffic / ongoing calls

17
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

Operation hints

DECT manager (with DECT)


LED 1 (left) LED 2 (right) Description
0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s 0.5 s

Not synchronised, DECT ready

Synchronised, DECT ready

Synchronised, system traffic,


no DECT traffic

Synchronised, DECT traffic

Synchronised, DECT overload

Depending on traffic state Connection to the Integrator lost

Resetting base stations to factory settings via power procedure


The following describes the procedure to reset base stations to factory settings via power proce-
dure. You can use it, if it is not possible to reset the device
• via the web configurator (¢ page 87), for instance because you have forgotten the pass-
word for the web configurator or you are experiencing problems accessing the LAN
• via the key procedure (¢ page 15), for instance because the devices are mounted in places
that are difficult to access.

The following procedure only applies to base stations. For DECT manager/Integrator
you need to use one of the above procedures.
Resetting the device to factory settings is performed by interrupting the boot process.
¤ Remove the power supply from the device (unplug the LAN cable or the power suply unit).
¤ Replug the LAN cable or the power suply unit . . . the reboot starts. If the boot process is not
interrupted, the standard reboot is performed.
¤ Interrupt the boot procedure after 30 sec. at the earliest and 40 sec. at the latest.
Once The device is reset as Integrator/DECT manager with dynamic IP settings.
Two times The device is reset as base station.
Four times The device is reset as Integrator/DECT manager/base station with dynamic IP
settings.
Template Module, Version 1.2, 11.09.2018,

This procedure resets all the settings you have made for the device. The procedure
deletes the saved data from the base stations and handsets. The base station's assign-
ment to the DECT manager is cancelled. Ongoing calls are cancelled. In the case of an
Integrator/DECT manager the whole configuration is reset.
To enable the restoration of your system configuration after a reset, you should regu-
larly save the configuration data to a file (¢ page 87).
If you intend to reset the role from base to DECT manager/base station, previously
delete the base at any other system where it was registered before.

18
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / starting.fm / 12/4/18

Operation hints

Emergency reset to factory settings


When the device is booting
¤ Press the device button for at least 10 seconds until all LEDs switch off release the button
. . . the device is now in programming mode.
¤ Press the device button until the LED lights green
¤ Press the device button for at least four seconds . . . the device is reset and rebooted.
Template Module, Version 1.2, 11.09.2018

19
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_intro.fm / 12/4/18

Configuring the system

Configuring the system


System settings are made via the web configurator of the N870 IP PRO (¢ page 20) and cannot
be changed using the handsets.
This applies in particular for:
• Registering and de-registering the handset at the telephone system, handset name.
• All settings for the VoIP account used by a handset for calls.
• Configuration of online directories.
Handset-specific settings are preset on your handset. You can change these settings.
This applies, for example, for
• Display settings, such as language, colour, backlight etc.
• Settings relating to ringtones, volume, speaker profiles etc.
Information about this can be found in the user guide for the relevant handset.

The web configurator


Use the web configurator to set up your N870 IP PRO and configure your DECT network.
• Set up the DECT network, register and synchronise the base stations.
• Make basic settings for the VoIP connections and register and configure the handsets you
wish to use in the DECT network.
• Make additional settings, e.g., meet particular prerequisites for connecting the handsets to a
corporate network or adjust the voice quality on VoIP connections.
• Save data required to access specific services on the Internet. These services include access
to online directories, as well as synchronising the date/time with a time server.
• Save your DECT network's configuration data as files on your PC and reload these in the event
of an error. Upload new firmware, if available, and plan firmware updates at a specific date.

Starting
At least one N870 IP PRO device is installed as Integrator/DECT manager
( page 15).
A standard web browser is installed on the PC/tablet.
The device housing the Integrator/DECT manager and the PC/tablet are directly
connected to one another in a local network. The settings of any existing firewall
Template Module, Version 1.2, 11.09.2018,

installed on your PC allow the PC/tablet and Integrator/DECT manager to communi-


cate with each other.

Depending on your VoIP PBX/VoIP provider, it is possible that you will be unable to
change individual settings in the web configurator.
While you are connected to the web configurator, it is blocked to other users. Simul-
taneous access is not possible.

20
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_intro.fm / 12/4/18

Configuring the system

¤ Launch the web browser on your PC/tablet.


¤ Enter the current IP address for the Integrator/DECT manager in the address field of the web
browser (for example: http://192.168.2.10).
IP address of the device
If the IP address is assigned dynamically via your local network's DHCP server, you can find the
current IP address on the DHCP server in the list of registered DHCP clients. The MAC address can
be found on the rear of the device. If necessary, contact the network administrator for your local
network.
Your DECT manager's IP address may change occasionally depending on the DHCP server
settings ( page 25).

Logging into/off the web configurator


Once you have successfully established the connection, the login screen is displayed in the web
browser. There are two user roles with different user IDs:
admin has unlimited access to all functions of the web configurator.
user has only limited access to some settings and system information, e.g., handset
registration and some system settings. The user role must be activated before it
can be used ( page 78).
¤ Enter the user ID in the Username text field (admin/user).
¤ Enter the password in the Password text field. Default admin/user
¤ Click on Login.
Logging in the first time
You will be asked to change the default password and to set the appropriate radio frequency
band.
¤ Enter a new password in the New password field and repeat it in the Repeat password field
¤ Select the radio frequency band used in your region from the list ( page 89).
¤ Click on Set to save the settings and to open the administrator interface.

If you do not make any entries for a lengthy period (approx. 10 minutes), you are auto-
matically logged off. The next time you try to make an entry or open a web page, the
login screen is displayed again. Enter the password again to log back in.
Any entries that you did not save on the telephone system before automatic logoff
will be lost.
Template Module, Version 1.2, 11.09.2018

Logging off
You will find the log off function at the top right of each web page, below the product name.
¤ Click on Logout

The session is automatically terminated after ten minutes of inactivity.


Always use the logout function to end the connection to the web configurator. If, for
example, you close the web browser without logging off beforehand, access to the
web configurator may be blocked for a few minutes.

21
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_intro.fm / 12/4/18

Configuring the system

Showing/hiding the navigation menu


On each web configurator page a side menu on the left allows you to navigate through the avail-
able functions. The menu currently used is unfolded and the currently selected menu entry is
coloured orange.
The navigation menu can be displayed permanently or can be hidden in the case the pointer is
moved out of the menu area.
¤ Use the Auto-hide menu check box beneath the menu list to show/hide the menu.
unchecked The navigation menu is shown permanently. (Default)
checked The menu is hidden as soon as you move the pointer out of the menu
area. Only the upper menu level symbols are shown on the left.
To re-display the menu: Move the pointer to the area the menu
symbols are shown.

Help function
Parameter description
¤ Click on the question mark next to the parameter for which you need information. A popup
window is opened displaying a short description for the selected parameter.
Function description for the entire web configurator page
¤ Click on the question mark in the upper right corner of the page. The online help is opened
in a separate window. It provides information about the functions and tasks that can be
performed via this page.
You have access to the total online help:
Browse through the online help: ¤ Use the buttons.
Open the table of contents: ¤ Click on the button.
Open the index to search for specific keywords: ¤ Click on the button.

Applying/discarding changes
Applying changes
¤ Select the Set button as soon as you have completed your change on a page . . . the new
settings are saved and activated on the DECT manager configuration.
Template Module, Version 1.2, 11.09.2018,

Changes that have not been saved are lost if you move to another web page or the
connection to the web configurator is lost, e.g., due to exceeding the time limit
(¢ page 21).
Discarding changes
¤ Select the Cancel button . . . changes made on the web page are rejected and the settings
that are currently saved in the telephone system configuration are reloaded.

22
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_intro.fm / 12/4/18

Configuring the system

Working with lists


Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
search item . . . only entries containing text matching the search item in the selected column
are shown in the table.
Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.
Displaying/ hiding columns:
¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.
Changing the number of list entries
¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.
Template Module, Version 1.2, 11.09.2018

23
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_intro.fm / 12/4/18

Configuring the system

Web configurator menu overview


Menu options that are available also in the DECT managers user interface are highlighted grey.
The other options are available only on the Integrator.

Settings Network IP page 25

DECT Manager Administration page 28


Synchronisation page 34

Base stations Administration page 37


Synchronisation page 42

Provider or PBX profiles page 50

Mobile devices Administration page 57


Registration Centre page 65

Telephony VoIP page 66


Audio page 67
Call settings page 68

Online directories Public page 75


Corporate page 71
XML page 75

Online services page 77

System Web configurator page 78


Integrator Config page 33
Provisioning and configuration page 80
Security page 81
System log page 94
Date and time page 83
Firmware page 84
Template Module, Version 1.2, 11.09.2018,

Save and restore page 87


Reboot and reset page 87
DECT page 88

Status Overview page 90


Statistics Base stations page 91
Incidents page 93

The user role has only restricted access to the user interface. If you login as user, most
of the menus entries are hidden.

24
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_Network.fm / 12/4/18

Network administration

Network administration

IP and VLAN settings


This page is used to integrate the DECT multicell system into your company‘s local network.
¤ Settings Network IP/LAN
If you change the IP address of the device or an error occurs when you are changing
the IP settings, the connection to the web User Interface may be lost.
IP address changed: ¤ Re-establish the connection with the new address.
An error occurred: ¤ Reset the device to the factory settings.
Defining the device role ( page 15)
Device name in the network
¤ Enter a label for the device. It is used to identify the device in network communication.

Address assignment
Network type
¤ Select the IP protocol used in your local network: Currently only IPv4 is supported.
IP address type
¤ Select Dynamic, if your device receives the IP address via a DHCP server.
¤ Select Static, if your want to assign a fixed IP address to the device.
If the Dynamic setting is selected, all further settings are automatically configured. They are
displayed and cannot be changed.
If you have selected Static as the address type, you must create the following settings.
IP address
¤ Enter an IP address for your device. This IP address allows your device to be reached by other
subscribers in your local network.
The IP address comprises four individual groups of numbers with decimal values from 0 to 255
that are separated by a dot, e.g., 192.168.2.1.
The IP address must be included in the address block used by the router/gateway for the local
network. The valid address block is defined by the IP address for the router/gateway and the
Template Module, Version 1.2, 11.09.2018

Subnet mask.

The IP address must be unique across the network, which means that it must not be
used by another device connected to the router/gateway.
The fixed IP address must not belong to the address block that is reserved for the
DHCP server for the router/gateway.
Check the settings on the router or ask your network administrator.

25
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_Network.fm / 12/4/18

Network administration

Subnet mask
The Subnet mask specifies how many parts of an IP address the network prefix must comprise.
For example, 255.255.255.0 means that the first three parts of an IP address must be the same for
all devices in the network, while the last part is specific to each device. In subnet mask
255.255.0.0, only the first two parts are reserved for the network prefix.
¤ Enter the subnet mask that is used by your network.
Standard gateway
The Standard gateway is generally the router/gateway of the local network. Your Integrator/
DECT manager device requires this information to be able to access the Internet.
¤ Enter the local (private) IP address for the standard gateway through which the local network
is connected to the Internet (e.g., 192.168.2.1).
Preferred DNS
DNS (Domain Name System) allows you to assign public IP addresses to symbolic names. The
DNS server is required to convert the DNS name into the IP address when a connection is being
established to a server.
¤ Enter the IP address for the preferred DNS server. You can specify the IP address for your
router/gateway here. This forwards address requests from the Integrator/DECT manager to
its DNS server. There is no default setting for a DNS server.
Alternate DNS
¤ Enter the IP address for the alternate DNS server that should be used in situations where the
preferred DNS server cannot be reached.
Template Module, Version 1.2, 11.09.2018,

26
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_Network.fm / 12/4/18

Network administration

VLAN
Details in this area are only required if you connect your phone system to a local network that is
divided into virtual subnetworks (VLAN – Virtual Local Area Network). In a tagged VLAN, data
packets are assigned to the individual subnetworks via tags (markings) that consist of a VLAN
identifier and the VLAN priority, amongst others.
You will need to save the VLAN identifier and VLAN priority on the phone system configuration.
Your VLAN provider will supply you with this data.
VLAN tagging
¤ Select the check box next to VLAN tagging, if you want the phone system to use VLAN
tagging.
VLAN identifier
¤ Enter the VLAN identifier that uniquely identifies the subnetwork. Value range: 0–4094.
VLAN priority
The VLAN priority allows voice data transport to take priority, for example.
¤ From the option menu select the priority for the phone system data.
Value range: 0–7 (0 = lowest, 7 = highest priority)

Ensure that the details in VLAN identifier or VLAN priority are set correctly. Incor-
rect settings can cause problems when connecting the DECT manger for configura-
tion purposes. Internal connections between DECT manager and base stations are
not tagged and therefore phone functions are not affected.
If required, you must carry out a hardware reset via power procedure ( page 18).
This means that all settings are lost.
Template Module, Version 1.2, 11.09.2018

27
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

DECT manager configuration


DECT manager configuration is only necessary in large installations with more than one DECT
manager. It is only available on the Integrator user interface.
To configure the DECT managers of your multicell system
• Create a list of DECT managers with identifier on the administration page
• Log in to the DECT manager devices and register the DECT managers at the Integrator
• Set up the DECT manager synchronisation, if applicable

DECT manager administration


The page allows you to manage the DECT managers of your multicell network.
¤ Settings DECT Manager Administration
The page shows the following information for the DECT managers that are registered at the Inte-
grator:
DM Id DECT manager identification within the multicell system.
DM Name Name of the DECT manager. It can be edited ( page 30).
RPN Group Part of the RFPI for a DECT manager. PARI and RPN must be locally unique
in order to achieve that the RPN group allocated for the base stations of a
DECT manager is locally unique in the system too.
PMID / TPUI Group DECT manager specific handset group. It is assigned automatically, when
the DECT manager is added to the system.
PMID (Portable part MAC IDentity) uniquely identifies an active handset
connection. Assigned individual TPUI uniquely identifies a handset.
Assigned PMID is derived from the assigned TPUI.
The column is hidden by default.
IP address IP address of the DECT manager.
¤ Click on to open the web user interface of the related DECT
manager.
Connection status Shows whether the DECT manager is currently connected to the multicell
system or not (Connected / Not connected).
Connecting a DECT manager page 33
Template Module, Version 1.2, 11.09.2018,

Bases Number of base stations located at this DECT manager.


Handsets Number of handsets assigned to the DECT manager.
Capacity The value indicates how many base stations, handsets and calls can be
handled by the DECT manager. It depends on the activation of the local
base of this DECT manager ( page 7).
Medium The local base of this DECT manager is deactivated. The
capacity is 60 external base stations, 250 handsets, 60 calls.
Small The local base of this DECT manager is activated. The capacity is
9 external base stations, 50 handsets, 10 calls.

28
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

The actual values are shown in the Bases limit, Handsets limit and Calls
limit columns.
Bases limit Maximum number of base stations that are allowed to be assigned to the
DECT manager.
The column is hidden by default.
Handsets limit Maximum number of handsets that are allowed to be registered at the
DECT manager.
The column is hidden by default.
Calls limit Maximum number of calls that are allowed to be active simultaneously.
The column is hidden by default.

Actions
Adding a DECT manager to the list
Before you can integrate N870 IP PRO devices as DECT managers into your multicell system, you
first have to create a list of DECT managers on the administration page.
¤ Click on Add . . . the DECT manager page is opened ( page 30).
Deleting a DECT manager from the list
¤ Select the check box next to the DECT manager you want to delete. Multiple choice is
possible. Click on Delete Confirm with Yes . . . all selected DECT managers are deleted.
Before you delete a DECT manager, first consider what to do with the base stations
assigned to it. You could export them in order to import them into another configu-
ration. You could delete them from this DECT manager in advance.

Editing the data of a DECT manager


¤ Click on next to the DECT manager you want to edit . . . the DECT manager configuration
page is opened ( page 30).
Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
Template Module, Version 1.2, 11.09.2018

search item . . . only entries containing text matching the search item in the selected column
are shown in the table.
Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.
Displaying/ hiding columns:
¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.

29
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

Changing the number of list entries


¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.

Adding/editing a DECT manager


On this page you enter the data for a DECT manager to be added to the multicell system or edit
the data for a DECT manager that is already assigned to the multicell system.
DM Id
DECT manager identification within the multicell system. It is assigned automatically. The iden-
tity must be used when registering the DECT manager at the Integrator.
After the DECT manager has been added, you should note this identifier to have it available,
when you will have to enter the account data later at the DECT manager.
DM Name
The name is used to identify the DECT manager within DECT manager lists.
¤ Enter a meaningful name for the DECT manager, e.g., referring to the location or organisa-
tional unit.
Template Module, Version 1.2, 11.09.2018,

30
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

Password
The password must be entered when registering the DECT manager at the Integrator.
¤ Enter a password for DECT manager registration.
You should note this password to have it available, when you will have to enter the account data
later at the DECT manager.
RPN Group
Part of the RFPI for a DECT manager. PARI and RPN must be locally unique in order to achieve that
the RPN group allocated for the base stations of a DECT manager is locally unique in the system
too.
¤ Select the RPN group number for the DECT manager from the option menu. Values: 0 – 3
Four RPN groups imply that there are potentially eight neighbours for a DECT manager. Neigh-
bouring DECT managers must not have the same RPN group.
Example:
RPN groups of neighbouring DECT managers
0 1 0
2 3 2
0 1 0
To ensure, that a handset in 3 cannot see two identical RPN from the left 2 and the right 2 area,
it is necessary, that any DECT manager coverage area in any direction is large enough, to provide
enough isolation between two DECT manager areas of the same RPN group.
Example: Any handset in 3 should either see base stations from the left 2 or from the right 2, but
it must be impossible, that a handset in 3 can see base stations from the left 2 and at the same
time from the right 2.
Capacity
Defines the role of the device the DECT manager is located on. The device role has an impact on
how many base stations and handsets can be handled by the DECT manager ( page 7).
Small Besides the DECT manager the device acts also as a base station. The DECT
manager can handle up to 10 base stations and up to 50 handsets.
Medium There is only the DECT manger running on the device. The DECT manager can
handle up to 60 base stations and up to 250 handsets.
¤ Select the desired device role for the DECT manager.
Template Module, Version 1.2, 11.09.2018

If you change the device role from Small to Medium and the local base station was
synchronization level 1, it will be deactivated. Base stations synchronization needs
to be adjusted in order to re-synchronize the system.

Reboot
¤ From the Reboot of option menu select the devices you want to reboot: the DECT Manager
only or the DECT manager and base stations.
¤ Click on Reboot now Confirm with Yes . . . the reboot starts immediately.

All existing connections managed by the affected base stations are terminated.
To reboot one single base station: page 39

31
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

DECT Manager log


System log
The system report (SysLog) gathers information about selected processes performed by the
DECT manager and base stations during operation and sends this to the configured SysLog
server.
Activate system log
¤ Mark/unmark the check box to activate/deactivate the logging function.
Server address
¤ Enter the IP address or the (fully qualified) DNS name of your Syslog server. Value: max. 240
characters
Server port
¤ Enter the port number, where the Syslog server expects to receive requests.
Range: 1-65535; Default: 514
If you want to use the Integrator‘s system log server configuration settings for the DECT
manager:
¤ Click on the Use Integrator settings button.

To set up the system log server settings page 94.

SNMP statistics
The Simple Network Management Protocol (SNMP) is a common protocol used for monitoring
and controlling of network devices. To gather management and statistical information
concerning base station events to be processed by an SNMP manager you have to enter the
address and authentication information according to the SNMP server configuration.
¤ Enter the IP address of the SNMP manager server in the SNMP manager address field and
the port number used by the SNMP manager in the SNMP manager port field. Default: 162
To access the SNMP database authentication is necessary.
¤ Enter the SNMP username and the SNMP password.
The SNMP manager access data can be set for the individual DECT manager or for all DECT
managers via Integrator configuration ( page 94).
¤ If for the DECT manager the Integrator configuration should be used, click on Use Integrator
Template Module, Version 1.2, 11.09.2018,

settings.

Storing management information in MIB format


You can store management information for all base stations of the DECT manager in MIB syntax.
¤ Click on Download MIB Select the location where the MIB file should be stored using the
system file selection dialogue . . . the file with the MIB information is stored in TXT format.

32
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

DECT manager registration


You can now register the DECT managers at the Integrator.
¤ Assign the device role Base station and DECT manager with dynamic IP settings to the
devices that are defined to act as DECT manager ( page 15).
¤ Enter the IP address for a DECT manager device in the address field of the web browser and
login ( page 21).
¤ Open the Settings System Integrator Config page
Integrator IP Address
¤ Determine the IP address of the Integrator (e.g. from the VM software or the DHCP server of
your network) and enter the IP address in the field.
DM Id
¤ Enter the identifier of the DECT manager as defined in the Integrator‘s DECT manager admin-
istration.
Connection password
¤ Enter the password that is assigned to the corresponding DM Id in the Integrator‘s DECT
manager administration.
Connection status
¤ Shows whether the DECT manager is currently connected to the multicell system or not
(Connected / Not connected).
If a DECT manager is successfully registered, the corresponding entry in the Integrator‘s DECT
manager list is supplemented by the IP address ( page 28).
Template Module, Version 1.2, 11.09.2018

33
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

DECT manager synchronisation


This page allows you to configure external synchronisation references for synchronisation clus-
ters of your DECT managers. This way you could configure inter DECT manager synchronisation
rules, to get base stations of multiple DECT managers in sync. Cluster-internal synchronisation is
defined via base station synchronisation ( page 42).
A cluster can synchronise to a cluster-external source, for example:
• The best base station of another cluster within the same multicell system.
Best means the base station with the strongest radio signal.
• An external DECT system referenced by its RFPI.
RFPI is a unique identifier for a DECT system. You can enter a full matching RFPI to reference
a specific base station or a part of an RFPI in order to reference a group of base stations.
• The LAN master of a DECT manager.

Further information on RFPI: wiki.gigasetpro.com

The page allows you to add, edit and delete the cluster synchronization references.
¤ Settings DECT Manager Synchronisation
The table shows the currently defined synchronisation references with the following informa-
tion:
DM Name
Name of the DECT manager in the multicell system.
Cluster
Cluster number of the DECT manager to which the synchronisation setting applies.
Cluster external sync
Indicates how the cluster is synchronized:
No external sync Level 1 base of the cluster will only synchronise internally.
Best DECT base of DM Level 1 base of the cluster will synchronise with the best accessible
base station of the DECT manager shown in the Reference column,
regardless of the cluster.
Ext RFPI xxx Level 1 base of the cluster will synchronise with another DECT system
referenced by the RFPI shown in the Reference column. Different RFPI
Template Module, Version 1.2, 11.09.2018,

matching levels are possible, e.g., Ext RFPI (full match), Ext RFPI (-1
match), Ext RFPI (-2 match), ...
LAN Master of DM Level 1 base of the cluster will synchronise with the LAN master of the
DECT manager shown in the Reference column.

Reference
Reference to the synchronizing external DECT system. In case of Best DECT base of DM and LAN
Master of DM the DECT manager identifier. In case of Ext RFPI xxx the RFPI or a part of an RFPI.

34
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

Actions
Adding a synchronization reference to the list
¤ Click on Add . . . the DECT manager synchronization page is opened ( page 30).
Deleting a synchronization reference from the list
¤ Select the check box next to the sync reference you want to delete. Multiple choice is
possible. Click on Delete Confirm with Yes . . . all selected sync references are deleted.
Editing a synchronization reference
¤ Click on next to the DECT manager synchronization you want to edit . . . the DECT
manager synchronization page is opened ( page 30).
Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
search item . . . only entries containing text matching the search item in the selected column
are shown in the table.
Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.
Displaying/ hiding columns:
¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.
Changing the number of list entries
¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤
Template Module, Version 1.2, 11.09.2018

Click on Previous or Next to scroll through the list page by page.


¤ Click on a specific page number, to go to the desired page directly.
Adding/Editing a synchronization reference
This page allows you to define which DECT device is responsible to synchronize a cluster
managed by the DECT manager. You can edit an existing entry of the DECT manager synchroni-
zation table or add a new entry.
DM Name
¤ For a new entry: Select a DECT manager from the option menu.
For an existing entry the identifier is shown.

35
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_DM.fm / 12/4/18

DECT manager configuration

Cluster
¤ For a new entry: Select a cluster number of the selected DECT manager. Only one synchroni-
sation reference can be set for a cluster.
For an existing entry: The cluster number of the selected DECT manager is shown.
Cluster external sync
¤ Select the cluster‘s synchronisation reference:
No external sync Level 1 base of the cluster will only synchronise internally.
Best DECT base of DM Level 1 base of the cluster will synchronise with the best accessible
base station of the DECT manager. The DECT manager must be
selected from the Reference option menu.
Ext RFPI xxx Level 1 base of the cluster will synchronise with another DECT
system. Different RFPI matching levels are possible.
Ext RFPI (full match) All bits of the RFPI are considered, i.e., one
specific DECT system is referenced
Ext RFPI (-1 match) -1 match: the last bit of the RFPI is ignored.
Ext RFPI (-2 match) -2 match: the last two bits are ignored
... ...
The RFPI or a part of an RFPI must be entered in the Reference text
field. Matching base stations are used to synchronise.
LAN Master of DM Level 1 base of the cluster will synchronise with the LAN master of
the DECT manager. The DECT manager must be selected from the
Reference option menu.

Reference
In case of Best DECT base of DM and LAN Master of DM:
¤ From the Reference option menu select the DECT manager.
In case of Ext RFPI xxx:
¤ In the Reference field enter the RFPI or the part of the RFPI of the base station(s) to which the
cluster can be synchronised.
Template Module, Version 1.2, 11.09.2018,

36
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Base stations
The Integrator automatically recognises the base stations within the network. Base stations
need to be confirmed, activated and synchronised.
The menu is only available in the Integrator user interface.

Base stations administration


Use the following web configurator page to assign base stations to the DECT manager.
¤ Settings Base stations Administration
There are two tables:
• Connected base stations lists all base stations which are already connected to the DECT
manager.
• Pending base stations lists all base stations which are not yet connected to a DECT manager.

Connected base stations


The page shows the connected base stations with the following information:
MAC address Hardware address of the base station. With this address the device is uniquely
identified within the LAN.
Base station Name of the base station. When added to the list the MAC address is used as
name. The base station located at the same device as the DECT manager is
shown as LocalBS.
The name can be edited ( page 39)
RPN (Radio Fixed Part Number) Part of the RFPI. Identifies the base station on the
air interface. It also enumerates the base station within a DECT manager. Each
DECT manager gets a group of RPN to assign to its base stations. So it is
possible to identify the DECT manager the base station belongs to.
DM Name Name of DECT manager the base station belongs to.
FW Version of the currently installed firmware.
Status Synchronization status of the base station:
0 Offline Not available
1 Deactivated Available but not activated
Template Module, Version 1.2, 11.09.2018

2 No Sync Activated but not synchronised


3 Sync Activated and synchronised,
4 Sync Overload Synchronised but DECT overload

37
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Actions
Editing base station data
¤ Click on next to the base station you want to edit . . . the data page for the base station
is opened ( page 39).
Deleting base station
¤ Select the check box of one or more base stations Click on Delete Confirm with Yes . . .
All selected base stations are deleted. They are shown in the list of pending base stations
again.
Exporting/Importing the base station configuration
You can export the base station configuration and import it into another Integrator, in order to
change the DECT manager assignment.
Exporting:
¤ Select all base stations you want to be transferred via the check mark next to the MAC
address.
¤ Click on Export Select the location where the export file should be stored using the system
file selection dialogue.
Preferably, you want to export and import base stations DECT manager by DECT manager:
¤ Filter the base station list by DM Name. So you can easily export base stations of this specific
DECT manager.
Importing:
¤ Click on Import Select the previously exported base station configuration file from your
computer’s file system.
¤ Select the DECT manager into which base station export should be imported from the DM
Name list and the IP address type from the corresponding list. Click on Import.
Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
search item . . . only entries containing text matching the search item in the selected column
Template Module, Version 1.2, 11.09.2018,

are shown in the table.


Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.
Displaying/ hiding columns:
¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.
Changing the number of list entries

38
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.
Pending base stations
The Pending base stations list shows the automatically recognised DECT base stations in the
network that have not yet been registered. If a base station is detected by several DECT
manages, there are several entries for one base station. To integrate them into your DECT multi-
cell system, they need to be confirmed and activated.
The base stations are identified by their MAC address.
You can filter the list of pending base stations by specific DECT managers to get the list shorter
and to add the base stations DECT manager by DECT manager.
Assigning a base stations to your DECT manager
¤ Click on in the row of the base station you want to add to your system . . . the data page
for the base station is opened.

The relation to a DECT manager cannot be edited and changed. To assign a base
station to another DECT manager:
¤ Delete it from the Connected base stations list . . . The base station is displayed
again in the Pending base stations list, with one entry for each DECT manager
that is detecting it on the DECT network.
¤ Select the base station entry of the desired DECT manager and add it to the
system.

Adding/Editing base stations


On this page you enter the data for a base station to be added to the DECT manager or edit the
data for a base station that is already assigned to the DECT manager.
The following information is displayed and cannot be changed:
MAC address
Hardware address of the base station. With this address the device can be uniquely identified
Template Module, Version 1.2, 11.09.2018

within the Ethernet. It cannot be changed


DM Name
Name of DECT manager the base station belongs to. local: The base station belongs to the
configuring device.

39
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Status
Synchronization status of the base station:
0 Offline Not available
1 Deactivated Available, but not activated
2 No sync Activated, but not synchronised
3 Sync Activated and synchronised
4 Sync overload Synchronised, but DECT overload

IP address
Current IP address of the Base station.
RFPI = PARI + RPN (hex)
(RFPI = Radio Fixed Part Identity) unique name of the base station in a multicell DECT network.
It consists of:
• PARI (Primary Access Rights Identity): unique system ID of a base station
• RPN (Radio Fixed Part Number): base station number within the DECT network
The two most significant bits in the RPN represent the RPN group of the DECT manager.
Current firmware version
Firmware version currently installed.
Template Module, Version 1.2, 11.09.2018,

40
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

The following data can be edited


Name / Location
This name should make it easier to assign the base station within the logical and spatial structure
of the DECT network.
¤ In the text field enter a descriptive name or description for the base station. Value: max. 32
characters
IP address type
The IP address type is copied from the setting for the DECT manager on the Network – IP page
( page 25). You can change the IP address type. The settings for the DECT manager and the
base stations do not have to match. For example, the DECT manager could receive a fixed IP
address so that it will always be able to access the web configurator with the same address, while
the base stations receive their IP addresses dynamically.
¤ Select the desired IP address type from the option menu.
If the IP address type is Static, you have to enter the IP address.
IP address
¤ Enter an IP address for the base station.
Reduce TX power by 8dB for external antenna operation
The transmitting power of the external antennas can be reduced. This may be needed in order
not to violate emission regulations, in case the device is equipped with external antennas.
¤ Click on Yes/No to reduce/not reduce the transmitting power by 8 dB.
Activating/deactivating the base station
A base station must be active to manage the calls of the connected handsets. If it is deactivated,
it will no longer connect handsets but it still stays in the list of connected base stations.
¤ Select Yes/No to activate/deactivate the base station.

Please ensure that the base station you want to deactivate is not on sync level 1.
Check your sync settings before deactivating a base station. Otherwise your system
may no longer work properly.
Adding a base station to the Connected Base Stations list
¤ Click on Confirm
Delete the base station
¤
Template Module, Version 1.2, 11.09.2018

Click on Delete base station Confirm with Yes . . . the base station is deleted. It is shown
in the list of pending base stations again.
Reboot the base station
¤ Click on Reboot base station Confirm with Yes . . . the base station is rebooted. All existing
connections managed by the base station are terminated.

41
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Base station synchronisation


Synchronisation and the logical structuring of the base stations in clusters are prerequisites for
the functioning of the multicell system, intercell handover, and (over)load balancing. Overload
balancing means that a handset can roam to a free base, when current base is fully loaded and
cannot accept further handset connections.
Base stations can be synchronised "over the air", meaning that they are synchronised via DECT.
If the DECT connection between specific base stations seems to be not reliable enough, synchro-
nisation can also take place via LAN. To carry out the synchronisation you will need the plan of
the clusters with the synchronisation level for each base station.

Synchronisation always refers to a cluster. In case you set up several clusters that are
not synchronised with one another, there will be no possibility of a handover or
(over)load balancing between them.
Synchronisation for handover between base stations in clusters managed by
different DECT managers can be configured via DECT manager administration
( page 34).
For detailed information on DECT network planning, please refer to the "N870 IP PRO - Site Plan-
ning and Measurement Guide".

A base station shows its synchronisation status with an LED ( page 34).

Synchronisation planning
Base stations that combine to form a DECT wireless network must synchronise with one another
to ensure a smooth transition of the handsets from cell to cell (handover). No handover and no
(overload) balancing is possible between cells that are not synchronised. In the event of loss of
synchronisation, the base station stops accepting calls once all ongoing calls that were being
conducted on the asynchronous base station have ended and then it re-synchronises the asyn-
chronous base station.
The synchronisation within a cluster takes place in a master/slave procedure. This means that
one base station (sync master) defines the synchronisation cycle for one or more additional base
stations (sync slaves).
The synchronisation needs some kind of synchronisation hierarchy with the following criteria:
1 There must be one single and common root source for the synchronisation in the hierarchy
(sync level 1).
Template Module, Version 1.2, 11.09.2018,

2 With synchronisation over LAN there are just two levels needed (LAN-Master and LAN-Slave).
3 DECT synchronisation usually needs more than two levels and just one hop, because most
base stations won't be able to receive the DECT signal from the root source of the synchroni-
sation (sync level 1). DECT signal providing reference timer synchronisation is relayed along
a chain of multiple base stations, until it finally synchronises the last base station in a sync
chain.
4 The number of hops along any branch of DECT synchronisation tree should be minimised,
because any hop can introduce jitter in the synchronisation timer and could so lower the
quality of the synchronisation.

42
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

DECT-based synchronisation
To relay DECT synchronisation signals from base station A to base station B, base station B must
be able to receive signals from base station A with sufficient signal quality.

DECT manager and base stations must be connected to the same Ethernet or virtual
LAN sharing a common broadcast domain.
A base station can synchronise with each base station on a higher sync level. The sync level
concept allows base stations to automatically select the best suitable base station (having a
lower sync level number) to receive synchronisation signal from. Simultaneously, it guarantees
a strictly limited number of hops along any branch in the synchronisation tree and to prevent
circles between automatically optimised synchronisation chains.
During configuration, assign one level in the synchronisation hierarchy (sync level) to each base
station. Sync level 1 is the highest level; this is the level of the sync master and appears only once
in each cluster. A base station always synchronises itself with a base station that has a better sync
level. If it sees several base stations with a better sync level, it synchronises itself with the base
station that provides the best signal quality. If it does not see any base station with a higher sync
level, it cannot synchronise.

LAN-based synchronisation
If the DECT connection between base stations seems to be not reliable enough to permanently
guarantee a stable DECT over the air synchronization, e.g., because they are separated by iron
doors or a firewall, you can determine that synchronisation should take place via LAN. In this
case the base station with the higher sync level will act as LAN master, the base station with the
lower sync level is a LAN slave. One base station must be explicitly be defined as LAN master.
Currently, it must be on DECT sync level 1.
Advantages of LAN synchronisation compared with DECT synchronisation:
• Higher flexibility in the arrangement of the base stations as no synchronisation chains need
to be formed.
• Fewer base stations required as the overlapping area of the base stations is smaller. The over-
lapping area for handset handover can be smaller, because neighboured base stations do
not need to receive each other in stable error free quality, but they must still be able to detect
each other for the process of dynamic channel selection.
• Configuration of the system is simplified as all base stations can be synchronised on one
synchronization master.
Template Module, Version 1.2, 11.09.2018

43
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Requirements for LAN synchronisation


Minimum packet delay jitter is crucial for successful synchronisation over LAN. As multiple LAN
traffic parameters could have an impact on packet delay and its jitter, specific switches and
maximum number of switch hops are required, to guarantee sufficient maximum packet delay
jitter.
Consider the following:
• The less switch hops, the lower the transmission delay and its jitter will be.
• The higher the bandwidth or quality of used switches is regarding packet delay and its jitter,
the lower the packet delay and the lower the packet delay jitter will be.
• Enhanced packet processing logics (like L3 switching or packet inspection) could have signif-
icant negative impact on the resulting packet delay jitter. If possible, they should be deacti-
vated for Gigaset N870 IP PRO base stations connected switch ports.
• Significantly increased traffic load on a switch, in the range of the maximum throughput,
could have significant negative impact on the packet delay jitter.
• VLAN based prioritisation of LAN packets could be a fruitful measure to minimize packet
delay and its jitter for Gigaset N870 IP PRO base stations.
Hints regarding PTP deviation
LAN synchronisation is based on a two layer design:
• Native PTPv2 is used to synchronise a common reference timer along all base stations
involved.
Target quality benchmark to provide sufficient PTP synchronisation along the base stations,
is to have a PTP deviation lower than 500 ns (rms). For this PTP synchronisation a few single
deviations > 500 ns are accepted and might just generate first warnings. If the PTP sync
packet deviation does continuously exceed this limit of 500 ns, the PTP synchronisation is
considered broken and will lead to new start synchronisation procedure.
• Based on the PTP synchronisation LAN master and LAN slave adjust their DECT reference
timer to one common offset to the common PTP reference timer. This common offset will be
permanently monitored by a proprietary communication.
The target quality benchmark for this synchronisation level is to see reference timer devia-
tion by this DECT reference timer sync packets: DECT-LAN-Sync deviation lower than
1000 ns. A good mean value would be 500 ns (rms).
To meet this criteria the switches themselves do not necessarily need to be PTP aware. But the
network should consider the above mentioned guidelines to meet this criteria.
Template Module, Version 1.2, 11.09.2018,

44
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Scenarios for LAN/DECT synchronisation hierarchy

Scenario 1: Pure LAN synchronisation


Use such a configuration, if all requirements for LAN synchronisation are
fulfilled and the radio coverage is not stable enough to ensure reliable synchro-
nisation.

LAN master
base 2 base 4 base 6

base 1 base 3 base 5 base 7

Configuration: Simple LAN synchronisation with base station 4 as LAN master. The DECT level
has no relevance for this configuration.

Base station Cluster DECT Level LAN Master Sync Slave


1 1 1 LAN
2 1 2 LAN
3 1 2 LAN
4 1 2

5 1 2 LAN
6 1 2 LAN
7 1 2 LAN
Template Module, Version 1.2, 11.09.2018

45
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Scenario 2: Pure DECT synchronisation


Use such a configuration if your environment ensures a stable DECT over the
air synchronisation or your LAN does not fulfil the requirements for LAN
synchronisation.
Prior to installation of base stations for DECT synchronisation, you should have
an idea, where in the centre to plan the level 1 base station and in which
distances around the centre to place the next sync level's base station. To proof
and optimise this idea into a plan you should use a coverage measurement kit.

DECT Level
3 2 1 2 3

base 3

base 4
base 7
base 2

base 1 base 5 base 6

Configuration: Pure DECT synchronisation. Each base station can synchronise with a base
station on a higher level. If more than one base station is possible the base
station with the better signal is used. The base station in the centre of the
cluster is on DECT level 1. That reduces the amount of necessary sync levels.

Base station Cluster DECT Level LAN Master Sync Slave


1 1 3 DECT
2 1 2 DECT
3 1 2 DECT
4 1 2 DECT
5 1 1
Template Module, Version 1.2, 11.09.2018,

6 1 2 DECT
7 1 3 DECT

46
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Scenario 3: Mixed
Use such a configuration, if your environment is mainly able to synchronise via
DECT but there are particular circumstances which cannot always guarantee
reliable DECT synchronisation, e.g., a passage through a fire door.
For all base stations on levels lower than the LAN master you can individually
decide whether it should be synchronised via DECT or LAN.

DECT Level
3 2 1 2 3

base 3
base 1 base 2 base 6

base 4 base 5

LAN

base 7 base 8

4 5

DECT Level

Configuration: Mixed scenario. The base stations of the cluster are separated by a firewall. The
overlap area may be large enough for handover and dynamic channel selection
but not for synchronisation. Therefore the synchronisation between one base
station on each side of the firewall takes place via LAN. The other base station
are synchronised via DECT. As the LAN master must be on DECT level 1 the base
station 4 is used as LAN master.

Base station Cluster DECT Level LAN Master Sync Slave


1 1 3 DECT
2 1 2 DECT
Template Module, Version 1.2, 11.09.2018

3 1 2 DECT
4 1 1

5 1 2 DECT
6 1 3 DECT
7 1 4 LAN
8 1 5 DECT

47
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

List of synchronised base stations


All activated base stations contained in the Connected base stations list ( page 37) appear in
the Base station synchronisation list.
¤ Settings Base stations Synchronisation
For each registered base station the following information is shown:

MAC address Hardware address of the base station. With this address the device is
uniquely identified within the LAN.
Base station Name of the base station.
DM Name Name of DECT manager the base station belongs to.
Cluster Number of the cluster to which the base is assigned.
Sync Level Synchronisation level within the sync hierarchy.
LAN Master The base station acting as LAN master is marked by a .
Sync Slave Indicates if the base station is synchronised via DECT or via LAN. For the Sync
master there is no entry in this column.
Status Synchronization status of the base station:
0 Offline Not available
1 Deactivated Available but not activated
2 No Sync Activated but not synchronised
3 Sync Activated and synchronised,
4 Sync Overload Synchronised but DECT overload
Cluster configuration
The page allows you to synchronise the system manually.
¤ Select the DECT manager you want to synchronise from the DM Name option menu . . . the
cluster configuration of the selected DECT manager is displayed below
Synchronising all clusters of the DECT manager
¤ Click on Synchronise all
Synchronising a specific cluster of the DECT manager
¤ From the Sync Slave option menu select which kind of synchronisation you want to perform
(LANor DECT) Click on Synchronise
Template Module, Version 1.2, 11.09.2018,

48
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_basestations.fm / 12/4/18

Base stations

Actions
Setting up the base station synchronisation
¤ Select the cluster to which the base should be assigned to from the Cluster option menu.
Base stations only synchronise within the same cluster, meaning that a handover of a
handset from one cluster to a neighbouring cluster is not possible. The DECT multicell system
can manage up to nine clusters.
¤ Select the synchronisation level for the base station from the DECT Level option menu.
DECT level 1 is the highest level and may appear only once in each cluster. A base station
always synchronises itself with a base station that has a better sync level. If it sees several
base stations with a better sync level, it synchronises itself with the base station that has the
strongest signal. If it does not see any base station with a higher sync level, it cannot synchro-
nise.
¤ Mark the LAN Master check box, if the base station should act as LAN master.
If synchronisation via LAN is used, there must be one base station acting as LAN master.
Currently the LAN master can only be configured on DECT level 1.
¤ From the Sync Slave option menu select whether the base station is to be synchronised via
DECT or via LAN. For the Sync master leave this column empty.
Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
search item . . . only entries containing text matching the search item in the selected column
are shown in the table.
Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.
Displaying/ hiding columns:
¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.
Template Module, Version 1.2, 11.09.2018

Changing the number of list entries


¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.

49
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

Provider and PBX profiles


Only available in the Integrator user interface.
You can use up to ten different VoIP PBX or VoIP provider profiles, e.g.
• your company's VoIP PBX
• and/or public providers from which you have requested VoIP services.
This page allows you to create a list of systems providing VoIP connections and other services for
your phones.
¤ Settings Provider or PBX profiles
The page lists the available VoIP connections.
Name The name that you have defined for the connection is displayed, or the default name
(IP1 - IP10). It can be edited ( page 50).
Domain Domain part of the user address. In the case that a connection is not used Not
configured is displayed.

Configuring provider and/or PBX profiles


¤ Click on next to the name of the VoIP connection you want to edit . . . the provider/PBX
configuration page is opened ( page 50).

Configuring provider or PBX profiles


On this page you can edit the data for the selected provider or PBX profile.
Connection name or number
¤ Enter a name for the provider or PBX profile. This name is shown in the Provider/PBX list. To
distinguish between different connections it should specify the respective VoIP service
provider.

Phone system
System
¤ Select the type of PBX you use for VoIP provisioning from the option menu.

General provider data


Template Module, Version 1.2, 11.09.2018,

Domain
¤ Enter the domain part of the user address (SIP URI). Together with the phone‘s user name it
is used to build the Address Of Record (AOR) or to build a destination out of the dialed
number.
Examples:
sip.domain.net for john.smith@sip.domain.net
10.100.0.45 for 02871913000@10.100.0.45

50
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

Proxy server address


The SIP proxy is your VoIP provider's gateway server and the first SIP server, where the device
should send SIP requests and expects to receive requests.
¤ Enter the IP address or the (fully qualified) DNS name of your SIP proxy server (max. 74 char-
acters, 0 - 9, a - z, A - Z, -, ., _).
Examples: 10.100.0.45 or sip.domain.net or sipproxy01.domain.net
Proxy server port
¤ Enter the port number of the first SIP server, where the device should send SIP requests and
expects to receive requests.
Range: 1-65535; Default: 5060 (for UDP/TCP), 5061 (for TLS)
DNS SRV SIP server redundancy lookup might provide a different server port which is used then.
Registration refresh time
¤ Enter the time intervals (in seconds) at which the phone should repeat the registration with
the VoIP server (SIP proxy). A request will be sent to establish a session. The repeat is required
so that the phone's entry in the tables of the SIP proxy is retained and the phone can there-
fore be reached. The repeat will be carried out for all enabled VoIP connections.
Values: 1 - 5 digits, > 0; Default: 600 seconds
Transport protocol
¤ Select between UDP, TCP and TLS.
UDP (User Datagram Protocol) UDP is a non session-based protocol. UDP does not establish a
fixed connection. The data packets ("datagrams") are sent as a broadcast. The recipient is
solely responsible for making sure the data is received. The sender is not notified about
whether it is received or not.
TCP (Transmission Control Protocol) TCP is a session-based transmission protocol. It sets up,
monitors and terminates a connection between sender and recipient for transporting
data.
TLS (Transport Layer Security) TLS is a protocol for encrypting data transmissions on the
Internet. TLS is a superordinate transport protocol.

Use SIP Security (SIPS)


Only if TLS is selected. SIPS enhances SIP with TLS/SSL encryption. Using SIPS makes it more diffi-
cult to listen in on the connection. Data is transmitted encrypted over the internet.
¤ Mark/unmark the check box to enable/disable the use of SIPS.
Template Module, Version 1.2, 11.09.2018

SRTP options
Only available if TLS is selected. SRTP (Secure Realtime Protocol) is a security profile to ensure
confidentiality, integrity, replay protection and message authentication for audio-visual data
transmission over IP-based networks.
¤ Select which calls should be accepted:
Secure Real Time Protocol Security is activated for voice connections.
Accept non-SRTP calls Insecure calls are accepted even when SRTP is activated.

51
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

Redundancy settings
Redundancy - DNS query
VoIP providers provide SIP server redundancy for load balancing and service reliability. SIP
servers can be identified by DNS using different queries:
A Records just the specified IP addresses and the related port numbers.
SRV + A Finds an available server port for the specified proxy and registration server. DNS
SRV allows a client to only have to know what type of service it is looking for instead
of the actual server.

Failover server
If Redundancy - DNS query = A
In case your provider supports a failover server you can enter the data here.
¤ Enable/disable the use of a failover server via the radio boxes next to Enable registration.
Registration server
¤ Enter the IP address or the (fully qualified) DNS name of the failover registration server.
SIP server port
¤ Enter the communication port used on the failover registrar.
Range: 1-65535; Default: 5060 (for UDP/TCP), 5061 (for TLS)

Network data of the service provider


Outbound proxy mode
The DECT IP multicell system allows you to configure an outbound proxy. Despite any other SIP
protocol rules, if activated (Always), the system will always send all outgoing requests towards
this outbound proxy. It can be an outbound proxy in the local network provided by the local
network provider or in the public network provided by the network/VoIP provider.
¤ Specify when the outbound proxy should be used.
Always: All signalling and voice data sent by the system is sent to the outbound proxy.
Never: The outbound proxy is not used.
If the further outbound proxy configuration is identical to the proxy and registrar configuration
it is useless and will be ignored.

The DHCP option 120 ”sip server” sent by a SIP phone would internally overrule the
outbound proxy address and port setting. Outbound proxy mode is still and exclu-
Template Module, Version 1.2, 11.09.2018,

sively in the hands of the local device administrator. By setting Outbound proxy
mode to Never, you can prevent any usage of DHCP option 120 by the DECT VoIP
phone. To allow for DHCP option 120, you should set Outbound proxy mode to
Always.

Outbound server address


This is the address, where the device should send all SIP requests to and where (in case of
successful registration) it expects to receive requests from.
¤ Enter the (fully qualified) DNS name or the IP address of your provider's outbound proxy.
Example: 10.100.0.45 or sip.domain.net or sipproxy01.domain.net

52
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

If the Outbound server address field is empty, the system behaves independently of the
selected mode, as with Outbound proxy mode = Never.
Outbound proxy port
This is the port number of the outbound proxy server, where the device should send all SIP
requests to (and where it in case of successful registration expects to receive requests from)
¤ Enter the communication port used by the outbound proxy.
Range: 1-65535; Default: 5060 (for UDP/TCP), 5061 (for TLS)
Outbound proxy port is empty and Outbound server address is a name:
The RFC3263 rules will be used to locate SIP servers and select them for load balancing and
redundancy.
Outbound proxy port is a fixed number:
The usage of DNS SRV records according to RFC3263 is blocked.
SIP SUBSCRIBE for Net-AM MWI
If activated a subscription is established for the purpose of receiving notifications about new
messages on the network mailbox.
¤ Enable/disable SIP subscription via the radio boxes next to SIP SUBSCRIBE for Net-AM MWI.

DTMF over VoIP Connections


DTMF signalling (Dual Tone Multi Frequency) is required, for example, for querying and control-
ling certain network mailboxes via digit codes, for controlling of automatic directory enquiries
or for remote operation of the local answering machine.
To send DTMF signals via VoIP, you must define how key codes should be converted into and sent
as DTMF signals: as audible information via the speech channel or as a "SIP Info" message.
Ask your VoIP provider which type of DTMF transmission it supports.
Automatic negotiation of DTMF transmission
¤ For each call, the phone attempts to set the appropriate DTMF signalling type for the codec
currently being negotiated: select Yes.
The system will use the transmission method matching best the received capabilities from
the peer based on the following priority order:
• send via RFC2833, if PT for telephone event is provided by the peer
• send via SIP INFO application/dtmf-relay, if SIP INFO method is supported by the peer
• send in-band audio
¤ Specify the DTMF signalling type explicitly: select No Select the send settings for DTMF
Template Module, Version 1.2, 11.09.2018

transmission:
Send settings of DTMF transmission
¤ Make the required settings for sending DTMF signals:
Audio or RFC 2833 DTMF signals are to be transmitted acoustically (in voice packets).
SIP Info DTMF signals are to be transmitted as code.

53
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

Settings for codecs


The voice quality of VoIP calls is mainly determined by the codec used for the transmission and
the available bandwidth of your network connection. A "better" codec (better voice quality)
means more data needs to be transferred, i.e. it requires a network connection with a larger
bandwidth. You can change the voice quality by selecting the voice codecs your phone is to use,
and specifying the order in which the codecs are to be suggested when a VoIP connection is
established. Default settings for the codecs used are stored in your phone; one setting optimised
for low bandwidths and one for high bandwidths.
Both parties involved in a phone connection (caller/sender and recipient) must use the same
voice codec. The voice codec is negotiated between the sender and the recipient when estab-
lishing a connection.
Active codecs / Available codecs
The following voice codecs are supported:
G.722 Outstanding voice quality. The G.722 wideband voice codec works at the same bit rate
as PCMA/PCMU (64 kbit/s per voice connection) but at a higher sampling rate (16 kHz).
To enable wideband connections via G.722 you have to activate the codec explicitly on
the Telephony – VoIP page ( page 67)
PCMA/ (Pulse Code Modulation) Excellent voice quality (comparable with ISDN). The required
PCMU bandwidth is 64 kbit/s per voice connection.
PCMA (G.711 a law): Used in Europe and most countries outside of USA.
PCMU (G.711 μ law): Used in USA.
G.729A Average voice quality. The necessary bandwidth is less than or equal to 8 kbit/s per
voice connection.

Activate/deactivate a codec:
¤ Select the required codec from the Available codecs/Active codecs list and click on / .
Define the sequence in which the codecs should be used:
¤ In the Active codecs list select the required codec and click on / to move it up/down.

Selection of codecs G.722 and G.729 influence the system capacity in direction to
lower amount of parallel calls per base station.

Number of parallel calls per base station depending on bandwidth

Codecs enabled Number of calls


Template Module, Version 1.2, 11.09.2018,

G711 only 10
G729 and G711 8
G722 and G729 and G711 5

54
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

RTP Packetisation Time (ptime)


Length of time in milliseconds represented by the audio data in one packet.
¤ Select the size of RTP packets to send. Select between 10 / 20 / 30 ms.
Signalling options for 'Hold' in Session Description Protocol (SDP)
Call hold means that a user requests to put an active call on hold. The holding part sends a
re-INVITE request to the held client with an SDP offer (Session Description Protocol). This SDP
offer contains the attribute line a=inactive or a=sendonly.
¤ Select which attribute should be sent in the SDP offer:
inactive The SIP endpoint would neither send nor receive data.
sendonly The SIP endpoint would only send and not receive data.

Hold towards Transfer-Target


The device enables call transfer after consultation or without consultation.
¤ Define, whether a consultation call with transfer target is put on-hold prior to the execution
of the call transfer (Yes) or not (No).

Display of caller information


¤ From the Calling Party (User Part) option menu select which information is allowed to be
transferred to the receiving part within the SIP header. Which information is actually trans-
ferred is determined by the provider.

FROM Only the FROM information can be added.


Caller identity in the form number@server, e.g.:12345678@192.168.15.1
PPI+FROM P-Preferred-Identity (PPI) or FROM can be added
The P-Preferred-Identity header field is used from a user agent to a trusted
proxy to carry the identity the user sending the SIP message wishes to be
used for the P-Asserted-Header field value that the trusted element will
insert.
PAI+PPI+FROM P-Asserted-Identity (PAI) or PPI or FROM can be added
The P-Asserted-Identity header field is used among trusted SIP entities
(typically intermediaries) to carry the identity of the user sending a SIP
message as it was verified by authentication.
Service Codes
Service codes are key sequences provided by the provider or PBX in order to activate/deactivate
Template Module, Version 1.2, 11.09.2018

specific functions on the handset. You can set the adequate service codes for activating/deacti-
vating CCBS and CCNR.
CCBS (Completion of Call to busy Subscriber) Ringback if busy
CCNR (Completion of Calls on No Reply) Ringback if no answer
¤ In the text fields Call Completion on (CCBS, CCNR)/Call Completion off (CCBS, CCNR) enter
the key sequence for activating/deactivating CCBS and CCNR.

55
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_provider.fm / 12/4/18

Provider and PBX profiles

CSTA
Computer Supported Telecommunications Applications is a standard for the interaction
between a computer and a PBX, independently from the manufacturer. If your PBX provides
CSTA applications to be used by the registered handsets you have to activate the standard here.
Account data for handset access can be configured for each handset ( page 64).
¤ Define, whether CSTA should be activated (Yes) or not (No).

Deleting the profile


¤ Click on Delete to delete the profile Confirm the operation with Yes.
Template Module, Version 1.2, 11.09.2018,

56
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

Mobile devices
You can use the web configurator to register all handsets at the DECT network and for a VoIP
connection. Use the add function of the Administration page to register single handsets or use
the Registration Centre to register groups of handsets in one process.
You can edit the settings for handsets, deactivate or delete them and make further settings e.g.,
for using directories and network services.
The menu is only available in the Integrator user interface.

Mobile devices
¤ Settings Mobile devices Administration
The currently registered handsets and place holders for handsets that could be registered are
listed on the page with the following information:
IPUI International Portable User Identity used in order to uniquely identify a
handset within the DECT network.
Username User name from the SIP account that is assigned to the handset, usually the
phone number. The name is displayed on the handsets when they are in idle
status. The setting can be changed.
Display name Display name from the SIP account that is assigned to the handset. The
display name indicates the originator of the request when the user initiates a
call.
Location Name of the DECT manager the handset belongs to.
DECT DECT registration state of the handset:
Status Meaning
ToReg System ready to register a handset
NotReg Registration not possible
InReg Registration in progress
Registered Handset is registered
SIP Indicates, if the handset has a working VoIP connection.
A VoIP connection is registered for the handset and a connec-
tion has been established successfully.
Template Module, Version 1.2, 11.09.2018

There is no VoIP connection configured or it is not possible to


establish a connection to the configured VoIP provider.
Type Model designation of the handset.
FW Current firmware version of the handset.

57
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

Actions
Adding a handset to the list
¤ Click on Add . . . the mobile devices data page is opened ( page 59).
Copying handset data for another configuration
¤ Select the check box next to the handset whose settings you want to copy. Click on Copy
. . . the mobile devices data page is opened ( page 59). The settings of the selected mobile
device except personal data are taken over for the new handset configuration.
Deleting a handset from the list
¤ Select the check box next to the handset you want to delete. Multiple choice is possible.
Click on Delete Confirm with Yes . . . all selected handsets are deleted.
Exporting/Importing the handset configuration
You can export the handset configuration and import it into another device, in order to change
the DECT manager assignment, e.g., when migrating the multicell system from a single to a
multiple DECT manager system ( page 96).
Exporting:
¤ Select all handsets you want to be transferred via the check mark next to the IPUI.
¤ Click on Export Select the location where the export file should be stored using the system
file selection dialogue.
Importing:
¤ Click on Import Select the previously exported handset configuration file from your
computer’s file system.
Editing the data of a handset
¤ Click on next to the handset you want to edit . . . the mobile devices data page is opened
( page 59).
Setting the name to be displayed in the idle display
By default, the Username is displayed in the handset’s idle display. You can determine that the
Display name should be used instead.
Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
Template Module, Version 1.2, 11.09.2018,

matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
search item . . . only entries containing text matching the search item in the selected column
are shown in the table.
Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.

58
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

Displaying/ hiding columns:


¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.
Changing the number of list entries
¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.

Registering/de-registering handsets
The page allows you to register a handset with the DECT multicell network or to prepare the
registration of numerous handsets via the Registration Center. You can assign a VoIP account,
enable online directories, and make further settings for the handsets.

Registration/de-registration in this context refers to the handset’s relationship to the


DECT network but not to SIP registration.
Template Module, Version 1.2, 11.09.2018

59
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

Registering handsets
¤ Enter an IPUI, if you want to restrict the registration to a specific handset.
¤ Enter an authentication code manually or generate it via the Generate random PIN button.
¤ Enter all configuration data for the handset.
¤ Click on Register now.
The handset with the matching IPUI is now allowed to register. If no IPUI is defined all handsets
within range can register.

The system stays in registration mode as long as it is defined via the Registration
duration parameter on the Registration Centre page ( page 65). Default: 3 min.
On the handset
¤ Start the registration procedure as described in the appropriate documentation. When
prompted, enter the PIN that has been entered or generated.

Registering a set of handsets


You can register a set of handsets without restarting the registration mode. Prepare registration
for new mobile devices as follows:
¤ Enter the actual IPUI and maybe an individual PIN
or
¤ Use wildcards as IPUI (0_1, 0_2, 0_3 … ) and preferably the same PIN for all handsets.
¤ Set the RegStatus of the handsets to To register
¤ Open the registration window for a desired time and register all handsets without further
Web UI interaction via the Registration Centre ( page 65).

Parameters
IPUI
(International Portable User Identity) Unique identifier of a handset within the DECT network. If
you edit an existing handset registration entry, the IPUI is shown and cannot be changed.
For a new entry:
¤ Enter the IPUI of the handset that should be allowed to register with the DECT network in the
text field.
If the field is empty, any handset will be allowed to register.
Template Module, Version 1.2, 11.09.2018,

60
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

RegStatus
DECT registration status of the handset entry. The option menu allows you to change the status.

Status Meaning / possible action to change the status


To register The system is ready to register a handset using these settings.
¤ Select Not registered to disable registration.
Not registered No registration possible.
¤ Select To register to allow a handset to register using these settings.
In registration Registration in progress.
¤ Select Not registered to cancel the running registration process.
Registered The handset is registered.
¤ Select To deregister to de-register the handset.
Authentication Code (PIN)
This PIN must be used on the handset to register with the DECT network.
¤ Enter a PIN in the text field. Value: 4 digits
or
¤ Click on Generate random PIN . . . a four-digit PIN is generated and shown in the text field.

De-registering handsets
¤ In the handset list click on next to the handset you want to de-register. The status is
Registered.
¤ From the RegStatus option menu select To deregister. Click on Set . . . the handset is de-
registered.
DECT de-registration successful: The handset is deleted from the Mobile devices list.
DECT de-registration not successful: The handset stays in the Mobile devices list with
status To deregister.

Settings for the handset


When registering a handset you can define important settings and assign functions at the same
time.

Personal provider data


Template Module, Version 1.2, 11.09.2018

Configure the VoIP account for the handset. If the handset is successfully registered, will be
shown in the SIP column in the Mobile devices list.

The VoIP/PBX account must be set-up beforehand ( page 50).

61
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

VoIP provider
¤ Choose a configured VoIP PBX/provider from the option menu.
The connection must be configured on the Provider or PBX profiles page ( page 50).
¤ Enter the access data for the VoIP account in the relevant fields. These fields may vary
depending on the PBX/provider profile.
Authentication name
¤ Specify the SIP authentication (HTTP digest) name. The Authentication name acts as access
ID when registering with the SIP proxy/registrar server. It is usually identical to the phone
number for the VoIP account. Value: max. 74 characters
Authentication password
¤ Enter the password for SIP authentication (HTTP digest). The phone needs the password
when registering with the SIP proxy/registrar server. Value: max. 74 characters
Username
¤ Enter the caller ID for the VoIP provider account. It is usually identical to the phone number
for the VoIP account. Value: max. 74 characters
Display name
The display name is used for presentation of the caller‘s name. In rare cases SIP networks check
the display name for any local policy of the SIP network.
Usually, the display name is optional.
¤ Enter any name that should be shown for the caller on the other participant‘s display.
Value: max. 74 characters
If Display name is empty, the Username or the phone number will be used.

Online directories
The user can call up various directories using the handset control or INT key.
Directory for direct access
The user can press and hold the directory key (bottom of the control key) to open either the list
of online directories or the local directory of the handset.
¤ Choose which directory is called up with the directory key.
Online directories A list of online directories is opened via the directory key.
Local directory The local directory is opened via the directory key..
Template Module, Version 1.2, 11.09.2018,

Corporate directory for INT key


If a corporate directory is available and configured the user can open it by pressing the INT key
(left on the handset’s control key).
¤ Choose from the list which corporate directory is opened with the INT key.
Automatic look-up
¤ Select an online directory from the list for Automatic look-up or deactivate this option.
When there is an incoming call, the caller's name is read from this directory and shown in the
display (the availability of this function depends on the online directory provider).

62
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

LDAP authentication
Up to 10 directories in LDAP format can be provided by the phone system. The access to a corpo-
rate directory can be provided individually for specific handsets.
Selected LDAP book
¤ Select the LDAP directory to be provided on the handset from the option menu.

At least one LDAP directory must have been set-up ( ).

Show other LDAP servers


¤ Select Yes if directories of other LDAP servers should be allowed to be shown.
LDAP authorisation type
¤ Select how the user authentication should be performed:
Global Credentials are set for all handsets during the LDAP directory set-up.
User Individual credentials are used.
¤ Enter Username and Password in the appropriate text fields.
SIP The credentials for the user’s SIP account are used (Authentication name and
Authentication password).

Network mailbox configuration


If a network mailbox is available for the VoIP account assigned to the handset, you have to acti-
vate this function.
¤ Enter the Call number or SIP name (URI) for the network mailbox.
¤ Activate the function via the check box.

Group pick-up
Group pick-up enables a user to accept a call for another subscriber, e.g., a pick-up group. Users
belonging to the same call pick-up group can accept all calls for the group. A pick-up group must
be established during SIP account registration. The call number or the SIP URI of a pick-up group
can be assigned to the mobile device.
¤ Enter the Call number or SIP name (URI) of the pick-up group.
¤ Activate the function via the check box.

Call manager
Template Module, Version 1.2, 11.09.2018

¤ From the Accept calls directly via Call Manager option menu select whether calls that are
transferred via the PBX call manager are to be accepted directly via Headset, via Handsfree
or not at all (No).

63
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

Missed calls and alarms


You can define if missed and accepted calls should be counted and if new messages of specific
types should be indicated via the MWI LED on the handset’s message key.
¤ Select Yes/No next to Missed calls count/Accepted calls count, to activate/deactivate the
call counter for missed and accepted calls. The information is displayed in the handset’s call
lists, missed calls are also shown on the handset’s idle display.
¤ Select Yes/No next to the message type (missed calls, missed alarms, new message on the
network mailbox), to activate/deactivate the MWI LED for the message type.
If Yes is selected, the message key will flash, if a new message of the selected types is
received.

CSTA
CSTA (Computer Supported Telecommunications Applications) is a standard for the interaction
between computer and PBX, independently from the manufacturer. If the provided CSTA appli-
cations require individual access control you can enter the access data for the handset here.

CSTA must be provided by your PBX and must be activated in the provider/PBX profile
( page 56)
Username
¤ Enter the user name for the handset’s access to CSTA applications.
Authentication name
¤ Specify the authentication name for the handset’s access to CSTA applications.
Authentication password
¤ Enter the password for the handset’s access to CSTA applications.

Broadsoft XSI services


If BroadSoft XSI services should be provided to the user on the handset, enter the credentials.

XSI services must be activated ( page 70).

Use SIP credentials


If activated, the credentials for the user’s SIP account (Authentication name and Authentication
password are used.
Alternatively, define the following credentials.
Template Module, Version 1.2, 11.09.2018,

Username
¤ Enter a user name for the user access to the menu (max. 22 characters).
Password
¤ Enter a password for the user access to the menu (max. 8 characters).

64
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_mobileDevices.fm / 12/4/18

Mobile devices

Handset Registration Centre


The registration centre allows you to register groups of handsets in one registration process. All
handsets which are listed in the mobile devices list and have the registration status To register
or Registering can be registered together.
¤ Settings Mobile devices Registration Centre
The page shows the number of mobile devices in registration status To register, Registering and
the total number of entries in the mobile devices list, including those in registration status
Registered and Not registered.
Additionally, the page shows the total amount of DECT managers and DECT managers that are
currently ready to register handsets. DECT managers are set in registration status Registering
when a registration process is started automatically according to the time settings on this page
or when registering handsets manually.

Registering handsets time-controlled


Shows the current system time. Time settings: page 83
¤ In the Registration start time field enter the time when the next registration process should
be started. Format: YYYY-MM-DD HH:mm.
¤ Click on Start now. . . . the DECT manager starts a registration process at the given time. If no
time is set, the DECT manager will start registration at once.
Setting the registration duration
¤ In the Registration duration fields determine how long (days, hours, minutes and seconds)
the DECT manager should stay in registration mode. Default: 3 min.
Closing the window and resetting the timers
¤ Click on Close . . . the registration window is closed, the time settings are reset.

When the first handset tries to register, the base closes the registration window and
finalises the registration within a very few seconds. During this time any second
handset registration attempt would be rejected. When the first handset is fully regis-
tered the base re-opens the registration window as long as defined with the Regis-
tration start time and Registration duration parameters.
If all handsets try to register in parallel, a lot of them will enter the base one by one
and so will be successfully registered, but others might enter while another registra-
tion is not yet completed and so they will be rejected.
Template Module, Version 1.2, 11.09.2018

Single handsets that are rejected have to be registered by a new registration proce-
dure or manually.

65
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_telephony.fm / 12/4/18

Telephony settings

Telephony settings
The menu is only available in the Integrator user interface.

General VoIP settings


¤ Settings Telephony VoIP
This page allows you to make some general settings for the VoIP connections.
SIP port
¤ Enter the SIP port used for VoIP connections.
Range: 1-65535; Default: 5060
Secure SIP port
¤ Enter the SIP port used for secure VoIP connections (TLS).
Range: 1-65535; Default: 5061
SIP timer T1
¤ Enter the estimated round trip time of an IP packet between a SIP client and a SIP server (the
time it takes between sending out the request to the point of getting a response).
Default: 500 ms
SIP session timer
¤ Defines a session expiry interval: If the session isn't refreshed within the interval, the session
is released. Session refresh is started after half of the interval by a re-INVITE message, which
the peer side has to confirm to get the session refreshed.
Values: max. 4 digits, min. 90 sec; Default: 1800 sec;
Failed registation retry timer
¤ Specify after how many seconds the phone should attempt to re-register when the initial
registration has failed.
Values: max. 4 digits, min. 10 sec; Default: 300 sec;
Subscription timer
¤ Defines the expiration time (in seconds) of a subscription. In order to keep subscriptions
effective, subscribers need to refresh subscriptions on a periodic basis.
Template Module, Version 1.2, 11.09.2018,

Default: 1800 s
PRACK
¤ (Provisional Response Acknowledgement) SIP provisional responses do not have an
acknowledgement system so they are not reliable. The PRACK method guarantees a reliable
and ordered delivery of provisional responses in SIP.

66
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_telephony.fm / 12/4/18

Telephony settings

Security settings
The phone system supports the establishment of secure voice connections over the internet via
TLS certificates. Thereby, public and private keys are used to encrypt and decrypt the messages
that are exchanged between SIP entities. The public key is contained within the certificate of an
IP entity and is available for everyone. The private key is kept secret and is never revealed to
anyone. The server certificate and the private key must be uploaded to the base stations.
¤ Click on Browse... and choose the file containing the certificate or the private key from the
file system of your computer or network click on Upload . . . the file is uploaded and
shown in the appropriate list.
SIP security password
¤ If your private key is protected by a password, enter it here.

Quality of Service (QoS)


The voice quality depends on the priority of the voice data in the IP network. Prioritising the VoIP
data packets is done using the QoS protocol DiffServ (Differentiated Services). DiffServ defines a
number of classes for the quality of service and, within these classes, various priority levels for
which specific prioritisation procedures are defined.
You can specify different QoS values for SIP and RTP packets. SIP packets contain the signalling
data, while RTP (Real-time Transport Protocol) is used for the voice transfer.
¤ Enter your chosen QoS values in the SIP ToS / DiffServ and RTP ToS / DiffServ fields. Value
range: 0 - 63.
Common values for VoIP (default setting):
SIP 34 High service class for fast switching of the data flow (Expedited Flow)
RTP 46 Highest service class for fast forwarding of data packets (Expedited Forwarding)

Do not change these values without consulting your network operator first. A higher
value does not necessarily mean a higher priority. The value determines the service
class, not the priority. The prioritisation procedure used in each case meets the
requirements of this class and is not necessarily suitable for transferring voice data.

Audio quality
The phone system allows the user to make calls with excellent voice quality using the wideband
codec G.722. One base station enables a maximum of five wideband calls.
¤ Settings Telephony Audio
Template Module, Version 1.2, 11.09.2018

The page allows you to enable/disable the use of the wideband codec G.722 for the telephone
system.
¤ Mark/unmark the check box to enable/disable wideband calls
¤ Click on Set to save the settings of this page.

To allow users to make wideband calls, the codec G.722 must have been activated for
the provider profile that is used for the connection ( page 54).

67
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_telephony.fm / 12/4/18

Telephony settings

Call settings
On this page you can make advanced settings for VoIP connections.
¤ Settings Telephony Call settings

Call transfer
Participants can transfer a call to another participant as long as the PBX/provider supports this
function. The call is transferred using the handset menu (via the display key) or using the R key.
You can expand or change the settings for call transfer.
Call transfer via R key
Activated: Users can connect two external callers with each other by pressing the R key. The
connections with both parties are terminated.
Transfer call by on-hook
Activated: The two participants are connected with one another when the user presses the end
call key. The intermediary's connections with the participants are terminated.
Determine transfer target address
¤ Select how the transfer target address (Refer-To URI) is to be derived:
From transfer target's AOR (Address of Record)
From transfer target's transport address (Contact URI)
Most common PBX platforms show good results by using the AOR as transfer target address.
In case there are problems with transfer especially via transparent proxies, rather than call
switching PBX, it might be worthwhile to test with transfer target address derived from transfer
target’s transport address.

Access Code
You may have to enter an access code for external calls (external prefixes e.g., "0"). You can save
this access code in the DECT manager configuration. These settings apply to all registered hand-
sets.
¤ Enter an access code in the Access Code text field. Value: max. 3 digits (0 – 9, *, R, #, P)
¤ Select when the phone numbers should be automatically prefixed with the digits, e.g. when
dialling from a call list or a directory.
Template Module, Version 1.2, 11.09.2018,

68
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_telephony.fm / 12/4/18

Telephony settings

Area Codes
If you use VoIP to make a call to the fixed line, you may also have to dial the area code for local
calls (depending on the provider).
You can set your telephone system so that the access code is automatically predialled when any
VoIP call is made in the same local area, and also for national long-distance calls. This means that
the access code is set before all phone numbers that do not start with 0 – even when dialling
numbers from the directory and other lists.
You can change these settings if required.
Country
¤ From the option menu select the country or region where your telephone system is to be
used . . . the international and national prefix is then entered in the Prefix and Area code
fields.

International settings
Prefix Prefix of the international area code. Value: max. 4 digits, 0-9
Area code International area code. Value: max. 4 digits, 0-9
Example "Great Britain": Prefix = 00, Area code = 44

Local settings
Prefix Prefix of the local area code. Value: max. 4 digits, 0 - 9. These digits are placed in
front of the local area code for national long-distance calls.
Area code Local area code for your town/city (depending on country/provider). Value:
max. 8 digits, 0-9
Example "London": Prefix = 0, Area code = 207

Tone Selection
Tones (e.g., dialling tone, ring tone, busy tone or call waiting tone) vary from one country or
region to another. You can choose from various tone groups for your telephone system.
Tone scheme
¤ Select the country or region whose ring tones are to be used for your phone from the option
menu.
Template Module, Version 1.2, 11.09.2018

69
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_telephony.fm / 12/4/18

Telephony settings

XSI services
BroadSoft XSI (Xtended Service Interface) allows remote applications to integrate with Broad-
Soft services to perform telephony-related actions and to be notified about telephony events.
N870 IP PRO enables the use of XSI services to provide the user with XSI directories and call lists.
If you want to use XSI services, you need to enable the services and enter the XSI server address
on this page.
¤ Settings Telephony XSI Services
Server address
¤ Enter the URL of the XSI server in the text field.
Enable XSI directories
¤ Mark the check box, if you want to use XSI directories. Specific XSI directories must be set up
as online directory on the XSI page ( page 75).
Enable XSI call logs
¤ Mark the check box, if you want to use XSI call logs.
Template Module, Version 1.2, 11.09.2018,

70
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineDirectories_Gigaset.fm

Online directories

Online directories
N870 IP PRO allows you to set up up to ten corporate directories in LDAP format, a public and a
corporate directory in XML format, as well as different XSI directories and make them available
to the registered handsets.
Use the handset settings ( page 61) to specify which keys are to call up the directory.

Corporate online directories (LDAP)


You can set up up to ten corporate directories in LDAP format for the phone system and make
one of them available to the registered handsets. If you wish to use a company directory on the
telephone system, you must activate it on the Web configurator.
¤ Settings Online directories Corporate
The page lists the available LDAP directories.
Name The name that you have defined for the directory is displayed, or the default name
(LDAP1 - LDAP10). It can be edited ( page 71).
Server url If the directory is configured, the server URL is displayed.

Configuring LDAP directories


¤ Click on next to the name of the LDAP directory you want to edit . . . the LDAP configu-
ration page is opened ( page 71).

Detailed information about LDAP configuration can be found at wiki.gigasetpro.com

Configuring an LDAP directory


On this page you can edit the data for the selected LDAP directory.

Access to the LDAP data server


The directory is provided via an LDAP server. You need the server address, the server port and
the access data for the directory that you wish to use.
¤ Enter a name in the Directory name field (max. 20 characters). This is the name under which
the directory will be displayed on the handsets.
¤ Mark the Enable directory option, so that the directory is displayed on the telephones.
Template Module, Version 1.2, 11.09.2018

Server address / Server port


¤ Enter the URL of the LDAP server and the port the LDAP server expects database requests
(Default: 389)
LDAP Search base (BaseDN)
¤ The LDAP database is hierarchical in design. With the LDAP Search base (BaseDN) param-
eter, stipulate in which area the search should begin.
Default: 0, the search starts at the upper area of the LDAP database.

71
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineDirectories_Gigaset.fm

Online directories

User access data


If you want to define access data that have to be used by all users:
¤ Enter the access data for the LDAP directory in the Username and Password fields (max. 254
characters each).
If you want to use individual access data for each handset, the access data is to be set during the
handset configuration ( page 63).

Settings for searching the LDAP database and displaying the result
Enable list mode
¤ Define what should be initially shown, when the user opens the LDAP directory.
Activated: A list of all entries of the LDAP directory is shown.
Not activated: An editor is opened first that allows the user to select a specific search area
within the LDAP database and thereby to reduce the number of entries.

Filters
Using the filters, you can define criteria against which specific entries can be searched in the
LDAP database. One filter consists of one or more search criteria. A search criterion contains the
query for an LDAP attribute.
Example: sn=%
The sn attribute stands for surname. The percent sign (%) is a place holder for the user entry.
Rules for defining filters:
• Multiple criteria can be connected using logical AND (&) and/or OR (|) operators.
• The logical operators "&" and "|" are placed before the search criteria.
• The search criterion must be placed in brackets and the whole expression must be termi-
nated with a bracket again.
• AND and OR operations can be combined.
Examples:
AND operation: (& (givenName=%) (mail=%))
Searches for entries in which the first name and mail address begin with
the characters entered by the user.
OR operation: (| (displayName=%) (sn=%))
Searches for entries in which the display name or surname begins with the
Template Module, Version 1.2, 11.09.2018,

characters entered by the user.


Combined (|(& (displayName=%) (mail=%))(& (sn=%) (mail=%)))
operation: Searches for entries in which the display name and mail address or the
surname and mail address begin with the characters entered by the user.
Information on attributes page 74

72
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineDirectories_Gigaset.fm

Online directories

Name filter
The name filter decides which attribute is used for the search.
Example:
(displayName=%). The percent sign (%) is replaced by the name or part of the name entered
by the user.
If a user enters the letter "A", for example, all entries in which the attribute displayName
begins with "A" are searched for in the LDAP database. If the user then enters a "b", entries are
searched in which the displayName begins with "Ab".
Number filter
The number filter stipulates the criteria for the automatic completion of telephone numbers.
Example:
(|(telephoneNumber=%)(mobile=%)). The percent sign (%) is then replaced by the part of the
telephone number entered by the user.
When dialling, if a user enters the numbers "123", for example, all telephone numbers that
begin with "123" are searched for in the LDAP database. The telephone number is completed
with the addition of information from the database.
Additional filters
You can set two additional filters that will be offered to the user in order to specify the search
more detailed.
¤ In the additional name fields enter the attribute name.
¤ In the corresponding value fields enter the attribute values.
Example:
Additional filter #1 name City
Additional filter #1 value (|(l=%))
Additional filter #2 name Street
Additional filter #2 value (|(street=%))
In addition to the fields defined in the Name filter parameter, the City and the Street fields
are provided to the user. The user input for City is passed to the LDAP server in the I attribute,
the user input for Street is passed in the street attribute.

Display format
In the Display format field you can stipulate how the search result is to be displayed on the
handset.
¤ Enter combinations of different name and number attributes and special characters. You can
Template Module, Version 1.2, 11.09.2018

select common formats from the attributes that are listed in the Configuration of directory
items section of the page.
For the attribute values to be shown for the required attribute, the attribute name must be
preceded by a percent sign (%).

73
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineDirectories_Gigaset.fm

Online directories

Example:
Data of an directory entry on the LDAP server:
displayName Peter Black telphoneNumber 0891234567890
givenName Peter mobile 012398765432
sn Black
...
Attribute definition in the Web configurator:
Display format %sn, %givenName; %telephoneNumber/%mobile
The entry is shown on the handset as follows:
Black, Peter; 0891234567890/012398765432

Max. number of search results


¤ Enter the maximum number of search results that is to be returned by one search operation.

Attributes
A range of attributes are defined in the LDAP database for a directory entry, e.g. surname, first
name, telephone number, address, company, etc. The quantity of all attributes which can be
saved in one entry is stored in the relevant LDAP server scheme. In order to be able to access
attributes or define search filters, you must know the attributes and their designation in the
LADP server. The majority of attribute designations are standardised, however specific attributes
can also be defined.
¤ For each field of a directory entry that should be displayed on the handsets enter the name
of the corresponding LDAP attribute. Multiple attributes can be separated by commas.
Examples:
Field of a directory entry Attribute name in the LDAP database
First name givenName
Surname sn, cn, displayName
Phone (home) homePhone, telephoneNumber
Phone (office) telephoneNumber
Phone (mobile) mobile
E-mail mail
Fax facsimileTelephoneNumber
Company company, o, ou
Template Module, Version 1.2, 11.09.2018,

Street street
City I, postalAddress
Zip postalCode
Country friendlyCountryName, c
Additional attribute user-defined
¤ Mark the check box Additional attribute can be dialled, if an additional attribute is defined
and it is a phone number.
A detailed configuration example can be found in section "LDAP directory – configuration
example" page 103

74
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineDirectories_Gigaset.fm

Online directories

Online directories in XML format


A public and/or a corporate online directory in XML format can be made available to the user.
Use this page to enter the provider's details and a name for the directory.
¤ Settings Online directories XML
¤ Select Public or Corporate
Directory name
¤ Enter a name for the directory. This is the name that will be displayed on the handsets when
the user opens the directory list by pressing the directory key.
Server address
¤ Enter the URL of the online directory provider in the Server address field.
Username / Password
¤ Enter the access data for the online directory in the Username and Password fields.
List update / Refresh
Activated: The result list at the handset will automatically request the next portion of results
when browsing through it.

Enabling online directories


You can enable/disable different kinds of public directories (White Pages, Yellow Pages or Public
Private Pages) that are provided by the given provider.
¤ Mark/unmark the check box next to the public directory you want to enable/disable.
¤ Click on Set to save the settings of this page.

Online directories – XSI


If one or more online directories are provided via an BroadSoft XSI service, use this page to set
up the server access, enable the directories and assign directory names that are to be displayed
on the users‘ handsets.

The XSI directory service must be enabled on the Telephony – XSI Services page
( page 70).

¤
Template Module, Version 1.2, 11.09.2018

Settings Online directories XSI


Server address
If XSI services are enabled the address of the XSI server is shown here.
Enable XSI directories
¤ Mark the check box, if you want any of the following XSI directories to be provided on the
users‘ handsets.
Enable specific XSI directories
¤ Mark the check box next to the XSI directories that should be provided.

75
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineDirectories_Gigaset.fm

Online directories

Directory name
¤ For the selected XSI directories enter a name in the Directory name field. This is the name
under which the directory will be displayed on the handsets.
Template Module, Version 1.2, 11.09.2018,

76
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_onlineServices.fm / 12/4/18

Online services

Online services
Additional functions as Info services, PBX control, and customer specific RAP (XHTML) applica-
tions can be made available to the user via the handset menu Info Centre . For this purpose four
additional menu entries can be defined that will be inserted into the handset user interface.
The additional functions must be available as well formatted XHTML pages. For information on
the supported XHTML format, please visit wiki.gigasetpro.com.
¤ Settings Online services XHTML
The page shows the following information for the defined menus:
Name The name that you have defined for the menu is displayed.
Server url If the XHTML access is configured, the server URL is displayed.

Add SIP-ID
If the option is enabled, the device will add the SIP ID in the GET request that are addressed to
the server.
¤ Mark the check box Add SIP-ID in order to activate the option.

Adding / editing an entry


You can define up to four menu entries.
¤ Click on in an empty row or in a row with an already configured entry in order to edit it.
Activate
¤ Mark the option, so that the menu is displayed on the handsets.
Name for menu
¤ Enter a name in the text field (max. 22 characters). This is the name under which the menu
will be displayed on the handsets.
Server address
¤ Enter the URL of the server providing the service.
The access to the service can be protected by user name and password.
Use SIP credentials
If activated, the credentials for the user’s SIP account are used (Authentication name and
Template Module, Version 1.2, 11.09.2018

Authentication password, page 61).


Alternatively, the following credentials can be used.
Username
¤ Enter a user name for access to the menu (max. 22 characters).
Password
¤ Enter a password for access to the menu (max. 8 characters).

77
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

System settings

Web configurator access rights


On this page you define the access rights for the web configurator user interface.
¤ Settings System Web configurator

Changing the web configurator password


For security reasons, you should frequently change the password for web configurator access.
There are two user roles with different user IDs, admin and user ( page 21). The user ID is disa-
bled by default. You can activate it here.
The password is set depending on the user role. The administrator is allowed to change the pass-
word for both admin and user. Logged on as user you can only change the password for user.

If you have forgotten the password, you will have to reset the device to the factory
settings ( page 18).

New password
¤ Enter a new password for the administrator/user access to the web configurator. Default:
admin/user
Repeat password
¤ Repeat the new password entered in the Repeat password field.
Show password
¤ To view the entered characters mark the check box near Show password.
Change password for all Dect Managers
¤ Click on the button, if you want the password to be assigned to all DECT managers.
The password can also be set individually for each DECT manager using the web configurator on
the DECT manager systems.
Activate user access
¤ Click on Yes/No to enable/disable the ID for the user role.
Template Module, Version 1.2, 11.09.2018,

Enabling CLI access to the device configuration


Only available in the Integrator user interface.
It is possible to perform the device configuration via CLI (Command Line Interface) using SSH
from a remote system. Secure Shell (SSH) is a program for logging into a remote machine and for
executing commands on a remote machine. It provides secure encrypted communications
between two untrustworthy hosts over an insecure network.
Detailed information on CLI commands can be found in the online help of the web configurator.

78
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Activated if password is longer than 7 characters


The CLI access is automatically enabled if you have entered a valid password that has more than
seven characters and click on the Set button. = enabled; = disabled
CLI password
¤ Enter a password for the administrator access to the configuration via SSH. Value: min. 8, max.
74 characters
Repeat password

The user name for the CLI access is cli.

¤ Repeat the new password entered in the CLI Password (Admin) field.
Show password
¤ To view the entered characters mark the check box next to Show password.

Loading the web security certificate


Only available in the Integrator user interface.
The web configurator is protected by SSL/TLS security mechanism. That means that data transfer
is encrypted and that the website is identified to be who it claims to be. The Internet browser
checks the security certificate to determine that the site is legitimate. The certificate may be
updated from time to time. If a new certificate is available you can download it to your computer
or network and then upload it to the device.
¤ Click on Browse... next to Web security certificate and select the local certificate file from
your computer‘s file system click on Upload . . . the selected certificate file is loaded and
added to the certificate lists.
¤ If the certificate requires a password, enter it in the Web security password field.
Template Module, Version 1.2, 11.09.2018

79
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Provisioning and configuration


Only available in the Integrator user interface.
Provisioning is the process for uploading the necessary configuration and account data to the
VoIP phones (here the DECT bases). This is done by means of profiles. A profile is a configuration
file that contains VoIP phone-specific settings, VoIP provider data as well as user-specific
content. It has to be available on an HTTP provisioning server which is accessible in the public
(Internet) or local network.
Auto-configuration is defined as the mode of operation by which the telephone system
connects automatically to a server and downloads both provider-specific parameters (such as
the URL of the SIP server) and user-specific parameters (such as the user name and password)
and stores them in its non-volatile memory. Auto-configuration is not necessarily limited to the
parameters required for doing VoIP telephony. Auto-configuration can also be used to configure
other parameters, e.g. settings for online service, if the VoIP phones support these features.
However, for technical reasons auto-provisioning is not possible for all configuration parameters
of the phone.

Detailed information on how to establish a provisioning server and create provi-


sioning profiles for Gigaset phones: wiki.gigasetpro.com

¤ Settings System Provisioning and configuration


This page allows you to define the provisioning server for the telephone system or download a
configuration file and to start an auto-configuration process.
Provisioning server
¤ Enter the URL of your provisioning server in the text field. Value: max. 255 characters; Default:
the Gigaset provisioning server
Auto configuration file
If you have received a configuration file from your provider, you download it to the phone
system.
¤ Click Browse... and select the configuration file from your computer‘s file system click on
Upload . . . the selected configuration file is loaded.
Start auto configuration
¤ Click on the button . . . the provisioning profile is downloaded and installed on the system.

The process will take some time and requires a system restart. Connections with
Template Module, Version 1.2, 11.09.2018,

mobile devices will be terminated.


For security reasons you should save the configuration before you start an auto-
configuration process ( page 87).

80
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Security
Only available in the Integrator user interface.
The page allows you to organise the certificates used for secure internet communication and to
define the credentials for HTTP authentication.
¤ Settings System Security

Certificates
The phone system supports the establishment of secure data connections on the Internet with
the TLS security protocol (Transport Layer Security). With TLS, the client (the phone) uses certif-
icates to identify the server. These certificates must be stored on the base stations.
Accept all certificates
¤ Mark the Yes radio button, if you want to accept all certificates.
Server certificates / CA certificates
The lists contain the server certificates or CA certificates that have been certified by a certifica-
tion authority (CA). The certificates in both lists have already been implemented by default or
have been downloaded via the Web configurator and are classed as valid, i.e., have been
accepted.
If one of the certificates becomes invalid, e.g., because it has expired, it is transferred to the
Invalid certificates list.
Invalid certificates
The list contains the certificates that have been received from servers but have not passed the
certificate check, and certificates from the Server certificates / CA certificates lists that have
become invalid.
Accepting / rejecting invalid certificates
Accepting a certificate:
¤ Select the certificate and click on the Accept button . . . depending on its type, the certificate
is transferred to one of the Server certificates / CA certificates lists (even if it has already
expired). If a server responds again with this certificate, this connection is accepted immedi-
ately.
Reject a certificate:
¤ Select the certificate and click on the Reject button . . . the certificate is transferred to the
Server certificates list with the label Rejected. If a server responds again with this certificate,
Template Module, Version 1.2, 11.09.2018

this connection is rejected immediately.


Checking information about a certificate
¤ Select the certificate and click on the Details button. . . . a new web page appears, displaying
the properties of the certificate.
Deleting a certificate from one of the lists
¤ Select the certificate and click on the Remove button. The certificate is deleted from the list
immediately.

81
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Import local certificate


You can make available further certificates to your phone system. The certificates must have
been downloaded to your computer before.
¤ Click Browse... and select the local certificate file from your computer‘s file system click on
Upload . . . the selected certificate file is loaded and, depending on its type, added to one of
the certificate lists.

HTTP authentication
Define the credentials (user name and password) for HTTP authentication. The credentials are
used for HTTP digest authentication of the provisioning client with the provisioning server.
HTTP digest username
¤ Enter the user name for HTTP authentication. Value: max. 74 characters
HTTP digest password
¤ Enter the password for HTTP authentication. Value: max. 74 characters
Template Module, Version 1.2, 11.09.2018,

82
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Date and time


Only available in the Integrator user interface.
By default, the system is configured so that the date and time are transferred from a time server
on the internet. The page allows you to change the time servers, to set your time zone, and to
make arrangements in case the internet time servers are not available.
¤ Settings System Date and time
Time server
There are some common time servers preset in the field.
¤ Enter your preferred time server in the text field. Multiple time servers can be entered sepa-
rated by commas. Value: max. 255 characters
Time Zone
¤ Select the time zone for your location from the option menu.
System time
Shows the time currently set for the phone system. It is updated every minute.

Fallback option
In case the internet time servers are not available you can set the time manually.
¤ Enter the time in the System time text field. Once you have started editing the automatic
time update stops.
Act as Local Time Server
You can determine the internal time server to act as local time server for your network.
¤ Click on Yes/No to determine the internal time server to act/not to act as local time server.
¤ Click on Set to save the settings on this page.

Date and time are synchronised system-wide on all base stations and handsets. it can
take up to one hour until the manually changed time is visible on every handset.
Synchronisation is carried out in the following cases:
• If the date or time has been changed on the DECT manager.
• If a handset is registered to the telephone system.
• If a handset is switched off and switched back on again, or is outside the wireless
range of the telephone system for more than 45 seconds and then comes back
Template Module, Version 1.2, 11.09.2018

into range.
• Automatically every night at 4.00 am.
You can change the date and time on the handset. This setting only applies for that
handset and will be overwritten when the next synchronisation takes place.
The date and time are displayed in the format set for that handset.

83
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Firmware
Regular updates to the firmware for the Integrator/DECT manager and base stations are
provided by the operator or supplier on a configuration server. You can upload these updates
onto the Integrator/DECT manager as required. If a firmware update is provided in the form of
an update file, you can store it on your computer and download it from there.

The base stations‘ firmware is updated automatically by the DECT manager.

¤ Settings System Firmware

Firmware of the local system


Current version
Shows the current firmware version of the Integrator/DECT manager on which you are logged in.
Backup available for previous version
You can downgrade the firmware by installing any older version. When installing a new firmware
the system automatically creates a data backup for the recent firmware. If you later downgrade
to this version the data backup will be installed on the system. This way you have a downgrade
to previous firmware version and data settings.

Downgrade to any other version will reset the device to factory settings.

Selecting the firmware update file


¤ In the URL to firmware file text field specify the URL of the configuration server where the
firmware is located
or
¤ Click Browse... and select the firmware file from your computer‘s file system.
Starting the firmware update

At a specific date: ¤ Deselect the check box Immediately Enter the exact start time in the
format: YYYY-MM-DD HH:mm
Immediately: ¤ Select the check box next to Immediately (default) . . . the firmware
update is started when you click on the Set button.
Template Module, Version 1.2, 11.09.2018,

Confirmed schedule
Shows Immediately or the date for the next planned firmware update.
¤ Click on Set to save the settings and to start the firmware update.
Once the update process starts, the system updates the DECT manager and all subordinate base
stations automatically. No action is needed. The handsets lose their connection to the bases
during the updating process. You can tell that the update has been successful when the hand-
sets re-establish the connection to the base.
You can monitor in the base station list the current version of base station and the base stations
and DECT managers offline most likely for firmware update.

84
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

The firmware update may take up a longer period. Do not disconnect the devices
from the local network during this time.

For test reasons (e.g. for testing a new release) it is possible to have a specific firmware
version on a DECT manager subsystem which may be different from the rest of the
system.
Handover between DECT manager systems is only possible if they have a matching
protocol version.
A DECT manager with protocol version different to the system integrator cannot start
it's service because it is not interoperable to the system integrator. It just could do a
software update to a matching software and protocol version.

Firmware of all DECT managers


The DECT managers used in the multicell system are listed with their name, the current firmware
version, and, if applicable, the settings for planned firmware updates.
Firmware update configuration is carried out analogous to the configuration for the local
system.
Editing the data of a DECT manager
¤ Click on next to the DECT manager you want to edit . . . the DECT manager firmware
page is opened.
Changing the appearance of the list
Filtering the list:
¤ Enter a search item (full field content) in the text field . . . only entries containing text
matching the search item in any column are shown in the table.
Filtering the list by column content:
¤ In the Search in option menu select the columns which should be searched for the entered
search item . . . only entries containing text matching the search item in the selected column
are shown in the table.
Sorting the list:
¤ Click on the arrows next to the column header to sort the table on the column content in
ascending or descending order.
Displaying/ hiding columns:
¤ Click on the View option menu on the right Select the columns you want to be displayed
Template Module, Version 1.2, 11.09.2018

in the table ( / = displayed/hidden).


Names of columns which cannot be hidden are greyed out.
Changing the number of list entries
¤ On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).

85
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Browsing through the list


If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.

Managing firmware updates for DECT managers


This page is used to manage the firmware updates of a DECT manager.
DM Name
Name of the DECT manager. It can be edited.
Current version
Shows the current firmware version of the Integrator/DECT manager.
URL to firmware file
¤ In the text field specify the URL of the configuration server where the firmware is located.
Starting the firmware update

At a specific date: ¤ Deselect the check box Immediately Enter the exact start time in the
format: YYYY-MM-DD HH:mm
Immediately: ¤ Select the check box next to Immediately (default) . . . the firmware
update is started when you click on the Set button.
Confirmed schedule
Shows Immediately or the date for the next planned firmware update.
Template Module, Version 1.2, 11.09.2018,

86
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Save and restore


Only available in the Integrator user interface.
This page allows you to save and restore the system configuration.
¤ Settings System Save and restore
Once you have configured the DECT manager and after making any changes to the configura-
tion, particularly registering or de-registering handsets, you should save the latest settings in a
file on the computer so that the current system can be restored quickly if problems occur.
If you change the settings accidentally or you need to reset the DECT manager due to a fault, you
can reload the saved settings from the file on your computer to your telephone system.
The configuration file contains all system data including the DECT registration data of the hand-
sets, but not the calls list on the handsets.
Saving configuration data
¤ Click on Save settings Select the location where the configuration file should be stored
using the system file selection dialogue. Enter a name for the configuration file.
Restoring configuration data
¤ Click on Browse... Select the previously saved configuration file from the file system of
your computer. Click on Upload . . . the selected configuration file is loaded.

The secure configuration file can also be loaded onto a new device.
Prerequisites:
• The old device must no longer be in operation.
• The firmware version of the new device must correspond, at least, with the version
of the device from which the data is saved, including the set patches.

Reboot
Only available in the Integrator user interface.
This page allows you to reboot the device.
¤ Settings System Reboot and reset
¤ Click on Reboot now Confirm with Yes . . . the reboot starts immediately.

On a system with embedded Integrator you can decide, if you want to reboot the
Template Module, Version 1.2, 11.09.2018

local DECT manager too.


All existing connections managed by the affected base stations are terminated.
To reboot one single DECT manager: page 31
To reboot one single base station: page 39

87
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

DECT settings
Only available in the Integrator user interface.

Changing one of these settings requires a restart of the system. Ongoing calls will be
cancelled.

ECO DECT
ECO DECT is an environment-friendly technology which reduces the power consumption and
enables a variable reduction of transmission power.
DECT Radiation power
¤ Set the DECT radiation power to your needs:
Maximum The device range is set to maximum (default). This guarantees the best
range: connection between the handset and the base stations. In idle status, the
handset will not send radio signals. Only the base station will maintain
contact with the handset via a low wireless signal. During a call, the trans-
mission power automatically adapts to the distance between the base
station and handset. The smaller the distance to the base, the lower the
radiation.
Limited range: The radiation is reduced by up to 80 %. This will also reduce the range.

DECT security settings


DECT radio traffic between base stations and handsets is encrypted by default. The following
options allow you to define the security settings in more detail.
DECT Encryption
¤ Activate/deactivate the option.
Activated: All calls are encrypted.
Deactivated: No calls are encrypted.

Enhanced Security - Early Encryption and Re-Keying


¤ Activate/deactivate the option.
Activated: The following messages are encrypted:
• CC (Call Control) messages in a call
• Data that may be sensitive at early stages of the signalling, e.g., dialling
Template Module, Version 1.2, 11.09.2018,

or CLIP information sending


The key used for encryption is changed during an ongoing call and thus
improving the security of the call.
Deactivated: No CC messages or early data are encrypted.

88
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / settings_system.fm / 12/4/18

System settings

Enhanced Security - Automatic release for non-encrypted calls


¤ Activate/deactivate the option.
Activated: If encryption is activated, it will be released in the case that a call is initiated
by a device that is not supporting encryption.
Deactivated: Encryption is never released.

DECT radio settings


Due to different national regulations DECT units are required to use different frequency ranges
to make them compatible with DECT systems in other areas. You can adapt the frequency range
of the N870 IP PRO Multicell System to the requirements of your region.
DECT Radio band
¤ Select the radio frequency band used in your region.

Please select the DECT frequency band your system should operate according to
your region.This is a system wide setting. Changing the setting will reboot the DECT
radio part. Wrong setting may cause violation of legal regulations. In case of doubt,
contact your Telecommunications Authority.
Template Module, Version 1.2, 11.09.2018

89
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / dignostics.fm / 12/4/18

Diagnostics and troubleshooting

Diagnostics and troubleshooting

Status information
The web configurator provides a status page with important information on the multicell system
operation and the connected devices.
¤ Status Overview
The following information is provided.
Integrator status • Device name *
• Device role *
• MAC address *
• IP address *
• DECT Frequency band
• DECT PARI
• Firmware version *
• Date and time *
• Last backup
DECT managers • Number of DECT managers
• Number of DECT managers with deviating Firmware Version
Base stations • Number of active base stations
• Number of pending base stations
• Call limit for base station
Mobile devices • Number of registered mobile devices
• Number of mobile devices to register
• Number of mobile devices with SIP registration

The list shows the items that are shown on the Integrator. Items marked by an asterisk
(*) are also displayed on the status page of the DECT managers.
Template Module, Version 1.2, 11.09.2018,

90
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / dignostics.fm / 12/4/18

Diagnostics and troubleshooting

Base station events


Only available in the Integrator user interface.
This page displays counters for diagnostic purposes relating to various events that affect the
base stations, e.g. active radio connections, handovers, unexpectedly terminated connections,
etc.
¤ Status Statistics Base stations
The following information is given:
DECT Manager Name of the DECT manager responsible for the base stations, period of time
during which the events have been collected, total number of missed calls
of all managed base stations within the given time period
¤ Click on next to the DECT Manager entry to display the clusters of the
DECT manager.
Note: The symbol next to the DECT manager name indicates that there
could be a situation which requires attention.
Cluster Cluster number, summary of the collected events for all cluster base stations
¤ Click on next to the Cluster entry to display the base stations of the
cluster.
Base station Name of the base station

Some of the following information may be hidden. Use the View option menu to
display the desired columns.

Properties
MAC address MAC address of the base station
RPN Radio Fixed Part Number, identifying the radio-entity
Sync RPN RPN of the other base station the base station is synchronising with
Sync Level Synchronisation level
Statistics
Conn Number of connections, i.e. calls made
Ho setup Number of incoming handovers
Ho release Number of outgoing handovers
Template Module, Version 1.2, 11.09.2018

Call drops Number of lost connections, i.e. interrupted calls


Async How often the base station has lost on-air DECT synchronisation
Busy How often the maximum number of possible connections of the module
was achieved. The base station has entered busy-state and pointed to other
modules for load balancing.
Conn. drops How often the LAN connection to the base station was interrupted

91
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / dignostics.fm / 12/4/18

Diagnostics and troubleshooting

Actions
Downloading the information in MIB format
For further processing of the statistic data using a MIB browser (Management Information Base)
you can download the data in MIB format (Managed Objects).
¤ Click on Download MIB Select the location where the MIB file should be stored using the
system file selection dialogue.
Exporting the information into a CSV file
For further processing of the statistic data you can export the data into a file with CSV (Comma
separated Value) format.
¤ Click on Export Select the location where the file should be stored using the system file
selection dialogue.
Displaying a graphical view of the cluster hierarchy
You can open a graphic that shows the cluster base stations, their relationship to the
surrounding base stations, and the synchronisation hierarchy.
¤ Open the cluster tree of a DECT manager Select a cluster Click on Show Cluster graph
. . . the base stations of the selected cluster are shown in a graphic.
Saving the graph as a file: Click on Save image Select the location where the graphic file
should be stored using the system file selection dialogue . . . the graph is stored in PNG format.
Resetting the statistics
¤ Click on Reset statistics . . . the counters in the table are reset to 0.
Filtering the list
¤ From the Choose column option menu select the column for which you want to set a filter.
Note that columns may be hidden.
¤ In the text field enter the filter criteria Click on Filter . . . only the entries matching the filter
are shown.
For filtering the list according to specific counter values the following operators are possible:
< less than > more than = equal to
<= less or equal >= more or equal

For the MAC address column only the following condition is allowed: = MAC address
The MAC address must be in the following format: aabbccddeeff (without colons)
Template Module, Version 1.2, 11.09.2018,

Deleting the filter: Click on Clear


Examples:
Only base stations with more than 20 busy situations should be displayed in the table. This could
be achieved by the following filter settings.
Busy >20 Filter Clear

Only base stations with less than 5 call interruptions should be displayed in the table. This could
be achieved by the following filter settings.
Call drops <5 Filter Clear

92
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / dignostics.fm / 12/4/18

Diagnostics and troubleshooting

Displaying/ hiding columns


¤ Click on the View option menu on the right Select the columns you want to be displayed
in the table ( / = displayed/hidden).
Names of columns which cannot be hidden are greyed out.

Incidents
Only available in the Integrator user interface.
¤ Status Statistics Incidents
The page contains the following information on incidents concerning DECT manager operation.
Timestamp Date and time of the incident
DECT Manager DECT manager affected
Incident Type e.g. Crash, Reboot, Reset
Info Detailed information, e.g., the component producing the problem

Actions
Downloading detailed information to a file
To get detailed information about the circumstances causing the error, you can download the
incident information to a file. If required, you can pass it to the responsible service personnel.
¤ Mark the check box next to one or more incidents you want to download or next to
Timestamp, if you want to download all incidents.
¤ Click on Download and select the desired file location for the log files in the file system . . . for
each selected incident a log file is created. All log files are taken into a tar file.
Deleting entries
¤ Mark the check box next to one or more incidents you want to delete or next to Timestamp,
if you want to delete all incidents.
¤ Click on Delete.
Refreshing the list
¤ Click on Refresh, to update the information in the table.
Changing the number of list entries
¤
Template Module, Version 1.2, 11.09.2018

On the right side below the list select the maximum number of entries that should be
displayed on a page (10, 25, 50, 100).
Browsing through the list
If there are more list entries than the selected number, you can browse through the whole table
page by page. The number of pages is shown below the list. The current page is highlighted.
¤ Click on Previous or Next to scroll through the list page by page.
¤ Click on a specific page number, to go to the desired page directly.

93
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / dignostics.fm / 12/4/18

Diagnostics and troubleshooting

System log and SNMP manager


Only available in the Integrator user interface.
The system report (SysLog) gathers information about selected processes performed by the
DECT managers and base stations during operation and sends this to the configured SysLog
server.
¤ Settings System System log
Activate system log
¤ Mark/unmark the check box to activate/deactivate the logging function.
Server address
¤ Enter the IP address or the (fully qualified) DNS name of your Syslog server. Value: max. 240
characters
Server port
¤ Enter the port number, where the Syslog server expects to receive requests.
Range: 1-65535; Default: 514
Log level
¤ Mark/unmark the check boxes next to the log information that should be included/not
included in the system log.
If you want to use the same system log server configuration for all DECT managers:
¤ Click on the Use on all DECT Managers button.

To set up the system log server individually for each DECT manager page 32.

SNMP statistics
The Simple Network Management Protocol (SNMP) is a common protocol used for monitoring
and controlling of network devices. To gather management and statistic information concerning
base station events to be processed by an SNMP manager you have to enter the address and
authentication information according to the SNMP server configuration.
¤ Enter the IP address of the SNMP manager server in the SNMP manager address field and
the port number used by the SNMP manager in the SNMP manager port field. Default: 162
Template Module, Version 1.2, 11.09.2018,

To access the SNMP database authentication is necessary.


¤ Enter the SNMP username and the SNMP password.
The SNMP manager access data can be set for all DECT managers here or for each individual
DECT manager ( page 32).
¤ If the access data defined here should be used for all DECT managers, click on Use on all
DECT Managers.

94
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / dignostics.fm / 12/4/18

Diagnostics and troubleshooting

Storing management information in MIB format


You can store management information for all base stations in MIB syntax.
¤ Click on Download MIB Select the location where the MIB file should be stored using the
system file selection dialogue . . . the file with the MIB information is stored in TXT format.
Template Module, Version 1.2, 11.09.2018

95
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / migration.fm / 12/4/18

Migration

Migration
In order to migrate a small or medium N870 IP PRO Multicell System multicell system with one
single DECT manager into a multi DECT manager installation, please perform the following
steps:
1 Export the base station and handset configuration of your current installation
¤ Settings Base stations Administration (¢ page 38)
¤ Settings Mobile devices Administration (¢ page 58).
2 Import the integrator virtual machine (*.ova file) into hypervisor (¢ page 14).
3 Define the device role for the devices that are defined to act as DECT manager in the future
(¢ page 15).
4 Add DECT managers to the Integrator’s administration
¤ Settings DECT Manager Administration (¢ page 28).
5 Register the DECT managers on the Integrator
¤ Settings System Integrator Config (¢ page 33).
6 Import the base station and handset configuration into the new configuration
¤ Settings Base stations Administration (¢ page 38)
¤ Settings Mobile devices Administration (¢ page 58).
7 Set up the new base station synchronisation hierarchy
¤ Settings Base stations Synchronisation (¢ page 42).
8 If necessary, set up cross-cluster synchronisation via DECT manager synchronisation
¤ Settings DECT Manager Synchronisation (¢ page 34).
During migration the base station synchronisation will be lost. Ongoing calls would
be cancelled. Please ensure, that the phone system is not in use during the migra-
tion procedure.

The procedure only applies to the migration of a first DECT manager to a new multi
DECT manager system. The handsets of a second system imported into the multi
DECT manager system cannot import their old system PARI into the new multi DECT
manager installation, thus these handset will be imported as "to-register" and need
to repeat on air DECT registration procedure.
Base station import of a second system does not need repetition of base station regis-
tration.
Template Module, Version 1.2, 11.09.2018,

96
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / telephony.fm / 12/4/18

Using a handset connected to an N870 IP PRO base

Using a handset connected to an N870 IP PRO base


The functions of your N870 IP PRO are available on the registered handsets. The functions of the
telephone system are added to the handset menu. Handset-specific functions, e.g., local direc-
tory or organiser, are not described here. Information about this will be found in the relevant
handset user guide. The availability of functions or their designations may differ on individual
handsets.

For information about which Gigaset handsets support the complete functionality of
the N870 IP PRO muliticell system please refer to wiki.gigasetpro.com.

Making calls
You can make calls using any handset registered to your N870 IP PRO.
Prerequisite: You are located in the cell of at least one of the base stations registered to the tele-
phone system.
The cells of the base stations together form the DECT wireless network of the telephone system.
You can initiate or answer calls on a handset across the whole wireless network and change cells
during a call (handover).
Prerequisite for handover: The base stations involved must be assigned to the same cluster and
must be synchronised (¢ page 42).
Each handset is assigned a send and receive connection (¢ page 61).
If your N870 IP PRO is connected to a PBX that permits the formation of groups, VoIP connections
can also be assigned to groups. In this case, you will also receive calls on your handset that have
been sent to your group number.
The N870 IP PRO uses a VoIP PBX Communication System or the services of a VoIP provider for
Internet telephony. The availability of some phone functions depends on whether they are
supported by the PBX/provider and whether they have been enabled. If necessary, you can
obtain a description of the services from the operator of your PBX.

Depending on the specifications of your PBX, you may need to dial an access code for
calls outside the area covered by your VoIP PBX (¢ page 68).

Calling
¤ . . . use to enter a number Briefly press the Talk key
Template Module, Version 1.2, 11.09.2018

or
¤ Press and hold the Talk key . . . use to enter a number
The connection is established using the SIP connection assigned to the handset (¢ page 61).

If you make a call to the fixed line network, you may also have to dial the area code for
local calls (depending on the PABX/provider). This is not necessary if the area code is
entered in the configuration on the DECT Manager (¢ page 69).

97
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / telephony.fm / 12/4/18

Using a handset connected to an N870 IP PRO base

Dialling from the redial list


The redial list contains the numbers last dialled with the handset.
¤ Briefly press the Talk key . . . the redial list is opened . . . use to select an entry
Press the Talk key
If a name is displayed:
¤ View . . . the number is displayed . . . use to browse numbers if necessary . . . when
the desired number is reached press the Talk key

Dialling from the call list


The call lists contain the most recent accepted, outgoing and missed calls.
¤ . . . use to select Call Lists OK . . . use to select a list OK . . . use
to select an entry Press the Talk key

The Missed calls list can also be opened by pressing the Message key .

Initiating ringback
If the number you have called is engaged or the participant called does not reply, you can
arrange a ringback if your PBX/provider supports the CCBS and CCNR services.
CCBS (Completion of Call to busy Subscriber) Ringback if busy
CCNR (Completion of Calls on No Reply) Ringback if no answer
The service code for activating/deactivating CCBS, CCNR must be configured on the DECT
manager (¢ page 55).
Activating ringback:
¤ Enter the service code defined for the PBX/provider, e.g., *6
If you decide you do not want a ringback, you can switch the function off again:
¤ Enter the service code defined for the PBX/provider, e.g., #6
Template Module, Version 1.2, 11.09.2018,

98
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / telephony.fm / 12/4/18

Using a handset connected to an N870 IP PRO base

Accepting calls
Incoming calls for the connection assigned to your handset are signalled.
¤ Press the Talk key to accept the call.
Switch off ringtone: ¤ Silence . . . the call can be accepted for as long as it is shown on the
display
Reject a call: ¤ Press the End call key

Information about the caller


The caller's phone number is displayed, if provided. If the caller's number is saved in the direc-
tory, the name is displayed.
Using a PBX call manager
In case a PBX call manager is used it is possible to define that incoming calls are accepted directly
via headset or handsfree. This has to be configured for the handset via web configurator in the
Call manager section (¢ page 63).

Group pickup
You can also accept incoming calls for the group.
Group pickup must be activated and the call number or SIP URI of the group must be entered.
This has to be configured for the handset via web configurator in the Group pick-up
section(¢ page 63)

Accepting/rejecting call waiting


A call waiting tone indicates a call during an external call. The number or the name of the caller
is displayed if the phone number is transferred.
• Reject a call: Options Reject waiting call OK
• Accept a call: Accept . . . speak to the new caller. The previous call is placed on hold.
• End the call, resume the on-hold call: Press the End call key .

Conversation with three participants

Consultation calls
Template Module, Version 1.2, 11.09.2018

Make another external call during an external call. The first call is placed on hold.
¤ Ext. Call . . . use to enter the number of the second participant . . . the active call is
placed on hold and the second participant is called
If the second participant does not answer: End

Ending a consultation call


¤ Options End active call OK . . . the connection to the first caller is reactivated
or
¤ Press the End call key . . . a recall to the first participant is initiated

99
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / telephony.fm / 12/4/18

Using a handset connected to an N870 IP PRO base

Call swapping
Switching between two calls. The other call is placed on hold.
¤ During an external call, dial the number of a second participant (consultation call) or accept
a waiting caller . . . the display shows the numbers and/or names of both call participants
¤ Use the control key to switch back and forth between participants

Ending a currently active call


¤ Options End active call OK . . . the connection to the other caller is reactivated
or
¤ Press the End call key . . . a recall to the first participant is initiated

Conference
Speaking to both participants at the same time.
¤ During an external call, dial the number of a second participant (consultation call) or accept
a waiting caller . . . then
Initiate conference call:
¤ Conf. . . . all callers can hear one another and hold a conversation with one another
Return to call swapping:
¤ End Conf. . . . You will be reconnected to the participant with whom the conference call was
initiated
End call with both participants:
¤ Press the End call key
Each of the participants can end their participation in the conference call by pressing the End
call key or hanging up.

Call transfer
Connecting an external call with a second external participant.
¤ Use the display key Ext. Call to establish an external consultation call . . . use to enter
the number of the second participant . . . the active call is placed on hold . . . the second
participant is called press the End call key (during a conversation or before the
second participant has answered) . . . the call is transferred
Template Module, Version 1.2, 11.09.2018,

Call transfer options must be set correctly for the PBX/provider (¢ page 54).

100
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / telephony.fm / 12/4/18

Using a handset connected to an N870 IP PRO base

Message indication
Notifications about accepted and missed calls, missed alarms and messages on the network
mailbox are saved in messages list and can be displayed on the handset display.
Which messages are displayed on the handset is defined during handset configuration in the
Missed calls and alarms section (¢ page 64)

Missed calls count


If the option is activated, the number of missed and accepted calls will be shown on the handset
display in idle mode.

Message Waiting Indication (MWI)


For each message type (missed call, missed alarm, new message the network mailbox) the MWI
option can be activated or deactivated via the web configurator.
If activated, the LED on the message key flashes, in the case a new message arrives indi-
cating missed calls, missed alarms or new messages on the network mailbox.

Using directories
The options are:
• The (local) directory for your handset (see handset user guide)
• Corporate directories provided by an LDAP server (¢ page 103)
The directories available are defined by the web configurator of the telephone system
(¢ page 71).

Opening directories
Opening the corporate directory using the INT key
The INT key (press left on control key) on the handsets opens a corporate directory, provided
that this is set up via the web configurator using the Corporate directory for INT key option and
can be accessed by the telephone system. The directory to be opened can be set for each
handset (¢ page 62).

Opening directories using the directory key


The directory key (press down on the control key) for the handset is normally set as follows:
• Press briefly to open the local directory
Template Module, Version 1.2, 11.09.2018

• Press and hold to open the selection of available network directories.


This assignment can be changed for each handset via the web configurator using the Directory
for direct access option (¢ page 62). Direct access can be assigned to a specific online direc-
tory. In this case, open the local directory by pressing and holding the directory key.
The description below assumes the default assignment.

101
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / telephony.fm / 12/4/18

Using a handset connected to an N870 IP PRO base

Opening directories via the menu


Depending on the handset used you can access all available directories also via the handset's
menu:
. . . use to select Directory OK Local directory
. . . use to select Net Directories OK List of all online directories set up on
the telephone system
The directories are displayed with the names specified in the web configurator.
Example for handling a corporate directory on the handset page 109

If handsets are connected to an N870 IP PRO, it is not possible to transfer entries from
the local directory to another handset.

Using the network mailbox


The network mailbox accepts incoming calls made via the corresponding line (corresponding
VoIP phone number).

Prerequisites
In order to allow the user to listen voice messages stored one a network mailbox the following
settings are necessary:
On the VoIP PBX
¤ Set up a network mailbox for the VoIP connection that is to be assigned to the handset.
On the N870 IP PRO
¤ In the provider/PBX configuration activate the SIP SUBSCRIBE for Net-AM MWI option
(¢ page 52). A subscription is established for the purpose of receiving notifications about
new messages on the network mailbox.
¤ In the mobile devices configuration enter the Call number or SIP name (URI) and activate
the network mailbox in the Network mailbox configuration section (¢ page 63).
¤ Optional: In the mobile devices configuration enable the Flashing LED (MWI) for network
mailbox option (¢ page 64). New messages on the network mailbox are indicated by the
MWI light on the Message key.

Playing back messages on the handset


¤ Press and hold (if key 1 has been assigned to the network mailbox)
Template Module, Version 1.2, 11.09.2018,

or
¤ Press the Message key . . . use to select the network mailbox OK
or
¤ . . . use to select Answer Machine OK Play Messages OK
Listen to announcement out loud: Press the handsfree key

102
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

LDAP directory – configuration example


To allow the entries of an LDAP directory to be displayed on the handsets, you will need to
configure the phone’s LDAP client. This involves the following:
• Setting up access to the LDAP server and database
• Specifying the attributes to be displayed (¢ page 105)
• Defining search criteria (filters) (¢ page 105)

Access to the LDAP server


To ensure that entries from the LDAP database are displayed on the phones, enter the access
data via the web configurator.
¤ Settings Online directories Corporate
¤ Click on next to the name of the LDAP directory you want to edit . . . the LDAP configu-
ration page is opened.

Our Directory

ldap.ourserver.com

cn=phonebook,dc=example,dc=com

cn=user_1,ou=users,dc=company,dc=com

************

¤ Enter a name for the directory in the Directory name field.


This is the name under which the directory will appear in the list of network directorys on the
telephones (¢ page 109).
Template Module, Version 1.2, 11.09.2018

¤ Select the option Enable directory, so that the directory will be displayed on the telephones.
¤ Enter the access data for the LDAP server
Server address IP address or domain name of the LDAP server, e.g. 10.25.62.35 or
ldap.example.com
Server port Port on which the LDAP server expects queries from the clients.
Normally the port number 389 is used (default).
Username / Password Credentials for access to the LDAP server.

It is also possible to use individual access data for each handset ( page 61).

103
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

LDAP Search base (BaseDN)


The LDAP Search base (BaseDN) parameter specifies the starting point for the search in the
LDAP directory tree. This starting point must be defined on the LDAP server and entered here for
the LDAP client according to the server configuration. BaseDN is a special LDAP name which
represents an object including its position in a hierarchical directory.
BaseDN is used to define which section of the hierarchical LDAP database is to be searched.
Access to the entire directory can be enabled (e.g. to the corporate directory) or only to a subdi-
rectory (e.g. the directory of a particular organisational unit).
BaseDN is created from series of RDNs (Relative Distinguished Names) found by walking up the
directory information tree.
The BaseDN is specified as follows:
• The directory hierarchy is specified from left to right from the lowest level to the highest, e.g.
object, organisational unit, organisation, domain.
• A hierarchical level has the following format: keyword=object, e.g. cn=PhoneBook.
• Hierarchical levels are separated by commas.
• It must be unique in the directory information tree.
The following objects are often used as hierarchical levels:
cn: common name
ou: organisational unit
o: organisation
c: country
dc: domain component
But other objects can also be used. For this parameter you require information on the structure
of the LDAP server.
For the meaning of the objects, see section Filters ¢ page 105
Examples:
Starting point: Object PhoneBook, in the domain example.com
Definition: cn=PhoneBook,dc=example,dc=com

Starting point: Object PhoneBook in the subdirectory sales/support, in the domain


example.sales.com.
Definition: cn=PhoneBook,o=support,ou=sales,dc=example,dc=sales,dc=com
Template Module, Version 1.2, 11.09.2018,

104
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Filters
With filters you define criteria by which the phone searches for certain objects in the LDAP data-
base
• The name filter determines which attributes are used in the search for directory entries.
• The number filter specifies which attributes are used for the automatic search in the LDAP
database when phone numbers are entered.
• Additional filters can be defined to enable detailed search

The LDAP protocol offers various setting options for filters and search functions, e.g.
wildcards, fixed character strings and further operators. For full details see the
RFC 4515.
Template Module, Version 1.2, 11.09.2018

105
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Filter format
A filter consists of one or more criteria. A criterion defines the LDAP attribute in which the
entered string is to be searched for, e.g. sn=%. The percent sign (%) is a placeholder for the user
input.

Operators
Following operators can be used to create filters:
Operator Meaning Example
= Equality (attribute1=abc)
!= Negation (!(attribute1=abc))
>= Greater than (attribute1>=1000)
<= Less than (attribute1<=1000)
~ Proximity (LDAP server dependent) (attribute1~=abc)
* Wildcard (attr1=ab*) or (attr1=*c) or (attr1=*b*)

Multiple criteria can be connected with logical AND (&) and/or OR operators (|). The logical oper-
ators "&" and "|" are placed in front of the criteria. The criterion must be placed in brackets and
the whole expression must be bracketed again. AND and OR operations can also be combined.
Examples
AND operation: (&(givenName=%)(mail=%))
Searches for entries in which the first name and e-mail address begin with the
characters entered by the user.
OR operation: (|(displayName=%)(sn=%))
Searches for entries in which the display name or surname begins with the
characters entered by the user.
Combined (|(&(displayName=%)(mail=%))(&(sn=%)(mail=%)))
operation: Searches for entries in which the display name and e-mail address or the
surname and e-mail address begin with the characters entered by the user.

Special characters
It is also possible to find entries containing special characters. If you want to compare these char-
acters within an attribute string use backslash (\) and a 2-digit hex ASCII code as follows:
Special character ASCII code Special character ASCII code
Template Module, Version 1.2, 11.09.2018,

( \28 = \3d
) \29 & \26
< \3c ~ \7e
> \3e * \2a
/ \2f | \7c
\ \2a

Example
(givenName=James \28Jim\29)
will find any entry with givenName attribute's value equal to "James (Jim)"

106
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Name filter
The name filter determines which attributes are used for the search in the LDAP database.

Examples:
(displayName=%) The attribute displayName is used for the search.
The percent sign (%) is replaced with the name or part of the name
entered by the user.
If you enter e.g. the character "A", the phone searches the LDAP database
for all entries in which the attribute displayName begins with "A". If you
then enter a "b", it searches for entries in which the displayName begins
with "Ab".
(|(cn=%)(sn=%)) The attributes cn or sn are used for the search.
If you enter e.g. the character "n", the phone searches the LDAP database
for all entries in which the attribute cn or sn begins with "n". If you then
enter an "o", it searches for entries in which the attribute cn or sn begins
with "no".

LDAP does not distinguish between upper and lower case in the search request.

Number filter
The number filter defines which attributes are used in the automatic search for a directory entry.
The automatic search is performed when a phone number is entered and in the case of an
incoming call with calling line identification. If an entry is found for a phone number, the display
shows the name instead of the number.
Entries are only found and displayed if the stored phone number matches the entered phone
number exactly.

Examples:
(homePhone=%) The attribute homePhone is used for the search.
The percent sign (%) is replaced with the phone number entered by the
user.
If you enter the numbers "1234567" when dialling, the phone searches the
LDAP database for entries with the private phone number "1234567".
Template Module, Version 1.2, 11.09.2018

(|(telephoneNumber=%)(mobile=%)(homePhone=%))
The attributes telephoneNumber, mobile and homePhone are used for
the search.
If you enter the numbers "1234567" when dialling, the phone searches the
LDAP database for entries with the private or mobile or work number
"1234567".

107
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Attributes
For a directory entry (an object), a series of attributes are defined in the LDAP database, e.g.
surname, first name, phone number, address, company etc. The set of all attributes that can be
stored for an entry is stored in the schema of the relevant LDAP server. To access attributes or
define search filters, you must know the attributes and their names in the LDAP server. Most
attribute names are standardised, but there can also be specific ones defined.
Which attributes can actually be displayed on a phone depends on
• which attributes are defined for an entry in the LDAP database,
• which attributes are set in the web configurator for display on the phone,
• which attributes can be displayed on the phone or handset.

Available attributes on handsets or phones


The following table shows the attributes that could be used for a directory entry on a handset or
phone. Of course, the set of attributes that are actually shown depends on the specific handset
used.
Attributes of a directory entry Attribute name in the LDAP database
First name givenName
Surname sn, cn, displayName
Phone (home) homePhone, telephoneNumber
Phone (office) telephoneNumber
Phone (mobile) mobile
E-mail mail
Fax facsimileTelephoneNumber
Company company, o, ou
Street street
City I, postalAddress
Zip postalCode
Country friendlyCountryName, c
Additional attribute can be freely defined
Template Module, Version 1.2, 11.09.2018,

108
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Specifying attributes for display on the phone


In the web configurator you specify which of the available attributes from the LDAP database are
to be queried and displayed on the phone.
¤ For each attribute of a directory entry, select the appropriate attribute from the LDAP data-
base. There are predefined settings at choice. Alternatively you can enter manually a
different attribute defined in the LDAP database for this field.
¤ If an attribute is not to be displayed, select the option none.
In the Additional attribute field, you can enter an additional attribute that is available in the
LDAP database and should be displayed. If the attribute is a number to be dialled, the option
Additional attribute can be dialled must be checked.
The attributes First name and Surname will be used for the following functions:
• Display in the list of directory entries in the form Surname, First name
• Alphabetical sorting of the directory entries on the phone
• Name display of a caller or call participant
If the database query only produces one of the attribute values (e.g. because a contact is only
stored with their first name), only this one will be displayed.

Display on the handsets


If one or more LDAP directories are set up in the web configurator, they will be available on the
handsets with the following functions:
• Scroll through directory or search for directory entries,
• Display directory entries with detailed information (no edit or delete),
• Dial phone numbers directly from the directory,
• Add directory entries to the local directory.
When a phone number is entered or a call comes in, the directory is automatically searched for
an entry that matches the phone number. If an entry is found, the name is displayed instead of
the phone number.

To display the corporate directory on the telephone screen


The corporate directory is assigned to the INT key: press

Depending on the settings for the handset in the web configurator (¢ page 62), you
,

may also be able to access a corporate directory via the directory key .
Template Module, Version 1.2, 11.09.2018

Some handsets provide access also via the display menu. For details, see the user
guide for your phone.

109
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Entries in the directory


The following description shows an example for the display of an LDAP directory on a handset.
The menu shows all directories that have been set up and acti-
vated on the Online directories page in the web configurator. Directories
Each one appears with the name entered under Directory name
in the web configurator (¢ page 103). In the example on the
Our Directory
right, the LDAP directory is shown as Our Directory. Directory 3
¤ . . . use to select the directory OK Directory 4
The phone initiates a query to the LDAP server defined in the Directory 5
web configurator.
Directory 6

Back OK

The LDAP directory is displayed according to the following rules:


Our Directory
• The search begins in the directory/subdirectory which is
defined as the search base on the LDAP server and specified Albert
with the LDAP Search base (BaseDN) parameter in the web
configurator (¢ page 104). Bond
• The entries are listed in alphabetical order. Bond, James
• The entries are displayed with Surname and First name if Bond, Paul
both attributes are available in the LDAP database. Other-
wise only the surname or first name is displayed. Brown, Charly

View Options

Searching the directory


¤ Use to scroll through the direc-
b br
tory
or Bond Brown, Charly
¤ Use to enter a name (or the first Bond, James
few letters).
Bond, Paul
As soon as you press a key on the
keypad, the telephone goes into Brown, Charly
search mode. You can enter up to 15
Template Module, Version 1.2, 11.09.2018,

characters. All entries in the LDAP


directory that match your input are Options Options
displayed.
¤ Use to delete the last character you entered.
The current search string is shown in the top line.

110
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / LDAP_example.fm / 12/4/18

LDAP directory – configuration example

Displaying a directory entry


¤ Use to select the entry you want.
¤
Brown, Charly
Press the display key View or the navigation key .
or Surname:
¤ Press the display key Options View Brown
First Name:
The directory entry is displayed with its detailed information.
Only attributes for which a value is stored are shown Charly
(¢ page 105). Phone (home):
¤ Use to scroll through the entry. 1234567890
¤ Press the End call key or the Back display key to close Back
the entry.

Dialling a number from the directory


¤ Use to select the entry you want in the directory.
¤ Brown, Charly
Press the Talk key . If only one phone number is stored, it
is dialled. If there are several phone numbers, they are Phone (office):
displayed in a selection list. 0987654321
or Phone (mobile):
¤ Use to select the phone number you want in the detailed 0908987876
view of an entry: Phone (home), Phone (office) or Phone Street:
(mobile).
¤
Avenue 12
Press the Talk key . The number is dialled.
Back
Template Module, Version 1.2, 11.09.2018

111
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / appendix_legal.fm / 11/7/18

Appendix

Appendix

Safety precautions
Read the safety precautions and the user guide before use.

Comprehensive user guides for all telephones and telephone systems as well as for accessories
can be found online at gigasetpro.com in the Support category. We thereby help to save paper
while providing fast access to the complete up-to-date documentation at any time.

Do not use the devices in environments with a potential explosion hazard (e.g. paint shops).

The devices are not splashproof. For this reason do not install them in a damp environment such as
bathrooms or shower rooms.
Remove faulty devices from use or have them repaired by our Service team, as these could interfere
with other wireless services.
Using your telephone may affect nearby medical equipment. Be aware of the technical conditions in
your particular environment, e.g. doctor's surgery. If you use a medical device (e.g. a pacemaker),
please contact the device manufacturer. They will be able to advise you regarding the susceptibility
of the device to external sources of high frequency energy (for the specifications of your Gigaset pro
product see "Specifications").
For outdoor installations, please observe the Safety precautions of the installation environment, in
particular with regard to lightning protection.

Service (Customer Care)


Do you have any questions?
For quick help and information, please refer to this user guide or visit gigasetpro.com.
For online information and services concerning
• Products
• Documents
• Interop
• Firmware
• FAQ
• Support
please refer to wiki.gigasetpro.com.
Template Module, Version 1.2, 11.09.2018,

For further information our Gigaset specialised reseller will be happy to help you related to your Gigaset
product.

112
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / appendix_legal.fm / 11/7/18

Appendix

Authorisation
Voice over IP telephony is possible via the LAN interface (IEEE 802.3).
This device is intended for use worldwide. Use outside the European Economic Area (with the exception of
Switzerland) is subject to national approval.
Country-specific requirements have been taken into consideration.
Hereby, Gigaset Communications GmbH declares that the radio equipment type N870 IP PRO Multicell System
is in compliance with Directive 2014/53/EU.
The full text of the EU declaration of conformity is available at the following internet address:
www.gigasetpro.com/docs.
This declaration could also be available in the "International Declarations of Conformity" or “European Decla-
rations of Conformity” files.
Therefore please check all of these files.

Environment

Our environmental statement


We at Gigaset Communications GmbH are aware of our social responsibility. That is why we actively take steps
to create a better world. In all areas of our business – from product planning and production to sales and waste
of disposal – following our environmental conscience in everything we do is of utmost importance to us.
Learn more about our earth-friendly products and processes online at www.gigaset.com.

Environmental management system


Gigaset Communications GmbH is certified pursuant to the international standards ISO 14001 and
ISO 9001.
ISO 14001 (Environment): Certified since September 2007 by TÜV SÜD Management Service
GmbH.
ISO 9001 (Quality): Certified since 17/02/1994 by TÜV SÜD Management Service GmbH.

Disposal
All electrical and electronic products should be disposed of separately from the municipal waste stream via
designated collection facilities appointed by the government or the local authorities.
This crossed-out wheeled bin symbol on the product means the product is covered by the Euro-
pean Directive 2012/19/EU. The correct disposal and separate collection of your old appliance will
help prevent potential negative consequences for the environment and human health. It is a
precondition for reuse and recycling of used electrical and electronic equipment.
For more detailed information about disposal of your old appliance, please contact your local council refuse
Template Module, Version 1.2, 11.09.2018

centre or the original supplier of the product.

113
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / appendix_legal.fm / 11/7/18

Appendix

Care
Wipe the device with a damp cloth or an antistatic cloth. Do not use solvents or microfibre
cloths.
Never use a dry cloth; this can cause static.
In rare cases, contact with chemical substances can cause changes to the device’s exterior. Due
to the wide variety of chemical products available on the market, it was not possible to test all
substances.
Impairments in high-gloss finishes can be carefully removed using display polishes for mobile
phones.

Contact with liquid


If the device comes into contact with liquid:
1 Unplug all cables from the device.
2 Allow the liquid to drain from the device.
3 Pat all parts dry.
4 Place the device in a dry, warm place for at least 72 hours (not in a microwave, oven etc.)
with the battery compartment open and the keypad facing down (if applicable).
5 Do not switch on the device again until it is completely dry.
When it has fully dried out, you will normally be able to use it again.
Template Module, Version 1.2, 11.09.2018,

114
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / appendix_technical.fm / 11/7/18

Technical data

Technical data

Specifications

Power consumption
Operation as N870 IP PRO (DECT manager) < 3.8 W
Operation as N870 IP PRO (base station) < 3.8 W

General specifications
DECT Manager and base stations
Power over Ethernet PoE IEEE 802.3af < 3.8 W (Class 1)
LAN interface RJ45 Ethernet, 10/100 Mbps
Protection class IP20
Ambient conditions for operation +5°C to +45°C indoors; 20% to 75% relative humidity
Protocols IPv4, SNTP, DHCP, DNS, TCP, UDP, VLAN, HTTP, TLS,
SIP, RTP, MWI, SDP, SRTP
Base stations
DECT standard DECT EN 300 175-x
Radio frequency range 1880–1900 MHz (Europe), 1910-1930 MHz (Latin
America),
1910-1920 MHz (Brazil)
Transmission power 10 mW average power per channel, 250 mW pulse power
No. of channels 120 channels
Number of connections 10 simultaneous connections per base station
(G.726, G711, G.729ab codec),
5 connections in wideband operation (G.722)
Range Up to 300 m outdoors, up to 50 m indoors
Template Module, Version 1.2, 11.09.2018

Codec G.711, G.722, G.729ab


Quality of Service TOS, DiffServ

115
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / appendix_technical.fm / 11/7/18

Accessories

Accessories
Power adapter
You only need a power adapter if your devices are not powered by PoE (Power over Ethernet).
EU: Item number: C39280-Z4-C706
UK: Item number: C39280-Z4-C745

N720 IP PRO Site Planning Kit (Site Planning Kit)


Equipment for planning and analysing your DECT multicell system. The case contains two cali-
brated Gigaset S650 H PRO handsets and one Gigaset N510 IP PRO base station, plus other useful
accessories for measuring the signal quality and wireless coverage on your DECT network.
Item number: S30852-H2316-R101

Gigaset handsets
Upgrade your telephone system with extra handsets.
For information on handset functions in relation to Gigaset base stations, visit
wiki.gigasetpro.com.
Template Module, Version 1.2, 11.09.2018,

116
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminSIX.fm / 11/7/18

Index

Index
Authentication code for handset registration . . . 61
A Authorisation . . . . . . . . . . . . . . . . . . . . . . . . 113
Access code . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Automatic search . . . . . . . . . . . . . . . . . . . . . 109
Access data for LDAP server . . . . . . . . . . . . . . 103
Activating base station . . . . . . . . . . . . . . . . . . . 41 B
Additional attributes . . . . . . . . . . . . . . . . . . . 109
Base station
Address of LDAP server . . . . . . . . . . . . . . . . . 103
activating . . . . . . . . . . . . . . . . . . . . . . . . . . 41
AND operator . . . . . . . . . . . . . . . . . . . . . . . . 106
administration . . . . . . . . . . . . . . . . . . . . . . 37
Answer machine, playing back messages. . . . . 102
assign to a DECT manager . . . . . . . . . . . . . . 39
Area code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
belonging cluster . . . . . . . . . . . . . . . . . . . . 48
local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
connected . . . . . . . . . . . . . . . . . . . . . . . . . 37
prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Area codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
c . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74, 108
IP address type . . . . . . . . . . . . . . . . . . . . . . 41
cn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
LED display for operational states . . . . . . . . . 17
company . . . . . . . . . . . . . . . . . . . . . . . . . 108
LED display for synchronisation status . . . . . . 17
displayName . . . . . . . . . . . . . . . . . . . . . . . 108
LED display, DECT traffic . . . . . . . . . . . . . . . 17
facsimileTelephoneNumber . . . . . . . . . . . . 108
MAC address . . . . . . . . . . . . . . . . . . . . . . . . 37
friendlyCountryName . . . . . . . . . . . . . . . . 108
name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
givenName . . . . . . . . . . . . . . . . . . . . . . . . 108
number . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
homePhone . . . . . . . . . . . . . . . . . . . . . . . 108
organising clusters . . . . . . . . . . . . . . . . . . . 42
I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
pending . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
rebooting . . . . . . . . . . . . . . . . . . . . . . . . . . 41
mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
resetting . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
responsible DECT manager . . . . . . . . . . . . . 37
ou . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
sync level . . . . . . . . . . . . . . . . . . . . . . . . . . 48
postalAddress . . . . . . . . . . . . . . . . . . . . . . 108
synchronisation status . . . . . . . . . . . . . . 37, 48
postalCode . . . . . . . . . . . . . . . . . . . . . . . . 108
Base stations
sn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
synchronised . . . . . . . . . . . . . . . . . . . . . . . 48
street . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
synchronising . . . . . . . . . . . . . . . . . . . . . . . 42
telephoneNumber. . . . . . . . . . . . . . . . . . . 108
BroadSoft XSI . . . . . . . . . . . . . . . . . . . . . . . . . 70
user-definied . . . . . . . . . . . . . . . . . . . . . . 109
Attributes
defining for display . . . . . . . . . . . . . . . . . . 109 C
in LDAP database . . . . . . . . . . . . . . . . . . . 108 Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Attributes in the LDAP database . . . . . . . . . . . . 74 Call list, dialling from . . . . . . . . . . . . . . . . . . . . 98
Attributes, LDAP Call manger, accepting call directly . . . . . . . . . . 63
cn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Call on hold settings . . . . . . . . . . . . . . . . . . . . 55
company . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Call swapping, two external calls . . . . . . . . . . . 100
displayName . . . . . . . . . . . . . . . . . . . . . . . . 74 Call transfer settings . . . . . . . . . . . . . . . . . . . . 68
facsimileTelephoneNumber . . . . . . . . . . . . . 74 Call waiting, external
friendlyCountryName . . . . . . . . . . . . . . . . . 74 accepting/rejecting . . . . . . . . . . . . . . . . . . . 99
givenName . . . . . . . . . . . . . . . . . . . . . . . . . 74 Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Template Module, Version 1.2, 11.09.2018

homePhone . . . . . . . . . . . . . . . . . . . . . . . . 74 Calling party information . . . . . . . . . . . . . . . . . 55


I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Care of the device . . . . . . . . . . . . . . . . . . . . . 114
mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 web configurator . . . . . . . . . . . . . . . . . . . . 79
ou . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
postalAddress . . . . . . . . . . . . . . . . . . . . . . . 74 CLI (Command Line Interface) . . . . . . . . . . . . . . 78
postalCode . . . . . . . . . . . . . . . . . . . . . . . . . 74 CLI access to the device configuration . . . . . . . . 78
sn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6, 48
street . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 configuring . . . . . . . . . . . . . . . . . . . . . . . . . 42
telephoneNumber. . . . . . . . . . . . . . . . . . . . 74 graphical view . . . . . . . . . . . . . . . . . . . . . . 92
user-defined . . . . . . . . . . . . . . . . . . . . . . . . 74 cn, attribute . . . . . . . . . . . . . . . . . . . . . . 74, 108
Audio quality . . . . . . . . . . . . . . . . . . . . . . . . . 67 Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

117
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminSIX.fm / 11/7/18

Index

Column DHCP server . . . . . . . . . . . . . . . . . . . . . . . . . . 25


displaying/hiding23, 29, 35, 38, 49, 59, 85, 93 Diagnostics
Company directory . . . . . . . . . . . . . . . . . . . . . 71 base stations . . . . . . . . . . . . . . . . . . . . . . . . 91
company, attribute . . . . . . . . . . . . . . . . . 74, 108 DECT manager incidents . . . . . . . . . . . . . . . 93
Conference . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Dialling
Conference call from the call list . . . . . . . . . . . . . . . . . . . . . 98
end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 from the redial list . . . . . . . . . . . . . . . . . . . . 98
two external calls . . . . . . . . . . . . . . . . . . . 100 DiffServ (Differentiated Services) . . . . . . . . . . . . 67
Connected base stations . . . . . . . . . . . . . . . . . 37 Directory
Connecting accessing . . . . . . . . . . . . . . . . . . . . . . . . . 101
power cable . . . . . . . . . . . . . . . . . . . . . . . . 14 attributes . . . . . . . . . . . . . . . . . . . . . . . . . 108
Connecting the PC to the web configurator . . . . 20 configuring . . . . . . . . . . . . . . . . . . . . . . . . . 71
Connecting to the LAN. . . . . . . . . . . . . . . . . . . 13 configuring handset access . . . . . . . . . . . . . 62
Connection name . . . . . . . . . . . . . . . . . . . . . . 50 corporate . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Consultation call . . . . . . . . . . . . . . . . . . . . . . . 99 displaying attributes . . . . . . . . . . . . . . . . . 109
ending . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Consumption of electricity, see Power consumption opening . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Contact with liquid . . . . . . . . . . . . . . . . . . . . 114 searching . . . . . . . . . . . . . . . . . . . . . . . . . 110
CSTA using . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
access data . . . . . . . . . . . . . . . . . . . . . . . . . 64 XML format . . . . . . . . . . . . . . . . . . . . . . . . . 75
CSTA (Computer Supported Telecommunications Directory entry
Applications) . . . . . . . . . . . . . . . . . . . . . 56 attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 74
CSV file, statistics . . . . . . . . . . . . . . . . . . . . . . . 92 searching . . . . . . . . . . . . . . . . . . . . . . . . . 110
Customer Care . . . . . . . . . . . . . . . . . . . . . . . 112 Display format, LDAP . . . . . . . . . . . . . . . . . . . . 73
Display name, handset . . . . . . . . . . . . . . . . . . . 57
D displayName, attribute . . . . . . . . . . . . . . . 74, 108
Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Data protection notice . . . . . . . . . . . . . . . . . . . 14
DNS (Domain Name System) . . . . . . . . . . . . . . 26
Database access . . . . . . . . . . . . . . . . . . . . . . 103
DNS redundancy method . . . . . . . . . . . . . . . . . 52
Date
Domain name . . . . . . . . . . . . . . . . . . . . . . . . 103
setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Domain part of the user address . . . . . . . . . . . . 50
synchronisation . . . . . . . . . . . . . . . . . . . . . 83
Download log files . . . . . . . . . . . . . . . . . . . . . . 93
DECT
Dynamic IP address
radiation. . . . . . . . . . . . . . . . . . . . . . . . . . . 88
base station . . . . . . . . . . . . . . . . . . . . . . . . 41
security . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
DECT integrator . . . . . . . . . . . . . . . . . . . . . . . . . 4
DECT level . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 E
DECT manager . . . . . . . . . . . . . . . . . . . . . . . . . 5 ECO DECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
adding . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Emergency reset . . . . . . . . . . . . . . . . . . . . . . . 19
administration . . . . . . . . . . . . . . . . . . . . . . 28 Environment . . . . . . . . . . . . . . . . . . . . . . . . . 113
capacity . . . . . . . . . . . . . . . . . . . . . . . . 28, 31
configuration . . . . . . . . . . . . . . . . . . . . . . . 28 F
identifier . . . . . . . . . . . . . . . . . . . . . . . . . . 30
facsimileTelephoneNumber, attribute . . . . 74, 108
LED display DECT traffic . . . . . . . . . . . . . . . . 18
Factory settings see Reset . . . . . . . . . . . . . . . . 15
number . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Failed registation retry timer . . . . . . . . . . . . . . . 66
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
registering at the Integrator . . . . . . . . . . . . . 33
criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Template Module, Version 1.2, 11.09.2018,

reseting . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
format . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
synchronisation . . . . . . . . . . . . . . . . . . . . . 34
name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
DECT manager operation, incidents . . . . . . . . . 93
number . . . . . . . . . . . . . . . . . . . . . . . . . . 107
DECT radio settings . . . . . . . . . . . . . . . . . . . . . 89
Filter, LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
DECT registration state
Firmware
handset . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
base station . . . . . . . . . . . . . . . . . . . . . . . . 37
DECT traffic
current version . . . . . . . . . . . . . . . . . . . 84, 86
base station . . . . . . . . . . . . . . . . . . . . . . . . 17
handset . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
DECT manager . . . . . . . . . . . . . . . . . . . . . . 18
previous version . . . . . . . . . . . . . . . . . . . . . 84
Deployments . . . . . . . . . . . . . . . . . . . . . . . . . . 7
update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Device button . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Firmware update
Device role
LED display . . . . . . . . . . . . . . . . . . . . . . . . . 17
setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
scheduled. . . . . . . . . . . . . . . . . . . . . . . 84, 86
Device roles . . . . . . . . . . . . . . . . . . . . . . . . . . 15

118
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminSIX.fm / 11/7/18

Index

friendlyCountryName . . . . . . . . . . . . . . . . . . . 74 base station . . . . . . . . . . . . . . . . . . . . . . . . 41


friendlyCountryName, attribute . . . . . . . . . . . 108 IP configuration . . . . . . . . . . . . . . . . . . . . . . . . 25
IPUI (International Portable User Identity) . . . . . 57
G IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
G.711 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
G.722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 L
enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 LAN master . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
G.729A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 LAN master/slave. . . . . . . . . . . . . . . . . . . . . . . 43
Gigaset N720 SPK PRO (Site Planning Kit) LAN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
item number. . . . . . . . . . . . . . . . . . . . . . . 116 LAN slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Gigaset N870 DECT IP Multicell System . . . . . . . . 4 LAN synchronisation . . . . . . . . . . . . . . . . . . . . 43
Gigaset N870 IP PRO base station . . . . . . . . . . . . 5 advantages . . . . . . . . . . . . . . . . . . . . . . . . . 43
Gigaset N870 IP PRO DECT manager . . . . . . . . . . 5 requirements . . . . . . . . . . . . . . . . . . . . . . . 44
givenName, attribute . . . . . . . . . . . . . . . . 74, 108 LDAP
Graphical view of cluster hierarchy . . . . . . . . . . 92 display format . . . . . . . . . . . . . . . . . . . . . . . 73
Group pick-up . . . . . . . . . . . . . . . . . . . . . . . . . 63 name filter . . . . . . . . . . . . . . . . . . . . . . . . . 73
number filter. . . . . . . . . . . . . . . . . . . . . . . . 73
H search base . . . . . . . . . . . . . . . . . . . . . . . . . 71
LDAP attributes . . . . . . . . . . . . . . . . . . . . 74, 108
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
LDAP authentication for handset . . . . . . . . . . . 63
Handset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
LDAP directory
belonging DECT manager . . . . . . . . . . . . . . 57
configuring . . . . . . . . . . . . . . . . . . . . . . . . . 71
configuring mailbox access . . . . . . . . . . . . . 63
name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
DECT registration state . . . . . . . . . . . . . . . . 57
server access data . . . . . . . . . . . . . . . . . . . . 71
de-registering . . . . . . . . . . . . . . . . . . . . . . . 61
LDAP filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
directory assignment . . . . . . . . . . . . . . . . . . 62
LDAP filter see Filter
display name . . . . . . . . . . . . . . . . . . . . . . . 57
LDAP name . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . 57
LDAP search base . . . . . . . . . . . . . . . . . . . . . 104
LDAP authentication . . . . . . . . . . . . . . . . . . 63
LDAP server
menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
address . . . . . . . . . . . . . . . . . . . . . . . . . . 103
MWI settings . . . . . . . . . . . . . . . . . . . . . . . . 64
domain name . . . . . . . . . . . . . . . . . . . . . . 103
PIN for DECT registration . . . . . . . . . . . . . . . 61
IP address . . . . . . . . . . . . . . . . . . . . . . . . . 103
registering . . . . . . . . . . . . . . . . . . . . . . 57, 60
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
registration centre . . . . . . . . . . . . . . . . . . . . 65
User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
LDAP server scheme . . . . . . . . . . . . . . . . . . . . 74
time-controlled registration . . . . . . . . . . . . . 65
LDAP server, URL . . . . . . . . . . . . . . . . . . . . . . . 71
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
LED displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
user name . . . . . . . . . . . . . . . . . . . . . . . . . 57
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
VoIP account registration data . . . . . . . . . . . 62
Liquid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Handsets
List
administration . . . . . . . . . . . . . . . . . . . . . . 57
browse . . . . . . .23, 30, 35, 39, 49, 59, 86, 93
registered . . . . . . . . . . . . . . . . . . . . . . . . . . 57
filtering . . . . . . . . . 23, 29, 35, 38, 49, 58, 85
Handsets, recommended . . . . . . . . . . . . . . . . 116
sorting . . . . . . . . . . 23, 29, 35, 38, 49, 58, 85
Help function, web configurator . . . . . . . . . . . . 22
Local area code . . . . . . . . . . . . . . . . . . . . . . . . 69
homePhone, attribute . . . . . . . . . . . . . . . 74, 108
Local network . . . . . . . . . . . . . . . . . . . . . . . . . 25
HTTP authentication . . . . . . . . . . . . . . . . . . . . 82
Local Time Server . . . . . . . . . . . . . . . . . . . . . . 83
Log file download . . . . . . . . . . . . . . . . . . . . . . 93
Template Module, Version 1.2, 11.09.2018

I Log level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Logical operators see Operator
Installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . 14 M
INT key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
MAC address, base station . . . . . . . . . . . . . . . . 37
assigning directory . . . . . . . . . . . . . . . . . . . 62
mail, attribute . . . . . . . . . . . . . . . . . . . . . 74, 108
Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Mailbox configuration . . . . . . . . . . . . . . . . . . . 63
installation . . . . . . . . . . . . . . . . . . . . . . . . . 14
Making calls . . . . . . . . . . . . . . . . . . . . . . . . . . 97
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Medical equipment . . . . . . . . . . . . . . . . . . . . 112
IP Address
Menu overview
IPV4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 41
handsets . . . . . . . . . . . . . . . . . . . . . . . . . . 97
IP address of LDAP server . . . . . . . . . . . . . . . . 103
web configurator . . . . . . . . . . . . . . . . . . . . 24
IP address type . . . . . . . . . . . . . . . . . . . . . . . . 25

119
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminSIX.fm / 11/7/18

Index

MIB (Management Information Base) . . . . . 32, 95 postalCode, attribute . . . . . . . . . . . . . . . . 74, 108


MIB format, statistics . . . . . . . . . . . . . . . . . . . . 92 Power adapter
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 item number . . . . . . . . . . . . . . . . . . . . . . . 116
Mobile devices . . . . . . . . . . . . . . . . . . . . . . . . . 5 Power cable slot . . . . . . . . . . . . . . . . . . . . . . . . 9
number . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Power consumption. . . . . . . . . . . . . . . . . . . . 115
mobile, attribute . . . . . . . . . . . . . . . . . . . 74, 108 Power over Ethernet (PoE) . . . . . . . . . . . . . . . . 10
Multicell system . . . . . . . . . . . . . . . . . . . . . . . . 4 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . 14
MWI settings . . . . . . . . . . . . . . . . . . . . . . . . . . 64 P-Preferred-Identity (PPI) . . . . . . . . . . . . . . . . . 55
PRACK (Provisional Response Acknowledgement)66
N Priority of voice data . . . . . . . . . . . . . . . . . . . . 67
Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
N870 IP PRO DECT multicell system . . . . . . . . . . . 4
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Name filter . . . . . . . . . . . . . . . . . . . . . . 105, 107
Profile, VoIP provider/PBX . . . . . . . . . . . . . . . . . 50
Name filter, LDAP. . . . . . . . . . . . . . . . . . . . . . . 73
Provider profile . . . . . . . . . . . . . . . . . . . . . . . . 50
Navigation menu, show/hide . . . . . . . . . . . . . . 22
Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Network mailbox
Provisioning server . . . . . . . . . . . . . . . . . . . . . 80
entering number . . . . . . . . . . . . . . . . . . . . 102
Proxy server
playing back messages . . . . . . . . . . . . . . . 102
address . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Network MB, see Network mailbox
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Network protocol . . . . . . . . . . . . . . . . . . . . . . 25
PTP deviation . . . . . . . . . . . . . . . . . . . . . . . . . 44
Non-SRTP calls, accepting . . . . . . . . . . . . . . . . 51
Public online directory . . . . . . . . . . . . . . . . . . . 75
Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Number filter . . . . . . . . . . . . . . . . . . . . 105, 107
Number filter, LDAP . . . . . . . . . . . . . . . . . . . . . 73 Q
QoS (Quality of Service) . . . . . . . . . . . . . . . . . . 67
O
Online directory R
LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Radiation power . . . . . . . . . . . . . . . . . . . . . . . 88
public. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Reboot
XSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 base station . . . . . . . . . . . . . . . . . . . . . . . . 41
Online services . . . . . . . . . . . . . . . . . . . . . . . . 77 LED display . . . . . . . . . . . . . . . . . . . . . . . . . 17
Operator manually . . . . . . . . . . . . . . . . . . . . . . . . . . 31
AND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Redial list . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
OR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Registering a set of handsets . . . . . . . . . . . . . . 60
OR operator . . . . . . . . . . . . . . . . . . . . . . . . . 106 Registering DECT managers at the Integrator . . . 33
ou, attribute . . . . . . . . . . . . . . . . . . . . . . 74, 108 Registering handsets . . . . . . . . . . . . . . . . . 57, 60
Outbound proxy mode . . . . . . . . . . . . . . . . . . 52 time-controlled . . . . . . . . . . . . . . . . . . . . . . 65
Outbound proxy port. . . . . . . . . . . . . . . . . . . . 53 Registering, with web configurator . . . . . . . . . . 21
Outbound server address . . . . . . . . . . . . . . . . . 52 Registration centre . . . . . . . . . . . . . . . . . . . . . 65
Registration refresh time . . . . . . . . . . . . . . . . . 51
P Reset
emergency . . . . . . . . . . . . . . . . . . . . . . . . . 19
Package content . . . . . . . . . . . . . . . . . . . . . . . 10
to factory settings . . . . . . . . . . . . . . . . . . . . 18
Packet delay jitter . . . . . . . . . . . . . . . . . . . . . . 44
using the device button . . . . . . . . . . . . . . . . 15
P-Asserted-Identity (PAI). . . . . . . . . . . . . . . . . . 55
via power procedure . . . . . . . . . . . . . . . . . . 18
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Restore configuration . . . . . . . . . . . . . . . . . . . 87
Password, web configurator . . . . . . . . . . . . . . . 21
RFPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Template Module, Version 1.2, 11.09.2018,

changing . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Ringback
PBX (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
switching function off if busy . . . . . . . . . . . . 98
PBX access code . . . . . . . . . . . . . . . . . . . . . . . 68
when the number is busy . . . . . . . . . . . . . . . 98
PBX profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Roaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
PCMA/ PCMU . . . . . . . . . . . . . . . . . . . . . . . . . 54
RPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Pending base stations . . . . . . . . . . . . . . . . . . . 39
RPN group . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Phone number
RTP (Realtime Transport Protocol) . . . . . . . . . . . 67
dialling . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
RTP packetisation time (ptime) . . . . . . . . . . . . . 55
Phone number in directory. . . . . . . . . . . . . . . 108
Place holder for user input . . . . . . . . . . . . . . . 106
PoE (Power over Ethernet) . . . . . . . . . . . . . . . . 14 S
Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Safety precautions . . . . . . . . . . . . . . . . . . . . . 112
postalAddress, attribut . . . . . . . . . . . . . . . . . . 108 Save configuration. . . . . . . . . . . . . . . . . . . . . . 87
postalAddress, attribute . . . . . . . . . . . . . . . . . . 74 SDP (Session Description Protocol) . . . . . . . . . . 55

120
Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / AdminSIX.fm / 11/7/18

Index

Search base. . . . . . . . . . . . . . . . . . . . . . . . . . 104 Time


Search mode . . . . . . . . . . . . . . . . . . . . . . . . . 110 synchronisation . . . . . . . . . . . . . . . . . . . . . 83
Search start point . . . . . . . . . . . . . . . . . . . . . 104 zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Secure Real Time Protocol . . . . . . . . . . . . . . . . 51 Time server . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Secure Shell (SSH) . . . . . . . . . . . . . . . . . . . . . . 78 Time, setting . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Timer
SIP port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 failed registration retry . . . . . . . . . . . . . . . . 66
SIP redundancy . . . . . . . . . . . . . . . . . . . . . . . . 52 SIP session . . . . . . . . . . . . . . . . . . . . . . . . . 66
SIP server port . . . . . . . . . . . . . . . . . . . . . . . . . 52 SIP timer T! . . . . . . . . . . . . . . . . . . . . . . . . . 66
SIP session timer . . . . . . . . . . . . . . . . . . . . . . . 66 subscription . . . . . . . . . . . . . . . . . . . . . . . . 66
SIP timer T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Tone scheme . . . . . . . . . . . . . . . . . . . . . . . . . . 69
SISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Transport protocol . . . . . . . . . . . . . . . . . . . . . . 51
Site Planning Kit . . . . . . . . . . . . . . . . . . . . . . . . 8 TX power, reduce . . . . . . . . . . . . . . . . . . . . . . . 41
sn, attribute . . . . . . . . . . . . . . . . . . . . . . 74, 108
SNMP (Simple Network Management Protocol) 32, U
94 Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SNMP manager . . . . . . . . . . . . . . . . . . . . . 32, 94
user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Specifications . . . . . . . . . . . . . . . . . . . . . . . . 115
User input, place holder . . . . . . . . . . . . . . . . . 106
SRTP options . . . . . . . . . . . . . . . . . . . . . . . . . . 51
User name
Standard gateway . . . . . . . . . . . . . . . . . . . . . . 26
handset . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Statistics
web configurator . . . . . . . . . . . . . . . . . . . . 21
CSV file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
download in MIB format . . . . . . . . . . . . . . . 92
resetting. . . . . . . . . . . . . . . . . . . . . . . . . . . 92 V
Status information . . . . . . . . . . . . . . . . . . . . . . 90 Virtual machine . . . . . . . . . . . . . . . . . . . . . . . . 14
street, attribut . . . . . . . . . . . . . . . . . . . . . . . . 108 Voice quality . . . . . . . . . . . . . . . . . . . . . . . . . . 67
street, attribute . . . . . . . . . . . . . . . . . . . . . . . . 74 VoIP provider, configure profile . . . . . . . . . . . . . 50
Subnet mask . . . . . . . . . . . . . . . . . . . . . . . . . . 26 VoIP settings . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Subscription timer . . . . . . . . . . . . . . . . . . . . . . 66
Sync level . . . . . . . . . . . . . . . . . . . . . . . . . 43, 48 W
Sync master/slave . . . . . . . . . . . . . . . . . . . . . . 42 Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . 16
Sync slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Wall mounting slots . . . . . . . . . . . . . . . . . . . . . . 9
Synchronisation . . . . . . . . . . . . . . . . . . . . . . . 42 Web configurator
best base of DM . . . . . . . . . . . . . . . . . . . . . 34 applying/discarding changes . . . . . . . . . . . . 22
cross-cluster . . . . . . . . . . . . . . . . . . . . . . . . 34 changing password . . . . . . . . . . . . . . . . . . . 78
DECT manager . . . . . . . . . . . . . . . . . . . . . . 34 connecting with PC . . . . . . . . . . . . . . . . . . . 20
external with RFPI . . . . . . . . . . . . . . . . . . . . 34 logging in . . . . . . . . . . . . . . . . . . . . . . . . . . 21
over LAN . . . . . . . . . . . . . . . . . . . . . . . 42, 43 logging off . . . . . . . . . . . . . . . . . . . . . . . . . 21
over the air . . . . . . . . . . . . . . . . . . . . . . 42, 43 menu overview . . . . . . . . . . . . . . . . . . . . . . 24
Synchronisation hierarchy . . . . . . . . . . . . . . . . 42 online help function . . . . . . . . . . . . . . . . . . 22
examples . . . . . . . . . . . . . . . . . . . . . . . . . . 45 password . . . . . . . . . . . . . . . . . . . . . . . . . . 21
graphical view . . . . . . . . . . . . . . . . . . . . . . 92 security certificate . . . . . . . . . . . . . . . . . . . . 79
Synchronisation planning . . . . . . . . . . . . . . . . 42 starting . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Synchronisation status working with lists . . . . . . . . . . . . . . . . . . . . 23
base station . . . . . . . . . . . . . . . . . . 17, 37, 48
SysLog . . . . . . . . . . . . . . . . . . . . . . . . . . . 32, 94
System configuration . . . . . . . . . . . . . . . . . . . . 20 X
Template Module, Version 1.2, 11.09.2018

System report (SysLog) . . . . . . . . . . . . . . . 32, 94 XHTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77


XSI (Xtended Service Interface) . . . . . . . . . . . . . 70
XSI call log, enable . . . . . . . . . . . . . . . . . . . . . . 70
T
XSI directories
Telephone system enabling . . . . . . . . . . . . . . . . . . . . . . . . 70, 75
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 XSI services
preparing to use . . . . . . . . . . . . . . . . . . . . . 10 credentials . . . . . . . . . . . . . . . . . . . . . . . . . 64
telephoneNumber, attribute . . . . . . . . . . . 74, 108

All rights reserved. Rights of modification reserved.

121
Template Module, Version 1.2, 11.09.2018 / ModuleVersion 1.0 Gigaset N870 IP PRO / Admin IE-UK-International en / A31008-XXXXX-XXXX-X-XXXX / cover_back.fm / 11/7/18

Issued by
Gigaset Communications GmbH
Frankenstr. 2a, D-46395 Bocholt

© Gigaset Communications GmbH 2018


Subject to availability.
All rights reserved. Rights of modification reserved.
www.gigasetpro.com

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy