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.
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 A1||Handset 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
Potential 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.
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.