CallChange novinky Table of contents User documentation Administrator documentation Documentation for developers Technical support Search on-line

CallChange installation

This document guides you through CallChange server installation. But please first read document Before installation.

Log on to Windows under the same account which will be used by CallChange services. Installation is started by autorun.exe program in the root folder of installation CD. Select CallChange product in the menu and CallChange Server [Run setup] in next dialog.

Installation is guided by setup wizard, which helps you to smooth passing whole procedure so setup will be finished successfully and CallChange will work corectly. When setup is started (by Autorun or \CallChange\Server\setup\setup.exe program), setup engine is copied to your harddrive and restart can be acquired -- in that case restart the server and start setup again. Then first wizard's dialog appears.

Setup by default configures Calchange search server to use Exchange server. If you want to switch it for Lotus Notes, you must do it manually, read here.


Setup first checks for correct Windows Scripting Host version. If it isn't found, you'll be prompted to install it.
Press "Next -->" and WSH will be updated.
Now you are promted to read license agreement and confirm you are accepting it. Without agreement setup can not continue.
Next dialog offers reading of installation directions. Directions from installation CD are displayed, the most actual version can be found on the web.
Now select CallChange components you want to install (standard, enterprise, callcenter). Information about components are described here. For every component you need separete activation key.
Enter individual activation keys (sequence of letters and numbers - do not exchange number 1 with small L!) after component selection. Key for line monitoring is entered always first. Keys can be stored on the floppy disk in file with appropriate name, then you can read them from the floppy drive A: or B:
  • cxlines.key - for line monitoring
  • cxstd.key - standard component
  • cxent.key - enterprise component
  • cxcc.key - callcenter component
When key is accepted, its parameters are displayed in dialog box.
If your key is for demonstration or internal use only, you'll be informed by info dialog (this applies to all keys).
Enter keys for other components (standard component here).
Select folder, where CallChange server will be installed into.
Select webroot folder of Internet Information Server (root path where web pages are published).
Enter domain account in form domain\account and its password under which CallChange services will be run. This account must have administrative rights (necessary for registry access).

If standard component wasn't selected, next 3 dialogs will be skipped and setup continues here.

If standard component was chosen, select e-mail client now - Outlook for Exchange server or Lotus Notes, if you are using this system.

You can not continue until Outlook is running. WARNING - Outlook must have Collaboration Data Objects component installed, otherwise setup stops. Default Outlook installation doesn't contain this component - you must explicitly select it during setup.

If Lotus Notes system was chosen, next 2 dialogs will be skipped and setup continues here.

Select public folders, where public contacts will be searched. You can select more folders by pressing Ctrl key + mouse click or nothing can be selected.

Only folder with contacts are displayed.

If you need to refresh folder list (when some folders were added), press "Back" and then "Next" in the previous dialog window.

Enter information used by CallChange for connecting to Exchange server - Exchange server name and mailbox name.
ATTENTION - account selected for CallChange services must have access to this mailbox. Therefore is good idea to be logged in under this account during installation and to have Outlook propfile configured for this mailbox.
Now CallChange database will be configured. Database is stoted in MS SQL server - if you do not have it, check "Install MSDE", this installs MS SQL Desktop Engine (desktop version of SQL).
Database parameters:
  • "SQL server name" - name of PC where SQL is installed
  • "Trusted connection" - if checked, CallChange uses his service Windows account for SQL server access. If unchecked, following two parameters will be used.
  • "Administrator name" - SQL user name, which is allowed to create databases
  • "Password" - password for this user
Only "Password" is needed for MSDE installation, other settings are unavailable.
If MSDE installation was acquired, it will be started after presing "Next" button. If restart is required at the end, press <No> button and stop CallChange installation in the next dialog. Then restart your server and run CallChange setup again. IF MSDE installation doesn't require restart, continue in CallChange setup.
For correct standard component of CallChange function must have every user filled in phone number in his properties.
  • Exchange 5.5 - Business phone
  • Exchange 2000 - Telephone number
  • Lotus Notes - Office phone
Now you need to discover common part of phone number. What does it mean?

You can see view from Outlook to global address book of MS Exchange server on the picture. All users have phone number in form "+420 225 308 xxx", where "xxx" is extension number. So common part of phone number is "+420 225 308 ".

Here is done configuration of PBX properties and contact searching:
  • "Area Code" - preselection of your area (national preselection of your city; leave empty in CR).
  • "Area Code Escape" - distance call preselection (it is dialed before long distance call), empty in CR.
  • "International Access Code" - international call preselection (it is dialed before international call), usually 00.
  • "Local Country Code" - preselection of your country
  • "PBX Common part" - common part of phone number for your users.
  • "PBX digits" - number of digits for your extensions (after common part of phone number)
  • "PBX Incoming Prefix" - what is given by PBX before caller's phone number during external incoming call. Usually "0" or nothing.
  • "PBX Outside Access Code" - preselection for calling outside of your PBX. This text is trimmed from caller's numbers, otherwise contact can not be found.
  • "Trunk wildcard" - 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.
    For Siemens PBXs with two or three digits extensions you can set 78??, or ???? here. Consult documentation for your PBX.
  • "PubFolders" - list of public folders with shared contacts relativo to PubRootCZ.
  • "PubRootCZ" - public folder root name.
Last two parameter are used only for standard component, can be empty in other cases.
Now select PBX to CallChange connection type, setup goes by different ways according this:
  • TAPI - no other settings is needed, continue here.
  • Ericsson Business Phone (XAPI) - setup continues by this dialog.
  • Siemens HiCom/HiPath 3000 (CSTA) - set CSTA configuration, continue here.
  • Siemens HiPath 4000 (CAP) - you must set configuration, continue here.
  • Ericsson MD110 - enter MD110 configuration, continue here.
If you are running CallChange and VoiceChange together, you can use CxVxDriver.
You can register at the end, what allows you to access technical support.
Now is done CallChange setup - copying of files, services registration etc.

Finally, window with list of setup errors is displayed; if all is done without problems and no error occured, windows looks like this:
Setup is completed.

back to top


Configuring search server for Lotus Notes

You must perform these steps (locally installed Lotus Notes client is required, all mentioned registry items and their locations are described here):
  1. Set search server to connect Lotus Notes under context of specific user:

    Create a new user for this purpose (if you are using also other Datasys UMS products, you can use user in which context these products run, so user account can be shared) and store his ID file to the local disk. Log on to Windows under search server's service account, configure Lotus Notes client using ID file mentioned above and close the client.
    Copy notes.ini file from Notes program folder (typically it is \Lotus\Notes) into css.ini file ibidem and add EXTMGR_ADDINS=CSSAUTOPW line to the end of file. Write filename and path to this file into ln_ini_file registry value.
    Password for ID file is written into registry using cssenc.exe program, start it with password as parameter.

  2. Set registry values ProviderType=LN, GetUserModeOnly=0. According your needs set other LN provider settings (UserProperties_LN, Costs_LN, phone number mappings).
  3. Define CX_CRC_LN search set and restart UMS.Search service.
Search server configured in this way supports Call Resolution for Notes in case that client has "Search public contacts" option active.

back to top