CallChange novinky Table of contents User documentation Administrator documentation Documentation for developers Technical support Search on-line
Configuration items in registry and database

Most of CallChange settings in registry and database is described here. Description is divided into sections according to individual components:

Search server

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\UMS\ContactSearch] - global settings
Value Content example Description
AdoConnString Provider=sqloledb;Data Source=KIM;Initial Catalog=CallChange;User Id=sa;Password=heslo configuration of search server ADO database. If filled in, ADO database is used and search server creates tables automaticaly. If empty, SQLite database in DbPath folder is used.
AdoUser   user for connecting ADO database (optional). If set, it takes precedence over user setting in AdoConnString. User must be able to create tables in database.
AdoPass   password for connecting ADO database (optional). If set, it takes precedence over password setting in AdoConnString.
AdoConnOpt 16 other parameters (optional). 16 = asynchronous connection, -1 = synchronous connection
AllPubFolPrefix All Public Folders prefix for all public folders (root public folder), valid only for EX provider
AutReload 1 enables (1)/disables (0) automatic contacts update (e.g. when contact is not found). Default = 0.
CacheReload 3600 time in seconds; when this time expires, contact cache is updated. Default = 1999999.
DbPath C:\Program Files\Common Files\Datasys\DsCssSrv folder, where database of cached contacts is created (cssrv_ZZ.sdb file, where ZZ is provider type)
EX_Server ZL-EX Exchange server name for EX provider
EX_User Ums MBX mailbox used by search server (EX provider).

Alternatively you can create EX_Profile instead of EX_Server and EX_User, what is name of configured Outlook profile, which will be used for Exchange server connection. ATTENTION - service account must have right to use this profile!!
LogPath C:\Callchange\server\log folder, where search server creates log about its work. If this value doesn't exist or is empty, default location is used: path to local application settings in user's profile is read from registry value HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData and Datasys\Callchange\log folder is created here. Path to logfile is then
C:\Documents and Settings\<user>\Local Settings\Application Data\Datasys\Callchange\log.
Log 0 0 = don't create log, 1 = create log.
Log is written into file %LogPath%\cssearchYYMMDD.log, where %LogPath% is LogPath value in registry (see above). Individual file is generated for every day.
UserProperties MSGCLASS=1703996| EMAIL=805503006 MAPI properties for EX provider defined in form NAME1=EID1| NAME2=EID2...., which will be read in addition to default properties. This item doesn't exist after installation - it must be created manually, if necessary.
ProviderType EX List of active contact providers, separated by semicolon. Now are supported EX, LDAP, LN and ADO.
GetUserModeOnly 0 0 = Search server starts specified providers and searches public contacts (default), 1 = no provider is started.
xmlrpc_port 58081 Port, where is Search server accessible through XML RPC
Following settings are related to LDAP provider. If setting is missing, default values are used, which conforms to MS LDAP (Active directory).
UserProperties_LDAP MSGCLASS=objectClass| EMAIL=mail User properties defined in form NAME1=LDAP_NAME1| NAME2=LDAP_NAME2|..., which will be read in addition to default properties.
ldap_charset CP1250 Encoding on LDAP server side (default CP1250).
css_charset CP1250 Encoding on CSS server side (default CP1250).
ldap_filter (objectClass=person) Filter for object selection from LDAP server (default (objectClass=User)).
ldap_nm_EmplID mail Distinct user identifier - this property must have filled in all users and it must be unique.
For MS LDAP is used distinguishedName, for Lotus Notes set mail
ldap_nm_fName, ldap_nm_fName2 givenName
sn		 These two properties form Display Name
ldap_nm_PhoneNum, ldap_nm_HomeNum, ldap_nm_PagerNum, ldap_nm_FaxNum, ldap_nm_MobileNum, ldap_nm_IPNum telephoneNumber
homePhone
pager
facsimileTelephoneNumber
mobile
ipPhone		 Property names for phone numbers. If don't exist, setting for MS LDAP - Active Directory is used.
ldap_dv_xxx   Default value of xxx property - used if that value doesn't exist in LDAP. Use last part of any property name instead of xxx, so ldap_dv_PhoneNum is default value for ldap_nm_PhoneNum property.
Following settings are related to LN provider.
UserProperties_LN MSGCLASS=Form| EMAIL=MailAddress| MY_NAME=FirstName + MiddleInitial + LastName User properties defined in form NAME1=LN_NAME1| NAME2=LN_NAME2|..., which will be read in addition to default properties. MY_NAME is property composed from more Lotus properties.
Costs_LN MSGCLASS| Firm;LN_OFFICE_NUMBER;1| Person;LN_OFFICE_NUMBER;2 Weight settings for searching. The same phone number can be stored in more documents e.g. in person, company etc. Weights allow to find the most relevant document e.g. to find person contact rather than company contact. Documents being searched have weights assigned according to their type and document with the lowest weight is returned. After weight change you must stop UMS.Search, delete search server database and start UMS.Search again.

