Last modyfication:	12.08.2013 13:55
HKLM - HKEY_LOCAL_MACHINE
HKCU - HKEY_CURRENT_USER
TMC - SOFTWARE \ Teliman \ Client \
TMS - SOFTWARE \ Teliman \ Server \
DIS_Configure_ADS_FieldsAssignDefinition_in_CTI_CentralIni.sdf 2012_02_27
DIS_Configure_MAPI_FieldsAssignDefinition_in_CTI_CentralIni.sdf 2012_02_27
TMS_CSVImporter
TMS_Active_Directory__LDAP
TMS Active Directory (LDAP) add extra internal number
TMS Active Directory (LDAP) add extra internal number with replace
TMS Active Directory (LDAP) add extra internal number with replace. Use list of possible values (and replacements) to replace
References_Database
RefSearch_MdbFilePath
BCI
CalledID_Name
DIS_RefSearch.exe_for__TextFile__source_adds_extra_internal_ number_with_replace._It_uses_list_of_possible_values__ and_replacements__to_replace.
CAPIFax_–_Protocol_Configuration
DIS_TeliRef_To_CTI_Config.mdb–users_configuration_update_by_RefSearch_CTI_Server_7_0_5428_2012_01_19
DIS_External_Absence_Support_–_Synchronization_With_Lotus 2012_02_01
Database_CTI_CentralIni_moved_to_SQL_server
TMS CSVImporter	TMS: 4_5_811; 06.12.2007
1) Configuration: CSVImporter_Config.mdb
2) csvImporter_Destination.sql
csvImporter_Destination.sql
3) CSVImporter.zip
CSVImporter.zip
References Database	TMC>=4.5.2458, TMS>=4.5.384
0) DataBase in Mixed mode Start\Programme\...\Microsoft SQL Server 2005\SQL Server Management Studio Express Properties [ComputerName]\SQLExpress   Security: SQL Server and Windows Authentication mode
1) Create Database TeliMan
2) Sql script:
Create_Login.sql
CreateDB.sql
CreateDB_OlderThan_7_0_5204_2011_06_22.sql
or
CreateDB_Indexes.sql
or
Protocol.sql
Protocol_OlderThan_7_0_5204_2011_06_22.sql
or
Update_Protocol_Indexes.sql
or
TeliManUserMakeOwner.sql
3) user: TeliMan, password: TeliRefPass
4) Share CentralFolder
5) TbAssist
6) Start\Programme\...\Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager: SQL Server 2005 Network Configuration \ Protocols for SQLEXPRESS: Enable all protocols
7) Must working process SQLBROWSER: Start\Programme\...\Microsoft SQL Server 2005\Configuration Tools\SQL Server Surface Area Configuration Surface Area Configuration for Services and Connections SQL Server Browser
8) User Properties:User Mapping \ TeliMan: dbowner
9) RefSearch.reg
Warning: update mdb -> Sql: nvarchar -> varchar
Action Types: OutLook MAPI, TAPI, TMACTION, CMD: "StrCmd"="notepad.exe %1"
Action Types: CLIPBOARD%1-PhoneNumber,CLIPBOARD%2-ExtraField	21.08.2008, Cli: 5_0_2885
TMC_StrCmd.reg
Info:
Reference database on other computer than TMS please change C:\Programme\TeliMan Pro Server\TMServer\CentralFolder\PbIniSrv.mdb Table: DataBases, Column: RefConnStr
RefSearch MdbFilePath	TMS: 4.5.0.563; 05.10.2007
ShortCut: "E:\Programme\TeliMan Pro Server\TMRef\Refsearch.exe" SERVERMODE MdbFilePath="E:\Programme\TeliMan Pro Server\TMServer\CentralFolder\PbIniSrv2.mdb"
BCI	BCI_RefIdent_ver_1.0.3.42_05.11.2007_bin.zip
Telnet First please make telnet configuration for Alcatel connection.
Telnet configuration is at „Verbindung „ sheet of  BCI_RefIdent application
If no TMS then Make registry from file TMS_registry_Country_ Area_PABX.reg and edit values of CountryCode, AreaCode, PrefixIfMore	TMS_registry_Country_Area_PABX.reg
TeliRef For TeliRef connection please put connecton string into PbIniSrv.mdb and set path of PbIniSrv.mdb inside sheet „Datenpfade” of BCI_RefIdent application.	CreateDB.sql
If  database TeliMan/TeliRef no exist then use CreateDB.sql for create it.	CreateDB_OlderThan_7_0_5204_2011_06_22.sql
SQL database log For create table BCIEvents please use CreateDB.sql
Database access configuration details are at „Datenbankprotokoll” sheet of BCI_RefIdent application. Das Feld (SQL).TeliUsers.PhoneNumber entspricht dem Feld (SQL).BCIEvents.CalledId und dem Feld (TMSConfig.mdb).tblUsers.ExternalNumber Das Feld (SQL).TeliUsers.LineName wird nicht mehr verwendet
BCI-TMS-Protocol.mdb log Please install TMS as first.	TMS: 4.5.0.775;17.10.2007
C:\Programme\TeliMan Pro Server\TMConfig\TMS_Config.mdb
Table: tblUsers, Column: ExternalNumber
If problems then See BCIErrorLog.txt.
Debug on: „Ctrl + Alt + Shift + D”, off: „Ctrl + Alt + Shift + N”
CalledID Name	Cli: 4_5_2692, Srv: 4_5_831; 07.02.2008
C:\Programme\TeliMan Pro Server\TMConfig\TMS_Config.mdb tblCalledIDNames
TMS Active Directory (LDAP)	27.05.2008 Srv: 5_0_929
pbinisrv.mdb\ DataBases
Name = „Active Directory 01” Type = „ActiveDirectory” CnnString = “Provider=LDAP;Server=romico-server;User=TestUser;Password=test” RefConnStr = "Provider=SQLOLEDB.1;User ID=TeliMan;Password=TeliRefPass;Initial Catalog=TeliMan;Data Source=RomicoCtiRefSqlServer\SQLEXPRESS" RefTable = “TeliRef” Enabled = true
1. CnnString: Server - IP or DNS path 2. CnnString: User - user in domain
TMS Active Directory (LDAP) add extra internal number	19.08.2009 Srv: 5_0_3483
add second item (Intern) in TeliRef from source database. Remove main-part (configuration in pbinisrv) of complete number and check is it internal, if ok then add internal to reference database (for Active Directory)	Does not work from version 2011.05.27 Srv: 7_0_5165 (MainNumber format changed)
from number +49 1771234567 add also 67 when pbinisrv.mdb\ Database\ MainNumber= +49 17712345 and internal length=2 New column MainNumber (Text (20) Allow null) in table Databases
TMS Active Directory (LDAP) add extra internal number with replace	21.10.2009 Srv: 5_0_3512; RefSearch: 1_1_183
add second item (Intern) in TeliRef from source database. Replace main-part (configuration in pbinisrv) on part after ; of complete number and check is it internal, if ok then add internal to reference database (for Active Directory)	Does not work from version 2011.05.27 Srv: 7_0_5165 (MainNumber format changed)
from number +49 1771234567 add also 3267 when pbinisrv.mdb\ Database\ MainNumber= +49 17712345;32 and internal length=4 New column MainNumber (Text (50) Allow null) in table Databases
TMS Active Directory (LDAP) add extra internal number with replace. Use list of possible values (and replacements) to replace.	2011.05.27 Srv: 7_0_5165; RefSearch: 1_1_217
Add second item (Intern) in TeliRef from source database. Replace main-part (configuration in pbinisrv) on part in brackets of complete number and check is it internal, if ok then add internal to reference database (for Active Directory) from number +49 1771234567 add also 3267 when pbinisrv.mdb\ Database\ MainNumber= +49 17712345(32) and internal length=4. MainNumber can be list "+49 608495(1111);+49 6958(2222)” now.
RefSearch.exe for "TextFile" source adds extra internal number with replace. It uses list of possible values (and replacements) to replace.	CTI_Server > "16.11.2011, 10:01:00; 7.0.0.5377"; RefSearch: 1.1.0.238
Add second item (Intern) in TeliRef from source database. Replace main-part (configuration in pbinisrv) on part in brackets of complete number and check is it internal, if ok then add internal to reference database (for Active Directory and TextFile) from number +49 1771234567 add also 3267 when pbinisrv.mdb\ Database\ MainNumber= +49 17712345(32) and internal length=4. MainNumber can be list "+49 608495(1111);+49 6958(2222)” now.
CAPIFax – Protocol Configuration	CTI_Server > CTI_Server_7_0_5413_2012_01_12
1. CapiFax localization (whole CAPIFax directory containing all Client.CLT directories): [HKEY_LOCAL_MACHINE\SOFTWARE\ROMICO\CAPIFAX_Config] "CAPIConfig_Path"="\\\\192.168.11.123\\TeliFax" 2. CTI_Config.mdb – tblUsersFax configuration. Columns: UserName - CAPIFax userName (must be the same as “UserName.CLT” in CAPIFax directory (without “.CLT” string)) InternalNumber, UserID - from tblUsers.
TeliRef To CTI_Config.mdb–users configuration update by RefSearch CTI_Server_7_0_5428_2012_01_19	CTI_Server > CTI_Server_7_0_5428_2012_01_19
Description:
It is possible to update following fields in CTI_Server users configuration (CTI_Config.mdb.tblUsers) automatically: UserName, Name1, Name2, Company, E-Mail, using data from source reference database (SQL, MAPI, ADS, TextFile) when phone number matches CTI_Config.mdb.tblUsers InternalNumber or Phone2 or Phone3 or Phone4.
Note: UserName can be updated using following settings: “NoChange”, “InternalNumber”, “Name1, Name2”, “Name2, Name1”, “Name1 Name2”, “Name2 Name1”, “Name”. Where “Name” option can be configured as extra source column (in CTI_CentralIni.sdf.FieldsAssingDefinition.UserName column) for SQL and TextFile, and as account name for ADS.
Configuration (how to start CTI_Config.mdb auto-configuration):
a) [HKLM]\ SOFTWARE\ ROMICO\ CTI_Server\ Server001\ RefSearch\ CTI_Config_Actualize ="1"
b) Source database in CTI_CentralIni.sdf should have UseForCTI_Config flag set in order to be used as source database for CTI_Config.mdb contacts.
c) Start RefSearch – each contact found in reference source database that matches CTI_Config.mdb.tblUsers  numbers will be automatically used to update CTI_Config.mdb database.
*All changes in CTI_Config.mdb will be automatically reloaded in CTI_Server in one minute or less.
External Absence Support – Synchronization With Lotus	CTI_Server > CTI_Server_7_0_5598_2012_01_31
	TeliBar_2_0_3585_2012_02_01
