Outlook appointment synchronization
               
This website provides a short description how to configure appointment synchronization in your TeliBar and the CTI Server.        
               
Jump to:              
TeliBar configuration              
CTI Server configuration              
               
               
TeliBar configuration    
               
Registry entries    
[HKCU_CTI_Client] = HKEY_CURRENT_USER\ SOFTWARE\ ROMICO\ CTI_Client    
[HKCU_TeliBar] = HKEY_CURRENT_USER\ SOFTWARE\ ROMICO\ TeliBar    
               
Name Location Example Description Registry Key example Version    
Outlook_ DefaultCalendarOnly
AppointmentsImport
Params
[HKCU_CTI_Client]\
ExternalData
"Outlook_DefaultCalendarOnly"=
"0"
There are two available values of that entry:
“1”,
“0”.
Parameter =“1” means that MapiConnectorNet will search for appointments in default callendar only, else MapiConnectorNet will serch for appointments in all possible outlook callendars.
 [default "1"] restart not needed.
CTI_Client_ Outlook_  Appointments DefaultCalendarOnly_0.reg TeliBar: ≥ 2.0.0.4354; 23.08.2012    
Outlook_
AppointmentsImport
Params
[HKCU_CTI_Client]\
ExternalData
"Outlook_AppointmentsImportParams"=
"ImportAll"
There are two available values of that entry:
“ImportTimeRangeOnly”,
“ImportAll”.
The difference between those two options is that when “ImportTimeRangeOnly” is set, the imported appointments are described as “Outlook” and they do not contain the original subject. When “ImportAll” is set (which is the default value), the appointments have the original subject.
[default "ImportAll", restart unnecessary].
CTI_Client_Outlook_
AppointmentsImportParams_
ImportAll.reg
TeliBar: ≥ 2.0.0.3986; 27.04.2012    
Outlook_Appointments
Path
[HKCU_CTI_Client]\
ExternalData
"Outlook_AppointmentsPath"=
"C:\\AbsenceSynchronizer"
This registry entry defines the destination folder for the AbsenceSynchronizer-compatible appointment files.
When the key does not exist, the 'AbsenceSynchronizer' subdirectory of the CTI Server CentralFolder is used as the destination directory for Outlook appointments (…\CentralFolder\AbsenceSynchronizer).
CTI_Client_Outlook_
AppointmentsPath.reg
TeliBar: ≥ 2.0.0.3986; 27.04.2012    
Outlook_
AppointmentsImport
Params
[HKCU_TeliBar]\ExternalData "Outlook_AppointmentsImportParams"=
"ImportAll"
There are three available values of that entry:
“ImportNone”,
“ImportTimeRangeOnly”,
“ImportAll”.
If “ImportAll” or “ImportTimeRangeOnly” is set then TeliBar imports Outlook appointments together with contacts. The difference between those two options is that when “ImportTimeRangeOnly” is set, the imported appointments are described as “Outlook” and they do not contain the original appointment subject. However, when “ImportAll” is set, the appointments will have the original subject.
“ImportNone” disables the appointments import functionality and only contacts are imported.
[default "ImportNone", restart unnecessary].
TeliBar_Outlook_
AppointmentsImportParams_
ImportAll.reg
TeliBar: ≥ 2.0.0.3897; 28.03.2012    
Outlook_Appointments
Path
[HKCU_TeliBar]\ExternalData "Outlook_AppointmentsPath"=
"C:\\AbsenceSynchronizer"
This registry entry defines the destination folder for the AbsenceSynchronizer-compatible appointment files.
When the key does not exist, the CTI Server CentralFolder is used as the destination folder for Outlook appointments (…\CentralFolder\AbsenceSynchronizer).
TeliBar_Outlook_
AppointmentsPath.reg
TeliBar: ≥ 2.0.0.3897; 28.03.2012    
               
How to filter synchronized appointments    
There are two ways appointments can be filtered: based on a whitelist or based on a blacklist. A blacklist causes matching appointments to be rejected, whereas a whitelist causes only matching appointments to be accepted.    
               