First item is name of user property, which defines first column of table. Individual table rows follow separated by | character and columns separated by semicolon in sequence: document type, phone number type, weight. Types of searched phone numbers:
LN_OFFICE_NUMBER, LN_MOBILE_NUMBER, LN_TELEPHONE_NUMBER, LN_HOMEFAX_NUMBER, LN_OFFICEFAX_NUMBER.
ln_nm_fName FullName Display Name of the user (default settings, can be redefined).
ln_nm_PhoneNum, ln_nm_HomeFaxNum, ln_nm_OfficeNum, ln_nm_FaxNum, ln_nm_MobileNum, ln_nm_HomeNum PhoneNumber
HomeFAXPhoneNumber
OfficePhoneNumber
OfficeFAXPhoneNumber
CellPhoneNumber
PhoneNumber_4		 Property names for phone numbers (default settings, can be redefined).
ln_dv_xxx   Default value of xxx property - used if that value doesn't exist in LN database. Use last part of any property name instead of xxx, so ln_dv_PhoneNum is default value for ln_nm_PhoneNum property.
ln_ini_file C:\Lotus\Notes\css.ini Path and name of INI file for definition LN provider connection to Lotus server.
PI binary value Encoded password for LN provider connection to Lotus server.
Following settings are related to ADO provider. If setting is missing, default values are used as described in content example.
UserProperties_ADO ADR=address| EMAIL=mail User properties defined in form NAME1=ADO_FIELD1| NAME2=ADO_FIELD2|..., which will be read in addition to default properties. In this example address and mail fields must exist in queried table.
ado_nm_fID ID Unique user identifier - this field must be filled in for all users and must be unique. This field in database should be IDENTITY (i.e. automatically increased for new records)
ado_nm_fName FullName Name of field with user name
ado_nm_PhoneNum, ado_nm_HomeNum, ado_nm_HomeFaxNum, ado_nm_OfficeNum, ado_nm_FaxNum, ado_nm_MobileNum PhoneNumber
HomeNumber
HomeFaxNumber
OfficeNumber
OfficeFaxNumber
MobileNumber		 Database field names with phone numbers
ado_dv_xxx   Default value of xxx property - used if that value doesn't exist in database. Use last part of any property name instead of xxx, so ado_dv_PhoneNum is default value for ado_nm_PhoneNum property.

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\UMS\ContactSearch\PhoneNormalizer] - settings for phone number normalization
Value Content example Description
InternationalAccessCode 00 international call preselection (it is dialed before international call), usually 00
LocalCountryCode 420 international preselection of your country
AreaCodeEscape   distance call preselection (it is dialed before long distance call), empty in CR
AreaCode 57 preselection of your area (national preselection of your city; in CR leave empty)
PBXdigits 2 number of digits for your extensions (after common part of phone number)
PBXCommonPart +4205770023 common part of phone number for your users
PBXOutsideAccessCode 9 preselection for calling outside of your PBX. This text is trimmed from caller's numbers, otherwise contact can not be found
PBXIncommingPrefix   what is given by PBX before caller's phone number during external incoming call. Usually "0" or nothing
TrunkWildcard 78?? trunk mask. List of expressions in asterisk convention, which is used for detecting whether phone number is user's extension number or trunk number which connects PBXs

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\UMS\ContactSearch\UserSet] - sets of contacts being searched. You can have more sets defined with these limitations:
Value Content example Description
<set_name> Project Zlín\contacts For EX provider: list of public folders being searched relative to AllPubFolPrefix, separated by commas
<set_name> ZL02||CN=Administrator, CN=Users,DC=ds-ums,DC=cz| CN=Users,DC=ds-ums,DC=cz| 4C41C5B6531B1A8E739C6 For LDAP provider: list of connection strings in form host|port|rootdn|searchbase|password, separated by semicolons.
host = LDAP server name,
port = TCP/IP port (if empty, default port is used),
rootdn = DN of user used for LDAP connection,
searchbase = DN where searching starts,
password = encoded password for rootdn, coding is done by encpass.exe application from Mobilchange/bin folder on the installation CD
<set_name> LN:NOTES|LNSERVER|names.nsf| For LN provider: list of connection strings in form LN:type|server|database|filter, separated by semicolons.
type = NOTES (direct document reading from database) or VIEW (reading from given view - not implemented yet),
server = Lotus server name (if empty, local PC is accessed),
database = database name (*.nsf) being searched (usually names.nsf),
filter = for NOTES type expression compilable by NSFFormulaCompile() function; if empty, filter is not applied.
<set_name> ADO:Provider=sqloledb;Data Source=ZL02;Initial Catalog=CXUser|sa| 4C41C5B6531B1A8E739C6F679F253DF8| -1|10|SELECT * FROM USERS For ADO provider: list of connection strings in form ADO:connstr|user|pswd|openopt|cost|sqlcmd, separated by ¦ character (0x00a6).
connstr = ADO connection string
user = user name for connecting to the database
pswd = encoded user's password, coding is done by encpass.exe application from Mobilchange/bin folder on the installation CD
openopt: 16=asynchronnous connection or –1=synchronnous connection (default) – optional parameter
cost = cost of this SQL query (searching returns record with lowest cost)
sqlcmd = SQL select query

