2.3.8
Synchronization with OpenScape 4000 Manager/Assistant
2.3.8.1
Parameter Configuration for Common Directory Setup after Synchronization (OpenScape 4000 Manager/Assistant)
If some of the selected data from the response data (DTBIntGeheim.rsp and DTBExt.rsp) is not transferred into the company directory, the CFG files can still be adapted before synchronization in accordance with the following procedures:
hdms_conv_int.cfg file
The hdms_conv_int.cfg file is used to convert internal subscriber data (without secret
subscribers).
Structure
name
|christianname|salutation|title|org1|org2|org3|
extension
||||
Example:
name
|christianname|salutation|title|org1|||
extension
||||
hdms_conv_ext.cfg file
The hdms_conv_ext.cfg file is used to convert external subscriber data.
Structure
name
|christianname|salutation|title|org1|org2|org3|
extension
|
ext_areacode|ext_netcode|ext_ext|location
Example:
name
|christianname|salutation|title|org1|org2||
extension
|ext_areacode| ext_netcode|ext_ext|
NOTE:
The number of pipe characters (|) should remain the same.
Note:
•
The procedure described here only applies to synchronization in accordance with the PORTPERS (internal subscribers without secret subscribers) and PERSDAT (external subscribers from the OpenScape 4000 Manager central database) ODF tables. The data from both tables is used to create the company directory.
If secret subscribers are to be included in the DTB company directory, the “where“ clause should be deleted from the “DTBIntGeheim.req“ request file.
•
Field names printed in bold are mandatory fields. All other fields are optional. Fields that are not used must be indicated by separators.
•
These procedures must be observed, incorrect settings in the CFG files (missing separators, incomplete mandatory fields) are not checked by DTB V9.0 resulting in a defective (unusable) company directory.
•
The OpenScape 4000 Assiatant supports only switch-related data. Therefore, the synchronization of external user data is only done using the OpenScape 4000 Manager.
Selected Data from PORTPERS and PERSDAT ODF Tables for each Installation
Field
Type
Description
sortname
char(60)
Name
christianname
char(15)
First name of the subscriber
Salutation
char(15)
Greeting
Title
char(15)
Title
org1
char(40)
Organisational unit 1
org2
char(40)
Organisational unit 2
org3
char(40)
Organisational unit 3
Extension
char(6)
Internal number
ext_areacode
char(6)
Area code
ext_netcode
char(16)
Office number
ext_ext
char(6)
Number
location
char(5)
Location
Table 4
Selected Data from PORTPERS and PERSDAT ODF Tables for each Installation
If personal data is not maintained in the OpenScape 4000 Manager, the company directory can also be generated via the PORT ODF table with the display names from the “PORTDATA“ file.
Field
Type
Description
displayname
char(31)
name
extension
char(6)
internal telephone number
Platform Administration (Portal)
, ID:
P31003-H31A0-M101-03-76A9
Copyright ©
Unify Software and Solutions GmbH & Co. KG
07/2020
- All rights reserved.