To define a blacklist or a whitelist:    
1. Go to the “%AppData%\ROMICO” folder (for example “C:\Users\MyUserName\AppData\Roaming\ROMICO”).    
2. If you want to define a blacklist, just create there a file named “AppointmentBlacklist.txt”.    
3. If you want to define a whitelist, just create there a file named “AppointmentWhitelist.txt”.    
4. If you want to define an Outlook account filter, just create there a file named "AppointmentAccountWhitelist.txt.    
           
Each line in the file you decide to create must be an independent phrase. If a given line (a phrase) is found in the subject of an imported appointment, that appointment is considered as matching the filter. This means that the appointment is rejected (in case of blacklist) or accepted (in case of whitelist).    
If you define an Outlook account filter, you should list there only the names of the accounts which you want to be included during appointment synchronization. These should be the names which Outlook lets you assign to different accounts independently. By default, these names are e-mail addresses (unless changed manually).    
               
               
CTI Server configuration    
               
Useful registry entries    
[HKLM_AS] = HKEY_LOCAL_MACHINE\ SOFTWARE\ ROMICO\ AbsenceSynchronizer    
[HKLM_CTI_Server] = HKEY_LOCAL_MACHINE\ SOFTWARE\ ROMICO\ CTI_Server    
               
Name Location Example Description Registry Key example Version    
ExternalAbsenceList_Enable [HKLM_CTI_Server]\ Server001\AbsenceController “ExternalAbsenceList_Enable”=”1” If this value is set to 1, server enables external absence support. 0 means that this feature is disabled.
[default = “0”, restart necessary].
AbsenceController_
ExternalAbsenceList_Enable.reg
CTI_Server ≥ 31.01.2012, 7_0_5598    
ImportFromPath [HKLM_AS]\ Synchronizer001 "ImportFromPath"=
"C:\\Programme\\ROMICO\\
ExternalAbsence“
The path that is the source of user absence information. This directory should contain user appointment lists as CSV files in Lotus format. Only those files whose extension is either *.csv or *.txt are accepted.
This registry entry is optional. If not provided, the 'AbsenceSynchronizer' subdirectory of the CTI Server CentralFolder is used as the source of data (usually
"C:\ Program Files\ ROMICO\ CTI_Server\ TMServer\ CentralFolder\ AbsenceSynchronizer").
[default "", restart unnecessary].
AbsenceSynchronizer_
ImportFromPath.reg
CTI_Server ≥ 27.04.2012, 7_0_5719    
ExternalAbsenceList_
CheckInterval_s
[HKLM_CTI_Server]\
Server001\AbsenceController
“ExternalAbsenceList_
CheckInterval_s”=”120”
Defines how often CTI Server reloads external absence lists from user appointment files.
[default = “60”, restart not necessary].
AbsenceController_
ExternalAbsenceList_
CheckInterval_s.reg
CTI_Server ≥ 16.10.2012, 7_0_6060    
ExternalAbsenceList_
UserStateUpdateInterval_s
[HKLM_CTI_Server]\
Server001\AbsenceController
“ExternalAbsenceList_
UserStateUpdateInterval_s”=”60”
Defines how often CTI Server updates external absence status of each user (based on absence period).
[default = “30”, restart not necessary].
AbsenceController_
ExternalAbsenceList_
UserStateUpdateInterval_s.reg
CTI_Server ≥ 16.10.2012, 7_0_6060    
Outlook_LocalContacts_
Synchronize_Enable
[HKLM_CTI_Server]\ Server001\ RefSearch "Outlook_LocalContacts_
Synchronize_Enable"="1"
If this value is set to 1, the server includes private Outlook contacts during synchronization (which it normally ignores).
[default = “0”, restart unnecessary].
Outlook_LocalContacts_
Synchronize_Enable_1.reg
CTI_Server > 04.03.2013, 7_0_6443    
ImportFromPath [HKLM_AS]\ Synchronizer001 "ImportFromPath"=
"C:\\Programme\\ROMICO\\
ExternalAbsence“
The path that is the source of absence information. This directory should contain appointment information exported from Lotus in CSV format files. Only those files whose extension is either *.csv or *.txt are accepted.
[default "", restart necessary].
AbsenceSynchronizer_
ImportFromPath.reg
CTI_Server ≥ 31.01.2012, 7_0_5598
CTI_Server < 27.04.2012, 7_0_5719
   