When you change parameters in registry, you must restart UMS.Search service to activate new configuration. Configuration can be easily changed using DsCssCfg tool.

back to top

Level1 client

Settings are first read from HKCU registry branch and if not found, then from HKLM. When writing into registry, HKCU is always used. So some settings can exist under HKLM, other under HKCU. Following description refers to HKLM only.

[HKLM\Software\Datasys\CallChange\Client\Level1]
Value Content example Description
ServerName CXSERVER CallChange server name. If empty, program exits with error.
Path C:\CallChange\client folder where client is installed to.
LogPath D:\logfiles Gives path where log about level1 client's work is created (debug log). If this value doesn't exist or is empty, default location is used: path to local application settings in user's profile is read from registry value HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData and Datasys\Callchange\log folder is created here. Path to logfile is then
C:\Documents and Settings\<user>\Local Settings\Application Data\Datasys\Callchange\log.
Log 0 0 - turns logging off, 1 - turns logging on.
Log is written into file %LogPath%\CxClientYYMMDD.txt, where %LogPath% is LogPath value see above. Individual file is generated for every day.
Loader 1 0 - Loader folder synchronization from server is off, 1 - synchronization is on.
Value doesn't need to exist - synchronization is on by default.
AppPath C:\CallChange\client\Loader local folder for synchronization (files from server are downloaded here).
Value doesn't need to exist - default value is %Path%\Loader, where %Path% is Path value see above.
CxShare CX name under which is CXServer2.CXServer object shared by DSShareObj service on the server.
Value doesn't need to exist - default value is "CX".
CssName CXSERVER name of DsCssSrv server, which discovers identity of the user (client).
Value doesn't need to exist - default value is the same as Servername.
LineName CXSERVER:C:65 name of line for dialing calls.
ConnectionDelay 20 delay for next attempt for CX server connection [sec]
xmlrpc_server_url http://cxsrv.company.com:58080/RPC2 URL of CX server for communication through XML RPC. If not entered, DCOM connection is used (server is then specified by ServerName)
xmlrpc_css_url http://cxsrv.company.com:58081/RPC2 URL of CSS server for communication through XML RPC. If not entered, DCOM connection is used (server is then specified by CssName)

Settings in database
If DIAL_AFTER_INITIATE parameter of the line (in CC_LINES table) is set to value different than 0 or NULL, dialog asking for pick up the phone appears before call dialing and call will be dialed out after picking the handset. Dialog is showed for limited time given by DialAfterInitiateTimeout [sec] parameter from server configuration (CC_CONFIG table). If this value doesn't exist, 10 seconds is used.

When registry parameters are changed, you must restart the client to read new configuration. In common cases you need change logging settings only for debugging purposes, other settings are done by setup program. Name of line for dialing can be changed in client's menu.

