2.3.1 Configuration

Enable/ Disable
The integrated DTB is disabled by default. It needs to be enabled via Portal.
Figure 5
DTB Configuration
DTB Synchronization
Six synchronization modes are possible:
•
OFF
DTB will run, but the database will not be updated
•
with OpenScape 4000 Assistant (PERSDAT)
DTB will synchronize with the PERSDAT database from Assistant.
•
with OpenScape 4000 Assistant (DISPLAY_NAME)
DTB will synchronize with the DISPLAY_NAME database from Assistant.
•
with OpenScape 4000 Manager (PERSDAT)
DTB will synchronize with the PERSDAT database from Manager.
•
with OpenScape 4000 Manager (DISPLAY_NAME)
DTB will synchronize with the DISPLAY_NAME database from Manager.
•
with SFTP
DTB will synchronize with the database located on the SFTP server. The database files must be at "Path to DTB DB files" location and at least kunde.nam, kunde.rnr and kunde.t9i should be present. These mandatory files must be named "kunde" to work with iDTB. The rest of the database files are optional.
The PERSDAT and DISPLAY_NAME are the ODF (Object Description File) tables of the OpenScape platform.
Pressing the "Submit" button will install the selected synchronization mode. An "Action successfully completed" message will appear at the upper right corner to confirm you action.
The "Reset" button will reinstall the DTB with the default settings which means, that the DTB database will be cleared and the configuration files will be restored to the factory settings (CSTA port, synchronization time, etc.).
End Device Language:
Language of end devices can be chosen here. For the devices, one of the following languages can be chosen:
–
English
–
German
NOTE: Changing the DTB synchronization mode, or end device language, while DTB is already running leads to a restart of DTB Master and DTB Server!
Import/ Export of DTB Configuration
The integrated DTB has preconfigured settings e.g. for:
•
IP configuration
•
connection to CSTA
IP: 192.0.2.25 Port: 2209
•
connection to Assistant (for synchronization)
IP: 192.0.2.5
•
filesystem paths
•
filenames
If necessary the ini-files of DTB Master and DTB Server can be exported, manually modified using a preferred text editor and finally imported back.
NOTE: The default settings for the internal IP connection, filesystem paths, filenames, etc. should be left unchanged!
The zip-file must contain the following directory structure:
DTBMaster >config >dtbmaster.ini
DTBServer >config >DTBServer.ini
The zip-file contains also Portal configuration (synchronization type, language, synchronization time). These properties will be applied in the portal after pressing the Activation button.
Figure 6
DTB Configuration - Import/ Export
Activation
To activate the modified DTB Master and/or DTB Server configuration during runtime the Activation button needs to be clicked. This can be done only after the successful import of configuration files.
NOTE: If the DTB application is running and at least one of the ini-files has changed, activation leads to a restart of the DTB application!
DTB Database - Import/Export
Figure 7
DTB Database - Import/Export
DTB database files are exported according to the DTB directory structure. Files in the exported archive file will be stored in the DTBServer or DTBMaster directory.
DTB database files have to be imported as an archive file with *.zip format. Otherwise, import will not be successful. Files do not have to be imported in some directory structure. All files can be just stored in the *.zip archive.
Files with suffixes '*.nam, *.rnr, *.t9i, *.nax, *.rnx' will be renamed during the import. Suffixes of these files will remain the same. Files can be imported without any special naming.
Files firmlist.rnr, filtlist.rnr, config.dtb, privdt.dtb have to be imported as listed. These can not be renamed before the import.
NOTE: Files with the suffixes '*.nam, *.rnr (except firmlist.rnr and filtlist.rnr), *.t9i.' must all be imported together. Files 'firmlist.rnr, filtlist.rnr, config.dtb, privdt.dtb' and files with suffixes '*.nax, *.rnx' can be imported separately, or together with the files listed before. Otherwise, import will not be successful and changes can not be activated.
NOTE: Please include on single files in the imported *.zip archive. Otherwise, the import will not be successful.
 
NOTE: When synchronization is not set “OFF”, then the imported database files(.nam,.nax,.rnr,.rnx,.t9i) will be overwritten during the next synchronization!
Activation
Once import has been successful, the new DTB database files can be activated.
NOTE: During the activation, if the database has been changed, a restart of DTB will occur!
Phonebook Editor – PEDIT
The DTB uses the PEDIT tool for editing/sorting the database (DB) subscriber data. This tool can be accessed from two locations:
1.
An installation package can be downloaded from the OS4K Portal under System > DTB Configuration > Database Import Export > “PEDIT Download” button.
Figure 8
PEDIT Download
2.
The installed form can be accessed from the DTB-Win application’s directory, usually at C:\DTB\DTBNetzConfig\
The installation directory contains two executables that belongs to PEDIT: PEDIT.exe and peditw.exe.
Platform Administration (Portal), ID: P31003-H31A0-M101-03-76A9
Copyright © Unify Software and Solutions GmbH & Co. KG 07/2020  -  All rights reserved.