Appendix D: Database Maintenance - ASCOM IPBS Installation And Operation Manual

Installation and Operation Manual
IP-DECT Base Station & IP-DECT Gateway (software version 5.0.x)

Appendix D: Database Maintenance

This section describes how IP-DECT user configuration can be moved from one system to
another. By moving users, one IP-DECT system can be split into many systems or several IP-
DECT systems can be merged to one single system.
Before database merge you should consider if the IP-DECT R3 Multi Master concept can
be used instead and whether it is possible to have several Masters on one site.
D.1 Prerequisites
For all systems involved in the database maintenance procedure:
• It is highly recommended to have the same software version running on all systems.
• If a user is moved to a system with a different SARI, the target system must be
configured with multiple SARIs containing the SARI number of the originating system
as well as its existing SARI. For more information, see
• The systems must have the same DECT system name and the same DECT system
password (configured under DECT > System) as well as the same device password
(General > Admin).
• LDAP replication must not be activated.
D.2 Database Maintenance Procedure
1 Make sure the handsets that correspond to the moved user data have no contact
with the system. Turn off the handsets or switch off the Radio(s) in the area where
the handsets are located. Handsets should show "No system". Handsets may be
desubscribed if they have connection to the system during database maintenance.
2 Save a configuration file from each Master involved. See
3 Identify user records in the saved configuration files and modify them according to
the desired plan. User records are located at the end of the file beginning after the
row:
mod cmd FLASHDIR0 add-view 101 cn=PBX0
4 To remove a user, remove the corresponding line.
To add a user (from another file), insert a line that has been removed from another
file. Remove the following attributes:
(guid;bin=###)
(usn=###)
where ### denotes an arbitrary value.
5 Save modifications to the configuration files.
6 Make sure that step 1 is met, and upload configuration files to the corresponding
entities. See
7 Reset in order to make the changes take effect, see
Removing a User Example
This example shows part of the configuration file. There may also be other attributes in
the used system.
15 February 2012 / Ver. H
8.18.1 Update Configuration
8.5.26 SARI on page 100.
8.14 Backup
on page 130.
8.22 Reset on page 138.
TD 92579EN
on page 126.
156