back to top

Level2 clients

Settings are first read from HKCU registry branch and if not found, then from HKLM. When writing into registry, HKCU is used if user have insufficient right for writting into HKLM. So some settings can exist under HKLM, other under HKCU. Following description refers to HKLM only.

Every level2 client has its settings under [HKLM\Software\Datasys\CallChange\Client\Level2\<APP_NAME>] key.
Here is Disable value besides other, where 0 = application is active, 1 or other value = application is disabled.

Call Resolution

[HKLM\Software\Datasys\CallChange\Client\Level2\CxCROutl or CRLN]
Value Content example Description
InfoDelay 60 Maximal length of displaying info window about new call is seconds. If call was finished or connected, window disappears before elapsing this time.
Value doesn't need to exist, default value is 60 seconds.
PW 876219219219219 Encoded password for configuration protection. Do not change!
Alpha 50 Information window transparency in percent (0-100); default is 70
UseCSS 1 Should be search server used for phone numbers lookup? (0/1) [CRLN only]
LogPath D:\logfiles Gives path where log about Call Resolution's work is created (debug log). If this value doesn't exist or is empty, default location is used: path to local application settings in user's profile is read from registry value HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData and Datasys\Callchange\log folder is created here. Path to logfile is then
C:\Documents and Settings\<user>\Local Settings\Application Data\Datasys\Callchange\log.
Log 0 0 = don't log, 1 = log information about client's work. Log is written into %LogPath%\cxcroutl.YYMMDD.txt file for CRfO or %LogPath%\cxcrln.YYMMDD.txt for CRLN, where %LogPath% is registry value (see above).
RejectedShow 2 Gives number of unaccepted (rejected) calls, which open window with list of lost calls
RejectedMax 10 Max. number of displayed unaccepted (rejected) calls

Other values (WarnNOID, AutoCreate, ActivateCallsWindow, ActivateCallsWindowOut, Journal, Journal2, LostCallsB, ShowJournal, ShowJournal2, Event, AutoOpen, InternalUse, InternalSmall, Active, PersonalFirst, Personal, Public) contains 0 (zero) or 1 (one) and reflects current Call Resolution settings. You can change these settings directly in registry, but it is useless (you must restart client after changes to read new configuration). Simpler method is to change settings using menu. In common you need only change logging settings for error finding.

[HKLM\Software\Datasys\CallChange\Client\Level2\CxCROutl\lines]
List of lines monitored by client is stored here, for example
DEVRADEK:C:63 = 1 - line is monitored
DEVRADEK:C:64 = 0 - line is not monitored

Settings in database
Value Description
L2.CxCROutl.CssShareServer server name, where UMS.Search service runs
settings.user.%USER_NAME%.cradminpass centrally entered password for configuration menu protection, takes precedence over password entered in menu. Text %USER_NAME% is replaced by user's login name including domain, e.g. settings.user.DOM\user.cradminpass
PHONE.InternationalAccessCode, PHONE.LocalCountryCode, PHONE.AreaCodeEscape, PHONE.AreaCode, PHONE.PBXdigits, PHONE.PBXCommonPart, PHONE.PBXOutsideAccessCode, PHONE.PBXIncommingPrefix settings for phone number normalizer
L2.CxCRLn.ContactDbName LN database name in form server!!dbname.nsf, where new documents of given type will be created in Ekobal mode [CRLN only]
L2.CxCRLn.ContactTypeName document type for Ekobal mode [CRLN only]

When parameters in the database ar changed, you must restart the client.

"Reception" program

