Table of contents

User documentation

Administrator documentation

Documentation for developers

Technical support

Search on-line

This document gives you information about Callchange function and "backstage".

Content

• Callchange server components
• UMS.TaskManager service
• Callchange clients

Callchange server components

• UMS.Search service (search server) - this component delivers two functions:
  1. discovers under which account was client started (Windows identity of the user). This is used in all Callchange editions.
  2. supports Call Resolution. It searches for contacts in public folders of Exchange server and global address book. For this purpose MAPI session to Exchange is used. Data are cached in own SQLite/ADO database, what speeds up searching process.
     These fields of contacts are searched by default: PR_BUSINESS_TELEPHONE_NUMBER, PR_BUSINESS2_TELEPHONE_NUMBER, PR_HOME_TELEPHONE_NUMBER, PR_HOME2_TELEPHONE_NUMBER, PR_MOBILE_TELEPHONE_NUMBER, PR_ISDN_NUMBER, PR_ASSISTANT_TELEPHONE_NUMBER, PR_CAR_TELEPHONE_NUMBER, PR_OTHER_TELEPHONE_NUMBER, PR_PRIMARY_TELEPHONE_NUMBER, PR_PRIMARY_FAX_NUMBER, PR_HOME_FAX_NUMBER, PR_BUSINESS_FAX_NUMBER, PR_CALLBACK_TELEPHONE_NUMBER.

     It can also search contacts stored in databases on Domino server (see how to set this, in any LDAP server (include Active Directory) and common databases accesible through ADO interface.

  Service can be configured by registry settings. Search server is available to the client through XML RPC protocol on port 58081 (XML based protocol over HTTP).

  Contact searching sequence in Outlook (depends on client configuration):
  Internal calls: global address book is searched first (if enabled), then like external calls.
  External calls: personal contacts are searched first (if set to search them first), then public contacts with global address book and finally personal contacts (if not set to search them first). So if you have contact with the same external number in both public contacts and global address book, number will be found in public contacts.
  If you are using Lotus Notes, searching works in similar way with difference that Lotus Notes doesn't have global address book (so internal calls are processed the same way as external) and Domino directory works as public contacts (if search server is configured for cooperation with Lotus Notes, you can search public contacts also in other selected Lotus databases).

• UMS.ObjectShare service - this component works like catalog of running COM object instances. It allows to find COM objects registered inside UMS.ObjectShare using unique name. Object access is solved through DCOM technology.

  Callchange server and memory storage (DSMQ) are registered in ObjectShare. DSMQ is used for operative information storing about call states, operators etc. Further memory storage usage is for asynchronous message exchanging between system components.
  For purposes of debugging your own applications is useful memory storage browser dsmqexp.exe, which can be found in \Program Files\Common Files\Datasys\ folder.

• Last component is UMS.TaskManager service (TaskManager only in following text), which is shared with Voicechange and Mobilchange systems. This service is responsible for starting (and keeping in running state) of Callchange, eventually Voicechange a Mobilchange applications.

In context of TaskManager are started UMS products family scripts in VBScript language and common EXE applications. TaskManager watches them, if they are working correctly. If script / application doesn't respond, will be restarted.

There are two types of tasks in TaskManager. One is "startup" task, which is started only once when TaskManager system starts, second is "run" task, which is kept running by TaskManager.

TaskManager can be run as a service or as a console application on the desktop. Second mode is used mainly for debugging of new scripts, because script's output is visible on the screen. TaskManager can be started on desktop from Start menu by selecting Programs -> CallChange Server -> Run UMS.TaskManager on desktop.

When TaskManager receives stop command ("Stop" button in Services administrative tool / Control panel applet or "Ctrl-C" keys when running on desktop), it sends stop request to all processes under its control and after they are finished, TaskManager stops also. This allows processes to store their data.

Information about TaskManager work are written into application log; logging level can be set in registry HKLM/SOFTWARE/Datasys/UMS/ServMngr/loglevel (DWORD type) and can be assigned these values:

0	no logging
1	log errors only and start/stop
2	default value; same as 1 and information about aplications, which stopped to work unexpectly
3	log all

This option is setting the storage path for dssrvmngr logging - HKLM/SOFTWARE/Datasys/UMS/ServMngr/logfilefolder.
Tasks in TaskManager can be created and configured using umsTaskCfg.
Callchange uses these tasks:

• CX archiver - stores data about calls into database
• CX line monitor - monitors selected phone lines
• CX message routing - routes events from line monitor to the clients
• CX server - controls other components, checks for licenses. It comunicates with clients by XML RPC protocol on port 58080.
• CX CC router - transfer calls to agents

back to top

Callchange clients

• Client level1 - when started, it reads configuration from the registry and list of level2 applications to be run. It synchronizes local Loader folder - downloads new version of level2 clients from server and deletes applications removed from server (if enabled in the registry - user must have sufficient rights to register components. Otherwise you must update clients using UMS Remote installer). Connects to CX server and connects lines which is allowed to monitor. Starts level2 clients.
  Then displays icon in system tray and visible part of work is done, on the background it offers its services to level2 clients. Usage description can be found here.
• Client level2 - delivers basic functionality to the user. Communicates with CX server through layer 1.
  Available application: Call Resolution for Outlook or Lotus Notes (searches contacts for incoming calls - public using UMS.Search, personal locally on the client using Outlook/ Notes object model), Reception (supports call switching on the reception), Enterprise client, HELPi client (support for HELPi operator).
  Under development: CallCenter (support for call center operator).
• Client level3 - these clients are used only by CallCenter client (L2CC), which sends them phone events. Graphic interface of L2CC client is displayed at the moment of start level3 application.

back to top