AbsenceSynchronizer settings
This application is responsible for importing absence information from Lotus to CTI Server database. Before you run it, please go through the following steps:
1.     Absence data folder. Locate the folder where you keep appointment information exported from Lotus. This folder should contain either *.csv or *.txt files in Lotus format. Copy a complete path pointing to that folder and paste it into the following Windows registry key value:
[HKEY_LOCAL_MACHINE\SOFTWARE\ROMICO\ AbsenceSynchronizer\Synchronizer001]
"ImportFromPath"="C:\\Example\\MyLotusAppointments”.
2.     Database connection string. It is necessary to specify connection string to the database used by CTI Server, to which absence information will be imported from the folder mentioned above. The connection string should be added to the same registry key as the ImportFromPath value:
[HKEY_LOCAL_MACHINE\SOFTWARE\ROMICO\ AbsenceSynchronizer\Synchronizer001]
"ImportToDBConnectionString"="Data Source=(local)\\SQLEXPRESS;Initial Catalog=ROMICO-CTI;Integrated Security=SSPI;"
3.     Basic rules. The application referred to as AbsenceSynchronizer has to run all the time as otherwise no absence information will be imported. It is advisable to start it with Windows, for example by adding it manually to the Autostart folder.
4.     File names. AbsenceSynchronizer considers file names as phone numbers. If a file is named 1234.txt, its content (the absence information) is assigned to a phone number of 1234.
CTI Server settings
CTI Server supports both internal absence (the one it used to support so far) and a new kind of absence – the external one (that is, imported from an external application like Lotus). If you want it to handle external absences, please go through the following steps:
1.     Enable this feature. To enable external absence support just put a value of “1” in the following registry key value:
[HKEY_LOCAL_MACHINE\SOFTWARE\ROMICO\ CTI_Server\Server001\AbsenceController]
"ExternalAbsenceList_Enable"="1".
CTI_Server Restart is necessary.
2.     Create database table. It is necessary and very important to create a new database table that will keep the imported absence information. Please go to CTI Server support folder and find a file named UserExternalAbsence.sql (it is usually stored in the following folder: C:\Programme\ROMICO\CTI_Server\Support\). Open it with Microsoft SQL Server Management Studio and execute so that the new table is created in the ROMICO-CTI database.
Configure ADS FieldsAssignDefinition in CTI_CentralIni.sdf	CTI_Server_7_0_5643_2012_02_27
ADS – Possible values in CTI_CentralIni.sdf.FieldsAssignDefinition:
1.       FIRSTNAME - first name of the user
2.       LASTNAME - last name of the user
3.       USERNAME – ADS account login (sAMAccountName)
4.       FULLNAME - full name of the user
5.       OTHERNAME - additional name, such as the nickname,  or the middle name of the user
6.       COMPANY – company name
7.       EMAIL - email address of the user
8.       GUID - GUID of the object as stored in the underlying directory store
9.       ADSPATH
10.   TELEPHONEHOME - home phone number of the user
11.   TELEPHONEMOBILE - mobile phone number of the user
12.   TELEPHONENUMBER - work-related phone number
13.   FAXNUMBER - fax phone number
14.   TELEPHONEPAGER - pager phone number
15.   @ANY_Text – Constant text will be copied to selected  field when using “@”.
Configure MAPI FieldsAssignDefinition in CTI_CentralIni.sdf	CTI_Server_7_0_5643_2012_02_27
MAPI – Possible values in CTI_CentralIni.sdf.FieldsAssignDefinition:
1.       FIRSTNAME - first name of the user
2.       LASTNAME - last name of the user
3.       BUSINESSTELEPHONENUMBER - Business phone number
4.       BUSINESS – Business phone text
5.       HOMETELEPHONENUMBER – home phone number
6.       HOME – home phone text
7.       MOBILETELEPHONENUMBER - mobile phone number
8.       MOBILE – mobile phone text
9.       OTHERTELEPHONENUMBER - other phone number
10.   OTHER – other phone text
11.   BUSINESS2TELEPHONENUMBER - business2 phone number
12.   BUSINESS2 – business2 phone text
13.   HOME2TELEPHONENUMBER – home2 phone number
14.   HOME2 - home2 phone text
15.   PRIMARYTELEPHONENUMBER – primary phone number
16.   PRIMARY – primary phone text
17.   EMAIL1ADDRESS - Email
18.   COMPANYNAME –company name
19.   ENTRYID – Outlook entry ID
20.   FOLDERID – Outlook folder ID
21.   STOREID – Outlook store ID
22.   @ANY_Text – Constant text will be copied to selected field when using “@”.
Database CTI_CentralIni moved to SQL server	CTI_Server_7_0_6751_2013_08_08
Added user property DIS_Server, this property is used for DBConnector as param. Value of this property is calculated from config database, it is server path and database name to server sql with pbini data. Property DIS_Server is send to loged in CTI_Client by new network message.
Property of DIS_Server is calculated as:
use DIS_Server from user configuration,
if this configuration is no exist then,
use DIS_Server from UserGroup configuration,
if this configuration is no exist then,
use Main DIS_Server selected in configuration.
Main DIS_Server can be definened and main selected in Config database,
if this configuration no exist then,
we use default SQL Server from configuration of CTI_Server (TMS_Config->Algemein: SQL-Server and SQL-DBName).