[HKLM\Software\Datasys\CallChange\Client\Level2\Reception]
Value Content example Description
FILELOG 0 0 = don't log 1 = log information about application's work.
LOGPATH C:\Callchange\Recepce\ path setting for log file. If not set, "log" subfolder is created under application folder. Log file has name in logYYYYMMDD.log form.
DEBUGFEATURES 0 1 value switches application into DEBUG mode, where it have more detailed monitoring features and line control.
Line name, e.g. DEVRADEK:C:63 LOCAL There is as much such values as how many lines Reception monitors. When you delete value, program stops this line monitoring. LOCAL value says that this line is "your own" (it is phone on receptionist's desk). MONITORED value says that line is monitored and you can switch call to this line.
In common it is simpler to manage configuration using application's menu.

Other settings store window placement on the desktop and it is uselles to change them. After parameters changing you need to restart application to read new configuration. In common you need only change logging settings for error finding.

Enterprise client

[HKCU\Software\Datasys\CallChange\Client\Level2\EnterpriseClient]
Value Content example Description
CXServer zl02:58080 CX server name and communication port
EnableLog 0 0 = don't log, 1 = log information about application's work.
LineForDial ZL02:C:65 line for dialing

[HKCU\Software\Datasys\CallChange\Client\EnterpriseClient\Lines]
List of lines available to the client. Key name is line name, key value 0/1 says, if line is monitored or not.

[HKCU\Software\Datasys\CallChange\Client\EnterpriseClient\Plugins]
List of installed plugins. Key name is plugin class, key value 0/1 says, if plugin is active or not. Active plugins creates their own subkeys with their configuration.

Settings in database
Value Description
APP.CX_CallBar.RC2.PARAM List of call reasons in format "1,Company call|0,Private call|2,Call to customer", where number is call reason identifier assigned to the call and follows text visible to the users
APP.CX_CallBar.CallTypeRequired 1 = force user to set call reason, 0 = call reason need not to be entered
After parameters changing you need to restart application to read new configuration. In common you should change configuration using client menu.

back to top

CXC dialer

[HKEY_CURRENT_USER\SOFTWARE\DATASYS\Callchange\Client\Level2\CXC Dial] - CXC dialer plugin debug logging settings. This key and values don't exist after installation (are created at first run), debugging is off. If you need to switch it on, created this key and values manually.
Value Content example Description
Log 1 0 = debug log is not created, 1 = debug log cxcdial.YYMMDD.txt is created in folder specified by LogPath value
LogPath C:\Callchange\ Gives path where log about CXC dialer's work is created (debug log). If this value doesn't exist or is empty, default location is used: path to local application settings in user's profile is read from registry value HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData and Datasys\Callchange\log folder is created here. Path to logfile is then
C:\Documents and Settings\<user>\Local Settings\Application Data\Datasys\Callchange\log.

back to top

UMS dialer

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\UMS\UMSDial] - UMS dialer plugin debug logging settings. This key and values don't exist after installation, debugging is off. If you need to switch it on, created this key and values manually.
Value Content example Description
Log 1 0 = debug log is not created, 1 = debug log umsdial.YYMMDD.txt is created in folder specified by LogPath value
LogPath C:\Callchange\ Gives path where log about UMS dialer's work is created (debug log). If this value doesn't exist or is empty, default location is used: path to local application settings in user's profile is read from registry value HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData and Datasys\Callchange\log folder is created here. Path to logfile is then
C:\Documents and Settings\<user>\Local Settings\Application Data\Datasys\Callchange\log.

back to top

Common CallChange settings

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\CallChange\CSTAAgent] - CSTA settings is stored here if you are using this PBX connection.
Value Content example Description
ComName com2 Serial port name, where PBX cable is connected to
CommBaudRate 00004b00 (19200) Communication speed
DbgFileName C:\CallChange\server\log\ CSTALog Filename prefix for storing CSTA debug log; filename is in form prefix_RRRR_MM_DD_HH-MM.log, where HH-MM is time of file creation. For given example full filename can be C:\CallChange\server\log\CSTALog_2005_05_05_16-17.log. Separated file is created for every day.
More settings for Siemens and MD110 PBX are described in API documentation.

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\CallChange\Monitor] - Line monitor settings.
Value Content example Description
LogFileName C:\CallChange\server\log\ linemon.log Filename for storing line monitor debug information
It is bad idea to change other parameters.

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\CallChange\Server] - CallChange server settings, information entered during setup, CallChange licenses.
Value Content example Description
LogFileName C:\CallChange\server\log\ cxserver.log Filename for storing CallChange server debug information
xmlrpc_port 58080 Port, where is CX server accessible through XML RPC
It is bad idea to change other parameters.

back to top

Common UMS settings

Settings described here are common for any UMS product.

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\UMS\ServMngr] - settings of UMS.TaskManager tasks are stored here. All settings can be edited using umsTaskCfg tool.

[HKEY_LOCAL_MACHINE\SOFTWARE\DATASYS\UMS\StatusInfo] - all messages of all UMS products and information about current and last state of individual products are stored here. Do not change anything here, use umsMonitor to view information.

back to top