ImportToDBConnectionString [HKLM_AS]\ Synchronizer001 “ImportToDBConnectionString”=
”Data Source=(local)\\SQLEXPRESS;
Initial Catalog=ROMICO-CTI;
Integrated Security=SSPI;”
CTIServer database connection string (MSSQL). Refers to the database to which the imported absence information will be saved by AbsenceSynchronizer.
This registry entry is optional. If not provided, the default protocol database of CTI Server is used as the destination for user absence lists.
[default = “”, restart unnecessary].
AbsenceSynchronizer_
ImportToDBConnectionString.reg
CTI_Server ≥ 27.04.2012, 7_0_5719
CTI_Server < 16.10.2012, 7_0_6060
   
ImportToDBConnectionString [HKLM_AS]\ Synchronizer001 “ImportToDBConnectionString”=
”Data Source=(local)\\SQLEXPRESS;
Initial Catalog=ROMICO-CTI;
Integrated Security=SSPI;”
CTIServer database connection string (MSSQL). Refers to the database to which the imported absence information will be saved by AbsenceSynchronizer.
[default = “”, restart necessary].
AbsenceSynchronizer_
ImportToDBConnectionString.reg
CTI_Server ≥ 31.01.2012, 7_0_5598
CTI_Server < 27.04.2012, 7_0_5719
   
ExternalAbsenceList_
CheckInterval_s
[HKLM_CTI_Server]\
Server001\AbsenceController
“ExternalAbsenceList_
CheckInterval_s”=”120”
Defines how often CTI Server reloads external absence lists from user appointment files.
[default = “180”, restart not necessary].
AbsenceController_
ExternalAbsenceList_
CheckInterval_s.reg
CTI_Server ≥ 27.04.2012, 7_0_5719
CTI_Server < 16.10.2012, 7_0_6060
   
ExternalAbsenceList_
CheckInterval_s
[HKLM_CTI_Server]\
Server001\AbsenceController
“ExternalAbsenceList_
CheckInterval_s”=”120”
Defines how often CTI Server checks the database for external absence list changes. Those changes are detected only if AbsenceSynchronizer loads any data from its absence source directory.
[default = “900”, restart not necessary].
AbsenceController_
ExternalAbsenceList_
CheckInterval_s.reg
CTI_Server ≥ 31.01.2012, 7_0_5598
CTI_Server < 27.04.2012, 7_0_5719
   
ExternalAbsenceList_
UserStateUpdateInterval_s
[HKLM_CTI_Server]\
Server001\AbsenceController
“ExternalAbsenceList_
UserStateUpdateInterval_s”=”60”
Defines how often CTI Server updates external absence status of each user (based on the absence validity period).
[default = “90”, restart not necessary].
AbsenceController_
ExternalAbsenceList_
UserStateUpdateInterval_s.reg
CTI_Server ≥ 31.01.2012, 7_0_5598
CTI_Server < 16.10.2012, 7_0_6060
   
               
How to filter synchronized appointments globally    
There are two ways appointments can be filtered globally: based on a whitelist or based on a blacklist. A blacklist causes matching appointments to be rejected, whereas a whitelist causes only matching appointments to be accepted.    
               
To define a blacklist or a whitelist:    
1. Go to the folder specified by the “Path_Server” registry entry you can find in the following key: [HKLM]\ SOFTWARE\ ROMICO\ CTI_Server. It is usually “C:\Program Files\ROMICO\CTI_Server\TMserver\”.    
2. If you want to define a blacklist, just create there a file named “AppointmentBlacklist.txt”.    
3. If you want to define a whitelist, just create there a file named “AppointmentWhitelist.txt”.    
               
Each line in the file you create should be an independent phrase. If a given line (a phrase) is found in the subject of an imported appointment, this appointment matches the filter. This means that it is rejected (in case of blacklist) or accepted (in case of whitelist).