Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Valid for:





Embedded Integrator

Virtual Integrator

titleSystem overview

 An N870 Enterprise sized system is described below.

Minimum SizeMaximum Size

DECT Virtual Integrator

DECT Manager1100
Additional DECT Base16000
60 per DM
DECT Handsets*20000
Max. Parallel calls86000

Connection capacity
Enabled codecsDM + BaseBase only
G.711 only810
G.729 & G.71158
G.722 & G.729 & G.71155

* = Number of handsets is based on the required traffic volume (Erlang E), we recommend to use maximum 20 DECT handsets per DECT base.

titleAuto-provisioning & SIP Registration, handset in IDLE mode


When you use auto-provisioning, the provisioning server of the customer will always configure the Integrator. It does not matter if the Integrator is embedded in the device or the Virtual Integrator.

SIP Registration:

The SIP registration is always done by the DECT manager of the N870 multicell where the handset is connected.

The handset will:

  • Start location registration procedure if RPN-group is different.

  • Starts location registration, after returning from more than 40s asynchronicity

The Integrator will:

  • Transfer of all handset settings from the data base to the new DECT Manager

  • Start SIP registration at new DECT Manager

  • Start SIP deregistration at old DECT Manager

  • Transfer of calls list from old DECT Manager to new DECT Manager

Handset in range of N870 managed by DECT Manager A1Handset in range of N870 managed by DECT Manager A2

When the DECT handset is in the range of the N870 Multicell system that is managed

by DECT manager A1. The SIP Registration is done by DECT Manager A1.

When the handset moves from to the first N870 Multicell system, that is managed by DECT

A1 to the system managed by DECT manager A2. The SIP Registration will be done by DECT

manager A2.

titlePotential platform (miss) behavior
  • Some platforms do not accept a new contact while there is still and old contact registered, they reject the new registration.
  • Some platforms when receiving an deregistration, do not delete the old registration contact information.

The heal such issues, we have implemented.

  • Fast repetition of successful registration (5s) for roaming case

  • Fast repetition of unsuccessful registration (5s) for roaming case

In case of roaming to a new location, during 1-2 seconds an incoming/outgoing call could be rejected. An outgoing call must be repeated by the user.

titleSIP & RTP during a call

If you move during a call from N870 managed by DECT manager A1 to the N870 managed by DECT manager A2:

  • SIP signalling during the call will be handled by the DECT manager (A1) where the call has started. (SIP roaming is suppressed)
  • RTP will be routed internally from the DECT base the call has been started to the DECT base of the other system where the handset is connected.
  • When the call is ended, after 20 seconds, the SIP Registration will move to the DECT manager where the handset is in range. (To handle potential recalls, the radio link is artificially kept for 20 seconds)