06 ASC DataManager e TV

ASC DataManager
Installation Manual
Version
Date
10.0
2014/11/06
This manual is valid for the following ASC products:
EVOip Server Software

MARATHON EVOLUTION XXL / MARATHON EVOLUTION / MARATHON EVOlite
Please note, that you can always find the most up-to-date technical documentation on our web site at
http://www.asctelecom.com (partner area). The ASC partner portal also provides the latest product updates.
Copyright 2004-2014 ASC telecom AG. All rights reserved.
Windows is a registered trademark of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. MySQL
is a registered trademark of ORACLE Corporation. SUSETM and openSUSETM Linux are trademarks of Novell Inc. All other
marks and names mentioned herein may be trademarks of their respective companies.
ASC telecom AG - Seibelstr. 2-4 - D-63768 Hsbach - Germany
ASC Data Manager (ADM)
General ............................................................................................................................................. 5
1.1
1.2
1.3
1.4
System Requirements .........................................................................................................................................5

Hierarchical Structure of the ASC DataManager ................................................................................................5
Sorting Lists ........................................................................................................................................................6
Searching within Lists .........................................................................................................................................7
2
3
ASC DataManager Login................................................................................................................. 9

User Administration ...................................................................................................................... 11
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
3.1.10
3.1.11
3.1.12
3.1.12.1
3.1.12.2
3.1.12.3
3.1.12.4
3.1.12.5
3.1.12.6
3.1.12.7
3.2
3.3
3.4
3.5
3.6
User Administration - Users ..............................................................................................................................11

User Administration - Users - Tab Details..........................................................................................................13
User Administration - Users - Personal Information Tab....................................................................................15
User Administration - Users - UserRights Tab ...................................................................................................17
User Administration - Users - Channels Tab......................................................................................................20
User Administration - Users - Agents Tab..........................................................................................................21
User Administration - Users - Partner Phone Numbers Tab ..............................................................................22
User Administration - Users - Own Phone Numbers Tab ..................................................................................23
User Administration - Users - Fields Tab ...........................................................................................................23
User Administration - Users - Timespan Tab .....................................................................................................25
User Administration - Users - Forbidden Passwords Tab ..................................................................................26
User Administration - Users - Bookmarks / Keywords Tab ................................................................................27
User Administration - Rights / Roles ..................................................................................................................27
Rights .................................................................................................................................................................27
Access Right - Channels....................................................................................................................................29
Access Right - Partner Phone Numbers ............................................................................................................30
Access Right - Own Phone Number ..................................................................................................................30
Access Right - Fields .........................................................................................................................................30
Access Right - Timespan ...................................................................................................................................30
Roles ..................................................................................................................................................................30
User Administration - Agents ............................................................................................................................32
User Administration - Password Rules ..............................................................................................................34
User Administration - Forbidden Passwords .....................................................................................................35
User Administration - LDAP Mapping ...............................................................................................................36
Administration Rights ........................................................................................................................................36
Configuration ................................................................................................................................. 38
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8
4.1.9
4.1.10
4.1.10.1
4.1.10.2
4.1.10.3
4.1.10.4
4.1.10.5
4.1.10.6
4.1.10.7
4.1.10.8
4.1.10.9
4.1.10.10
4.1.10.11
4.1.10.12
4.1.11
4.1.11.1
4.1.11.2
4.1.11.3
Configuration - System ......................................................................................................................................39

Start/Stop and Activate/Deactivate Processes...................................................................................................42
Generate Certificate Request.............................................................................................................................43
Import Certificate................................................................................................................................................44
Configuration Alarm Manager ............................................................................................................................45
Configuration API Server ...................................................................................................................................54
Configuration Archive Manager..........................................................................................................................64
Configuration Database Inserter ........................................................................................................................69
Configuration Delete Manager ...........................................................................................................................71
Configuration Evolution Portal............................................................................................................................74
Configuration EVOip ..........................................................................................................................................76
Sublevel Expert Mode ........................................................................................................................................77
Sublevel Devices................................................................................................................................................77
Sublevel Sniffer ..................................................................................................................................................80
Sublevel SIP.......................................................................................................................................................86
Sublevel SCCP ..................................................................................................................................................87
Sublevel SIFA ....................................................................................................................................................88
Sublevel IGMP ...................................................................................................................................................88
Sublevel Receiver ..............................................................................................................................................89
Sublevel Calldata ...............................................................................................................................................90
Sublevel Signaling..............................................................................................................................................92
Sublevel MiXML .................................................................................................................................................93
Sublevel Loglevel ...............................................................................................................................................95
Configuration EVOip active ................................................................................................................................96
Sublevel Loglevel ...............................................................................................................................................97
Sublevel Registrar 1 and 2.................................................................................................................................98
Sublevel Multiregistrar........................................................................................................................................99
Installation Manual EVOip / EVOLUTION -10.0 Rev. 11
1/316
4.1.11.4
4.1.11.5
4.1.11.6
4.1.11.7
4.1.11.8
4.1.12
4.1.12.1
4.1.12.2
4.1.12.3
4.1.12.4
4.1.13
4.1.13.1
4.1.13.2
4.1.14
4.1.14.1
4.1.14.2
4.1.14.3
4.1.14.4
4.1.14.5
4.1.14.6
4.1.14.7
4.1.14.8
4.1.15
4.1.15.1
4.1.15.2
4.1.15.3
4.1.15.4
4.1.15.5
4.1.15.6
4.1.16
4.1.17
4.1.18
4.1.18.1
4.1.18.2
4.1.18.3
4.1.18.4
4.1.18.5
4.1.18.6
4.1.18.7
4.1.18.8
4.1.18.9
4.1.19
4.1.19.1
4.1.19.2
4.1.19.3
4.1.20
4.1.21
4.2
4.3
4.4
4.5
4.6
4.6.1
4.6.1.1
4.6.1.2
4.6.1.3
4.6.1.4
4.6.1.5
4.6.1.6
4.6.1.7
Sublevel Recorder............................................................................................................................................101
Sublevel Replay (Last Call Repeat) .................................................................................................................111
Sublevel KeepAlive ..........................................................................................................................................113
Sublevel Internal ..............................................................................................................................................113
Sublevel Common............................................................................................................................................114
Configuration License Server...........................................................................................................................114
Central License Server.....................................................................................................................................115
CLS Client Configuration..................................................................................................................................121
Dynamic Enterprise Licensing (Failover configuration)....................................................................................122
Sublevel WarnLevel .........................................................................................................................................125
Configuration Local Replay Service .................................................................................................................126
Sublevel Loglevel .............................................................................................................................................126
Sublevel LCR ...................................................................................................................................................127
Configuration Recording Manager ...................................................................................................................129
Sublevel Specific Loglevels..............................................................................................................................131
Sublevel Bus Configuration..............................................................................................................................135
Sublevel Options ..............................................................................................................................................138
Sublevel Voip ...................................................................................................................................................139
Sublevel ISDN Call Options .............................................................................................................................140
Sublevel Ticket ID ............................................................................................................................................141
Sublevel Hardware Configuration ....................................................................................................................142
Configuration Selective Data Distribution Manager (SDDM) ...........................................................................146
Log Level..........................................................................................................................................................146
Central Server ..................................................................................................................................................148
File Server........................................................................................................................................................149
Transfer............................................................................................................................................................150
Call Reference Extractor ..................................................................................................................................150
Secure Transfer ...............................................................................................................................................152
Configuration Window Manager.......................................................................................................................153
System - Recording Interface Adapter (RIA)....................................................................................................154
Configuration Avaya Interface..........................................................................................................................156
Sublevel Operation Mode.................................................................................................................................157
Sublevel Communication Manager ..................................................................................................................158
Sublevel AES Server........................................................................................................................................159
Sublevel Softphones ........................................................................................................................................160
Sublevel Recorder............................................................................................................................................161
Sublevel Alarm Management ...........................................................................................................................161
Sublevel RTP ...................................................................................................................................................162
Sublevel Audio .................................................................................................................................................162
VCAM (Visual Central Alarm Management).....................................................................................................164
Sublevel Identification ......................................................................................................................................165
Sublevel Alarm Connections ............................................................................................................................166
Sublevel Alarm Notification ..............................................................................................................................167
Recording Manager..........................................................................................................................................168
System - Errors ................................................................................................................................................179
Configuration - Alarm Notifications ..................................................................................................................179
Configuration - Channels ................................................................................................................................183
Configuration - EVOip Channels .....................................................................................................................197
Configuration - EVOip active Channels ...........................................................................................................202
Configuration - RIA (Recording Interface Adapter) .........................................................................................207
General Configuration ......................................................................................................................................208
Configuration of a RIA Instance .......................................................................................................................208
Configuration of VirtualRIAactiveChannel........................................................................................................209
Configuration of a RIA Statemachine...............................................................................................................211
Configuration of a RIA Serial Connection ........................................................................................................212
Configuration of a RIA TCP Connection ..........................................................................................................213
Configuration of a RIA TCP-Listener Connection ............................................................................................214
Configuration of a RIA Log Behaviour..............................................................................................................215
2/316
4.6.2
4.6.3
4.6.4
4.6.5
4.6.5.1
4.6.6
4.6.7
4.6.8
4.6.9
4.7
4.8
4.8.1
4.8.2
4.8.3
4.9
4.9.1
4.9.2
4.9.3
4.9.4
4.9.5
4.9.6
4.9.7
4.9.8
4.9.8.1
4.9.8.2
4.9.8.3
4.9.8.4
4.9.8.5
4.9.8.6
4.9.8.7
4.9.9
4.9.10
4.10
4.11
4.12
Configuration of RIApassive for Siemens HiPath Trading IP ...........................................................................215

Configuration of RIApassive for Siemens HiPath Trading ...............................................................................216
Configuration of RIAtagger for IPC ..................................................................................................................217
Configuration of RIApassive for DeTeWe OpenCom.......................................................................................220
Checking the Connection .................................................................................................................................222
Configuration of RIAtagger or RIApassive for Mitel SX2000/ICP2300 SMDR External...................................222
Configuration of RIApassive for Avaya INDeX.................................................................................................226
Configuration of RIApassive for BT ITSLink.....................................................................................................228
Configuration of RIAtagger for BT ITSLink.......................................................................................................230
Configuration - Auto Tagging ..........................................................................................................................232
Configuration - Channel guard ........................................................................................................................235
Configuration Channel guard ...........................................................................................................................235
Configuration Scheduling .................................................................................................................................236
Configuration Activation ...................................................................................................................................237
Configuration - Recording Planner ..................................................................................................................238
How the Recording Planner works...................................................................................................................238
Buttons of the Toolbar......................................................................................................................................241
Content of the Master Window Table...............................................................................................................241
Creating New Recording Profiles .....................................................................................................................242
Deleting Recording Profiles..............................................................................................................................242
Activating / Deactivating Profiles......................................................................................................................243
Assigning a Higher / Lower Priority ..................................................................................................................243
Creating New Recording Profiles .....................................................................................................................243
Configuration - Recording Planner - CTI Parameter ........................................................................................244
Configuration - Recording Planner - IP Addresses ..........................................................................................246
Configuration - Recording Planner - Phone Number List.................................................................................249
Configuration - Recording Planner - External Control Trigger .........................................................................251
Configuration - Recording Planner - Additional Criteria ...................................................................................252
Configuration - Recording Planner - Schedule Parameter...............................................................................254
Configuration - Recording Planner - Activation ................................................................................................257
Saving a New Recording Profile ......................................................................................................................260
Saving an Already Existing Recording Profile..................................................................................................261
Configuration - Recording Decision Preview ...................................................................................................261
Screen Recording ...........................................................................................................................................262
Configuration - Recorder Information ..............................................................................................................264
Archive Client............................................................................................................................... 266
5.1
5.2
Job Configuration ............................................................................................................................................266

Media Pool ......................................................................................................................................................267
SDDM Client ................................................................................................................................. 269
6.1
Overview .........................................................................................................................................................269
7
8
Backup.......................................................................................................................................... 271
Registry ........................................................................................................................................ 273
8.1
8.1.1
8.1.1.1
8.1.1.2
8.1.1.3
8.1.1.4
8.1.1.5
8.1.1.6
8.1.2
8.1.3
8.1.4
8.1.5
8.1.6
8.1.7
8.1.8
8.1.9
8.1.10
8.1.11
Registry - Phone Appliance - Config ...............................................................................................................276

Configuration of Call Statistics .........................................................................................................................276
Configuration of Chart Channel Total Usage ...................................................................................................277
Configuration of Global ....................................................................................................................................280
Configuration of the INSTANTplay...................................................................................................................280
Configuration of the Visual Central Alarm Management (VCAM) ....................................................................282
Registry - VOIP XML SERVICE .......................................................................................................................284
Registry - VOIP XML SERVICE - Config .........................................................................................................285
Registry - VOIP XML SERVICE - Recorders ...................................................................................................288
Registry - VOIP XML SERVICE - Languages ..................................................................................................288
Registry - UCVOIP XML SERVICE..................................................................................................................290
Registry - UCVOIP XML SERVICE - Config ....................................................................................................291
Registry - UCVOIP XML SERVICE - Recorders ..............................................................................................293
Registry - UCVOIP XML SERVICE - Languages.............................................................................................294
Registry - MARATHON XML SERVER ............................................................................................................295
Registry - MARATHON XML SERVER - Language.........................................................................................296
Registry - MARATHON XML SERVER - Config ..............................................................................................297
Registry - MARATHON XML SERVER - Users ...............................................................................................300
3/316
Information ................................................................................................................................... 303
9.1
9.2
9.2.1
9.3
9.4
9.5
Versions ..........................................................................................................................................................303
Update .............................................................................................................................................................304
Configuration of the FTP update ......................................................................................................................304
Version History ................................................................................................................................................304
License Overview ............................................................................................................................................305
Downloads ......................................................................................................................................................306
10
Troubleshooting .......................................................................................................................... 307
10.1
Alarm Messages .............................................................................................................................................307
4/316

General
General
HINT
Please change the advanced settings of the ASC DataManager only if
you are working closely together with the ASC support team or if your
knowledge about these settings is sufficient.
1.1
System Requirements
ASC DataManager runs with:
Microsoft Internet Explorer V 10.0 or V 11.0

Firefox V 32.0
1.2
Hierarchical Structure of the ASC DataManager
Fig. 1 - ASC DataManager window

After successful login the ASC DataManager initial screen is displayed. It is divided into two main
parts: a hierarchical structure with the configurable components of the MARATHON
EVOLUTION system on the left and a detail window on the right.
The list on the left-hand side initially shows only the first level of the components available in the
MARATHON EVOLUTION system. The type and number of components displayed depends on
the access rights of the login user. For more information on user rights see chapter '3.1.12 - User
Administration - Rights / Roles'. By clicking on the + resp. - symbols the tree is expanded /
collapsed and the details of the component become visible / invisible.
5/316

General
Fig. 2 - Hierarchical Structure

Depending on your ASC licences the structure tree could look different from the depicted
example.
The detail window on the right-hand side initially shows the ASC logo. If one component of the
MARATHON EVOLUTION system is selected from the list on the left-hand side, the settings for
this component will be displayed in the detail window and can be altered there.
1.3
Sorting Lists
If a long list must be searched for entries use the sorting function to provide a better overview.
Select a column to sort the entries of this column alphabetically. If, like in the following example,
the Version History list should be sorted according to the names of the modules click on the
column heading ModuleName and the list will be sorted alphabetically (see figure). If you click
the heading once, a triangle upward (arrow in the figure) appears, indicating that the column has
been sorted in alphabetical order from A to Z. If you click the heading once again, a triangle down
appears, indicating that the entries of the column have been sorted in reverse order from Z to A .
The list in the following example can be sorted according to the names of the modules (column
6/316

General
ModuleName), to the number of the version (column CompleteVersionNumber), to the date of

the installation (column InstallationDate) or to the comments (column Comment).
Fig. 3 - Sorting Lists

1.4
Searching within Lists
Search
word
Search
criteria
Search
Restart
search
Back to the
previous
menu
If you have to search within a long list, use the search button. Enter the word you want to search
in the current list into the textbox Search:. To select one of the following search criteria open the
dropdown list Compare:
Part of field content
Search word is somewhere in the text field
Begin of field content Search word is at the beginning of the text field
Exact Match
Search word must match exactly the content of

the text field
Regular Expression
Extended search functions which allows the

search for single characters or character
sequences (like [a,b,c,d]). Also the use of
wildcards is allowed (like [acc*] searching for all
entries with acc included).
7/316

General
To perform a case-sensitive search, leave the checkbox ignore case unchecked. To ignore
uppercase and lowercase make sure that the checkbox is selected.
Use the Search buttons to start a search. The button Search always searches for the next time
the searched word appears in the table, starting at the current position. To continue searching for
another entry including this word, click the Search button once again. The button Restart search
starts at the beginning of the table and will therefore only find the word when it first appears in the
table. To find other entries of the table including this word, click the Search button.
8/316

ASC DataManager Login

The browser-based application ASC DataManager is used for configuration and administration of
the MARATHON EVOLUTION system. The ASC DataManager is part of every MARATHON
EVOLUTION, but it can also be started on a client-PC.
You can start the ASC DataManager with the IP-address on your browser e.g.
https://192.168.1.100/ADM. By starting on the MARATHON EVOLUTION directly choose from
the Portal the application ASC DataManager on the right side.
After starting the ASC DataManager the following login screen appears:
Fig. 4 - Login screen

In order to administer the MARATHON EVOLUTION system the login user must have at least
one of the administration rights ConfigureUser, ConfigureSystem or ArchiveCreate. For more
detailed information on this topic see section 3.1.12 - User Administration - Rights / Roles.
To log into the application please proceed as follows:
To select the language click on the appropriate flag

Type in your user name and password
Click the following button to proceed with the login
9/316

Combi user login

The ASC DataManager provides the possibility to assign a combi user to an ASC DataManager
user. This function is very useful for safety reasons.
Fig. 5 - Combi user login

Those users assigned a combi user can only log into the ASC DataManager together with the
combi user. If the name and password of a combi user is required, click the following button.
Fig. 6 - Combi user button

Single Sign On
If your system is configured to use SSO (single sign on), just click on the SSO button to log in
with your Windows username.
Fig. 7 - Single Sign On button
10/316

User Administration
User Administration
The menu item User Administration in the hierarchical structure

provides the following six sub items:
Users - Creation and administration of users
Access Rights - Creation and administration of dedicated
access rights which can be assigned to single users
Agents - Creation and administration of agents
Password rules - Administration of the rules used for
passwords
Forbidden Passwords - Creation and administration of the list
of passwords which must not be used in the system
LDAP Mapping - LDAP Mapping is an automatic update
process for users, agents and access rights.
3.1
User Administration - Users

Click on the first sub item Users, and all users which are currently defined in the system are listed
in the detail window. This screen additionally provides the possibility to change user rights, to
create new users or to delete existing users.
New
Search
Print
Import to Import all Export Export

selected
selected all
Delete
Reload
Logout
Fig. 8 - User Administration - Users
11/316

User Administration
If there are more than 1000 items to display, a search mask is shown. The search is composed
of an object box where you can choose the field to search for (e.g. Username) and a box where
you can fill in search-strings. A wildcard search with the * - operator is possible (e.g. Schmi*). A
search with only * is not possible. After a search (with results) a filter-button will be displayed like
in INSPIRATIONpro where you can switch to the search mask or the standard view. You can set
the maximum numbers to display in the registry.
Fig. 9 - Registry - ASC DataManager - Configuration
12/316

User Administration
In the middle of the detail window all existing users are displayed with their user names and a
description (in the example above: 2 users). Above this list there is a toolbar providing the
following buttons for user administration configuration:
New:
Creates a new user
Search:
Searches for a user in the list (searches for login

name or description)
Print:
Prints the current user list (prints the login names

and user descriptions - not available if ADM is
executed on the recorder itself)
Show locked /
unlocked users
Shows the locked or the unlocked users
Import to selected:
Imports the user configuration to the selected user
Import all:
Imports the whole user configuration
Export selected:
Exports the selected user configuration
Export all:
Exports the whole user configuration
Delete:
Deletes the selected user
Reload:
Refreshes the data from the database (retrieves

current data)
Logout
Logs out the current user and returns to the login

window
HINT
Please note that the maximum size of the import file user.dat must not
exceed 2 MB.
The lower part of the detail window displays ten tabs, used to configure the dedicated rights and
more detailed information for each user.
If the login user has Superuser rights, only three tabs will be displayed:
3.1.1
User Administration - Users - Tab Details

The Details tab includes the parameters Username and Description as well as the parameter
Password. It is possible to assign a password to each single login user. To avoid spelling
mistakes, enter the password a second time into the Confirm Password textbox.
The LDAP-DN field shows the LDAP-DN of the user.
You can manually enter a LDAP-DN here or a windows user name (or parts of it) known to the
connected LDAP service (shown as dots).
13/316

User Administration
To build a LDAP-DN you

(DOMAINNAME/username).
have
to
enter
the
domainname
and
the
username
By pressing "Check LDAP" the entered user name is checked with LDAP and the LDAP-DN as
well as other user properties are automatically filled from the LDAP information.
If the "Login via LDAP" check box is selected the password of a user is checked through LDAP
on each login.
If the password is verified via LDAP, the password cannot be changed via the ASC software and
the ASC password rules do not apply.
The Combi User parameters provide the possibility to link the access of the currently defined
user to another, already configured user, additionally requiring the username and password of
this partner for login. To activate this function, check the Combi User checkbox and select a user
from the Username list below, that lists all currently configured users. You can choose up to
three combi users. One of them has to log in with the user. So if the first one is for example on
holiday, the second one could log in as the combi user.
Example: User 3 has been defined as Combi User for User 4.
If User '4' now wants to log into the MARATHON EVOLUTION (at the portal or a remote client
like the POWERplay) he/she will have to enter his/her personal username and password. But for
successful login the system will additionally require the username and password of the Combi
User (User 3) and only after this has been entered correctly, User 4 will get access to the
MARATHON EVOLUTION. User 3, on the other hand, will be able to log in on his own, if no
Combi User has been linked to him / her in the Details tab of the User Administration.
Fig. 10 - Details Tab

In the lower right area of the detail window the list of currently configured access rights for the
user is displayed and can be edited (added, deleted). To add another access right, mark it in the
14/316

User Administration
list box below and insert it by clicking the Add button. Delete an access right by marking it and
then clicking the Delete button.
Fig. 11 - Access Rights
In order to save the modified user configuration (i. e. sending the changes to
the database) click the Save button. If the changes should not be saved, the
original configuration can be retrieved by clicking the Reset button.
In order to save the user configuration for other users with the same settings
enter a new user name click the Save as button. Dont forget to change the
description and the password.
3.1.2
User Administration - Users - Personal Information Tab
Fig. 12 - User Administration - Personal Information Tab

Personal Information
Under Personal Information, you can change and see the agent data.
15/316

User Administration
Is Agent
Checkbox to see whether the user is an agent or not
First Name (mandatory field)
First name of the agent
Last Name (mandatory field)
Last name of the agent
eMailAddress
eMail address of the agent
Agent ID (PBX)
ID of the agent in the PBX
IP Address
IP address of the agent PC.
PC Name
PC name of the agent PC. This is a mandatory field if screen monitoring with fixed seating is
used.
PC Login
Login name used by the agent to log in at the network (Novell or Windows). This is a mandatory
field if free seating without CTI or free seating with CTI and screen recording are required.
Own Phone Number
Phone number of the agent
16/316

User Administration
3.1.3
User Administration - Users - UserRights Tab
Fig. 13 - User Rights Tab

The UserRights tab is used to define user rights concerning Search&Replay Client, Archive
Client and Configuration Client. Settings can be made as follows:
Superuser:
Mark this checkbox to grant the currently selected user Superuser rights. As Superuser rights
allow access to the entire system, all tabs except the Details and UserRights tabs will disappear
with this setting.
Search rights:
This group allows to grant two different search rights.
Firstly the user can be granted the DBSearch right which allows him / her to search and replay
calls with the POWERplay or WEBplay (the user must have access rights for one, multiple or all
channels).
Secondly the user can be granted the ArchiveSearch right which allows him / her to search calls
with the POWERplay on archive media (the user must have access rights for one, multiple or all
channels recorded on the archive medium).
17/316

User Administration
The Search rights only make sense for a user who has at least one of the Login rights (last
parameter of this screen) described below.
Monitor rights:
This group allows to configure two rights that provide access to an additional functionality in the
POWERplay.
The ChannelMonitoring right allows the user live monitoring of the channels via the POWERplay.
Provided that the user has the according rights, up to eight channels can be live monitored at the
same time.
The AlarmMonitoring right allows to monitor the alarm management of the MARATHON
EVOLUTION system via the POWERplay. The alarm management includes a Warning Light
which indicates the status of the MARATHON EVOLUTION system:
Warning Light grey: MARATHON EVOLUTION system OK
Warning Light red: An error has occurred in the MARATHON EVOLUTION system
Warning Light red blinking:New errors have occurred in the MARATHON EVOLUTION system
Click the Warning Light to access the current list of the Alarm Manager messages. This list
includes Errors, Warnings and Infos on the MARATHON EVOLUTION system which is
transferred from all MARATHON EVOLUTION modules to the Alarm Management.
Create rights:
This ArchiveCreate right allows to define and administer archive jobs in the Archive Client area of
the configuration program ASC DataManager which are then performed by the Archive Manager
on the MARATHON EVOLUTION system.
This right is currently used to activate and deactivate Bulk Archiving.
Configure rights:
This group allows to assign two configuration rights to the user.
The ConfigureUser right allows the user to access the area User Administration of the ASC
DataManager and to create and administer users. It allows the creation of Access Rights (which
then can be assigned to different users), of Agents and Forbidden Passwords for single users or
for all users.
18/316

User Administration
The ConfigureSystem right allows access to the area Configuration of the ASC DataManager
where the complete MARATHON EVOLUTION system can be configured. It includes the
settings for the complete MARATHON EVOLUTION.
The Shutdown recorder right allows the user to shutdown or restart the MARATHON
EVOLUTION recorder via the Portal.
This right also allows the user to see and use the button Start/Stop processes in the section
Configuration -> System of the ASC DataManager (for further information please refer to chapter
4.1.1 - Start/Stop and Activate/Deactivate Processes).
Login rights:
This group allows to define two basic access rights for each MARATHON EVOLUTION user.
The PortalLogin right allows the user to work directly at the MARATHON EVOLUTION PC by
defining a username and password for login at the portal. Depending on the rights assigned, the
user will also be able to start further applications (like e. g. POWERplay, WEBplay or ASC
DataManager).
The ClientLogin right allows the user to log in via an MARATHON EVOLUTION Client program
(like e.g. POWERplay, WEBplay, ASC DataManager and later maybe customer-specific
applications) over the network and access the MARATHON EVOLUTION system via LAN.
Audit trail rights:

This group is responsible for the audit trail log entries for the selected user.
The Search selection logs all search activities of the selected user.
The Play selection logs all replay activities of the selected user.
The Monitoring selection logs all monitoring activities of the selected user.
The Configure selection logs all configuration activities of the selected user.
19/316

User Administration
ESS rights:
This group is responsible for the ESS (External Start/Stop) rights for the selected user.
The Start/Stop selection allows the selected user to start/stop recordings on demand.
The Keep/Delete selection allows the selected user to keep/delete a call on demand.
The Mute/Unmute selection allows the selected user to mute/unmute during a call.
The Can tag selection allows the selected user to tag a call.
CCB rights:
This group is responsible for the CCB rights of the selected user.
The Can create selection allows the selected user to create call collection boxes in the
POWERplay.
Password rights:
This group manages the right whether a password expires or not. You can also disable the
password rules for the selected user.
3.1.4
User Administration - Users - Channels Tab

The Channels tab is used to define the access rights to single channels on the MARATHON
EVOLUTION system for each user individually. This list determines the channels of the
20/316

User Administration
MARATHON EVOLUTION recorder the current user is allowed to access for search, replay and
online monitoring.
Channel
Access
List
Selection
of
Recorders
Selection of
Channels
Fig. 14 - Channels Tab

The check box All recorders grants the user access to all channels of all recorders in the
MARATHON EVOLUTION system.
If All recorders is not desired, deactivate the checkbox and then select specific channels allowed
for the current user. To create such a list, select a recorder from the list box on the left-hand side
and the corresponding channels from the list box on the right-hand side. Click the Add button to
add the selected channel to the channel list of the current user. The first list element <All
channels> of the channel selection list box allows to add all channels of one MARATHON
EVOLUTION recorder to the channel list of the current user.
To delete the access to a certain channel for the user, mark the channel in the access list and
delete it by clicking the Delete button.
3.1.5
User Administration - Users - Agents Tab

The Agents tab is used to define the access rights for different agents of the MARATHON
EVOLUTION system. This list determines the agents of the MARATHON EVOLUTION recorder
the current user is allowed to access for search, replay and online monitoring.
Agent
Access List
Selection of
Agent ID
Selection of
Agent Name
Fig. 15 - Agents Tab

This tab works similar to the Channels tab: The check box All agents grants the user access to all
calls of Agents of all recorders in the MARATHON EVOLUTION system.
21/316

User Administration
If All agents is not desired de-activate the checkbox and then create a list of agents that may be
accessed by the current user. To create this list, select an AgentID from the list box on the left or
an AgentName from the list box on the right. Click the Add button to add the agent to the agent
list of the current user.
To delete the access to a certain agent for the user mark the agent in the access list and delete
the entry from the list by clicking the Delete button.
3.1.6
User Administration - Users - Partner Phone Numbers Tab

The Partner Phone Numbers tab is used to define access rights for calls with certain Partner
Phone Numbers on the MARATHON EVOLUTION system. This table lists partner telephone
numbers the user should be restricted to.
HINT
Please note the difference between the following two items:
Partner Phone Number

Stands for external party number.
Own Phone Number

Stands for internal party number.
Type in the new

partner phone number
Fig. 16 - Partner Phone Numbers Tab

The check box All partner phone numbers allows the user access to all calls on the MARATHON
EVOLUTION system with partner phone numbers included in the below column Partner Phone
Numbers.
To add a partner phone number to the Partner Phone Numbers list, click the Add button. A new
empty field will be created where you can enter the suitable partner phone number.
To delete an entry from the list, mark the entry and delete it from the list by clicking the Delete
button.
When the user searches for calls, only those calls with a partner phone number listed in this
Partner Phone Numbers list will be shown in the search result list.
22/316

User Administration
If you neither activate the control box All partner phone numbers nor enter a partner phone
number in the Partner Phone Numbers list the criterion Partner Phone Number will not be taken
into account when searching for calls.
3.1.7
User Administration - Users - Own Phone Numbers Tab

The Own Phone Numbers tab is used to define the access rights to calls with certain Own Phone
Numbers on a MARATHON EVOLUTION system. This table lists own phone numbers the
access of the user should be restricted to. The Own Phone Numbers used must not necessarily
be the complete telephone numbers but can only be the own phone numbers which clearly
identify the telephones recorded in the current LAN.
Administration of this list and adding list entries is equivalent to the previous tab Partner Phone
Numbers.
Type in the new

own phone number
Fig. 17 - Own Phone Numbers Tab

The check box All own phone numbers allows the user access to all calls on the MARATHON
EVOLUTION system with numbers included in the below column Own phone numbers.
To add an own phone number to the Own Phone Numbers list, click the Add'button. A new empty
field will be created where you can enter the suitable own phone number.
To delete an entry of the list, mark the entry and delete it from the list by clicking the Delete
button.
When the user searches for calls only those calls with an own phone number listed in this Own
Phone Number list will be shown in the search result list.
If you neither activate the control box All own phone numbers nor enter any own phone number
in the Own Phone Numbers list the criterion own phone numbers will not be taken into account
when searching for calls.
3.1.8
User Administration - Users - Fields Tab

The Fields tab is used to define access rights for users to calls in relation to the Tagging Fields
Text1 to Text20 (max 128 characters) as well as Comment and the 10 number fields Long1 to
Long10 which can hold a value from -2147483648 to 2147483647. These fields can specify the
23/316

User Administration
search and replay of calls more precisely and hold additional information for the call. If a user has
also write access (Write Access) to one or more fields, the call can be tagged later, meaning that
the user can later add information to the fields or change existing entries.
In the left-hand part of the tab, called Access right to, the different fields which are assigned to
the user are displayed, added or deleted. In the right-hand part of the tab, called Field parameter,
the limiting parameters for the currently marked field are displayed, added and deleted.
Fig. 18 - Fields Tab

To provide access to a new field for a user, select the field type (Text1 .. Text20, Comment,
Long1 .. Long10) from the drop-down list Field in the left-hand part of the tab. If the user should
merely be granted read access, just click the Add field button. To grant read and write access,
check the control box Write Access before clicking the Add field button.
Fig. 19 - Fields Tab - Adding New Fields
24/316

User Administration
To change the field access right from read only to read/write or vice versa, select the field from
the drop-down list and activate or deactivate the control box. After this, the field access right can
be updated by clicking the Change button.
To delete a field right from the list, select the respective entry and click the Delete button.
The Field parameter part on the right-hand side of the tab provides the possibility to define
limiting parameters for the currently marked field. If a field is not restricted by additional (limiting)
parameters, the user can access this field for all calls found in a search. If additional parameters
have been defined for the user, only those calls are searched and found with the field content
matching one of the given parameters.
Example: If a user is granted read access to TEXT1 and the limiting parameters are set as
strings Company Smith and internal, only calls which meet the previously selected search criteria
will be found. Additionally, only those calls with either Company Smith or internal as content of
TEXT1 are displayed in the Search Result List.
The type and content of the parameters that can be added depend on the type of the field. With
Field Type TEXT1 to TEXT20 and Field Type Comment, a field can hold a string of up to 128
characters. Allowed are characters (capital / small), numbers, space, comma, full stop etc. For
Field Type Long1 to Long10 only regular numbers (from -2147483648 to 2147483647) can be
entered.
All parameters already added to a field are displayed in the right-hand part of the tab when the
field is marked in the left window. To add a new parameter to a field, click the Add button to open
a new text field where the parameter must be entered. To add more than one parameter, repeat
the procedure. Clicking the Add to field' button assigns the parameters to the previously selected
field.
Use the Delete button to delete the current line from the criteria list. The Clear button deletes all
entries from the list. To change the existing selection of parameters for a field, select the field in
the left part of the tab, then change the entries in the right part of the tab as desired and update
the parameter list by clicking the Add to field button.
3.1.9
User Administration - Users - Timespan Tab

The Timespan tab is used to define the access rights to calls according to the recording time.
Only those calls will be searched that have been recorded during the selected time span. The
access may be restricted to calls recorded during the last minutes, the last ... hours or the last
... days. Additionally, a time frame (Between .. And ..) can be set. To grant unlimited access
select the option button unlimited access. If the last option button (no access) is selected, the
user will not have any access to any call. If this setting has been selected, a warning message
25/316

User Administration
stating that this user will not be able to search for any call will be displayed before the setting is
saved to the system.
Fig. 20 - Timespan Tab

In the example shown above the user has access to all calls recorded within the last 10 days.
3.1.10
User Administration - Users - Forbidden Passwords Tab

The Forbidden Passwords tab is used to define words which - for security reasons - the current
user is not allowed to use as passwords (e.g. first names of members of the family).
Fig. 21 - Forbidden Passwords Tab

Clicking the Add Button adds entries to the list. To delete entries from the list, click the Delete
button.
HINT
A second Forbidden Password list which is valid for all MARATHON
EVOLUTION users is available in the MARATHON EVOLUTION
system. It is located in the ASC DataManager as sub item under User
Administration.
26/316

User Administration
3.1.11
User Administration - Users - Bookmarks / Keywords Tab

The Bookmarks/Keywords tab is used to configure rights for the bookmarks and keywords during
the replay of calls in INSPIRATIONpro.
The following settings are possible:
Setting
Right
Bookmarks
No access
Keywords
Mute
Description
Read only access
The user is able to see the bookmarks in a

call
Read/write access
The user is able to create bookmarks
No access
Read only access
The user is able to see the keywords of the

call
Can mute - Yes/No
The user is able to mute parts of the call
3.1.12
User Administration - Rights / Roles
3.1.12.1
Rights
This part of the hierarchical structure is used for administration of standard access rights for the
MARATHON EVOLUTION system. These standard access rights make it easier to assign user
rights because rights which are identically assigned for multiple users can be administered at a
central point.
Example: In a call center department there are 10 agents who are not only allowed to search for
their own calls (tagged with their own AgentID) but also for all calls of all other agents of this
department. To achieve this without the central Access Rights feature, the administrator would
have to select every user individually and insert the AgentIDs of all other 9 users. If one user was
added or deleted, the access rights for all other users would have to be changed accordingly.
Using the Access Rights feature simplifies this configuration task. The administrator merely has
to create one Access Right which allows access to all calls with one of the AgentIDs of the 10
agents. This central Access Right can now be assigned to each agent and adding or deleting
agents has to be executed only in this single Access Right.
27/316

User Administration
The first step when configuring a new Access Right is to determine the type of Access Right
required. The following types of Access Rights are available: Agents, Channels, Partner Phone
Number, Own Phone Number, Fields and Timespan.
After you have selected the type of Access Right by selecting the appropriate option button click
Next to create the actual right.
New
Search
Print
Import to Import
selected
Export Export
selected all
Delete
Reload
Logout
Fig. 22 - Access Rights

Above this list there is a toolbar providindatabaseg the following buttons for user administration
configuration:
New:
Creates an access right
Search:
Searches for an access right in the list
Print:
Prints the current access right list (prints the login

names and user descriptions - not available if
ADM is executed on the recorder itself)
Import to selected:
Imports the access right to the selected access

right
Import all:
Imports the whole access rights
Export selected:
Exports the selected access right
Export all:
Exports the whole access rights
Delete:
Deletes the selected access right
28/316

User Administration
Reload:

current data)
Exit /
Closes the ASC DataManager and returns to the

Portal
window
Logout
The next page looks similar for all types. The Access Right Agents is presented as an example in
the following:
Fig. 23 - Access Rights: Agents

First assign a Name and a Description to every Access Right. By default, the Access Right is
allowed for all agents, i.e. in this example, the checkbox Access right to: All agents is selected. If
you intend to restrict access to a limited user group, deactivate this option and add the suitable
AgentIDs or AgentNames to the list. To achieve this, open the drop-down menu on the left or
right using the button and add the suitable agent to the agent list by clicking the Add button. To
delete an agent from the list, mark the respective entry and delete it from the list by clicking the
Delete button.
The remaining types of Access Rights are administered accordingly.
3.1.12.2
Access Right - Channels

This access right allows the user the access to the defined channels. Activating the checkbox All
recorders allows full access of all channels of all recorders.
HINT
This access right is only for the POWERplay and WEBplay. Dont use
this right for users of the INSPIRATIONpro because the restriction of
the access is based on agents.
29/316

User Administration
3.1.12.3
Access Right - Partner Phone Numbers

This access right allows the user access to the list with the partner phone numbers. Activating
the checkbox All partner phone numbers allows full access.
HINT
3.1.12.4
Access Right - Own Phone Number

This access right specifies the list Own phone number accessed by the user. The used own
phone numbers neednt to be composed of the whole telephone number. However the entered
extensions have to identify all recorded telephones in the LAN unique. Activating the checkbox
All own phone numbers allows full access.
HINT
3.1.12.5
Access Right - Fields

Please refer to the chapter 3.1.8 - User Administration - Users - Fields Tab for the configuration
of the access right Fields.
HINT
If you allow the right Writing for a configurable field the writing or
changing of this field is only possible by using the POWERplay or
WEBplay. This right is unapplicable by using the INSPIRATIONpro.
3.1.12.6
Access Right - Timespan

Please refer to the chapter 3.1.9 - User Administration - Users - Timespan Tab for the
configuration of the access right Timespan.
HINT
3.1.12.7
Roles
For users who should have the same attributes / rights, you can define roles. A role serves as a
standard mask for those user groups. You can understand a role as a default user, who has
every attribute and right required for all users within the group.
30/316

User Administration
Fig. 24 - Details - Role

Apart from the Details tab there are no diffenences between defining a role and defining a user.
For a user you can assign username, description, password, LDAP-DN and the option "User
must change his password at next login". For a role you have to assign role name and role
description.
Fig. 25 - Details - User

HINT
You cannot see immediately the rights and attributes of a user, who has
got a role assigned. Under the point right / roles - role you can see the
assigned attributes and rights of this role which are also the attributes
and rights of the user.
31/316

User Administration
3.2
User Administration - Agents

This part of the hierarchical structure is used to create and administer the agents for the
Fig. 26 - Agents
An Agent entry consists of the six fields AgentID, Agent Name, AgentFunction, PCName,
PCLogin and Own Phone Numbers. The AgentID is added to a call when tagging via ESS, CTI or
third party application. This ID is not visible for a user but the AgentName which is assigned to
this ID. The AgentName can be used when searching the database using the POWERplay. The
field AgentFunction can be filled optionally.
To add a new agent click the Add button and fill the fields. To delete an agent select the
respective agent and delete it from the list by clicking the Delete button.
If a tagging client has already tagged several calls without using the Agents table of the
MARATHON EVOLUTION system, i. e. new AgentIDs were used for tagging, these new
AgentIDs can be added to the Agents table by using the Autofill button. The fields AgentName
and AgentFunction are left empty for these AgentIDs.
HINT
If an agent is deleted from the list, the calls to and from this agent might
not be found any more.
Like in many other lists there is a toolbar providing the following buttons for user administration
configuration:
New:
Creates a new agent
Search:
Searches for entries in the list
32/316

User Administration
Print:
Autofill:
Prints the current list (not available if ADM is

If a tagging client has already tagged several calls
without using the Agents table of the INTERACTION Software system, i. e. 'new' AgentIDs were
used for tagging, these 'new' AgentIDs can be
added to the agents table by using the 'Autofill'
button. The fields 'AgentName' and AgentFunction' are left empty for these AgentIDs.
Export:
Exports the list to a text file
Import:
Imports an existing text file(s) into the current list
Delete:
Deletes the seleted agents
Reload:

current data)
Exit /

Portal
window
Logout
33/316

User Administration
3.3
User Administration - Password Rules

This part of the hierarchical structure is used to administer the password rules for the complete
Reload
Exit /
Logout
Fig. 27 - Password Rules

The Length rule sets a minimum and maximum value for the length of the password.
In Repeat char rule you can set a value for minimal repeat char rule. There must be at least one
different char in comparison to the previous password.
In Needed chars rule you can set minimum values for chars (letters), lower chars (lower case
letters), upper chars (upper case letters) and digits. This means e.g that if you write 3 into lower
chars and 2 into upper chars you have to choose at least 5 different characters, 3 lower case
letters and 2 upper case letters for your password. The minimum value will then be set to 2. If
you reduce the minimal value to 1, at least one lower case letter or one upper case letter (or
both) must appear. You can also activate all characters except the selected sets.
In the checkbox Minimal duration rule you can configure a minimal value in days within a
password cannot be changed.
In the checkbox History rule you can configure a minimal value how often you have to choose a
different password before you can enter a previous password again.
In the checkbox Password fail rule you can configure a minimal value how often you can enter
the wrong password until the login will be disabled.
34/316

User Administration
The checkbox Password expiration enables rules for the validity of the passwords.
The field Days after passwords will expire defines the number of days the password will be valid.
If you enter a 0 in this field, the user can still login after the expiration of his password to change
it.
The field Number of days after setting the password the user will be adviced for expiration
defines the number of days to elapse before a hint shall appear that informs about the imminent
expiration of the password. 0 means that no hint shall appear.
The field Number of days after setting the password the user cannot set the password when its
expired a number of days after the user is not able to change the password. If you enter a 0 in
this field, the default value is used (90 days).
When activating the checkboxes Inactivity lock and Inactivity warning you can configure a
minimal value of days the user can be inactive (not signed in) before the password will expire.
Under Mail settings you can choose if the user gets an e-mail when he is deactivated because of
inactivity, or new users get e-mails when they get their access data.
Under SMTP settings the required defines values for sending emails can be set.
configuration:
3.4
Reload:

current data)
Logout

window
User Administration - Forbidden Passwords

This part of the hierarchical structure is used to create and administer forbidden passwords for
the complete MARATHON EVOLUTION system. Forbidden passwords must not be used by any
user of the MARATHON EVOLUTION system as passwords (e. g. the name of the company).
Search
Print
Export
Import
Reload
Logout
Fig. 28 - Forbidden Passwords
35/316

User Administration
To add passwords to the list click the Add button. To delete entries select the respective entry
and click the Delete button.
HINT
New items added to the Forbidden Password list have no influence on
passwords which are already in use.
configuration:
3.5
Search:
Print:

Export:
Import:
Reload:

current data)
Logout

window
User Administration - LDAP Mapping

For information about configuring LDAP Mapping please refer to Installation Manual
06_LDAP_Connectivity_e_STV in the directory 06_Basic_Configuration.
3.6
Administration Rights
In order to use the ASC DataManager at least one of the administration rights ConfigureUser
(User can configure users), ConfigureSystem (User can configure the system) or ArchiveCreate
(User can create archive media) are required. A user with all 3 rights can administer the
complete MARATHON EVOLUTION system - except the Registry. A user with superuser status
in the MARATHON EVOLUTION database, i.e. he / she is assigned the Superuser right, may
administer the complete MARATHON EVOLUTION system - including the Registry with the ASC
DataManager.
Meaning of the administration rights:
ConfigureUser
Users with this right are allowed to create and administer users (except Superusers)
Limitation: If the user is not granted the right ConfigureSystem he/she can not assign this right to
another user.
ConfigureSystem
Users with this right are allowed to change system settings.
36/316

User Administration
ArchiveCreate
Users with this right are allowed to create and administer Archive Jobs.
HINT
Users with the access right Superuser are not able to log in to
INSPIRATIONpro. The INSPIRATIONpro access rights are required for
the log in to the INSPIRATIONpro. It is only possible to assign this
access rights without the right Superuser.
According to the rights assigned the users, different areas in the hierarchical structure are
visible/invisible to them. The following table gives an overview on the areas of the hierarchical
structure displayed depending on the administration rights:
Hierarchical Structure/
Rights:
User
System
ArchiveJobs
Superuser
User Administration
Configuration
Archive Client
Registry
Versions
37/316

Configuration
Configuration
This area of the hierarchical structure contains the hardware and software parameters of the
The menu item Configuration includes different sub menus and one or several recorder
configurations. The number of recorder items depends on the number of correctly licensed
recorders which can be found in the MARATHON EVOLUTION system. The System area is
used to administer the configuration settings which apply to all recorders. The items Channels
and Recorder information are used to configure the individual channels and display information
on the different recorders within the system.
Search
Print
Reload
Logout
Fig. 29 - Configuration
The toolbar provides the following buttons for configuration:
Search
Print

38/316

Configuration
Reload

current data)
Logout

window
The main screen provides the following items:

RecorderID:
Shows the own recorder ID, all slave MARATHON

EVOLUTIONS and all recorders transmitting calls
via SDDM.
Description:
Displays the recorder description configured in the

section Recorder Information (see also 0.1 Configuration - Recorder Information)
ControlRecorder:
The checkbox is activated if a slave recorder is

connected
to
the
master
MARATHON
EVOLUTION.
Connected
Shows the status of a slave connection.
The different buttons at the bottom of the screen have the following functions:
Adds a new recorder to the MARATHON EVOLUTION system
Deletes the selected entry from the list
Deletes all entries from the list
Searches for other recorder IDs in the database and adds them to the
list
Saves the current configuration
Resets the configuration to the last saved settings
4.1
Configuration - System
This part of the hierarchical structure is used to configure the whole MARATHON EVOLUTION
system. Besides it is possible to import, export, print and reload the current configuration. Also it
39/316

Configuration
is possible to Import certificate and Generate certificate request of the current configuration.
Additionally the current running processes can be displayed and restarted.
Start/Stop Import
Generate Print
processes certificate certificate
request
Export
Import
Reload
Logout
Fig. 30 - System
The toolbar provides the following buttons for system configuration:
Start/Stop processes
Displays a complete status overview of the

MARATHON EVOLUTION modules. Furthermore
you can restart single processes and the whole
recorder as well.
Import certificate
Imports a X.509 certificate from e.g. a USB stick or

network drive. The following formats are
supported: P12, PEM and CRT (base64 coded). A
CRT certificate has to be based on a certificate
signing request generated on this system (see
below). An import of a P12 certificate will prompt
for a password entry. After pressing this button the
location where the certificate file resides can be
selected.
Generate certificate request Generates a certificate signing request (also CSR

or certification request) which can be sent to a
certificate authority (such as verisign) in order to
apply for a digital identity certificate. The certificate
authority will send back an identity certificate
which can then be imported into the ASC recorder.
After pressing this button the location where the
generated CSR (certification signing request) file
can be stored (e.g. USB stick, network drive etc)
can be selected.
40/316

Configuration
Print configuration
Prints the current configuration (not available if

Export configuration
Exports the configuration to a file
Import configuration
Imports an existing configuration into the current

configuration
Reload configuration

current data)
Logout

window
HINT
Note: The import of a certificate requires that the corresponding root
certificate is installed on the clients accessing the recorder.
HINT
Note: The csr request is based on the IP address of the recorder.
Checks the configuration of the selected section
Checks the configuration of all sections
Resets the current section to the last saved settings
Resets all sections to the last saved settings
Saves the current configuration of the selected section
Saves the current configuration of all sections
41/316

Configuration
4.1.1
Start/Stop and Activate/Deactivate Processes

By clicking the button Start/Stop processes the following dialog box appears.
Fig. 31 - System - Restart Processes

To start/stop a process click the corresponding icon in the left column.
To activate/deactivate optional processes click on the corresponding icon in the right column.
The process will be started automatically.
The icons have the following meaning:
Column State
Column Activated/Deactivated
Process is running
Process is activated at system

startup
Mandatory process. Can not be

deactivated
Process is stopped
Process is deactivated
Shutdown the recorder
Restarts the recorder
42/316

Configuration
Reloads the process list

Closes the dialog box
HINT
If you shut down the recorder remotely it is not possible the boot up the
recorder from remote.
4.1.2
Generate Certificate Request

Upon clicking the
Generate Certificate Request button, the following dialog box will appear:
Fig. 32 - System - Generate Certificate Request

* = Mandatory fields
Common Name*
The Common Name is the Fully Qualified Domain Name (FQDN) for which you are requesting
the SSL certificate, e. g. www.asc.de.
Country Code*
The country is indicated by a two-character code -- for the United States, it's 'US'. For countries
outside of the United States, see our listing of SSL Certificate Country Codes
(http://www.digicert.com/ssl-certificate-country-codes.htm).
Organisation*
In this field, enter either your full legal company name or your name, as registered with your local
authority (e. g. ASC telecom AG).
43/316

Configuration
Organisation Unit
This field indicates the division or branch of your company which is ordering the certificate, such
as accounting, marketing, etc.
State
In this field you can enter the name of the state in which your company is located.
City
In this field you can enter the name of the city in which your company is located.
4.1.3
Import Certificate
Proceed as follows in order to import a certificate:
1. Click on the
Import Certificate button.
2. In the Import Certificate from field, enter the certificate to be imported, or choose the appropriate
file after clicking the Browse... button.
3. In the Certificate password field, enter the password assigned to the certificate.
4. Click on the
Send file button.
Fig. 33 - System - Import Certificate
44/316

Configuration
4.1.4
Configuration Alarm Manager
Fig. 34 - System - Alarm Manager

Configuration table:
Name
Value(s) [Default]
Description
Loglevel
The log level specifies how detailed

the log messages will be.
Off
GlobalLevel
(All log levels will be
restricted to the global level - Minimal
e.g. if the log file level is set
to extended but the global
level is only set to medium, [Medium]
the log file level will also be
reduced to medium.)
Extended
No log messages will be generated.
Debug
Only error and warning messages will

be generated.
Error, warning and hint messages will
be generated.
Error, warning, hint and detailed
status messages will be generated.
Full debug
generated.
messages
will
be
45/316

Configuration
Name
Value(s) [Default]
Off
ConsoleLevel
(Only relevant if the Alarm
Manager is manually started Minimal
from the console.)
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
LogFileLevel
(Relevant for the entries in
the log file of the Alarm Minimal
Manager.)
messages
will
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
LogFileSize
1 .. 10 MB
[10]
With this value you can define the

maximum log file size. The log file is
created as a ring log file. This means,
if the log file size has been reached
the oldest entries will be overwritten.
The bigger the log file the longer it
takes to overwrite the oldest entries.
LogFileHistorySize
1 .. X MB
[50]
Threshold value in MB to delete log

files from the log history path
Specific_Loglevels
(DBAccess)
Off
Minimal

be generated
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Timesystem
Module
messages
messages
will
will
be
be
The local time of the MARATHON

EVOLUTION can be synchronized
with various time systems. This is
useful for synchronizing the local time
of different systems.
No timesystem
connected
46/316

Configuration
Name
NTPServer
Value(s) [Default]
Description
Network Time Protocol
If the Network Time Protocol has

been configured you have to define
the IP address of the NTP server.
TAM connected via

network
Time synchronization via Time &

Alarm Manager. You have to
configure under the submenu TAM ->
TAM_List within the tab Timesystem
the required time system.
IP Address
IP address of the NTP server. Only

available if Module - Network Time
Protocol is selected. Multiple IP
addresses must be separated by
comma (,).
KMS
Key Management
The Key Management System

defines the key which is used to
encrypt calls.
[No Key Management ]
There is
chosen.
no
Key
Management
Managed by Central Key The Central Key Management will be

Management
used.
Use RSA Key
Management
RSA Key Management will be used.
Use ASC Key

Management
ASC Key Management will be used.
State
[Unknown]
Shows whether
available or not.
KeyCreateTime
[90]
The time in days after which a new
Value between 1 and 365 key is created for encryption.
KeyUseDelay
[48]
The time in hours after which a newly
Value between 0 and 336 created key becomes usable.
RSAKeyManager
IP Address
The address of the RSA Server.
RSAKeyClass
KeyClass
The RSA key class to use.
RSAServerPemFile
[upload]
Upload the certificate of the RSA

Server (Format: PEM).
RSAClientCertificate
[download]
Download the certificate

recorder to the RSA
(Format:PEM).
PasswordState
state
Shows if the password is valid or not.
PasswordHash
HashState
The hash code of the

password for the keystore.
Password
Password
The password for the keystore.
PasswordValidation
Password
The password validation for the

keystore.
the
keystore
is
of the
Server
current
47/316

Configuration
Name
Value(s) [Default]
Description
Keyfile
[download]
Download the keystore

recorder for backup.
KeyValidTime
[0]
Value between 0 and
999999
The time in days after which a key

can no longer be used for decryption.
If set to zero the key will never expire.
KeyRedundantStore
Yes
[No]
If true the key data of the master is

saved redundant locally.
DiskWatcher
EmergencyRecordingStop
the
The disk watcher monitores the fill

level of the partitions on the hard disk.
[Yes]
No
DiskWatcher
(WatchPoint_1)
active
of
If true and the watchpoint for any

partitions is activated and has
reached the error level the recording
is stopped.
The disk watcher monitors the fill level
of the root partition on the hard disk.
[Yes]
No
This parameter activates/deactivates

the disk watcher.
displayname
Displayed name of the mountpoint.

This value can not be changed.
mountpoint
Monitored partition on the hard disk.

warnlevel
0 ... 65535 MB
[1000]
If the free space on the hard disk falls

below the entered value a warning is
raised in the alarm management.
errorlevel
0 ... 65535 MB
[500]

below the entered value an error is
DiskWatcher
(WatchPoint_2)
active
The disk watcher monitors the fill level

of the call data partition on the hard
disk.
[Yes]
No
This parameter activates/deactivates

the disk watcher.
displayname
Displayed name of the mountpoint.

mountpoint
Monitored partition on the hard disk.

warnlevel
0 ... 65535 MB
[7000]

below the entered value a warning is
errorlevel
0 ... 65535 MB
[2500]

below the entered value an error is
48/316

Configuration
Name
Value(s) [Default]
Description
TAM
(TAM_List)
Serial Number
Configurable/Status
Automatic detection of the serial
number, if the TAM is installed inside
the current network segment.
Input field for TAM serial number, if
TAM is placed in a separate network
segment
Hardware
Status
Displays the hardware version of a
detected TAM (only displayed in
connected status)
Image
Status
Displays the loaded FPGA / CPU
version of a detected TAM (only
displayed in connected status)
Firmware
Status
Displays the loaded firmware version
of a detected TAM (only displayed in
connected status)
Enabled
Configurable
1 = Enables TAM for this recorder: All
alarms will be displayed for this TAM.
Time synchronization is available and
the COR inputs can be used.
0 = Disable TAM for this recorder; No
alarms will be displayed for this TAM.
Time synchronization is not available
and the COR Inputs can not be used.
Status
Status
Displays the status of the network
connection.
Connected = The Time & Alarm
Manager and the local recorder are
connected.
Disabled = The Time & Alarm
Manager and the local recorder are
not connected.
Master
Status
Displays which recorder has done the
last configuration for this TAM. This
recorder defines the loaded FPGA
and firmware version.
DHCP
Configurable
0 = DHCP disabled; TAM works with a
static IP address.
1 = DHCP enabled; TAM works with a
dynamic IP address.
49/316

Configuration
Name
TAM
(COR_List)
Value(s) [Default]
Description
IP Address
Configurable/Status
With DHCP: Displays the dynamic IP
address.
Without DHCP: User can configure IP
address.
Subnet Mask
Configurable/Status
With DHCP: Displays the dynamically
configured Subnet Mask.
Without DHCP: User can configure a
Subnet Mask.
Gateway
Configurable/Status
With DHCP: Displays the dynamically
configured Gateway.
Without DHCP: User can configure
the Gateway.
Timesystem
To configure the time system

=> No Time Synchronization;
=> DCF77; requires DCF77 receiver
=> GPS; requires GPS receiver
=> Netclock F1; ASCII Protocol
=> Hopf; ASCII Protocol
=> IRIG B; requires Time Code
Converter with IRIG option
=> IRIG E; requires Time Code
Converter with IRIG option
=> Meinberg; ASCII Protocol
Timestatus
Status
Displays the time synchronization
method.
Serial Number
Displays the serial number(s) of

connected TAM(s).
COR Number
Info Displays the number of COR

channels.
IN State
Status of COR input.
OUT State
Status of COR feedback output
50/316

Configuration
Name
Value(s) [Default]
Description
Mode
Configurable Mode of COR input:

Disabled = COR input functionality is
disabled
Start/Stop = Start and stop of a
recording can be triggered via this
input. Requires the configuration of
the Recording Start Mode - HOST in
ADM/Configuration/Channels.
Toggle Keep / Delete = Input will be
used for triggering the Storage Mode
extern save or extern delete.
Requires the configuration of the
Storage
Mode
in
ADM/Configuration/Channels.
Toggle Mute / Unmute = Input will be
used to mask audio data with a 2 kHz
tone insertion.
Toggle Mode
Configurable toggle mode of COR

Input:
Trigger each change (only input signal changes from "low" to "high" will
release a trigger -> this toggle mode
should be configured, when a "normal opened" push button is used)
Trigger only off to on (only input signal changes from "low" to "high" will
should be configured, when a "normal opened" push button is used)
Trigger only on to off (only input signal changes from "high" to "low" will
should be configured, when a "normal closed" push button is used)
Field
Configurable assignment method:

CHANNELINDEX = Channel number
of the local recorder.
CHANNELID = Uses the unique
CHANNELID to assign a channel to
another recorder.
AGENTID = Defines a channel via the
database field Agent tagged from CTI.
OWNNUMBER = Defines a channel
via the database field Own Phone
Number.
IP = Defines a channel via the IP
address of a VoIP telephone.
MAC = Defines a channel via the
MAC address of a VoIP telephone.
Value
Configurable
value
for
CHANNELINDEX,
CHANNELID,
AGENTID,
OWNNUMBER,
IP
address or MAC address.
51/316

Configuration
Configuration of the Key Management System

Open the ADM of the Interconnect Master and go to Configuration > System > Alarm Manager >
KMS. Click the button Download to get the current key store file (KeyStore.dat).
Fig. 35 - Configuration Key Management System - Interconnect Master: Saving KeyStore file
Open the alarm manager folder on the Interconnect Slave (for windows, see
%ASC_HOME%\bin\alarmman, for linux, see $ASC_HOME/bin/alarmman). Copy the
downloaded KeyStore file into this folder.
HINT
Make sure that the file has the correct spelling (case-sensitive). The
correct file name is KeyStore.dat.
52/316

Configuration
Fig. 36 - Configuration Key Management System - Interconnect Slave: Folder alarmman with
KeyStore file
Open the section KMS under Configuration > System > Alarm Manager in the ADM of the
Interconnect Slave. Under KeyManagement, select Managed by Central Key Management. Two
new fields appear. Set the field KeyRedundantStore to Yes. Save the changes and reload the
configuration. In the field State, The central keystore is available should be seen. The
configuration is now finished.
Fig. 37 - Configuration Key Management System - Interconnect Slave: Configuration finished
53/316

Configuration
HINT
In the case, Managed by Central Key Management was configured
before, the key management must be deactivated and activated again
to accept the new key store. To do so, select the option No Key
Management and save the settings. Subsequently, select the option
Managed by Central Key Management again and continue like
described before.
Alternatively, the alarm manager may be restarted.
4.1.5
Configuration API Server
Fig. 38 - System - API Server

Name
Value(s) [Default]
Loglevel
Description
54/316

Configuration
Name
Value(s) [Default]
Off
GlobalLevel
restricted to the global level - Minimal
e.g. if the log file level is set
to extended but the global
level is only set to medium, [Medium]
the log file level will also be
reduced to medium.)
Extended
ConsoleLevel
(Only relevant if the API
Server is manually started
from the console.)
LogFileLevel
the log file of the API
Server.)
LogFileSize
Description
be generated.
be generated.
Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[10]

messages
messages
messages
will
will
will
be
be
be
55/316

Configuration
Name
Value(s) [Default]
Description
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Specific_Loglevels
Channels
(Channel relevant
Information)
Recordable
(Call relevant information)
RecManConnection
(The connection to the
RecMan)
SlaveConnection
(The connection to all
slaves)
messages
messages
messages
messages
will
will
will
will
be
be
be
be
56/316

Configuration
Name
Value(s) [Default]
RIA Connection
OFF
(The Connection to the RIA)
Minimal
ESS
(ESS client access)
Parser
(Phone numbers
parsers(CLI/DTMF)
RecService
(Recording Planner)
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
messages
messages
messages
will
will
will
will
be
be
be
be
57/316

Configuration
Name
Value(s) [Default]
Description
DBAccess
(Database Access)
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
INSPIRATIONproProtocol
(INSPIRATIONpro
communication)
Agents
(Agent information)
Sessions
OFF
(INSPIRATIONpro Sessions)
Minimal
messages
messages
messages
will
will
will
be
be
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
will
be
58/316

Configuration
Name
Value(s) [Default]
Description
Licensing
(Licensing Information)
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
OFF
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Force SSL
SSL mode will force SSL
Force non SSL
SSL mode will force non SSL
[Prefer SSL]
SSL mode will prefer SSL
Prefer non SSL
SSL mode will prefer non SSL
APIClient
(API clients)
Retriever
(Data Retrieval)
ESSControl
API_SSL
(Requested SSL Mode)
messages
messages
messages
messages
will
will
will
will
be
be
be
be
59/316

Configuration
Name
Value(s) [Default]
Description
API_Port
0 .. 65.535
[4000]
With this value you can set the port

for the communication between the
API server and the clients. All ports of
this MARATHON EVOLUTION must
be unique.
Max_Search_Interval
0 .. 999 days
[[DDDDDD]HH:MM:SS]
[7]
This interval limits the time frame for

database scans.
ESS_UDP_Port
0 .. 65.535
[50050]
With this value you can set the port

for the communication between the
API server and the ESS clients. All
ports
of
this
MARATHON
EVOLUTION must be unique.
MasterMode
[Master EVOLUTION]
INSPIRATIONpro
With this value you can set if the

master
for
recording
planner
configurations is a MARATHON
EVOLUTION or an INSPIRATIONpro.
MasterEvolution_IAS
The
address
of
the
central
MARATHON EVOLUTION where all
ESS connections will be managed.
Example
for
a
MARATHON
EVOLUTION environment:
The Master/Slave configuration is
used to control all configured slaves
centralized
with
one
Master
EVOLUTION. The control concerns
ESS and/or CTI applications. To do so
the Slave EVOLUTIONS need to
connect to the Master EVOLUTION.
This has to be configured in the field
MasterEvolution_IAS.
After
the
successfully configuration the Slave
EVOLUTION connects automatically
to the Master EVOLUTION and the
Slave EVOLUTION can be controlled
via the Master EVOLUTION.
An overview about all connected
MARATHON EVOLUTION Slaves
can be found under Configuration
(see 4 - Configuration).
For an INSPIRATIONpro example
please refer to the INSPIRATIONpro
Installation
Manual
Part
F
Configuration.
FreeSeatingWithoutCTI_
AgentLogout
(How free seating without
CTI is handled if an agent
logs out)
[Keep mapping]
The mapping will be kept if the agent

logs out.
Erase Mapping
The mapping will be erased if the

agent logs out.
ClipExtenstionForAgent
[0]
Use only the last n digits of the
Value between 0 and 200 extension for the agent mapping. If
set to zero the complete extension is
used.
60/316

Configuration
Name
Value(s) [Default]
Description
Interconnect
IP or hostname
The IP or hostname
Interconnect master.
InterconnectSSL
(The requested SSL mode
for the connections)
[SSL]
If you choose "SSL" the connection

will be SSL encrypted.
No SSL
Connection will not be SSL encrypted
InterconnectLicensing
(License mode)
[Managed by Dongle]
The licenses will be managed by

Dongle.
Managed by
License Server
of
the
Central The licenses will be managed by

Central License Server.
Central License Manager Do not use.

Central License Server
The licenses will be manages by

Central License Server.
InterconnectSharing
(Share resources via
Interconnect)
[No]
Share resources via Interconnect is

not activated.
Yes
Share resources via Interconnect is

activated.
SingleSignOn
[No]
SingleSignOn is not allowed.
Yes
SingleSignOn is allowed.
Domain
Domain for Single Sign On.
Hostname
IP or hostname
The IP address or hostname of the

LDAP server.
Port
Port
The port of the LDAP server.
Use TLS
[No]
TLS connection is disabled.
Yes
TLS connection is enabled.
ServiceLogin
Name
The login name for an account to use

for searching on the LDAP server
ServicePassword
Password
The password for an account to use

for searching on the LDAP server
Upload certificate
pem file
Upload the certificate (PEM format) to

be used for TLS. This button is only
shown on linux recorders
Timeout
500 .. 10000
[10000]
Only DTMF sequences within this

timeout will be recorded. The timeout
will be checked between two digits.
Start
0-9,*,#
[*111#]
If you dial this combination on your

telephone the recording of your
communication will be started. Only
relevant if DTMF-Sequence is
configured as start trigger.
SSODomain
LDAP
DTMF
61/316

Configuration
Name
Value(s) [Default]
Description
Stop
0-9,*,#
[*222#]

communication will be stopped. Only
relevant if DTMF-Sequence is
configured as stop trigger.
Mute
0-9,*,#
[*333#]

communication will be muted.
Unmute
0-9,*,#
[*444#]

communication will be unmuted.
Save
0-9,*,#
[*555#]

communication will be saved.
Only relevant if storage mode is
configured as EXTERN_SAVE or
EXTERN_DELETE and a recording
profile with external triggers for DTMF
sequences - Can keep exists.
Delete
0-9,*,#
[*666#]

communication will be deleted.
Only relevant if storage mode is
configured as EXTERN_SAVE or
EXTERN_DELETE and a recording
profile with external triggers for DTMF
sequences - Can delete exists.
HINT
Make sure to assign a valid IP address (i. e. an IP address accessible
via the network) to the network interface card that should be used for
communication within the network. Those NICs, however, that should
be used for passive call recording (so-called sniffing NICs or monitoring
NICs) must be assigned invalid IP addresses, like 1.0.0.1, 1.0.0.2, etc.
For further information refer to Part I Setting up a VoIP Application of
the MARATHON EVOLUTION Installation Manual, section EVOip /
Network Connection and Configuration).
HINT
The MARATHON EVOLUTION is equipped with two network chips
onboard. To make use of both NICs, e. g. one for communication and
one for time synchronization, the IP addresses have to be configured
with different subnets.
The first IP address can be set to e. g. 192.168.1.115 while the second
IP address uses 192.168.2.115.
HINT
If you want to support the feature PostProcessor you have to connect
the INTERACTION Server via Interconnect with the option Interconnect
Sharing activated on the recorder.
62/316

Configuration
HINT
DTMF sequences which were configured as Start/Stop or Keep/Delete
will not be displayed in the DTMF field, in POWERplay, or in WEBplay.
HINT
If the partner's phone number is suppressed, the DTMF characters will
be written into the Partner's phone number field. This is continued until
a break takes place. The duration of this break depends on the settings
of the DTMF timeout (see section 4.1.5 - Configuration API Server,
configuration table, parameter DTMF).
The following parameters are visible on Linux systems only:
Name
Value(s) [Default]
Description
HOSTNAME
[evolution]
The host name of the MARATHON

EVOLUTION.
DOMAINNAME
[asc.de]
The domain name of the MARATHON

EVOLUTION.
DEFAULTGATEWAY
[192.168.1.254]
This setting is used to configure the

default gateway. The default gateway
is used to provide access to other
networks.
NAMESERVER
IP address
The IP address of the name server

(entries can be separated with , or ; ).
DOMAINSEARCH
Domain
The search domain (entries can be

separated with , or ; ).
Network
Devices (Device 0)
MACAddress
The MAC address is a unique

identifier of the network card. This
value can not be changed.
DeviceName
The device name describes the

network card. This value can not be
changed.
BootProtocol
IP

IP address of this network card.
CommIP
[Yes]
No
Select 'Yes', if this IP address should

be used for remote connections like
POWERplay, WEBplay and so on.
Select 'No' if this network card should
be used as sniffing device.
Broadcast
Netmask

netmask of this network card.
63/316

Configuration
4.1.6
Configuration Archive Manager
Fig. 39 - System - Archive Manager

Name
Value(s) [Default]
Loglevel
GlobalLevel
restricted to the global level
- e.g. if the log file level is
set to extended but the
global level is only set to
medium, the log file level
will also be reduced to
medium.)
Description
Off
Minimal

be generated.
[Medium]

be generated.
Extended
Error, warning, hint and detailed status

messages will be generated.
Debug
Full debug
generated.
messages
will
be
64/316

Configuration
Name
Value(s) [Default]
Off
ConsoleLevel
(Only relevant if the Archive
Minimal
Manager is manually
started from the console.)
LogFileLevel
the log file of the Archive
Manager.)
LogFileSize
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[10]

messages
messages
will
will
be
be
Drives
(ONLINE-STORAGE)
This submenu contains several menus

depending on the number of archive
devices.
For further information please refer to
the Installation Manual
08_Archiving_Online_Storage_e_STV
in the directory
08_Optional_Functions.
Name
The name of the device that will be

displayed at the Portal. This value can
not be changed.
Type
The drive type can not be edited. This

value is readout by the system.
Removable
This value indicates whether the

connected device is removable.
Please note, that removable devices
connected via USB must be detached
before you can disconnect them.
65/316

Configuration
Name
Value(s) [Default]
Description
Server-Type
Direct Access Storge
Direct Access Storage as archive

drive.
[Samba-Share]
Samba-Share as archive drive.
Centera-Server
Centera-Server as archive drive.
Direct-Path
Defines the path on a Direct Access

Storage.
Centera-Server
IP address of the centera server.
Centera-Login
[Username and
Password]
The method of authentication

username and password.
is
.pea-file
The method
peafile.
is
of
authentication
Centera-Username
The username for Centera access.
Centera-Password
The password for Centera access.
Centera-Peafile
upload
You can upload a *.pea file by

pressing the button.
Server
With this value you can define the IP

address of the connected onlinestorage server.
Please note, that the online-storage
has to support NFS.
Server-path
With this value you can define in which

path on the server the data should be
archived.
Username
The user name for network access

has to be entered. Please note that
the IP address or the domain needs to
be included in the user name (e. g.
192.168.1.170\asc).
Password
The password for network access has

to be entered.
Mode
Warnlevel
[Do not activate this drive] This drive will not be activated and
therefore not be displayed in the
Portal.
Not used for recording
This drive will not be used for

archiving.
Jobs choose drives

automatically
This drive can be used for all kinds of

archive jobs.
50 .. 100 %
[95]
A warning will be issued when the fill

level set is reached.
Drives (NAS-1 ... NAS-4)
66/316

Configuration
Name
Value(s) [Default]
Description
Name

not be changed.
For further information please refer to
the Installation Manual
in the directory
Type

Removable
[Yes]

Please note, that removable devices
connected via USB must be detached
before you can disconnect them.
Server-Type
Direct Access Storge
Direct Access Storage as archive

drive.
[Samba-Share]
Samba-Share as archive drive
Centera-Server
Centera-Server as archive drive
Direct-Path

path on the NAS the data should be
archived.
Server
With this value you can define the IP

address of the connected onlinestorage server.
Please note, that the online-storage
has to support NFS.
Server-path

path on the server the data should be
archived.
Username
The user name for network access

has to be entered. Please note that
the IP address or the domain needs to
be included in the user name (e. g.
192.168.1.170\asc).
Password
The password for network access has

to be entered.
Mode
[Do not activate this drive] This drive will not be activated and
therefore not be displayed in the
Portal.
Not used for recording
This drive will not be used for

archiving.
Jobs choose drives

automatically
This drive can be used for all kinds of

archive jobs.
Jobs choose the drive if This drive can be used if it is assigned

they are assigned to this to the archive manager.
drive
67/316

Configuration
Name
Value(s) [Default]
Description
Only available for single This drive can not be used for bulk
step jobs which are jobs. It is only possible to assign
dedicated jobs like CCB archiving or
dedicated
Rules Based archiving.
Warnlevel
50 .. 100 %
[95]

MaxArchiveSize
50 ... 250
[100]
Maximum size for the sub archives in

GB.
Drives (DVD-RAM-1)
Name

not be changed.
Type

Removable

Device
The drive interface can not be edited.

This value is readout by the system.
Filesystem
[ASCFS]
UDF
VFAT
Mode
[Do not activate this drive] Select the jobs mode.

Activate this drive only for
replay/update
'Continuous' jobs
'Single Step' jobs
Activate this drive for all
jobs types
Warnlevel
50 .. 100 %
[95]
Label Printer
Connect
Select the filesystem used to write.

In this section you can configure the
label printer settings.
Yes
The label printer is connected.
[No]
No label printer is connected.
NumberOfCallsToArchive [0]
Enter the quantity of new calls after

which the archiving should be started
again.
Note: With a value larger than 0, the
value entered for the parameter
CallArchiveInterval
will
not
be
considered.
68/316

Configuration
Name
Value(s) [Default]
Description
CallArchiveInterval
HH:MM:SS
[01:00:00]
In this interval steps the Archive

Manager searches for calls not yet
archived and transfers them to the
recording media.
OverwriteProtection
Period
DDD HH:MM:SS
[0 00:00:00]
For this duration the archive media will

be overwrite-protected.
ForceArchivingTimeout
[DDD] HH:MM:SS
[2 00:00:00]
Duration the Archive Manager waits

before archiving calls pending to be
processed.
AutoEjectinCascading
Mode
Yes
When the recording medium is full and

closed (only in cascading mode) it will
be ejected automatically.
[No]
No automatic eject.
[Yes]
An information will be sent to the

Alarm Manager when the recording
medium is full and the recording will
be continued on the next medium
(only in sequential mode).
No
No information will be sent.
MediaTakeOverInfo
4.1.7
Configuration Database Inserter
Fig. 40 - System - Database Inserter

Name
Value(s) [Default]
Loglevel
Description
69/316

Configuration
Name
Value(s) [Default]
Description
GlobalLevel
medium.)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
ConsoleLevel
(Only relevant if the
Database Inserter is
manually started from the
console.)
Off
LogFileLevel
the log file of the Database Minimal
Inserter.)
LogFileSize
messages
messages
will
will
be
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[10]

created as a ring log file. This means
messages
will
be
70/316

Configuration
4.1.8
Configuration Delete Manager
Fig. 41 - System - Delete Manager

Name
Value(s) [Default]
Description
Loglevel

Off
GlobalLevel
restricted to the global level Minimal
[Medium]
medium, the log file level will
also be reduced to medium.)
Extended
Debug

be generated.
be generated.
Full debug
generated.
messages
will
be
71/316

Configuration
Name
Value(s) [Default]
Off
ConsoleLevel
(Only relevant if the Delete
Manager is manually started Minimal
from the console.)
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[10]

[Delete calls at a daily

timepoint]
Select this setting if the Delete

Manager should work only once a
day. Dont forget to set the timepoint.
Delete calls at regular

intervals
Select this setting if the Delete

Manager should work in regular
intervals. Dont forget to set the
interval.
Timepoint
00:00:00: .. 23:59:59
[02:00:00]

time when the Delete Manager should
start to work.
Interval
00:01:00 .. 23:59:59
[00:01:00]

interval in which the Delete Manager
should start to work.
DeleteImmediately
Never
The database entries will never be

deleted.
[Always]
The database entries will be deleted

right after the call data.
If older than given age
The database entries will be deleted

after the configured call age.
LogFileLevel
the log file of the Delete
Manager.)
LogFileSize
messages
messages
will
will
be
be
DeleteConfig
CheckModeSelection
72/316

Configuration
Name
Value(s) [Default]
Description
AgeCheckModeSelection
[Delete entries at a daily

timepoint]
Select this setting if entries should be

deleted at a daily timepoint.
Delete entries at regular

intervals
Select this setting if entries should be

deleted at regular intervals.
AgeTimepoint
Value between 00:00:00 Set a value for daily timepoint to

check entries marked for deletion.
and 23:59:59
[02:00:00]
AgeInterval
Value between 1 minutes Set value for interval to check entries

and 24 hours
marked for deletion.
[00:01:00]
IPROSessionSurveillance
[No]
With this option INSPIRATIONpro

Sessions will not be deleted.
Yes
With this option INSPIRATIONpro

Sessions can be deleted.
[Ignore]
Calls in this state will be ignored.
archived
A call will be deleted if its state is

archived.
transferred

transferred.
archived an transferred

archived and transferred.
[Yes]
Choose setting if a session should be

deleted when the corresponding call
recording is deleted.
No
Choose setting if a session should not

be deleted when the corresponding
call recording is deleted.
[No]
Choose setting if a session should not

be deleted when the corresponding
screen recording is deleted.
Yes
Choose setting if a session should be

deleted when the corresponding
screen recording is deleted.
[Yes]
A session will be deleted if it is older

than the given age.
No
A session will not be deleted, even if it

is older than a given age.
YY:MM:DD:HH:mm
[00:13:00:00:00]
The minimum age of sessions to be

deleted
from
the
database
automatically.
ArchiveCheck
DeleteByCall
DeleteByScreen
DeleteByAge
SessionAge
PreserveEvaluatedSessions [No]
A session with an evaluation can be

deleted.
Yes
A session with an evaluation will not

be deleted.
73/316

Configuration
Name
Value(s) [Default]
Description
DeleteEvaluationByAge
[No]
An evaluation will not be deleted,

even if the age is older than the given
age.
Yes
An evaluation will be deleted if the

age is older than the given age.
YY:MM:DD:HH:mm
[00:13:00:00:00]
Minimum age of an evaluation to be

deleted from the database.
EvaluationAge
DeleteRemovedUserByAge [No]
4.1.9
Removed users will not be deleted.
Yes
Removed users will be deleted

according to theUserAge setting.
UserAge
YY:MM:DD:HH:mm
[00:13:00:00:00]
Minimum time a removed user will be

kept in the database before automatic
deletion.
CallAge
00:00:00:00:00 ..
99:00:00:00:00
[01:00:00:00:00]
With this value you can define after

which time interval the database
entries will be deleted.
DiskFreeSpace
10000 .. 100000 MB
[10000]
With this value you can define how

much space will be kept free on the
call data partition.
OnlineStorageSurveillance
[Yes]
No
With this value you can enable the file

deletion from the online storage.
OnlineStorageFreeSpace
10000 .. 4294967295 MB This value defines the minimum free

space which should be available on
[10000]
this medium.
Configuration Evolution Portal
Fig. 42 - System - Evolution Portal
74/316

Configuration
Name
Value(s) [Default]
Loglevel
GlobalLevel
medium.)
Description
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
ConsoleLevel
Evolution Portal is manually Minimal
messages
will
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
LogFileSize
1 .. 10 MB
[10]

SessionTimeout
[0]
The portal will automatically logout

after this time.
LogFileLevel
the log file of the Evolution
Portal.)
messages
messages
will
will
be
be
75/316

Configuration
4.1.10
Configuration EVOip
The tab EVOip is used to configure the EVOip module for passive VoIP recording. The EVOip
records all calls on the IP network (Bulk Recording or selective recording). It supports the SIP
(Session Initiated Protocol) as well as Ciscos Skinny protocol (SCCP). For connections with one
or two Mitel 3300 IP PBXs it also supports the MiXML standard.
Fig. 43 - System - EVOip

The tab EVOip includes the following sublevels:
4.1.10.1 - Sublevel Expert Mode

4.1.10.2 - Sublevel Devices
4.1.10.3 - Sublevel Sniffer
4.1.10.4 - Sublevel SIP
4.1.10.5 - Sublevel SCCP
4.1.10.6 - Sublevel SIFA
4.1.10.7 - Sublevel IGMP
4.1.10.8 - Sublevel Receiver
4.1.10.9 - Sublevel Calldata
4.1.10.10 - Sublevel Signaling
4.1.10.11 - Sublevel MiXML
4.1.10.12 - Sublevel Loglevel
Click the plus sign before each sublevel to display the respective parameters.
76/316

Configuration
4.1.10.1
Sublevel Expert Mode
Fig. 44 - System - EVOip - Expert Mode

4.1.10.2
Name
Value(s) [Default]
Description
EnableExpertMode
[No]
Yes
Enables the expert mode. This mode

shows more specific configuration
items and should only be used by
EVOip specialists.
Sublevel Devices
Fig. 45 - System - EVOip - Devices

The sublevel Devices includes parameters to enable or disable the individual Network Interface
Cards (NICs) available for recording and to define filter criteria for the packets to be forwarded
from these NICs to the EVOip for recording.
Name
Value(s) [Default]
DeviceX
Linux device name e.g. Select enabled to activate the

respective NIC, or select the
eth0
respective NIC from the dropdown
[disabled]
list.
DeviceXFilter
[ip and (udp or tcp)]

ip and udp
ip and (udp or tcp)) or
(vlan and ip and (udp or
tcp)
Description
Select a filter criterion from the drop

down list or enter a filter criterion of
your choice to define the IP packets
that will be recorded.
77/316

Configuration
Name
Value(s) [Default]
Description
FilterPresets
4.1.10.2.1
Filter out specific IP packets

Introduction
This short tutorial shows how specific IP packets can be filtered out. In the following example all
IP packets with the IP address 10.61.9.12 should be filtered out.
5. Launch the ASC DataManager and log in

6. Change filter presets:
Fig. 46 - Change filter presets

In the ASC DataManager open the submenu Configuration in the hierachical structure on the lefthand side of the window, and select the item System. On the right-hand side of the system
window, select the EVOip module.
Change the Filter string under FilterPresets like the following:
Original filter string: ip and (udp or tcp) || ip and udp || (ip and (udp or tcp) or (vlan and ip and
(udp or tcp))
Add the following string to the original filter string: || ip and (udp or tcp) and not net 10.61.9.12
New filter string: ip and (udp or tcp) || ip and udp || (ip and (udp or tcp) or (vlan and ip and (udp
or tcp)) || ip and (udp or tcp) and not net 10.61.9.12
78/316

Configuration
Hint
This example for a new filter string will discard all packet to and from IP
address 10.61.9.12
Hint
The syntax of the filter string is documented quite well in the man page
for tcpdump
7. Save section
8. Log out
9. Log in
10. Select the added filter string
Fig. 47 - System - EVOip - Devices - Select the added filter string

In the ASC DataManager, open the submenu Configuration in the hierachical structure on the
left-hand side of the window, and select the item System. On the right-hand side of the system
window, select the EVOip module.
Select the added filter string for the specific device.
11. Save section.
79/316

Configuration
4.1.10.3
Sublevel Sniffer
Fig. 48 - System - EVOip- Sniffer 1
Fig. 49 - System - EVOip - Sniffer 2
80/316

Configuration

The sublevel Sniffer includes parameters to define the so-called Sniffer, i.e. the module that
extracts IP packets from the network stream.
81/316

Configuration
Name
Value(s) [Default]
NonPhoneIPs
IP addresses separated Enter those IP addresses of non

by comma or semicolon phone devices such as gateways,
(max. 255 characters)
CallManagers or MOH servers whose
RTP packages should not be
recorded. Enter 0 if you do not want to
specify any address. A maximum of
255 characters is allowed. Multiple IP
addresses must be separated by
comma (,) or semicolon (;).
A range of IP addresses can be
entered by using CIDR notation.
Examples:
192.168.100.0/24 would specify the
whole range from 192.168.100.0 to
192.168.100.255.
192.168.100.0/26 would specify the
whole range from 192.168.100.0 to
192.168.100.063.
SnifferPriority
idle
The sniffer priority is idle
lowest
The sniffer priority is the lowest
below normal
The sniffer priority is below normal
normal
The sniffer priority is normal
above normal
The sniffer priority is above normal
[highest]
The sniffer priority is the highest
time critical
The sniffer priority is time critical
normal
The global priority is normal
ilde
The global priority is idle
high
The global priority is high
[realtime]
The global priority is realtime
[Yes]
No
This parameter is used to avoid wrong

interpretation of IP packets if one call
is split into several different RTP
packets. Select Yes to enable the
EVOip to defragment several different
RTP packets belonging to the same
call. Select No to disable this function.
GlobalPriority
IP_Defragment *
Description
82/316

Configuration
Name
Value(s) [Default]
Description
PreventDoubleChannel
Delay *
0 - 10 (seconds)
[2]
As the EVOip can record only one call

per channel, recording of telephones
supporting several simultaneous calls
(e.g. conference calls) would result in
a mixture of different conversations.
To avoid recording fractions of two
different calls into one file, enter a
time value (in seconds) defining a
delay. If EVOip has just started to
record a new call but receives again
RTP packets of the call it had
recorded previously within the time
span defined here, this old call will no
longer be recorded. In case of such
concurrent calls EVOip will therefore
always record the most recent of two
calls.
MitelPatchForPayloadType [No],
Change *
Yes
If you have any problems with the first

RTP packets of a call carrying
different payload types, set this
parameter to Yes. The payload type of
the first four RTP packets will then be
ignored and the payload type of the
fifth RTP packet will determine the
payload type of the entire call. If no
problems occur concerning the
payload type, use the default setting
No for this parameter.
VoxDelay
0.1 - 60 (seconds)
[3]
This parameter is a criterion that

stops the recording of RTP packets.
Select a time span (in seconds) that
has to elapse after the last RTP
packet of a stream has been detected
until the call is considered to be
ended and the recording is stopped.
DebugStateMachine *
Yes
[No]
This parameter determines whether

the phone state changes will be
indicated in the log file (Yes) or not
(No).
G729SingleSlot *
[RX]
TX
For recording G.729 streams in audio

mixing mode, this parameter defines
which of the two call directions
(Receive = RX or Transmit = TX)
should be recorded.
DeadCallTime *
600 - 6000 (seconds)

[600]
This parameter stops the recording of

SCCP calls. Enter a time span (in
seconds) that should elapse without
receiving RTP packets to stop
recording this SCCP call.
83/316

Configuration
Name
Value(s) [Default]
Description
DeadCallCheckDelay *
[1200] (seconds)
This parameter defines a regular

interval (in seconds) EVOip should
search for dead SCCP calls, i.e.
active recording processes of SCCP
calls without receiving any RTP
packets for the time defined with the
parameter DeadCallTime. In normal
cases use the default setting, if a lot of
dead calls are available in your
network, you can reduce the value
down to 300.
FilterESSPackages
[Yes]
No
This parameter is used to filter UDP

packages on ESS ports in order to
prevent them from being recognized
as RTP packages (Yes).
EnableProtocolControl
[Off]
On
Force
This parameter determines the

recording control. Select Force to
control the recording process via
SCCP and SIP protocol messages.
Select On to control the recording
process via VOX detection. In this
case, only call details will be obtained
from the protocol.
SearchForOldStreams *
[No]
Yes
When the recorder receives two

streams and recognizes these
streams as one call, then these
streams will be assigned to a channel
and will be recorded. When the
streams end, the recording will be
stopped. In specific call scenarios,
such as HOLD scenarios, it could be
that one recorded call is made up of
several streams. If the parameter
"SearchForOldStreams" is set to Yes,
a check will be performed at the end
of a stream, whether a stream, which
was already assigned to this channel
still exists. In that case, the stream will
be assigned again to the channel and
the recording will be continued.
DynamicProcessingSpeed* [Yes]
No
Enables the dynamic

speed algorithm.
MaxProcessingSleep *
50 ... 500
[350]
Maximum value for the dynamic

processing speed algorithm.
FilterBroadcasts *
Yes
[No]
This parameter is used to exclude

broadcast messages destined to the
entire network from recording (Yes).
To include broadcast messages in
recorded calls, set this parameter to
No.
TimestampAnalysis
[No]
Yes
IMPORTANT: Leave this parameter

as No.
processing
84/316

Configuration
Name
Value(s) [Default]
Description
RFC2833PayloadType *
1 - 255
[0]
If you are using DTMF according to

RFC 2833 without SIP decoding, use
this parameter to select an RTP
PayloadType value that is defined in
the RFC 2833 for DTMF transmission.
StaticChannelStartMode
not allowed
[start silence]
For external Start/Stop applications

this parameter defines if it is allowed
to start the recording process even
though a call is not yet available and
how to handle the time until audio
data will be received.
To allow call recording only with a call
actually being available, i.e. with
audio data being received, set this
parameter to not allowed.
If call recording should be allowed
without any audio data being
received, you can decide how to
handle the silence until the start of the
call:
Select either
start
silence, to start the
recording process immediately and
inserting silence packages until the
call starts and audio data is being
received.
InstantDTMFMonitoring
Yes
[No]
DTMF scanning is always activated

DTMF scanning only during active
calls
Do not change this parameter
RelevantExtentionDigits *
[0]
If their is a mapping extension /

channel it will be necessary to
configure how many digits will be
relevant for the comparison of the
extension in the signalling and the
configuration. The default value 0
means that the whole digits from the
signalling will be used for the
comparison.
EnableMACMode
Yes
Necessary configuration for recording

with MAC address. This feature can
only be used if the IP telephones are
not behind a router.
This adjustment is only allowed if their
is no static channel configuration with
MAC addresses.
[No]
ESSIPs
Please enter all IP addresses where

an ESS server is running. Please use
"," or ";" to separate the entries.
NonPhoneMACs
Please enter all MAC addresses of

non phone devices. Please use "," or
";" to separate the entries.
85/316

Configuration
Name
Value(s) [Default]
Description
ProcessingPriority *
(defines the priority of the
processing thread)
lowest
The process priority is very low.
low
The process priority is low.
below normal
The process priority is below normal.
normal
The process priority is normal.
above normal
The process priority is above normal.
highest
The process priority is the highest.
[time critical]
The process priority is time critical.
[Yes]
No
Checks for two sequential RTP

packets that must have sequential
SeqNo and time stamp before
creating an RTP stream object.
DoRTPStreamPreCheck *
* = These values are only displayed when Expert Mode is switched on

4.1.10.4
Sublevel SIP
Fig. 52 - System - EVOip - SIP

The sublevel SIP includes parameters to define the recording of SIP controlled calls.
Name
Value(s) [Default]
Description
EnableSIPDecoder
Yes
[No]
This parameter defines whether the

SIP Decoder for extracting call data
from the Sesssion Initiated Protocol
(SIP) should be enabled (Yes) or
disabled (No).
SIPPhoneNoDiscoverMode [all before @]

*
complete
This parameter defines which part of

a SIP URI (name and address of an
object in the WWW) should be used
as the extension of the IP phone. To
use the entire URI as extension,
select "complete". To use the part of
the URI before the @, select "all
before @".
SIPPorts *
This parameter determines the port

that will be used for recording SIP
calls. Do not change the default
setting.
[5060]
86/316

Configuration
Name
Value(s) [Default]
Description
SIPKeepAliveTime *
0 .. 4294967295 (sec)
[600]
This parameter defines the time in

seconds between SIP registration
requests. This is only used with TCP
to detect broken connections.
GetSIPExtensionFromReq* Yes
[No]
This parameter defines if the SIP

extension should be extracted from
the INVITE request line or from the To
field.
EnableCCM5SPIMode
Yes
[No]
Enables the special mode of acquiring

phone number from SIP messages
used by Cisco Call Manager version 5
and higher.
CheckForDuplicateSIPMess
ages *
Yes
[No]
With this paramerter you can activate

or deactivate if checks for duplicate
SIP messages should be performed.

4.1.10.5
Sublevel SCCP
Fig. 53 - System - EVOip - SCCP

The sublevel SCCP includes parameters to define the recording of SCCP controlled calls.
Name
Value(s) [Default]
Description
EnableSCCPDecoder
[No]
Yes

SCCP Decoder for extracting call data
from the CISCO Skinny Protocol
should be enabled (Yes) or disabled
(No).
RecordPrivateCalls *
[No]
Yes
This parameter allows to record calls

even if they have been indicated as
private calls on the SCCP phone by
the user. Select No to avoid recording
private calls. Select Yes to record all
calls, even those indicated as private
calls in the Skinny protocol.
87/316

Configuration
Name
Value(s) [Default]
Description
SCCPDelay *
1 - 3 (seconds)
[1]
This parameter allows to stop the

recording of SCCP or SIP controlled
calls . Select a time span between 1
and 3 seconds that has to elapse after
the last RTP packet of a stream has
been detected until the call is
considered to be ended and the
recording process is stopped.
CCMIPs
IP address(es)
Enter the IP addresses of all Cisco

CallManagers
that
should
be
monitored.
ResendCallData
No
[Yes]
This
parameter
provides
the
possibility to update the partner call
number that is saved with the call. It is
useful if the partner call number
changes in the course of the phone
conversation, e.g. due to call
forwarding.
To activate this function and to save
the latest partner phone number with
the call, set this parameter to Yes.
With the default setting No only the
partner phone number that is valid at
the beginning of the conversation will
be saved. Any changes in the partner
phone
number
during
the
conversation are not detected.
EnableJTAPIModule
Yes
[No]
Enables the JTAPI module in order to

receive AES encryption keys as well
as tagging data via the Cisco JTAPI
interface.

4.1.10.6
Sublevel SIFA
The sublevel SIFA is used to configure EVOip for Siemens radio applications (Siemens
Funkanschaltung / SIFA).
For
further
information
please
refer
to
06_EVOip+_fr_Siemens_SIFA_und_VASB_d_V
in directory 06_Basiskonfiguration\EVOip_Server_Software\Siemens.
4.1.10.7
Installation
Manual
Sublevel IGMP
Fig. 54 - System EVOip - IGMP
88/316

Configuration
4.1.10.8
Name
Value(s) [Default]
Description
EnableIGMP
[No]
Yes
Decide if IGMP Multicasts enabled
Sublevel Receiver
Fig. 55 - System - EVOip - Receiver

Name
Value(s) [Default]
Description
StartPort
Port number [20000]
This value determines the start of a

range of ports that are used to receive
tapped audio streams.
EndPort
Port number [25000]
This value determines the end of a

range of ports that are used to receive
tapped audio streams.
SSRCReceiveEnabled
Yes
[No]
Use this parameter for EVOip active

for OpenScape Xpert.
SSRCReceiveIP
IP address
The IP address for receiving SSRC

tagged RTP packets.
SSRCReceivePort
Port number
[15000]
The port for receiving SSRC tagged

RTP packets.
SkipNonSSRC*
Yes
[No]
Only enable this parameter if you

need all performance for SSRC
receiving. But be aware that all RTP
packets that do not match the SSRC
revceiving IP and port will be
discarded.
* = This value is only displayed when Expert Mode is switched on
89/316

Configuration
4.1.10.9
Sublevel Calldata
Fig. 56 - System - EVOip - Calldata

The sublevel Calldata includes parameters providing the possibilty to add additional information
to the call data by storing it into the fields of the database defined here.
Name
Value(s) [Default]
Description
EnableCallTagging
[Yes]
No
Enables the call tagging. This

parameter should be disabled if a
CTIC has been connected.
LocalIPField
[disabled]
ASCII 1 - 20
Select a field of the database where

the IP address of the local party
should be stored. If you do not want to
store the local partys IP address as
additional call information, select
disabled.
PartnerIPField
[disabled]
ASCII 1 - 20
Number 01 - 10

the IP address of the remote party
should be stored. If you do not want to
store the remote partys IP address as
additional call information, select
disabled.
90/316

Configuration
Name
Value(s) [Default]
Description
LocalNameField
[disabled]
ASCII 1 - 20

the text available on the display of the
local IP phone should be stored. If
you do not want to store the local
partys display text as additional call
information, select disabled.
PartnerNameField
[disabled]
ASCII 1 - 20

the text available on the display of the
remote IP phone should be stored. If
you do not want to store the remote
partys display text as additional call
information, select disabled.
SCCPLastRedirectingNum
ber
[disabled]
ASCII 1 - 20
Specifies the DB field to store the last

redirecting partys number (SCCP
only)
SCCPLastRedirectingNam
e
[disabled]
ASCII 1 -20
Specifies the DB field to store the last

redirecting partys name (SCCP only).
SCCPOriginalCalledNumb
er
[disabled]
ASCII 1 - 20
Specifies the database field where the

originally called party number will be
saved (SCCP only).
SCCPOriginalCalledName
[disabled]
ASCII 1 - 20
Specifies the database field where the

originally called party name will be
saved (SCCP only).
UseIPAsPhoneNo
[Yes]
No
Enables the tagging of IP addresses

into phone number fields if no phone
number is available.
OverwriteOwnPhoneNo *
Yes
[No}
Enables the tagging of the latest

received own phone number (from
signalling or external modules) even if
it changed after recording was
started.
Isub*
[disabled]
ASCII1-20
This parameter specifies the DB field

to store the SIP Isub value.
VASBName*
[disabled]
ASCII1-20

to store the caller name (VAS-B only).
VASBStreet*
[disabled]
ASCII1-20

to store the caller street (VAS-B only).
VASBCity*
[disabled]
ASCII1-20

to store the caller city (VAS-B only).
91/316

Configuration
Name
Value(s) [Default]
Description
ForceAvayaDMCCTagging
Yes
[No]
Forced tagging of Avaya DMCC call

related data. This parameter should
be enabled if EnableCallTagging is
set No, but call details from
AvayaInterface should be added to
the database.
ForceAvayaDMCCTagging will force
tagging for call details, available at
AvayaInterface, even if IP passive call
tagging is disabled
(see Installation Manual
06_EVOipactive_for_Avaya_DMCC_
e_V in directory
06_Basic_Configuration\EVOip_Serv
er_Software\Avaya).
SCCPCharsetEncoding
[ASCII]
UTF-8
Specifies the charset encoding of

SCCP call info fields. Set this option
to UTF-8 if this parameter is also set
on PBX site. This ensures that special
characters beyond the ASCII border
are tagged in the right way.

4.1.10.10
Sublevel Signaling
Fig. 57 - System - EVOip - Signaling - CornetIP

The sublevel Signaling is used to configure EVOip for the different signaling protocols of
different IP PBXs. It currently includes the sublevel CornetIP for operating EVOip with Unify
HiPath PBXs.
4.1.10.10.1 CornetIP / CornetIP225
The sublevel CornetIP includes parameters to configure EVOip for operation with the signaling
protocol CornetIP of Unify HiPath PBXs.
92/316

Configuration
4.1.10.11
Name
Value(s) [Default]
Description
EnableCornetIPDecoder
[No]
Yes

CornetIP Decoder for extracting call
data from the CornetIP Protocol
should be enabled (Yes) or disabled
(No).
HiPathIPs
IP address
Enter the IP addresses of all Unify

HiPath PBXs that should be
monitored.
CornetIPCommandPort
port number
[4060]
This parameter determines the port

that will be used for receiving
CornetIP command messages of the
Unify HiPath PBX.
DebugRawData
[No]
Yes
This
parameter
provides
the
possibility to save all data received by
the EVOip into a log file.
Activate this function (Yes) only if
problems occur with your EVOip
installation and send the log file for
further analysis to the ASC hotline.
In normal operation make sure to
deactivate this function (No).
Sublevel MiXML
Fig. 58 - System - EVOip - MiXML 1

The sublevel MiXML includes parameters to achieve a dynamic assignment of IP addresses and
phone numbers by a Mitel 3300 IP PBX.
93/316

Configuration
Name
Value(s) [Default]
Description
EnableMiXML
[No]
Yes
This parameter is used together with

a Mitel 3300 IP PBX, version 5 and
later, to define whether the PBX
should be polled to gather IP
addresses of configured IP Phones.
MitelXMLServerIP
IP address
Enter the IP address of the Mitel

MiXML Server.
MitelXMLServerPort
[18000]
If you used a different value than the

default value during the installation of
the Mitel MiXML Server, enter the
respective port number here.
MitelQueryInterval
min. 5 (minutes)
[60]
This parameter defines a regular

interval (in minutes) EVOip should
poll the Mitel 3300 IP PBX for the IP
addresses of all configured IP
phones.
MitelHTTPTimeout
10000 - 60000 (msec)

[20000]
This parameter is used to define a

time span (in milliseconds) the EVOip
should wait for replies from the IP
phones. Adapt this value to your
individual
network
configuration
following the rule: the more
telephones available in your network
the higher the value.
MitelPBXIP1
IP address
Enter the IP address of the first Mitel

3300 IP PBX.
MitelUser1
User name
Enter the user name to access the

first Mitel 3300 IP PBX.
MitelPass1
Password
Enter the password to access the first

Mitel 3300 IP PBX.
Mitel2ndEnabled
[No]
Yes
With Mitel 3300 IP PBXs version 5

and later it is possible to poll a second
Mitel 3300 IP PBX for IP addresses of
configured IP Phones. If a second
Mitel 3300 IP PBX is available in your
network that should be polled for IP
addresses, set this parameter to Yes.
MitelPBXIP2
IP address
Enter the IP address of the second

Mitel 3300 IP PBX.
MitelUser2
User name
Enter the user name to access the

second Mitel 3300 IP PBX.
MitelPass2
Password
Enter the password to access the

second Mitel 3300 IP PBX.
MitelRequestDelay
0 ... 4294967295
[20]
Enter the delay in milliseconds

between two subsequent MiXML
requests. Increase to reduce load on
the Mitel 3300 during MiXML data
transfer.
94/316

Configuration
4.1.10.12
Sublevel Loglevel
Fig. 59 - System - EVOip - Loglevel

The sublevel loglevel is used to specify the amount of information included in the log message.
Name
Value(s) [Default]
Description
globalLevel
- e.g. if the logFileLevel is
set to Extended but the
globalLevel is only set to
Medium, the log file level
Medium.)
Off
Minimal

be included in the log message.
[Medium]

Extended

status messages will be included in
the log message.
Debug
Full debug
generated.
consoleLevel
Off
(Only relevant if the EVOip
Minimal
passive has been started
manually from the console.)
messages
will
be

[Medium]

Extended

the log message.
Debug
Full debug
generated.
messages
will
be
95/316

Configuration
Name
Value(s) [Default]
Description
logFileLevel
the log file of the EVOip
passive.)
Off
Minimal

[Medium]

Extended

the log message.
Debug
Full debug
generated.
0 .. 10 MB
[9]
This value defines the maximum size

of the log file in megabytes. The log
file is created as a ring log file. This
means, if the log file size has been
reached the oldest entries will be
overwritten. The bigger the selected
log file size, the longer it will take until
logFileSize
4.1.11
messages
will
be
Configuration EVOip active

The tab EVOip active is used to configure the EVOip active module for active SIP recording. The
EVOip active is operated like a silent VoIP phone as an active part of the call-flow. If a call is
established on a phone that is monitored by the EVOip active, a third party conference between
the call participants (User A and User B) and the EVOip active software is established according
to user-definable rules for every conversation that has to be recorded. The EVOip active collects
the audio packets and combines them with further details like phone number, IP address or
agent ID and saves these data locally or on a central server.
Fig. 60 - System - EVOip active

With the JTAPI parameter you can click on the upload button to upload a jtapi.jar file to the
recorder. This may be necessary for some CTI integrations.
96/316

Configuration
The tab EVOip active includes the sublevels:

4.1.11.2 - Sublevel Registrar 1 and 2
4.1.11.3 - Sublevel Multiregistrar
4.1.11.4 - Sublevel Recorder
4.1.11.5 - Sublevel Replay (Last Call Repeat)
4.1.11.6 - Sublevel KeepAlive
4.1.11.7 - Sublevel Internal
4.1.11.8 - Sublevel Common
4.1.11.1
Sublevel Loglevel
Fig. 61 - System - EVOip active - Loglevel

The sublevel loglevel is used to specify the amount of information included in the log message.
Name
Value(s) [Default]
Description
globalLevel
- e.g. if the logFileLevel is
set to "Extended but the
globalLevel is only set to
"Medium", the log file level
"Medium".)
Off
Minimal

[Medium]

Extended

the log message.
Debug
Full debug
generated.
messages
will
be
97/316

Configuration
Name
Value(s) [Default]
consoleLevel
Off
(Only relevant if the EVOip
Minimal
active has been started
manually from the console.)
4.1.11.2

[Medium]

Extended

the log message.
Debug
Full debug
generated.
logFileLevel
Off
the log file of the EVOip Minimal
active.)
logFileSize
Description
messages
will
be

[Medium]

Extended

the log message.
Debug
Full debug
generated.
0 .. 10 MB
[10]
This value defines the maximum size

of the log file in megabytes. The log
file is created as a ring log file. This
means, if the log file size has been
reached the oldest entries will be
overwritten. The bigger the selected
log file size, the longer it will take until
messages
will
be
Sublevel Registrar 1 and 2
Fig. 62 - System - EVOip active - Registrar1

The sublevels Registrar1 and Registrar2 are used to specify the SIP registrar settings.
98/316

Configuration
4.1.11.3
Name
Value(s) [Default]
Description
IpAddress
Name or IP address
Enter the name or IP address of the

SIP registrar, server or proxy. If a
name is specified, a DNS has to be
available to resolve the name. If DNS
SRV is specified, this parameter has
to be the domain.
Expires
60 ... 3600 seconds

[3600]
Enter the registration expiration in

seconds. This value will automatically
be adapted to the min./max.
expiration value of the registrar.
DnsIpAddress
IP
Enter the IP address of the DNS

server if the system default specified
in the network configuration of the
recorder should not be used. Only
needed if the name of the registrar
needs to be resolved. Otherwise
leave this field empty.
Sublevel Multiregistrar
The sublevels Multiregistrar are used to specify up to 10 registrar settings including individual
extensions.
To activate Multiregistrar choose under System -> EVOip active -> Recorder -> Registration the
option Multiregistrar.
Fig. 63 - System - EVOip active - Multiregistrar
99/316

Configuration
Name
Value(s) [Default]
Description
Extension
SIP user name or

extension or range of
extensions
Enter the SIP user name or the phone

number / extenstion of the SIP
endpoint assigned to the EVOip
active. The EVOip active will use this
number to register at the specified
registrar and can be reached by other
SIP terminals. A range of extensions
can be specified with [begin-end]
(including brackets) where begin and
end have to be numerical extensions.
The range must not to exceed 1000
numbers.
Example: [1001-1005] will lead the
recorder to register the extensions
1001, 1002, 1003, 1004 and 1005 for
recording.
IpAddress
Name or IP address
Enter name or IP address of the SIP

registrar, server or proxy. If a name is
specified, a DNS has to be available
to resolve the name. If DNS SRV is
specified, this parameter has to be the
domain.
Expires
60 ... 3600 seconds

[3600]
Enter the registration expiration in

seconds. This value will automatically
be adapted to the min./max.
expiration value of the registrar (valid
for all Multiregistrars).
DnsIpAddress
IP
Enter the IP address of the DNS

server if the system default specified
in the network configuration of the
recorder should not be used. Only
needed if the name of the registrar
needs to be resolved. Otherwise
leave this field empty.
100/316

Configuration
4.1.11.4
Sublevel Recorder
Fig. 64 - System - EVOip active - Recorder

Name
Value(s) [Default]
Description
Extension
SIP user name or

extensions

numbers.
1001, 1002, 1003, 1004 and 1005 for
recording.
LocalIpAddress
IP address
Select the local IP address of the

interface that should be used for
recording. The first detected interface
is used as default.
If the IP address of an interface is
changed in the system network
configuration this parameter has to be
reconfigured manually.
LocalSipPort
[5060]
Enter the value of the SIP port for

incoming calls.
SipTransport
TLS
Select the type of the transport

protocol.
TCP
101/316

Configuration
Name
Value(s) [Default]
Description
[UDP]
DisableCertCheck
(only available if TLS is
selected as SipTransport)
[Yes]
No
Disable TLS certificate name check

and verification. Attention: Using TLS
without certificate authentification will
degrade security.
EnableClientCertification
(only available if TLS is
selected as SipTransport)
Yes
[No]
Enable TLS server mode.
SIPRealm
SIP Realm
SIP Realm identifies the line for the

SIP requests (separated by
semicolon)
Registration
[disabled]
Registrar1
Registrar2
both
Multiregistrar
Select the registrar where the

recorder should be registered. The
parameters of registrars have to be
specified in the corresponding
sublevel. For direct IP calls or trunk
recording registration has to be
disabled. Select both to register the
recorder on registrar 1 and registrar 2.
Select Multiregistrar if you want to use
several registrars with individual
extensions.
DigestAuthUser
User ID
User ID for SIP digest authentication.
DigestAuthPassword
Password
Password for SIP digest

authentication.
StereoCallIdentification
This parameter is only
necessary for specific PBX
integrations where two
separate calls have to be
combined into one stereo
channel.
[Automatic only]
This value detects stereo calls with

additional information provided by
signalling.
Even/odd recorder
extension
This value detects stereo calls by the

extensions of the recorder. This
means that an even extension and the
next following odd extension are
combined into one stereo channel.
[Continue
recording/insert
silence]
The recording will not be stopped

during hold and silence will be
inserted if no audio data is received.
Stop/restart recording
The recording will be stopped during

hold. A new recording will be started
after retrieve.
[Stop recording and

close call (BYE)]
In case of an external stop trigger the

recording will be stopped and the call
to the recorder will be closed by the
recorder via SIP BYE message.
A new call to the recorder is
necessary to start the recorder again.
OnHold
OnExternalStop
102/316

Configuration
Name
Value(s) [Default]
Description
Stop recording but

leave call established
In case of an external stop trigger the

recording will be stopped but the call
is left established until a SIP BYE is
received. The recording can be
started again as long as the call
remains established to the recorder.
The sublevel Recorder includes the sublevel:
4.1.11.4.1
4.1.11.4.1 - Sublevel Recorder - Alarming

4.1.11.4.2 - Sublevel Recorder - Codec
4.1.11.4.3 - Sublevel Recorder - Tagging
4.1.11.4.4 - Sublevel Recorder - Notification
Sublevel Recorder - Alarming
The sublevel Alarming is used to configure parameters for empty call alarming. Empty calls are
calls without received rtp data. Every empty call is logged in Alarming.log in ip_active folder.
Fig. 65 - System - EVOip active - Recorder - Alarming

4.1.11.4.2
Name
Value(s) [Default]
Description
AlarmEmptyCallsAmount
[10]
Specify the amount of empty calls

within certain period of time after
which an alarm will be issued.
AlarmEmptyCallsMinutes
[5]
During this period of time an alarm will

be issued if certain amount of empty
calls are received.
Sublevel Recorder - Codec
Fig. 66 - System - EVOip active - Recorder - Codec
103/316

Configuration
Name
Value(s) [Default]
CodecSelection
[Automatic]
(This setting is used to define
the codec negotiation method.)
Manual
4.1.11.4.3
Description
The recorder selects the most
preferred codec of the phone (one of
G.711 A-Law, G.711 -Law or G.729).
The recorder selects the most
preferred codec of the recorder which
is also supported by the phone.
Priority 1 is the highest and 3 is the
lowest. At least one codec has to be
enabled.
disabled
G711ALawPrio
[Prio 1]
(only available if
CodecSelection is selected as Prio 2
Manual)
Prio 3
Defines the priority of the G.711 ALaw.
disabled
711uLawPrio
Prio 1
(only available if
CodecSelection is selected as [Prio 2]
Manual)
Prio 3
Defines the priority of the G.711 Law.
disabled
G729Prio
Prio 1
(only available if
CodecSelection is selected as Prio 2
Manual)
[Prio 3]
Defines the priority of the G.729.
Sublevel Recorder - Tagging
Fig. 67 - System - EVOip active - Recorder - Tagging

Name
Value(s) [Default]
Description
OwnPhoneNumber
[From-Header]
To-Header
Contact-Header
Defines the SIP header that contains

the own phone number. Except for
special cases the From-Header
should be used.
104/316

Configuration
Name
Value(s) [Default]
Description
OwnPhoneNumberTagging
[Yes]
No
Enables tagging of own phone

number about header. Normally it
must be disabled if a CTIC is used.
PartnerPhoneNumber
[none]
To-Header
Contact-Header
From-Header
Diversion-Header
Defines the SIP header that contains

the partner phone number.
SipHeaderTagging
Yes
[No]
Defines the tagging of additional data

contained in the SIP extension header
of the INVITE message.
Call-Id
Enabled
[Disabled]
Enables tagging of SIP header field

Call-Id to ASCII1-ASCII20 assigned
field.
Configuration for the SIP Header Tagging
Fig. 68 - System - EVOip active - Recorder - Tagging

The option SipHeaderTagging is used for tagging additional data.
Name
Value(s) [Default]
Description
SipHeaderTagging
Yes
[No]
Enable this parameter to define the

tagging information.
SipHeader1 ... 5
X-...
Enter the name of the SIP extension

header to tag into the corresponding
database field (AssignedField1 ... 5).
Example: X-AgentID
105/316
4.1.11.4.4

Configuration
Name
Value(s) [Default]
Description
AssignedField1 ... 5
[disabled]
ASCII1
...
ASCII 20
Select the database field that should

be used for tagging of the
corresponding SIP extension header
(SipHeader1 ... 5).
Sublevel Recorder - Notification

The basic functionality of this feature is the provision of a recording notification when a SIP call
has been established to the EVOip active SIP. A pre-recorded audio file in the appropriate codec
and language (used for this SIP session) will be played back. In addition to that also the replay of
the corresponding ticket ID of this recording session (generated by the Recording Manager) has
to be provided by replaying each alpha numeric character of the ticket ID.
Fig. 69 - System -EVOip active - Recorder - Notification
Name
Value(s) [Default]
Description
disabled
Disables the functionality to replay a

message.
Play recording notification
Plays a recording message at the

beginning of a recording session.
Play ticket ID
Plays the internal ticket ID of this

recorded session. Therefore the ticket
ID creation in the Recording Manager
configuration has to be activated.
106/316

Configuration
4.1.11.4.4.1 Recording Notification
Fig. 70 - System -EVOip active - Recorder - Notification - Play recording notification

Displayed configuration items when selected "Play recording notification":
Name
Value(s) [Default]
Description
RepeatNotification
Yes
[No]
Indicates if the recording message will

be repeated in the specified interval.
NotificationInterval
1 ... 60 seconds
[30]
If "Repeat Message" is set to true the

message will be replayed in the
defined interval.
ExternalStart
Yes
[No]
Recording notification is only played

when voice message including
country code comes from UCVOIP.
107/316

Configuration
4.1.11.4.4.2 Ticket ID Announcement
Fig. 71 - System -EVOip active - Recorder - Notification - Play ticket ID

Displayed configuration items when selected "Play ticket ID":
Name
Value(s) [Default]
Description
PlayInitialMessage
Yes
[No]
Indicates if a pre-recorded message

will
be
replayed
before
the
announcement of the ticket ID.
PlayFinalMessage
Yes
[No]
Indicates if a pre-recorded message

will
be
replayed
after
the
announcement of the ticket ID
RepeatTicket
Yes
[No]
Indicates if the ticket ID will be

repeated after the first replay.
ExternalStart
Yes
[No]
Indicates if recording notification is

only played when voice message
including country code comes from
UCVOIP.
108/316

Configuration
4.1.11.4.4.3 Audio files

The EVOip active requires one audio file in the corresponding codec that is used for the sending
the audio data within the RTP packets. An audio file has to be available in the 3 supported
codecs:
G.711 A-Law
G.711 -Law
G.729 A
A replayed message will use the required audio files corresponding to the codec and to the
required content.
Within the EVOip active/media directory there will be the following folders:
Name
Description
defaultreplay
The directory where all default files (generated by ASC) are

stored as write protected files.
customreplay (has to be created) This directory has to be created in order to store custom
files. It is mandatory that all files with the same names of
"defaultreplay" are also located here - otherwise the
recording notification is not performed and an error is raised
in the log file of EVOip active
customreplay/xx-xx (has to be
created)
This directories are for language specific audio data. They

are only used in combination with special UCVOIP version
which hand over country codes and ExternalStart = true
(example for directory = "en-en").
The default files are created by ASC in english language.

The filenames have specified names that directly indicate the purpose and the codec - e.g.
"RecNotification.g711a"
"RecNotification.g711u"
"RecNotification.g729a"
"TicketID_InitialMsg.g711a"
... (in all 3 codecs)
"1.g711a"
"2.g711a"
"3.g711a"
...(up to)
"9.g711a"
"0.g711a"
109/316

Configuration
"A.g711a"
"B.g711a"
... (up to)
"Z.g711a"
NiceDay.g711a
NiceDay.g711u
NiceDay.g729
4.1.11.4.4.4 Failure scenarios
Whenever a required audio file is not available or cannot be opened an error message will be
generated in the log file. In case of such a failure no notification will be replayed. In no
circumstance the recording itself will be influenced and will continue until the end of the call.
The EVOip active needs to generate an error in the log file if "Play ticket ID" is configured but the
ticket ID creation is deactivated in recman.
If "TLS" is selected as transport protocol in the ADM/EVOip active configuration and also the
recording notification is activated an error will appear when storing these settings.
4.1.11.4.4.5 Limitations
The feature can only be used if the EVOip active is integrated to standard conference calls where
the TX stream of the EVOip active is recognized. There is no support of RTCP at the moment
within the EVOip active so the SIP environment has to support this as well.
Only available for:
EVOip active for Cisco (3 way conference)

Note: BIB (Built-in-bridge) is not possible as no TX stream to the calling device is possible.
EVOip active for SIP (as long as a TX stream is possible)

EVOip active for innovaphone
EVOip active for Unify OpenScape Voice (3 WAY CONFERENCE)
Encryption is not supported!
The customer specific audio files have to be transferred to the system via FTP access. Therefore
a specific user with a virtual directory to EVOip active/media has to be created. It is necessary to
provide write access for this user to be able to create the "customreplay" folder and upload the
required audio files. The audio files in the "defaultreplay" must not be modified.
It is the responsibility of the customer or partner to provide correct customer specific audio files i.e. the correct content and codec. The EVOip active is not able to identify if the codec or content
is incorrect - audio data from the file will just be transmitted via RTP.
110/316

Configuration
4.1.11.4.4.6 Example - Replay ticket ID

The EVOip active after connect plays a unique ID (eg. "12362") and this ID will be tagged into an
ASCII field.
Example:
1. Customer calls agent
2. Agent puts customer on hold
3. Agent calls EVOip active for SIP
4. EVOip active answers
5. EVOip active plays: ticket ID "12362"
6. EVOip active tags into ASCII1 the ID "12362"
7. EVOip active plays: "Have a nice day"
8. Agent takes down ID
9. Agent puts on 3 party conference
4.1.11.5
Sublevel Replay (Last Call Repeat)
Fig. 72 - System - EVOip active - Replay

The sublevel Replay is used to configure the optional Last Call Repeat (LCR) function which
provides the possibility to replay the last recorded call(s) with the EVOip active. To use this
function make sure to activate it in the Local Replay Service tab of the System screen (see
section 4.1.13 - Configuration Local Replay Service for details).
Name
Value(s) [Default]
Description
EnableReplay
Yes
[No]
Enables/disables the last call repeat

function.
111/316

Configuration
Name
Value(s) [Default]
Description
Extension
SIP user name or

extensions

numbers.
1001, 1002, 1003, 1004 and 1005 for
replay.
LocalIpAddress
IP address
Select the local IP address of the

interface that should be used for
replay. The first detected interface is
used as default.
LocalSipPort
[5062]
Enter the value of the SIP port for

incoming calls.
SipTransport
TCP
[UDP]
Select the type of the transport

protocol.
SIPRealm
SIP Realm
SIP Realm identifies the line for the

SIP requests (separated by
semicolon)
Registration
[disabled]
Registrar1
Registrar2
both
Select the registrar where the replay

should be registered. The parameters
of registrars have to be specified in
the corresponding sublevel. For direct
IP calls registration has to be
disabled. Select both to register the
replay on registrar 1 and registrar 2.
DigestAuthUser
User ID
User ID for SIP digest authentication.
DigestAuthPassword
Password
Password
for
authentication.
SIP
digest
HINT
Please note that the settings done at the recorder configuration do not
overlap with this configuration. The combination of extension, IP
address and port has to be unique for both configurations.
E. g. you cannot configure the recording for extensions 1001-1005 on a
specific IP with SIP port 5060 and use the same settings for LCR. At
least you have to vary one of the three parameters to get a unique
setting (e.g. use a different port[5062])
112/316

Configuration
4.1.11.6
Sublevel KeepAlive
Fig. 73 - System - EVOip active - KeepAlive

The sublevel KeepAlive is used to specify the keep alive settings.
Name
Value(s) [Default]
Description
KeepAliveMethod
[disabled]
Disables the keep alive.
INFO-Message
Keep alive via SIP INFO message (if

supported by the PBX).
Timeout
4.1.11.7
500 ... 10000 seconds Enter the keep alive timeout in

seconds.
[3000]
Sublevel Internal
Fig. 74 - System - EVOip active - Internal

The sublevel Internal displays some internal configuration values for informational purposes.
This values can not be changed in the ASC DataManager and the number of parameters may
vary from this figure.
113/316

Configuration
4.1.11.8
Sublevel Common
Fig. 75 - System - EVOip active - Common

The sublevel Common contents common parameters.
Name
Value(s) [Default]
Description
QueryForSrvRecords
[No]
Enables the DNS SRV mode.
Yes
4.1.12
DnsSrvCheckInterval
[300] seconds
Enter the desired interval in seconds

here. In case of failure of the primary
system, the EVOip active tries to
reconnect itself within this defined
time frame. But, the actual time
needed might be longer (interval +
registration time).
BigRtpBuffer
[Yes]
No
If Yes then ip_active worked with a rtp

buffer from 150 kb per channel. If no it
has only 30 kb rtp buffer.
Configuration License Server
Fig. 76 - System - License Server
114/316

Configuration
Name
Value(s) [Default]
Loglevel
GlobalLevel
medium.)

Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
ConsoleLevel
License Server is manually Minimal
LogFileLevel
the log file of the License
Server.)
LogFileSize
4.1.12.1
Description
messages
will
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[10]

messages
messages
will
will
be
be
Central License Server

Central License Server (CLS) configuration
1. Connect to the CLS via ASC DataManager.
2. Choose via ASC DataManager -> System the module API Server.
115/316

Configuration
3. Change the Interconnect Licensing Mode to Central License Server.

4. Press the button Reload configuration.
Fig. 77 - Configuring the CLS Mode
HINT
Ensure that both the client and the server connection are configured to
SSL encryption.
Upload the liclogids.loa

The liclogids.loa file is necessary and will be shipped with the dongle or dongle update file. This
file needs to be uploaded to the working directory of the license server. The following steps show
how to do this.
1. Connect to the CLS System via ASC DataManager.
2. Choose via ASC DataManager -> System the module License Server.
3. If the license server is configured in CLS mode, the following screen will appear:
Fig. 78 - Uploading the liclogids.loa

4. Press the button upload CLS Ids File.
5. Press the button Search.
Fig. 79 - Browsing for the liclogids.loa
116/316

Configuration
6. Search for your file on the local hard disk and press the button Open.
7. Press the button
to upload the file to the license server.
Fig. 80 - Sending the liclogids.loa

Configure the CLS
1. Connect to the CLS System via ASC DataManager.
2. Choose via ASC DataManager -> System the module License Server.
3. The following screen will appear:
Fig. 81 - Configuring the CLS

Description of the Client Section:
The clients section includes all clients already configured for the system.
The first client is always the local CLS itself with its:
Value
Description
LoggerID
The LoggerID of the local system
LoggerIDs
The LoggerIDs for the client systems
Details
Shows the details of each client
Licenses
License overview of available and granted licenses
117/316

Configuration
The section Details includes the following information:
Fig. 82 - Details Section

Value
Description
Connected
The connection status of the client (always Yes for CLS itself)
Hostname
The hostname of the client (always localhost for CLS itself)
Domain
The domain name of the client
IP Address
The IP address of the client
Description
The description of the client
Version
The current client version
MAC Address
One of three hardware identifiers
HDD SerialNumber
The HDD serial number
ProcessorID
The processor ID
The section Licenses gives you an overview over all licenses available for the system:
Fig. 83 - Licenses Section
118/316

Configuration
Value
Description
LicenseID
Unique identifier for each license
License
The name of the license
Count
The total number of licenses for the whole CLS environment
Available
The total number of licenses available for the clients
Assigned
The total number of licenses assigned to the currently selected client
Fig. 84 - Clients Section

4. Initially no client in the list LoggerIDs will be selected. To configure the CLS clients, always select
all in the list which shall be controlled Logger IDs by CLS.
HINT
De-selecting an already configured LoggerID (CLS client) will delete the
configuration for this client.
5. Press the button Save section.
7. Confiigure the CLS clients as described in chapter 4.1.12.2 - CLS Client Configuration.
119/316

Configuration
8. If the client is connected to the CLS Server, a new client section with the default IP address will
appear:
Fig. 85 - Client section with IP address

9. Select the LoggerID for this client.
10. Select the Licenses for this client.
11. Press the buttons Save section and Reload configuration.
120/316

Configuration
12. The licenses will be sent to the client and the following screen will appear:
Fig. 86 - Configuration Finished

4.1.12.2
CLS Client Configuration

For each CLS client
1. Connect to the CLS Client System via ASC DataManager.
2. Choose via ASC DataManager -> System the module API Server.
3. Change the Interconnect -> Master to the IP address of your central license server. Leave
Failover blank.
Fig. 87 - Configuring the CLS Client Mode
121/316

Configuration
4. Set Licensing to Managed by Central License Server.

5. Leave SSL to SSL and Sharing to No.
4.1.12.3
Dynamic Enterprise Licensing (Failover configuration)
A Dynamic Enterprise Licensing Model requires a Hot-Standby enviroment with identical physical
dongles. Both Central License Servers (CLS) have a connection to each other. Each client is
connected initially to the CLS Master. If the connection to the master is broken, each client
connects to the CLS Slave system automatically.
Fig. 88 - CLS Connection
122/316

Configuration
The configuration of the system will be done in the following way:
The example has the following parameters:

CLS Master with IP 192.168.1.113
CLS Slave with IP 192.168.1.121
CLS Client 1 with IP 192.168.1.117
CLS Master:
Connect to the CLS Master via ASC DataManager
Upload the liclogids.loa file as described in chapter 4.1.12.1 - Central
License Server
Choose via ASC DataManager -> System the module API Server.
Choose the Interconnect Section
Change the Interconnect Licensing mode to Central License Server
and change the field Failover to the IP adress of your CLS Slave.
Leave Master blank.
Fig. 89 - API Server Configuration of the CLS Master
CLS Slave:
Connect to the CLS Slave via ASC DataManager
Upload the liclogids.loa file as described in chapter 4.1.12.1 - Central
License Server. Choose via ASC DataManager -> System the module
APIServer

Change the Interconnect Licensing mode to Central License Server
Failover and change the field Master to the IP address of your CLS
Master System
Leave Failover blank.
123/316

Configuration
Fig. 90 - API Server Configuration of the CLS Failover
Each CLS Client:
Connect to each CLS Client via ASC DataManager

Choose via ASC DataManager -> System the module APIServer
Change the Interconnect Licensing mode to Managed by Central
License Server and change the field Master to the IP address of your
CLS Master and Failover to the IP address of your CLS Slave.
Fig. 91 - API Server Configuration Client

The configuration is now complete. Please check the configuration in the following way.
1. Connect to the CLS Master
2. Open the Portal and log in
3. Open the Event Log by double clicking the Status field
The Event Log should show the information the CLS Master is connected to the CLS Slave:
The Event Log has the information which server is connected to the clients an where the clients
could be configured:
The Event Log should show the information that all configured clients are connected to the CLS
Master or Slave:
124/316

Configuration
The clients can now be configured as described in chapter 4.1.12.1 - Central License Server
4.1.12.4
Sublevel WarnLevel
The warning level represents a mechanism that allows you to display messages in the alarm
management, when a certain recording license has reached a certain threshold.
The warning level can be set at the CLS as well as at the client. The setting on the CLS is only
present when it is a dynamic system and the licenses will be deducted from the CLS dynamically.
On the client, the settings are only available if it is a CLS client and if there was a file created
named notifyLicense in the directory of the recording manager.
The setting of the threshold is served in percent. That means that at a threshold value of 80 a
warning appears in alarm management if 80% of the licenses are used and only 20% are still
available.
To configure the warning level go to ASC DataManager -> Configuration -> System -> License
Server -> CentralLicenseServer -> WarnLevel:
Fig. 92 - System - License Server - CentralLicenseServer - WarnLevel
125/316

Configuration
4.1.13
Configuration Local Replay Service
Fig. 93 - System - Local Replay Service

The Local Replay Service tab is used to configure the optional Last Call Repeat function of the
recorders that provides the possibility to replay the latest call(s) via a connected telephone. It
consists of the sublevels loglevel, to configure the amount of information written into the log file,
and LCR to activate the LCR function via an EVOip active component.
4.1.13.1
Sublevel Loglevel
Fig. 94 - System - Local Replay Service - Loglevel

Name
Value(s) [Default]
Loglevel
GlobalLevel
medium.)
Description
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
will
be
126/316

Configuration
Name
Value(s) [Default]
Off
ConsoleLevel
(Only relevant if the Local
Replay Service is manually Minimal
LogFileLevel
the log file of the Local
Replay Service.)
LogFileSize
4.1.13.2
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[10]

messages
messages
will
will
be
be
Sublevel LCR
Fig. 95 - System - Local Replay Service - LCR

The sublevel LCR is used to activate the Last Call Repeat function via the EVOip active and to
configure individual settings.
To use this function, it is additionally required to define the EVOip active recorder that should be
called for replaying the latest calls in the sublevels LCR and Gatekeeper (see section 4.1.11.4.2
- Sublevel Recorder - Codec - Configuration for the SIP Header Tagging) of the EVOip active tab
in the System screen.
127/316

Configuration
Name
Value(s) [Default]
Description
EnableVOIP
Yes
[No]
Select Yes to activate the Last Call

Repeat function via an EVOip active
component. If you do not want to use
the LCR function, do not change the
default setting (No).
Language
[English]
Deutsch
This parameter defines the language

of the LCR function, i. e. of the
announcements like Please enter
your password.
SearchCountMaximum
1 - 100
[10]
Define the maximum number of

recorded calls that should be
available for replay at the EVOip
active recorder.
EnableTimeShiftLock
Yes
[No]
Enables time shift lock via special

logout key.
Users can flag the end of their shift by
pressing the * key on the telephone.
For every processed login the end of
a users shift will be stored. If the
same user logs in again, only the calls
that were received after the stored
end of the shift can be replayed. A
logout without TimeShiftLog can be
performed by pressing the 9 key.
TimeShiftOverlapping
[00:00:00]
Time shift overlapping duration

[hh:mm:ss].
Calls of the previous shift can be
replayed within the configurated
timeshift even if the logout key ("*")
was pressed.
HINT
The following Service SDDM (Selective Data Distribution Manager) is
deactivated by default. Deactivated Services are not listed in the
system module list. If you want to configure and use this service you
have to activate it and reload the ADM.
128/316

Configuration
4.1.14
Configuration Recording Manager
Fig. 96 - System - Recording Manager

Consistency check for the Recording Manager:
RIA Alerting
RIA Connect
Analog - Stop
PCM - Start
PCM - Stop
PRI int. passive - Start
PRI int. passive - Stop
PRI int. active - Start
PRI int. active - Stop
PRI ext. passive - Start
PRI ext. passive - Stop
MVTC - Start
MVTC - Stop
Phone
Connect
Alerting
OFF Hook
Analog - Start
IDLE Word
DTMF
COR
VOX
Contineous
Host
Ring
A consistency check of the record trigger based on INPUTsource and InputType will be
performed, because not all combinations are allowed. During the consistency check the ASC
DataManager will issue an error message if not at least one of the values per row of the table
below is set:
129/316

Configuration
* = in special cases
4.1.14.1
Sublevel Loglevel
Fig. 97 - System - Recording Manager- Loglevel

The log level specifies how detailed the log messages will be.
Name
Value(s) [Default]
Description
GlobalLevel
medium)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
ConsoleLevel
Recording Manager is
console)
messages
messages
will
will
be
be
130/316

Configuration
Name
Value(s) [Default]
Off
LogFileLevel
the log file of the Recording Minimal
Manager)
LogFileSize
4.1.14.2
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[1]

messages
will
be
Sublevel Specific Loglevels
Fig. 98 - System - Recording Manager- Specific Loglevels
131/316

Configuration
The specific log levels are useful to improve the messages for a certain module of the Recording
Manager.
Name
Value(s) [Default]
Off
RecManLevel
(Relevant for the Recording
Minimal
Manager specific
messages)
ComManLevel
(Relevant for command
messages from and to the
Communication Manager)
InputCtrlLevel
(Relevant for the hardware
specific messages)
CommandCtrlLevel
(Relevant for command
messages from and to the
Recording Manager)
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
messages
messages
messages
will
will
will
will
be
be
be
be
132/316

Configuration
Name
Value(s) [Default]
Off
ProcessCtrlLevel
(Relevant for messages on
Minimal
the internal processing of
the Recording Manager)

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
PackmanLevel
Minimal
the processing of call
packages)
messages
will
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
RecordCtrlLevel
Minimal
starting and stopping
communication recordings)
PriCtrlLevel
(Relevant for messages
from and to the PRI board)
Description
messages
will
be

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
messages
will
will
be
be
133/316

Configuration
Name
Value(s) [Default]
Description
AiLogixCtrlLevel
(Relevant for AiLogix
hardware specific
messages)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
IPMonCtrlLevel
(Relevant for EVOip
specific messages)
IPActiveCtrlLevel
(Relevant for EVOip active
specific messages)
ConnectionLevel
(Relevant for connection
messages)
messages
messages
messages
messages
will
will
will
will
be
be
be
be
134/316

Configuration
Name
Value(s) [Default]
Description
ScreenCtrlLevel
(Relevant for screen
recording messages)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
ConfigLevel
(Relevant for configuration
specific messages)
4.1.14.3
messages
messages
will
will
be
be
Sublevel Bus Configuration
Fig. 99 - System - Recording Manager- Bus Configuration

The bus configuration is used to define the connected bus system which transfers
communication data from the recording cards to the Communication Manager.
135/316

Configuration
Name
Value(s) [Default]
Description
BusMode
(This setting is used to
configure the connected
bus system)
H100_SLAVE
This value has to be used for a slave

on the H100 bus.
[H100_MASTER]
This value has to be used for the

master on a H100 bus.
MVIP_SLAVE

on the MVIP bus.
MVIP_MASTER

master on a MVIP bus.
SCSA_SLAVE

on the SCSA bus.
SCSA_MASTER

master on a SCSA bus.
2 Mbs
BusSpeed
select the bus speed for the
transfer of communication 4 Mbs
data between the recording
cards of the Recording
[8 Mbs]
Manager)
This value sets the bus speed to 2

Mbs
[A-Law]
BusLaw
configure the characteristic
-Law
line for communication
recording)
This setting suits all countries except

the USA.
IdleWord
configure the specific idle
word for the PBX )
0 .. 255
[0]

Mbs
Mbs
This setting is only for the USA.

It is recommended to set the specified
IdleWord for the connected PBX.
For example:
Unify PBX are often using:
213 (=0D5 hex) or 212 (=0D4 hex)
If IdleWord and IdleMask are not
properly configured you may get
truncated or concatenated calls.
It is also necessary to have properly
configured values for IdlePostTime
and IdleTimeMin to avoid truncated or
concatenated calls.
136/316

Configuration
Name
Value(s) [Default]
0 .. 255
IdleMask
[0]
mask the idle word in order
to soften the idle word. That
means that not only the idle
word but even similar bit
sequences will be accepted
as silence on the trunk)
Description
If you know the IdleWord it is
recommended to set the IdleMask to
255 (=0FF hex / 1111 1111 bin). But
the condition for this setting is a
definite IdleWord on the B-channel.
If there is no definite IdleWord e.g.
most significant bit (MSB) is jittering,
you have to use the IdleMask 127
(=07F hex / 0111 1111 bin) or if e.g.
the least significant bit (LSB) is
jittering, you have to use the IdleMask
254 (=0FE hex / 1111 1110 bin).
If IdleWord and IdleMask are not
properly configured you may get
truncated or concatenated calls.
It is also necessary to have properly
configured values for IdlePostTime
and IdleTimeMin to avoid truncated or
concatenated calls.
If the IdleMask and the IdleWord is set
to 0, the automatic idle word detection
will be activated. You can use this
setting if you dont know the correct
IdleWord.
IdleTolerance
0 .. 100 %
[5]
This parameter defines how many

percent of incorrect values will be
accepted for the idle detection. Only
values between 0 and 15 % are
reasonable.
137/316

Configuration
4.1.14.4
Sublevel Options
Fig. 100 - System - Recording Manager- Options

Name
Value(s) [Default]
Description
HH:MM:SS
MaxPackageDuration
(Maximum duration of a call [00:10:00]
package. This setting is
only relevant in conjunction
with storage mode
DIRECT_STORAGE)
0 ... 30000 ms
MinimumCallDuration
(If calls are shorter than the [0]
adjusted value the call will
be not recorded)
HH:MM:SS
ContinuousRestartTime
(If calls are longer than one [01:11:00]
day
[e.g.
continuous
recording channels], the
call will be split into
different packages at the
selected point of time)
BeepToneOutput
[Off]
No beep tone will be generated.
138/316

Configuration
Name
Value(s) [Default]
Description
On
The Telephone Interface generates a

beep tone which will be inserted
during communication recording if it
has been configured for the channel
under Configuration - Channels BeepToneEnable.
[Low]
The beep tone will be generated with

a low amplitude.
High
The beep tone will be generated with

a high amplitude.
Not pulsed
A static beep tone will be generated.
[Pulsed]
A pulsed beep tone will be generated.
FAX_FSK_Level
24 .. 60 dB
[39]

threshold for FSK fax tone detection.
FAX_FSK_Duration
40 .. 1280 ms
[200]

minimum fax tone duration.
FAX_Sine_Level
24 .. 60 dB
[39]

threshold for fax sine tone detection.
FAX_Sine_Duration
40 .. 1280 ms
[200]

minimum fax sine tone duration.
BeepToneAmplitude
BeepTonePulse
4.1.14.5
Sublevel Voip
Fig. 101 - System - Recording Manager- Options

Name
Value(s) [Default]
Description
EVOipActiveChannels
4 ... 2500
[240]
Number of EVOip active channels.

After change of this value a manual
restart of the recording manager is
necessary.
EVOipChannels
4 ... 2500
[500]
Number of EVOip passive channels.

After change of this value a manual
restart of the recording manager is
necessary.
139/316

Configuration
4.1.14.6
Sublevel ISDN Call Options
Fig. 102 - System - Recording Manager- ISDN Call Options

These options can be used to tag ISDN calls which are unanswered.
Name
Value(s) [Default]
Description
PRITaggingMode
Disabled
[For all calls]
Incoming calls only
Outgoing calls only
Enables call
decoding.
RingDurationASCIIField
[None]
Text 1 ... Text 20
RingDurationLongField
UnanswerdCallTag
by
ISDN
Select a text field where the ring

duration of the unanswerd call should
be tagged.
[None]
Number 1 ... Number 10
UnanswerdASCIIField
tagging
Select a number field where the ring

duration of the unanswerd call should
be tagged.
[None]
Text 1 ... Text 20
Select a ASCII field where the

message of an unanswerd call should
be tagged.
[unanswerd]
The value of the unanswered call

message.
140/316

Configuration
4.1.14.7
Sublevel Ticket ID
Fig. 103 - System - Recording Manager- Ticket ID

The Ticket ID will be used for the identification of calls.
Name
Value(s) [Default]
Description
Enable
[No]
With this value you deactivate the

creation of a Ticket ID.
Yes
With this value you can activate the

creation of a Ticket ID. This Ticket ID
will be available e. g. for the ESS API.
Numeric only
The Ticket
numbers.
[Alphanumeric]
The Ticket ID consists of numbers

and characters.
Length
3 ... 10
[8]

length of the Ticket ID. If you want to
have a unique Ticket ID you should
use a length of 10 digits. Be aware
that a short Ticket ID leads to earlier
repetition.
ASCIIField
None
Text 01 - 20
[Text 01]
With this value you can define in

which text field the Ticket ID will be
stored.
UseDescriptor
[No]
Only the Ticket ID will be stored.
Yes
The Ticket ID will be stored together

with a recorder descriptor. The
descriptor will be appended to the
Ticket ID.
CharacterSet
ID
only
consists
of
141/316
4.1.14.8

Configuration
Name
Value(s) [Default]
Description
DescriptorString
0-9 or A-Z
[0]

recorder descriptor which will be
appended to the Ticket ID (only one
digit).
ZeroFill
[No]
The Ticket ID will be stored without

leading zeros.
Yes
The Ticket ID will be filled up with

leading zeros.
Sublevel Hardware Configuration
Fig. 104 - System - Recording Manager- Hardware Configuration

Depending on the installed hardware you can see one or more of the following entries.
Name
Value(s) [Default]
CommunicationManager
Description
In this section you can see
information and make some settings
for the Communication Manager.
142/316

Configuration
Name
Value(s) [Default]
Description
Board_Information
In this section you can see the

information for the Communication
Manager.
BoardType
Here you can check the board type.

SerialNumber
Here you can check the serial

number. This value can not be
changed.
BootLoader
Here you can check the installed boot

loader version. This value can not be
changed.
Firmware
Here you can check the installed

firmware version. This value can not
be changed.
DSP-Module_1
Here you can check the DSP module

type. This value can not be changed.
DSP_Module_2
Here you can check the DSP module

Interface_1
Here you can check the local interface

Interface_2
Here you can check the interface type

on the expansion module. This value
can not be changed.
Configuration
In this section you can make some

settings for the Communication
Manager.
BusMaster
BusTermination
(The Communication
Manager with the highest
ID has to be terminated)
[Automatic (Master)]
Use this setting for automatical bus

master detection (recommended).
Yes
With this value you can activate this

Communication Manager as bus
master.
No
With this value you can set this

Communication Manager as slave.
Yes
With this value you can activate the

termination.
[No]
With this value you can deactivate the

termination.
[Use the setting from

BusLaw
(You can use a global Bus global bus configuration]
Law setting or individual for
A-Law
every Communication
Manager)
-Law
With this setting the global Bus Law

will be used.
A-Law will be used
Communication Manager.
for
this
-Law will be used

for
this
143/316

Configuration
Name
Value(s) [Default]
Description
Local_PRI_firmware
(You can choose the
firmware you currently
need in combination with
your PBX)
EDSS1_active
Unify PRI firmware
CAS_Selective_Recordin
g_Avaya
Avaya PRI firmware
ETRALI_PCM30
Etrali PRI firmware
AiLogix_Subsystem
In this section you can see some

information for the installed AiLogix
Board(s).
Version

smartworks version. This value can
not be changed.
HW_Information
Here you can check some values of

the installed AiLogix hardware. These
values can not be changed.
Board_X
BoardType
Here you can check the board type.

Firmware

firmware version. This value can not
be changed.
Number_Channels
Here you can check the number of

channels on the PRI board. This value
can not be changed.
BusMode
Here you can check the bus mode.

BusLaw
Here you can check the bus law type.

BusSpeed
Here you can check the bus speed.

Daughter_Card_X
PBX_Type
Here you can check the configured

PBX type. This value can not be
changed.
DChannel_Option
Here you can check if the D channel

option is enabled. This value can not
be changed.
Termination
Here you can check the type of

termination. This value can not be
changed.
Options
In this section you can make some

settings for the AiLogix hardware.
144/316

Configuration
Name
Value(s) [Default]
Description
NGX_BChannelMode
B1-Audio Stream
This setting defines that the audio

stream on the first B channel will be
recorded.
B1-Incoming Signal
This setting defines that only the

incomming signal on the first B
channel will be recorded.
B1-Outgoing Signal

outgoing signal on the first B channel
will be recorded.
B2-Audio Stream
This setting defines that the audio

stream on the second B channel will
be recorded.
B2-Incoming Signal

incomming signal on the second B
B2-Outgoing Signal

outgoing signal on the second B
Yes
This setting enables the VOX

detection of the NGX cards (needed
for special statemachines).
[No]
This setting disables the

detection of the NGX cards.
Disconnect_Delay
[No delay]
1-5 seconds
This setting will be used to bridge a

disconnection between the PBX and
the AiLogix board(s).
Enable_LogFiles
Yes
This setting enables the AiLogix log

files.
[No]
This setting disables the AiLogix log

files.
No buffering
1000;
2000 ... 10000 Events
[2000 Events]
This value defines how many entries

for each channel will be stored in the
AiLogix log file.
Activity_Detection
DC_Buffer_Size
VOX
145/316

Configuration
4.1.15
Configuration Selective Data Distribution Manager (SDDM)
Fig. 105 - System - Selective Data Distribution Manager

4.1.15.1
Log Level
The log level specifies how detailed the log messages will be.
Fig. 106 - Log Level

Name
Value(s) [Default]
Description
GlobalLevel
medium)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
will
be
146/316

Configuration
Name
Value(s) [Default]
Off
ConsoleLevel
(Only relevant if the SDDM
is manually started from the Minimal
console)
LogFileLevel
the log file of the SDDM)
LogFileSize
Description
be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[1]

messages
messages
will
will
be
be
147/316

Configuration
4.1.15.2
Central Server
The configuration of the central server settings.
Fig. 107 - Central Server

Name
Value(s) [Default]
ADAddress
Description
Please enter the IP address of the
central server for the ASCII data.
ADPort
0 .. 65535
[21]
Please enter the port for the FTP

connection to the central server.
ADUsername
[session]
Please enter the user name for the

FTP connection to the central server.
ADPassword
[session]
Please enter the password for the

ADFolder
[c:\temp\sddm\session]
Please enter the path of the ASCII

data folder. Only necessary if it is a
local file server (127.0.1).
BDAddress

central server for the binary data.
BDPort
0 .. 65535
[21]

connection to the central server.
BDUsername
[funk]

BDPassword
[funk]

148/316
4.1.15.3

Configuration
Name
Value(s) [Default]
Description
BDFolder
[c:\temp\sddm\funk]
Please enter the path of the binary

data folder. Only necessary if it is a
local file server (127.0.1).
File Server
Configuration of the file server system (only necessary if the file server is located on a remote
system).
Fig. 108 - File Server

Name
Value(s) [Default]
Description
Address
[127.0.0.1]
Please enter the IP address of the file

server for the call data.
Port
0 .. 65535
[21]

connection to the call data server.
Username
[asciaslocalaudio]

FTP connection to the call data
server.
Password
[asciaslocalaudio]

FTP connection to the call data
server.
Folder
[/calldata/CallPool]
Please enter the path of the call data

folder. Only necessary if it is a local
file server (127.0.1).
IPROSessionFolder
[D:\ASC\CallData\INSPIR The path for the INSPIRATIONpro

ATIONpro]
session files. The default value is the
Calldata folder.
149/316

Configuration
4.1.15.4
Transfer
Special transfer settings.
Fig. 109 - Transfer

4.1.15.5
Name
Value(s) [Default]
Description
TransferDelay
0..65535
[0]
This value delays the transfer of a

recorder audio (in minutes). E.g. the
call was recorded at 2009/05/24
14:00 and the transfer delay is set to 5
the call will be transferred via FTP at
2009/05/24 14:05.
DirectTransfer
No
[Yes]
If this value is enabled, the audio file

will be transferred without updating
the audio file header.
If files are transferred to another
systems with DirectTransfer=No the
encrypted audios will be transferred
without encryption.
SetToDeleteTimePoint
0..65535
[0]
This
value
changes
the
ToDeleteTimePoint of a local recorded
call (in minutes). 0 means do nothing,
1 means delete immediately. In case
of 1 each call transferred to a
subsystem
will
be
deleted
immediately on the local recorder by
the Delete Manager Module.
Call Reference Extractor

The Call Reference Extractor extracts all the calls performed during that day and puts the file on
customer's server via FTP for further analysis.
The name of the generated file will have the following format:
<prefix>.<date>.<IASid>
<prefix> is a configurable text, to be defined in an INI file
<date> is the date in the format YYMMDD
<IASid> is a configurable text, to be defined in an INI file in order to identify in a unique way the
IAS that is producing the file, because there are at least two IAS running this procedure and files
with unique names have to be generated.
150/316

Configuration
For example, the 2 files extracted on 2005, October 26, will have the following format:
u6.nas.r2.ftpxtg00.ordtelnw.d051026.IASMI
u6.nas.r2.ftpxtg00.ordtelnw.d051026.IASVR
Each record in the file will have the following format:
<date><ticket id>;<date time>;<operator userid>
1. The <date> field is 8 character long and has the following format: YYYYMMDD
2. The <ticket id> field contains the ticket assigned to the recording. According to project
specification, this field is the one related to Visual ID settings (see Unicredit project software
modification Phase 1 document - MTEVO_FSPEC_
MTVoIP_Unicredit_PB_Phase1_Features_0_10.doc, chapter 3.4.2). This data has to be read
from one of the ASCII fields. The field used (for example Ascii3) has to be configurable on the
.INI file.
3. The <date time> field is 19 characters in length. This string is the start time of the call and it has
the following format:
<YYYY-MM-DD HH:mm:ss>
HINT
There is a blank character between DD and HH.
4. The <operator userid> is the Operator ID (Agent ID) that started recording (the UserID used to
log-in to Call Manager) and is 7 character long.
For example:
2005092212345678;2005-09-22 13:25:47;4567890
The Path to the file is configurable via SDDM.
Fig. 110 - Call Reference Extractor

Name
Value(s) [Default]
Description
Prefix
[IAS]
The Prefix within a Call Reference

Extractor file.
151/316
4.1.15.6

Configuration
Name
Value(s) [Default]
Description
IASID
[1]
The ID within a Call Reference

Extractor file.
Path
[C:\temp\cde]
The local path to a Call Reference

Extractor file.
Field
[ASCII1]
The field for the TicketID.
Secure Transfer
Settings for secure file transfer.
Fig. 111 - Secure Transfer

Name
Value(s) [Default]
PublicKey
[C:\Program
The path and the file name of the
Files\ASC\EVOLUTION\bin\sddm\keys Public Key used for secure file
\ssh_host_key.pub]
transfer authentication.
PrivateKey
[C:\Program
The path and the filename of the
Files\ASC\EVOLUTION\bin\sddm\keys Private Key used for secure file
\ssh_host_key.ppk]
transfer authentication.
PassPhrase
[]
RWBufferSize 0..65535
[128] (kBytes)
Description
The password to decrypt the private

key if the file is encrypted.
The buffer size in kByte to read/write
the transfer data.
152/316

Configuration
4.1.16
Configuration Window Manager
Fig. 112 - System - Window Manager

Name
Value(s) [Default]
Loglevel
GlobalLevel
medium.)
ConsoleLevel
Window Manager is
console.)
Description
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
messages
will
will
be
be
153/316

Configuration
Name
Value(s) [Default]
Description
LogFileLevel
the log file of the Window
Manager)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[1]

LogFileSize
4.1.17
messages
will
be
System - Recording Interface Adapter (RIA)
Fig. 113 - System - Recording Interface Adapter

Name
Value(s) [Default]
Loglevel
Description
154/316

Configuration
Name
Value(s) [Default]
Description
GlobalLevel
medium)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[5]

ConsoleLevel
LogFileLevel
LogFileSize
messages
messages
messages
will
will
will
be
be
be
155/316

Configuration
Name
Value(s) [Default]
Description
Specific_Loglevels
APIServerProtocol
(The log level for the API
server communication)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
RIAConfig
(The log level for
configuration activities)
RessourceCtrl
(The log level for device
registration and licensing)
4.1.18
messages
messages
messages
will
will
will
be
be
be
Configuration Avaya Interface

The tab Avaya Interface is used to configure the Avaya Interface for active VoIP recording.
156/316

Configuration
Select Yes to activate the Avaya Interface.
Fig. 114 - System - Avaya Interface

The tab Avaya Interface includes the following sublevels:
4.1.18.1 - Sublevel Operation Mode

4.1.18.2 - Sublevel Communication Manager
4.1.18.3 - Sublevel AES Server
4.1.18.4 - Sublevel Softphones
4.1.18.5 - Sublevel Recorder
4.1.18.6 - Sublevel Alarm Management
4.1.18.7 - Sublevel RTP
4.1.18.8 - Sublevel Audio
4.1.18.1
Sublevel Operation Mode
Fig. 115 - System - Avaya Interface - Operation Mode

The sublevel Operation Mode includes parameters to enable or disable the CTI mode.
157/316

Configuration
4.1.18.2
Name
Value(s) [Default]
Description
CTI
[No]
The Avaya Interface creates an

appropriate number of softphones for
the physical devices to be monitored.
Every physical device is assigned a
specific softphone exclusively.
As soon as the Avaya Interface is
started, all created softphones will be
set to service observe mode.
When a call is initiated, the Avaya
Interface transmits the required
tagging information for this call to the
recorder.
Yes
The Avaya Interface provides a

specific number of softphones. They
have to be made known to the RIA
server.
If a physical device to be monitored is
involved in a call, the RIA server
initiates a single step conference from
this call to an available softphone.
At the beginning of a call, the RIA
server transmits the required tagging
information for this call to the
recorder.
Sublevel Communication Manager
Fig. 116 - System - Avaya Interface - Communication Manager

The sublevel Communication Manager includes the connection parameters to the Avaya
Name
Value(s) [Default]
Description
IP
[0.0.0.0.]
The IP address of the

Avaya
Name
[s8300]
The
name
of
the
Avaya
158/316

Configuration
4.1.18.3
Sublevel AES Server
Fig. 117 - System - Avaya Interface - AES Server

The sublevel AES Server includes the connection parameters to the Avaya AES server.
Name
Value(s) [Default]
Description
IP
[0.0.0.0.]
The IP address of the AES server.
PortEncrypted
0 ... 4294967295
[4722]
The communication port of the AES

server in case of encrypted data
exchange.
PortUnencrypted
0 ... 4294967295
[4721]
The communication port of the AES

server in case of unencrypted data
exchange.
Secure
No
Disables the secure data exchange.
[Yes]
Enables the secure data exchange.
TrustStoreLocation
The path and file name of the AES

certificate. If this field is empty the file
is located under
/usr/asc/bin/AvayaInterface/recources
/avaya.jks.
User
The user name to connect to the AES

server.
Password
The password to connect to the AES

server.
SessionDurationTimer
0 ...4294967295
(seconds)
[180]
Defines the timespan till the session

will be disconnected.
159/316
4.1.18.4

Configuration
Name
Value(s) [Default]
Description
SessionCleanupDelay
0 ...4294967295
(seconds)
[0]
Defines the timespan till the active

session will be deleted. The value 0
indicates that the session will be
deleted
immediately
after
disconnecting.
Sublevel Softphones
Fig. 118 - System - Avaya Interface - Softphones

The sublevel Softphones includes parameters which determine the extentions of the softphones.
Only three number ranges can be configured (SoftphoneRange_0 to SoftphoneRange_2). The
number range to be used is configured by entering the first number of the range (Range-Start)
and the length of the range (RangeLen).
Name
Value(s) [Default]
Description
RangeStart
0 ...4294967295
First extention number of this range.
RangeLeng
0 ...4294967295
Length of the extension range.
SoftphoneRange_0 ... 2
160/316

Configuration
4.1.18.5
Sublevel Recorder
Fig. 119 - System - Avaya Interface - Recorder

The sublevel Recorder includes parameters to connect to the MARATHON EVOLUTION server.
4.1.18.6
Name
Value(s) [Default]
Description
IP
[0.0.0.0]
IP address of the
EVOLUTION recorder.
MsgPort
0 ...4294967295
[8765]
IP port for exchanging XML

messages between the Avaya
interface and the EVOip passive
module.
ReconnectDelay
0 ...4294967295
(seconds)
[15]
Delay for reconnection to the EVOip

passive module running on the
MARATHON EVOLUTION recorder.
MARATHON
Sublevel Alarm Management
Fig. 120 - System - Avaya Interface - Alarm Management

The sublevel Alarm Management includes the connection parameters to the Alarm management.
Name
Value(s) [Default]
Description
IP
[127.0.0.1]
IP address of the Alarm Management.
Port
0 ...4294967295
[4567]
Port of the Alarm Management.
161/316
4.1.18.7

Configuration
Name
Value(s) [Default]
Description
ReconnectDelay
0 ...4294967295
(seconds)
[15]
Delay for reconnection to the Alarm

Management module running on the
Sublevel RTP
Fig. 121 - System - Avaya Interface - RTP

The sublevel RTP includes parameters for the RTP stream from the Avaya PBX to the
4.1.18.8
Name
Value(s) [Default]
Description
RtpTargetIP
[0.0.0.0]
IP address for the RTP streams.

Please note that is necessary to fill
this field with the appropriate IP
address
of
the
MARATHON
EVOLUTION recorder.
RtpBasePort
0 ...4294967295
[22222]
IP port for the RTP streams.
RtcpTargetIP
[0.0.0.0]
IP address for the RTCP streams.

Please note that is necessary to fill
this field with the appropriate IP
address
of
the
MARATHON
EVOLUTION recorder.
RtcpBasePort
[22223]
IP port for the RTCP streams.
Sublevel Audio
Fig. 122 - System - Avaya Interface - Audio
162/316

Configuration
The sublevel Audio includes parameters for the Audio stream from the Avaya PBX to the
Name
Value(s) [Default]
Encryption
AUTOMATIC: NONE or
AES
Codec
4.1.18.9
Description
NONE
The audio stream is not encrypted.
[AES]
The audio stream is AES encrypted.
G.711U or G.711A
[G.711U]
G.711A
G.729
G.729A
G.723
Select the audio data compression

configured at the Avaya PBX. The
codec G.723 will not be supported at
the moment.
Sublevel Loglevel
Fig. 123 - System - Avaya Interface - Loglevel

The sublevel Loglevel specifies how detailed the log messages will be.
Name
Value(s) [Default]
Description
globalLevel
- e. g. if the log file level is
medium)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
will
be
163/316

Configuration
Name
Value(s) [Default]
Description
consoleLevel
(Only relevant if the Avaya
interface is manually
started from the console)
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
1 .. 10 MB
[1]

logFileLevel
the log file of the Avaya
interface)
logFileSize
4.1.19
messages
messages
will
will
be
be
VCAM (Visual Central Alarm Management)

The VCAM service is disabled by default. For activating VCAM you have to start the process as
described in chapter 4.1.1 - Start/Stop and Activate/Deactivate Processes. Return to the
164/316

Configuration
MARATHON EVOLUTION Portal and start the ASC DataManager again to activate the changes.
Now you can select the VCAM module in the System menu.
Fig. 124 - System - VCAM

4.1.19.1
Sublevel Identification
Fig. 125 - System - VCAM - Identification

Name
Value(s) [Default]
Description
alarm-user
User to log in to the

alarmmanagement.
alarm-pw
Password to log in to the

alarmmanagement.
HINT
A user CTIC with password CTIC with at least user rights Alarm
Notification and Client Login has to be configured on all observed
servers.
165/316

Configuration
4.1.19.2
Sublevel Alarm Connections
Fig. 126 - System - VCAM - Alarm Connections

Name
Value(s) [Default]
AddConnection
Description
Adds a new connection.
Connection-1 ... n
IP
IP address of the observed server.
Port
0 ... 4294967295
[4000]
IP port of the observed server.
Type
Recorder
The observed server is a recorder.
CTIC
The observed server is a CTIC

system.
IAS
The
observed
server
INTERACTION Software.
Delete Connection
is
an
Deletes the current connection.
HINT
The changes take effect after restarting the VCAM server.
166/316

Configuration
4.1.19.3
Sublevel Alarm Notification
Fig. 127 - System - VCAM - Alarm Notification

Name
Value(s) [Default]
Description
email-sender
Email address of the sender.
SMTP-server
Address of the SMTP server.
SMTP-user
User name of the SMTP server.
SMTP-password
Password for the SMTP server.
email-recipients
Email address of the receiver.
SNMP-recipients
SNMP address of the receiver.
UTCforSNMP
[No]
Yes
Use UTC time stamp for the SNMP

traps.
HINT
The changes take effect after restarting the VCAM server.
167/316

Configuration
4.1.20
Recording Manager
Fig. 128 - Recording Manager
Fig. 129 - Recording Manager - loglevel

The sublevel Loglevel specifies how detailed the log messages will be.
Name
Value(s) [Default]
globalLevel
Description
All log levels will be restricted to the
global level- e. g. if the log file level
isset to extended but the global level
is only set to medium, the log file level
will also be reduced to medium.
Off
Minimal

be generated.
[Medium]
Error, warning, hint, and detailed

Extended

be generated.
Debug
Full debug
generated.
messages
will
be
168/316

Configuration
Name
Value(s) [Default]
consoleLevel
Only
relevant
if
the
ScreenProxyinterface is manually
started from the console.
Off
Minimal

be generated.
[Medium]

Extended

be generated.
Debug
Full debug
generated.
logFileLevel
logFileSize
Description
messages
will
be
Relevant for the entries in the log file

of the ScreenProxyinterface.
Off
Minimal

be generated.
[Medium]

Extended

be generated.
Debug
Full debug
generated.
1 .. 10 MB
[10]

if the log file size has been reached,
the
oldest
entries
will
be
overwritten.The bigger the log file, the
longer it takes to overwrite the oldest
entries.
messages
will
be
169/316

Configuration
Fig. 130 - Recording Manager - specific log level
Name
Value(s) [Default]
RecManLevel
Description
The log level for the Recording
Manager
Off
Minimal

be generated.
[Medium]

Extended

be generated.
Debug
Full debug
generated.
CommManLevel
messages
will
be
The log level for the Communication

Managers
Off
No log messages will be generated
Minimal

be generated
[Medium]

Extended

be generated.
170/316

Configuration
Name
Value(s) [Default]
Description
Debug
Full debug
generated.
InputCtrLevel
messages
will
be
The log level for the Input Controls

Off
Minimal

be generated.
[Medium]

Extended

be generated.
Debug
Full debug
generated.
CommandCtrlLevel
messages
will
be
The log level for the Command

Control
Off
Minimal

be generated.
[Medium]

Extended

be generated.
Debug
Full debug
generated.
ProcessCtrlLevel
messages
will
be
The log level for the Process Control

Off
Minimal

be generated
[Medium]

Extended

be generated
Debug
Full debug
generated.
PackmantLevel
The log
Manager
messages
level
for
the
will
be
Package
Off
Minimal

be generated
[Medium]

171/316

Configuration
Name
Value(s) [Default]
Description
Extended

be generated.
Debug
Full debug
generated.
RecordControlLevel
messages
will
be
The log level for the Recording

Control
Off
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
PriCtrlLevel
messages
will
be
The log level for the PRI Control

Off
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
AiLogixCtrlLevel
messages
will
be
The log level for the AiLogix Control

Off
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
IPMonCtrlLevel
messages
will
be
The log level for the IP-Passive

Control
Off
Minimal

be generated
172/316

Configuration
Name
Value(s) [Default]
Description
[Medium]

Extended

be generated.
Debug
Full debug
generated.
IPActiveCtrlLevel
messages
will
be
The log level for the IP-Active Control

Off
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
ConnectionLevel
messages
will
be
The log level for the Connections

Off
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
ScreenCtrlLevel
messages
will
be
The log level for the Connections

Off
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
ConfigLevel
messages
will
be
The log level for the configuration

activites
Off
173/316

Configuration
Name
Value(s) [Default]
Description
Minimal

be generated
[Medium]

Extended

be generated.
Debug
Full debug
generated.
messages
will
be
Fig. 131 - Recording Manager - Bus Configuration
Name
Value(s) [Default]
BusMode
Description
The bus mode to use between modes
H100_SLAVE
H100_MASTER
MVIP_SLAVE
MVIP_MASTER
SCSA_SLAVE
SCSA_MASTER
BusSpeed
The speed of the used bus

2Mbs
4Mbs
8Mbs
BusLaw
The compression of audio

transferred by bus or PCM30
data
A-Law
-Law
174/316

Configuration
Name
Value(s) [Default]
Description
IdleWord
The idle word pattern used for PCM30
IdleMask
The bitmask to use with the PCM30

idle word pattern
IdleTolerance
0-100%
The tolerance to use for idle word

detection
Fig. 132 - Recording Manager - Options
Name
Value(s) [Default]
Description
MaxPackageDuration
00:00:30 - 03:00:00
[00:10:00]
The maximum duration of call

packages
in
conjunction
with
DIRECT_STORAGE
[[DDDDD
]HH:MM:SS].
MinimumCallDuration
0 - 30000
[0]
The minimum duration in milliseconds

of a call to be stored to the database.
ContinuousRestartTime
00:00:00 - 23:59:59
[01:11:00]
Time to close and restart continuous

channels.
BeepToneOutput
[Off]
On
Activate beep tone generator
BeepToneAmplitude
[Low]
High
The amlitude of the inserted beep

tone.
BeepTonePulse
Not pulsed
[Pulsed}
The pulse mode of the inserted beep

tone.
175/316

Configuration
Name
Value(s) [Default]
Description
FAX_FSK_Level
24dB - 60dB
[39db]
Threshold value for sensitivity of FSK

Fax tone detection.
FAX_FSK_Duration
40ms - 1280ms
[200ms]
Minimum FAX tone duration
FAX_Sine_Level
24dB - 60dB
[39dB]
Threshold value for sensitivity of FAX

Sine tone detection.
FAX_Sine_Duration
40ms - 1280ms
[200ms]
Minimum FAX Sine tone duration.
FAX_ASCII_Field
None - Text 20
[None]
The text field to receive the FAX

tagging.
FAX_Tagging
[FAX]
The tagging for FAX recordings.
Fig. 133 - Recording Manager - Voip
Name
Value(s) [Default]
Description
EVOipActiveChannels
4 - 2500
[240]
The number of VoIPActiveChannels
EVOipChannels
4 - 2500
[500]
The number of VoIPPassiveChannels
Fig. 134 - Recording Manager - ISDN CallOptions
Name
Value(s) [Default]
Description
PRITaggingMode
Disabled
Enable call tagging by ISDN decoding
176/316

Configuration
Name
Value(s) [Default]
Description
[For all calls]

Incoming calls only
Outgoing calls only
RingDurationASCIIField
None - Text20
[None}
The text field to fill with the ring

duration.
RingDurationLongField
None - Number10
[None}
The number field to fill with the ring

duration.
UnansweredASCIIField
None - Text20
[None]
The text field to

unanswered call tag.
UnansweredCallTag
[unanswered]
The text to tag to unanswered calls.
fill
with
the
Fig. 135 - Recording Manager - TickedID
Name
Value(s) [Default]
Description
Enable
[No]
Yes
Enable the creation of TicketIDs
CharacterSet
Numeric only
[Alphanumeric]
The character set to use for the

TicketID
Length
3 - 10
[8]
The length of the TicketID
ASCIIField
None - Text20
[Text20]
The text field to fill with the TicketID
UseDescriptor
[No]
Yes
Append a recorder descriptor to the

TicketID
DescriptorString
[0]
The
alphanumeric
recorder
descriptor. One character or digit only.
ZeroFill
[No]
Yes
Fill the TicketID with leading zeros.
177/316

Configuration
Fig. 136 - Recording Manager - Hardware Configuration
Name
Value(s) [Default]
Description
AiLogix_Subsystem
Version
Installed smartworks version
HW_Information
Options
NGX_BChannelMode
The B-Channel to use for all NGX

channels.
[B1-Audio Stream]
B1-Incoming Signal
B1-Outgoing Signal
B2-Audio Stream
B2-Incoming Signal
B2-Outgoing Signal
Activity_Detection
Yes
[No]
Enable activity detection
Disconnect_Delay
No delay - 5 seconds
[No delay]
Delay for recording stop due to line

disconnects.
Enable_LogFiles
Yes
[No]
Enable DChannel log files for NGX

channels.
DC_Buffer_Size
No buffering
Events
[2000 Events]
10000 DChannel buffer size for all NGX

channels
178/316

Configuration
4.1.21
System - Errors
Fig. 137 - System - Errors

In a later version it will be possible to configure different errors.
4.2
Configuration - Alarm Notifications

In this area the alarm notifications can be configured.
Copy
Paste
Paste
to all
Reload
Logout
Fig. 138 - Alarm Notifications
179/316

Configuration
Above this list there is a toolbar providing the following

configuration:
buttons for alarm notifications
Copy:
Copies the selected entry
Paste:
Pastes the
entry/entries
Paste to all:
Pastes the copy content to the whole list
Reload:
Reloads the last saved settings
Logout

window
copy
content
to
the
selected
SMTP Settings:
Sender
Please
enter
an
email
address
like
MARATHON@asc.de. The domain must be valid!
SMTPServer
Please enter the IP address of the email (SMTP)

server
User
If the SMTP server requires a user login please

enter the user name in this field
Password
If the SMTP server requires a password please

enter the password in this field
SMTP Timeout [secs] Please enter the value for the SMTP timeout in
seconds.
Additional SNMP setting:

UTC for SNMP
Use UTC time stamp for the SNMP traps.
SNMP Get
With SNMP-GET packets, values of network

elements can actively be requested. The
AlarmManager will support the request of the
system state via SNMP-GET if the SNMP service
has been started and has been correctly
configured. This option enables or disables this
function.
SNMP Status
Address
As soon as the system state (OK, Warning or

Error) changes, an SNMP message with the new
state will be sent to the network elements
specified here. You can enter several addresses,
seperated by commas.
Community
Default is public.
You can configurate the community string which
will used by the SNMP Traps. The maximum
length of the string is 32 characters. You can only
use the characters a-z and the numbers 0-9.
SNMP Timeout [secs] If this time period is exceeded for the transfer of
the SNMP message, a warning will be displayed in
the event log. This does not mean that the
message was not transferred, but it may point out
that there are problems.
180/316

Configuration
The screen shows the following information/columns:

Module
Shows the module where the error occurs
Value
Shows the message code.

By clicking the icon
a window with detailed
information will be displayed (see Fig. 139 - Alarm
Notification Information Box).
Persistent
You can activate and deactivate persistent. If you

activate persistent, a new persistent message will
be created for seperate configuration.
LType
Shows the message type
Action
In this column you can see the alarm actions.

By clicking the button you can configure actions.
You can activate or deactivate the following:
Default configuration (activate Default Info
Action)
Beep
Permanent Beep
Acoustic Relais
Optical Relais
Default Info Action
Default Warn Action
Default Error Action
Restart Module
SNMP
Here you can type in the SNMP-Server

address(es) - separated by semicolon - the alarm
messages should be sent to
Email
Here you can type in the email address(es) separated by semicolon - the alarm messages
should be sent to
Active
Select this option to receive a notification when an

error/warning/hint/audit occurs
Update
Select this option to receive a notification when an

error/warning/hint/audit occurs again while the
same error/warning/hint/audit is already active
Reset
Select this option to receive a notification after the

error/warning/hint/audit has been solved
181/316

Configuration
Saves the current configuration of the Alarmnotifications
Fig. 139 - Alarm Notification Information Box

The information box shows the following information:
Code
Shows the error code of the corresponding

module.
Description
Shows the description of the error code.
To Do
Shows the to do list of the occured error.
182/316

Configuration
4.3
Configuration - Channels
This menu is used for hardware configuration and channel assignment of every specific recorder.
Show Print Second Copy

Paste
license config. channel channel channel
info
marking config. config.
mode
Paste
Search
config.
to all
channels
Export
config.
Import
config.
Reload Logout
config.
Fig. 140 - Configuration of the channels

Above this list there is a toolbar providing the following buttons for channel configuration:
Show license
information:
Shows the current status of the licenses
Print configuration:
Prints the current channels list (not available if

Second channel
marking mode
By marking a number of channels, every second

channel will be selected. This is especially useful
for the configuration of stereo channels.
Copy channel
configuration:
Paste channel
configuration:
Pastes the
entry/entries
copy
content
to
the
selected
183/316

Configuration
Paste configuration
to all channels:
Search:
Searches for a channel in the list
Export configuration: Exports the whole channel configuration

Import configuration: Imports the whole channel configuration
Reload
configuration:
Logout

window
Checks the whole channel configuration
Resets the selected channel configuration to the last saved settings
Resets the whole channel configuration to the last saved settings
Saves the current channel configuration
Name
Value(s) [Default]
Description
*RecordStartMode
[HOST
(External application)]
The recording will be started by an

external application (e.g. user
programmed application which is
using the Start/Stop-API).
CONTINUOUS
(Always recording)
This channel is always recording

independent of the signals.
[VOX (Signal level)]
The recording will be started if the

selected
VOXLevel
has
been
exceeded for the minimum VOX time.
COR (Contact operation)
The recording will be started if there is

a low voltage on the contact
(telephone is off-hook).
IDLEWORD
(Idle word pattern)
The recording will be started if there

has been no idle word pattern on the
stream during the minimum idle time.
OFF-HOOK
(On-Hook/Off-Hook
detection)
The recording will be started if the

telephone is hooked off.
ALERTING (Conversation The recording will be started with the

indication)
first ringing of the telephone.
184/316

Configuration
Name
Value(s) [Default]
Description
CONNECT (Conversation The recording will be started if the

detection)
telephone connection has been
established.
PHONE (Phone key)
The recording will be started via the

telephone keys.
DTMF-Sequence
(DTMF sequence)
The recording will be started if a

DTMF sequence is received. The
different sequences for starting,
stopping, muting and resuming, keep
and delete can be configured in the
system configuration of the API
Server
(see
section
4.1.5
Configuration API Server).
RING (Triggerd by ring The recording will be started if the

tone detection)
configured ring level has been
exceeded for the minimum ring
duration.
RIA_ALERTING
(Triggered by external configured
RIA
indicates
a
conversation
indication conversation.
(RIA) )
RIA_CONNECT (Triggerd The recording will be started if a
by external conversation configured
RIA
detects
a
detection (RIA) )
conversation.
*RecordStopMode
[- (Use the triggers from The recording will be stopped if the

recording start)]
stop trigger according to the start
trigger has been detected.
HOST
(External application)
The recording will be stopped by an

external application (e.g. user
VOX
(Signal level)
The recording will be stopped if the

selected VOX level has been underrun for the VOX post time.
COR
(Contact operation)
The recording will be stopped if there

is a high voltage on the contact
(telephone is on-hook).
IDLEWORD
(Idle word pattern)

stream contained the idle word
pattern for the idle post time.
OFF-HOOK
(On-Hook/Off-Hook
detection)

telephone is on-hook.
CONNECT (Conversation The recording will be stopped if the

detection)
telephone connection has been cut
off.
PHONE (Phone key)
The recording will be stopped via the

telephone keys.
185/316

Configuration
Name
Value(s) [Default]
Description
DTMF-Sequence
(DTMF sequence)

Server
(see
section
4.1.5

RIA
detects
a
detection (RIA) )
conversation.
StorageMode
NO_STORAGE
(No storage)
No communication will be recorded

(makes only sense for testing
purposes).
[DIRECT_STORAGE
(Store immediately)]
The communication will be stored

immediately after the end of a call or
after the end of a call package.
This setting can not be used with
recording profiles.
COMPLETE_CALL_INFO Should not be used

(Store when all call data is
available)
*VoxLevel
EXTERN_SAVE
(recording planned)
This setting should be used for

recording planned scenarios if the
calls should be deleted initially.
All communications will be deleted
except for those the user wants to
keep (using an external command,
e.g. via DTMF sequence or user
Dont forget to configure a
recording profile for keep/delete
functionality.
EXTERN_DELETE
(recording planned)
This setting should be used for

recording planned scenarios if the
calls should be saved initially.
All communications will be saved
except for those the user wants to
delete (using an external command,
Dont forget to configure a
recording profile for keep/delete
functionality.
0 .. 62 dB
[20 dB]
The threshold which has to be

exceeded for the minimum VOX time
to
identify
the
signal
as
communication.
186/316

Configuration
Name
Value(s) [Default]
Description
Timespan_Until_Deletion YY:MM:DD:HH:mm
[00:00:00:00:00]
The communication will be stored for

the selected time span (if there is
sufficient
hard
disk
capacity
available). After the defined time span
has run out, the call data will be
deleted.
The call information in the database
can be kept forever, immediately
deleted or deleted after a configured
time interval. Please refer to chapter
"4.1.8
Configuration
Delete
Manager" for this setting.
The default value 00:00:00:00:00
means that the oldest calls will be
deleted at first if there is no more
space available on the hard disk.
CLIEnable
Yes
The CLI (Caller Line Identification) will

be stored as call information.
[No]
The CLI (Caller Line Identification) will

not be stored.
Yes
The DTMF (Dual Tone Multi

Frequency) signal will be stored as
call information.
[No]
The DTMF (Dual Tone Multi

Frequency) signal will not be stored.
[0..51] * 100 ms
[20]
The pre trigger is a communication

buffer. If the start trigger has been
detected, the content of the pre
trigger buffer will be stored at the
beginning of the communication. The
selected value should be the same or
greater than the value for the
minimum VOX time resp. minimum
IDLE time.
*DTMFEnable
*PreTrigger
PCM_A_LAW
*Compression
(The greater the
compression the lower is
the storage requirement on
the hard disk or archive
media)
The recording characteristic is a-law

(everywhere except U.S.A.) without
compression. Use this setting to
achieve the best replay quality.
PCM_U_LAW
The recording characteristic is -law

(format
for
U.S.A.)
without
compression. Use this setting to
achieve the best replay quality.
ADPCM_40 (40 kbps)
The compression rate is 40 kbps. Use

this setting to achieve a very good
replay quality.
ADPCM_32 (32 kbps)

this setting if you want to achieve a
good replay quality.
187/316

Configuration
Name
Value(s) [Default]
Description
ADPCM_24 (24 kbps)

this setting for a satisfying replay
quality.
[ADPCM_16 (16 kbps)]

this setting for a sufficient replay
quality.
SPIRIT_4.8 (4.8 kbps)
The compression rate is 4.8 kbps.

Use this setting for good replay
quality and very high compression.
This setting is only available with the
appropriate license.
*VoxPostTime
(Only important if the stop
trigger VOX has been
selected)
100ms+[0..1023] * 100ms If the VOX level has been under-run

for the selected VOX post time the
[79]
recording will be stopped. Select a
value high enough not to separate
one call into two calls but low enough
not to concatenate different calls.
*VoxTimeMin
(only important if the start
trigger VOX has been
selected)
100 ms .. 3200 ms
[1000 ms]
*IdlePostTime
(only important if the stop
trigger IDLEWORD has
been selected)
100ms+[0..1023] * 100ms If the Idle word pattern has been

detected
during
the
selected
[49]
IdlePostTime, the recording will be
stopped. Select a value high enough
not to separate one call into two calls
but low enough not to concatenate
different calls.
*IdleTimeMin
(only important if the start
trigger IDLEWORD has
been selected)
100 ms .. 3200 ms
[500 ms]
If there has been no Idle word pattern

on the stream for the selected
minimum IDLE time the signal will be
accepted as a regular call. This value
defines the length of the shortest call
on your system.
*RingLevel
0 .. 62 dB
[36]
The threshold which has to be

exceeded for the minimum ring
duration to identify the signal as
communication.
*RingDuration
100 .. 3200 ms
[100]
If the ring level has been exceeded

for the configured value the signal will
be accepted as start trigger.
PackageTimeout
0 ms .. 1.000.000 ms
[100 ms]
Call packages will be handled after

the adjusted package timeout or the
next call on this channel has been
started. This setting is invalid if the
direct storage mode is selected.
*AGCEnable
Disabled
AGC (automatic gain control) is

disabled.
The
MARATHON
EVOLUTION does not modify the
audio level.
The VOX level has to be exceeded for

the selected minimum VOX time to
detect the signal as a regular call.
This value defines the length of the
shortest call on your system.
188/316

Configuration
Name
Active Hook
Value(s) [Default]
Description
[Enabled (Mono)]
AGC is enabled for this channel. The

AGC increases or decreases the
recorded mono signal to a defined
level.
Enabled (Stereo)
AGC is enabled for this channel. The

AGC increases or decreases the
recorded stereo signal to a defined
level.
On
Requires a Telephone Interface with

Conference Module. Enables the
active mode of the Telephone
Interface.
The
MARATHON
EVOLUTION will automatically accept
an incoming call.
[Off]
The Telephone Interface is working in

passive mode.
On
BeepToneEnable
(The Telephone Interface
inserts a beep tone into the
phone line. The tone is
audible for the participants
of the recorded
communication)
Available for analog channels only.

Please note that the beep tone has to
be configured under Configuration System - Recording Manager.
[Off]
No BeepTone is inserted for this

channel.
*AnalogGain
0..38 dB
[0 dB]
Analog
Gain
is
an
analog
preamplifier, located in the Telephone
Interface. If there is a small input level
of the audio signal, you can improve
the signal to noise ratio of the
analog/digital conversion.
*AGCRaiseTime1
200..4715 ms
[608 ms]
Defines the delay time for the

Automatic Gain Control (AGC) for the
first input source of this channel.
Small values cause a fast regulation
of the AGC output level, high values
causes a slow regulation of the AGC
Output level.
*AGCRaiseTime2
200..4715 ms
[608 ms]
Defines the delay time for the

Automatic Gain Control (AGC) for the
second input source of this channel.
Small values cause a fast regulation
of the AGC output level, high values
cause a slow regulation of the AGC
Output level. Only used in a 4-wire
configuration.
*AGCMaxGain1
10..41 dB
[41 dB]
Defines the maximum amplification of

the AGC at input source one. If this
channel has a problem with crosstalk,
the amplification of the AGC can be
decreased.
189/316

Configuration
Name
Value(s) [Default]
Description
*AGCMaxGain2
10..41 dB
[41 dB]
Defines the maximum amplification of

the AGC at input source two. If this
channel has a problem with crosstalk,
the amplification of the AGC can be
decreased. Only used in a 4-wire
configuration.
[COMMAN
*InputSource1
(Defines the recording card (Analog / PCM30)]
which provides the audio
data for this channel)
Choose this selection to configure an

analog, PCM 30 or an active or
passive PRI channel on the
NGX
(MVTC)
Select NGX to configure a MVTC

channel.
DP_XXXX
(PRI (E1/T1) passive)
Select DP_XXXX to configure a

passive PRI channel.
[DISABLED (Disabled)]
*InputType1
(Defines the interface
supported by the recording
card)
Disables this channel.
LVDS_TIMESLOT
(TIF Input)
Select LVDS_TIMESLOT to configure

an analog channel.
PCM30_TIMESLOT
(PCM30 input)
Select
PCM30_TIMESLOT
configure a PCM 30 channel.
to
PRI_ACTIVE_TIMESLOT Select PRI_ACTIVE_TIMESLOT to

(Active PRI input)
configure an active PRI channel on
the Communication Manager.
PRI_PASSIVE_TIMESLO Select PRI_PASSIVE_TIMESLOT to
T
configure a passive PRI channel on
(Passive PRI input)
the Communication Manager.
INCOMING_TIMESLOT
(Incoming audio signal)
Select INCOMING_TIMESLOT to
configure this channel to record
incoming audio signals.
OUTGOING_TIMESLOT
(Outgoing audio signal)
Select OUTGOING_TIMESLOT to
configure this channel to record
outgoing audio signals.
AUDIO_STREAM
Select AUDIO_STREAM to get
(Mixed incoming and incoming and outgoing data mixed on
outgoing audio signal)
this channel.
INCOMING_TIMESLOT_ Select INCOMING_TIMESLOT_B2 to
B2 (Incoming audio signal configure this channel to record
on the second B channel) incoming audio signals on the second
B channel (only NGX).
OUTGOING_TIMESLOT_ Select OUTGOING_TIMESLOT_B2
B2 (Outgoing audio signal to configure this channel to record
on the second B channel) outgoing audio signals on the second
B channel (only NGX).
AUDIO_STREAM_B2
Select AUDIO_STREAM_B2 to get
(Mixed incoming and incoming and outgoing data mixed on
outgoing audio signal on the second B channel (only NGX).
the second B channel)
190/316

Configuration
Name
Value(s) [Default]
Description
*InputSlot1
(Defines the physical input
channel on the interface of
the recording card)
0..23 TIF1;
24..47 TIF2;
48..71 TIF3;
72..95 TIF4
If the input type is configured to LVDS

the input slot assigns an analog input
at the Telephone Interface.
0..23 MVT card no. 1

If the input type is configured to NGX

the input slot assigns a digital channel
at the MVTB.
1..15 and17..31
PCM 30 trunk 1
33..47 and 49..63
PCM 30 trunk 2
65..79 and 81..95
PCM 30 trunk 3
97..111 and 113..127
PCM 30 trunk 4
If the input type is configured to PCM

30 the input slot assigns a digital
channel at the PCM 30 interface.
Please note that the time slots 0, 16,
32, 48, 64, 80, 96 and 112 include no
communication data and should not
be used as recording time slot.
0..29 board 1 trunk 1

If the input type is configured to PRI

board the input slot assigns a digital
channel at the PRI board.
65535
If the input type 1 is disabled the

value for input slot 1 will be set to
65535 automatically.
*NGXStateMachine1
The values depend on the This setting is used to configure the

connected PBX
suitable state machine for the
connected phone set.
*InputSource2
[COMMAN
(Analog / PCM30)]
This setting is used to configure a 4wire system and defines the recording
card of a second input source. It can
be only used if the first physically
input is configured. The configuration
is like InputSource1.
NGX
(MVTC)
Select NGX to configure a MVTC

channel.
[DISABLED (Disabled)]
This setting is used to configure a 4wire system and defines the interface
supported by the recording card. It
can be only used if the first physically
input is configured. The configuration
is like InputType1.
LVDS_TimeSlot
(TIF Input)
Select LVDS to configure an analog

channel.
*InputType2
191/316

Configuration
Name
Value(s) [Default]
Description
*InputSlot2
0..120
[65535]
This setting is used to configure a 4wire system and defines the second
physically
input
channel
with
InputSource2 and InputType2. The
InputSlot1 and InputSlot2 are mixed
to one audio stream. It can be only
used if the first physically input is
configured. The configuration is like
InputSlot1.
ManualStartEventType
[Not used]
No manual start event type selected

to start the recording.
Soft button pressed
This setting is used to start the

recording via telephone soft buttons.
Function button pressed

recording via telephone function
buttons.
Feature button pressed

recording via telephone feature
buttons.
Light off
Light on
Light flashing
Light fast flashing
Light very fast flashing
Light quick flash
Light wink
Light slow wink

recording
if
the
ManualStartLightEventType is in this
configured mode.
ManualStartLightEvent
Type

recording if the configured light is in
the above configured mode.
ManualStartButton
0...4294967295
[0]
The button number which should be

used to start the recording. The
button counting depends on the used
telephone end set. Normally the
buttons are counted ascending from
left to right and start with button
number 1. Each button must be used
only once. Start and stop of the
recording must be programmed on
different buttons.
ManualStopEventType
[Not used]
No function button type selected for

stop.
Soft button pressed
This setting is used to stop the


buttons.

buttons.
192/316

Configuration
Name
Value(s) [Default]
Description
Light off
Light on
Light flashing
Light fast flashing
Light quick flash
Light wink
Light slow wink

recording
if
the
ManualStopLightEventType is in this
configured mode.
ManualStopLightEvent
Type

ManualStopButton
0...4294967295
[0]

used to stop the recording. The button
counting depends on the used
number 1. Each button must be used
only once. Start and stop of the
recording must be programmed on
different buttons.
ManualSaveEventType
[Not used]

manual keep.
Soft button pressed
This setting is used to keep the


buttons.

buttons.
Light off
Light on
Light flashing
Light fast flashing
Light quick flash
Light wink
Light slow wink

recording
if
the
ManualSaveLightEventType is in this
configured mode.
0...4294967295
[0]

used to save the recording. The
number 1.
ManualSaveButton
ManualSaveLightEvent
Type

193/316

Configuration
Name
Value(s) [Default]
Description
ManualDeleteEventType
[Not used]

manual delete.
Soft button pressed
This setting is used to delete the


buttons.

buttons.
Light off
Light on
Light flashing
Light fast flashing
Light quick flash
Light wink
Light slow wink

recording
if
the
ManualDeleteLightEventType is in
this configured mode.
ManualDeleteLightEvent
Type

ManualDeleteButton
0...4294967295
[0]

used to delete the recording. The
number 1.
Availability
Yes
Not configurable
No
Not configurable
* = If one of this settings will be changed an automatic stop and restart of the recording will be
executed.
To save the configuration of the channels click on the Save Configuration button.
194/316

Configuration
To check the configuration click on Check all.
Fig. 141 - Checking configuration

If no errors have been found the following window will appear:
Fig. 142 - Configuration check of the channels passed

After the checking has been successfully completed please confirm with OK.
To check the available licenses click on the info button on top of the Channels dialog box.
195/316

Configuration
After the check on available licenses has been finished, the following window will appear:
Fig. 143 - License information

HINT
Licenses are only used if the channel is not disabled (Configuration Channels).
Licensing for channels:

License
Usage
COMP_G726
A COMP_G726 license is necessary for every configured

channel if the communication data should be recorded in a
compressed mode.
CLI
A CLI license is necessary for every configured channel if

the caller line identification (CLI) should be stored as call
information.
FOUR_WIRE
A FOUR_WIRE license is necessary for every configured

channel if both input sources are used.
DTMF
A DTMF license is necessary for every configured channel

if the Dual Tone Multi Frequency (DTMF) should be stored
as call information.
CHANNELS_PCM30
A CHANNELS_PCM30 license is necessary for every

configured PCM 30 channel.
CHANNELS_ANALOG_ACTIV
A CHANNELS_ANALOG_ACTIV license is necessary for

every configured active analog channel (recording with
conference module).
CHANNELS_ANALOG_PASSIV
A CHANNELS_ANALOG_PASSIV license is necessary for

every configured passive analog channel.
196/316
4.4

Configuration
License
Usage
CHANNELS_PRI_ACTIV
A CHANNELS_PRI_ACTIV license is necessary for every

configured active PRI channel.
CHANNELS_PRI_PASSIV
A CHANNELS_PRI_PASSIV license is necessary for every

configured passive PRI channel.
CHANNELS_MVTC_PASSIV
A CHANNELS_MVTC_PASSIV license is necessary for

every configured MVTC channel.
COMP_SPIRIT_ICELP4800
A COMP_SPIRIT_ICELP4800 license is necessary for the

compression of 4.8 kbps for every configured channel.
VOIP_ACTIVE
A VOIP_ACTIVE license is necessary for every configured

VoIP active channel.
VOIP_PASSIVE
A VOIP_PASSIVE license is
configured VoIP passive channel.
necessary
for
every
Configuration - EVOip Channels

This sublevel is used to configure the available channels for passive VoIP recording via the
EVOip module.
Show Print
license config.
info
Copy
Paste
channel channel
Paste
config.
Search
Export
config.
Import
config.
Reload
config.
Logout
Fig. 144 - Configuration of the EVOip channels
197/316

Configuration
Above this list there is a toolbar providing the following

configuration:
Show license
information:
buttons for user administration

Copy channel
configuration:
Paste channel
configuration:
Pastes the
entry/entries
Paste configuration
to all channels:
Search:
copy
content
to
the
selected

Reload
configuration:
Logout

window
Select a channel from the list in the upper part of the screen and set the parameters for this
channel in the lower part. The first channel in the channels list above is always the dynamic
master channel defining the settings for all dynamic channels.
The following channels (EVOip Channel 001 to EVOip Channel 240) can be configured
individually. Use the parameter InputType1 below to configure each channel as dynamic or
static channel. If you set this parameter to DYNAMIC_STEREO_STREAMS
(DYNAMIC_STEREO_STREAMS), the channel will be configured as a dynamic channel and the
settings made for the first channel called DYNAMIC VOIP CHANNEL will apply. To configure a
static channel, select a static value (STATIC_AUDIO_STREAM or STATIC_STEREO_STREAM)
198/316

Configuration
for the parameter InputType1. These static channels can then individually be configured with
the following parameters.
HINT
If you only use static channels, please make sure to disable all not
required channels.
HINT
For selective recording of specific IP phones please configure static
channels and define either the IP address or the extension number of
the IP phone that should be recorded.
HINT
For EVOip (universal) you have to define the IP address instead of the
extension numbers because in universal mode EVOip can not analyze
extension numbers.
HINT
The extension number on the static channel settings must be set for
EVOip+ for Cisco with SCCP, EVOip+ for SIP and EVOip+ for MITEL.
HINT
The parameter InputType1
can only be set to
STATIC_
AUDIO_STREAM if the IP phones are using exclusively G.711
(uncompressed). As soon as a compression like G.729 is used, you
have to select the value STATIC_STEREO_STREAM. Please note that
it is not possible to mix compressed data.
Name
Value(s) [Default]
RecordStartMode
(Defines how the
recording process will be
started. It is possible to
select several values
which will be OR
combined)
[HOST
Description
The recording process will be started

by an external application (e.g. user
indication)
CONNECT (Conversation The recording will be started after the
detection)
established.
DTMF-SEQUENCE
(DTMF sequence)
Server
(see
section
4.1.5
199/316

Configuration
Name
Value(s) [Default]
Description
RIA_ALERTING
(Triggered by external configured
RIA
indicates
a
conversation
indication conversation.
(RIA) )
RIA
detects
a
detection (RIA) )
conversation.
RecordStopMode
(Defines how the
stopped. It is possible to
which will be OR
combined)

stop trigger, according to the start
recording start)]
trigger, has been detected.
HOST
external
application
(e.g.
user
CONNECT (Conversation The recording will be stopped after
the telephone connection has been
detection)
cut off.
The recording will be stopped if a
DTMF-SEQUENCE
(DTMF sequence)
Server
(see
section
4.1.5
RIA
detects
a
detection (RIA) )
conversation.
StorageMode
NO_STORAGE
(No storage)

(this setting only makes sense for
testing purposes).
[DIRECT_STORAGE
(Storage immediately)]

COMPLETE_CALL_INFO Not available

available)
EXTERN_SAVE
(Keep (on user demand))
EXTERN_DELETE
(DELETE
(on
demand))

except of those the user wants to
e.g. via VoIP XML service or user

user except of those the user wants to
e.g. via VoIP XML service or user
200/316

Configuration
Name
Value(s) [Default]
Description
[50:00:00:00:00]
The communication data will be

stored for the selected time span
(provided that there is sufficient hard
disk capacity available). After the
defined time span has run out, the call
file will be deleted but the additional
call information will be preserved in
the database with the hint that the
respective call file is no longer stored.
PackageTimeout
0 ms .. 1.000.000 ms
[100 ms]

StorageMode DIRECT_STORAGE is
selected.
AGCEnable
[Disabled]
Enabled (Mono)
Enabled (Stereo)
Enables
control).
InputType1
[DYNAMIC_STEREO_
STREAMS
(DYNAMIC_STEREO_
STREAMS)]
STATIC_ / DYNAMIC_
AUDIO_STREAM
STATIC_ / DYNAMIC_
STEREO_STREAM
INCOMING
Select this value to record all possible

conversations on the defined dynamic
channels.
OUTGOING
AGC
(automatic
gain
Select this value to configure the

channel for audio mixed recording.
channel for stereo recording.
selected channel for recording the
incoming stream, only.
outgoing stream, only.
IP
IP address
Enter either the IP address or the

MAC address in the next parameter
(only applies to static channels).
Note that this parameter and the
parameter Extension are AND
combined which is relevant for shared
lines.
MACAddress
MAC address
Enter either the MAC address or the

IP address in the previous parameter
(only applies to static channels). If
your IP phones are having dynamic IP
addresses
(DHCP),
use
MAC
addresses.
parameter Extension are AND
lines.
201/316
4.5

Configuration
Name
Value(s) [Default]
Description
Extension
Extension
Enter the extension (only applies to

static channels).
preceding parameter IP are AND
lines.
For SIFA channels always use the
prefix SIFA_ before each extension.
Availability
Yes
No
This parameter indicates whether the

channel is physically available. The
value is not configurable by the
customer.
PostCompression
[disabled]
G729
Enables post compression.
Configuration - EVOip active Channels

This sublevel is used to configure the available channels for active VoIP recording via the EVOip
active module.
Show Print
license config.
info
Copy
Paste
channel channel
Paste
config.
Search
Export
config.
Import
config.
Reload
config.
Logout
Fig. 145 - Configuration of the EVOip active channels
202/316

Configuration
Above this list there is a toolbar providing the following buttons for channel configuration:
Show license
information:

Copy channel
configuration:
Paste channel
configuration:
Pastes the
entry/entries
Paste configuration
to all channels:
Search:
copy
content
to
the
selected

Reload
configuration:
Logout

window
Select a channel from the list in the upper part of the screen and set the parameters for this
channel in the lower part. The first channel in the channels list above is always the dynamic
master channel defining the settings for all dynamic channels.
The following channels (EVOip active Channel 001 to EVOip active Channel 240) can be
configured individually. Use the parameter InputType1 below to configure each channel as
dynamic or static channel. If you set this parameter to DYNAMIC_STEREO_STREAMS
(DYNAMIC_STEREO_STREAMS), the channel will be configured as a dynamic channel and the
settings made for the first channel called DYNAMIC VOIP CHANNEL will apply. To configure a
static channel, select a static value (STATIC_AUDIO_STREAM or STATIC_STEREO_STREAM)
203/316

Configuration
for the parameter InputType1. These static channels can then be configured individually with
the following parameters.
HINT
If you only use static channels, please make sure to disable all not
required channels.
HINT
For selective recording of specific IP phones please configure static
channels and define either the IP address or the extension number of
the IP phone that should be recorded.
Name
Value(s) [Default]
RecordStartMode
(Defines how the
which will be OR
combined)
[HOST
Description

indication)
CONNECT (Conversation The recording will be started after the
detection)
established.
DTMF-SEQUENCE
(DTMF sequence)
Server
(see
section
4.1.5
RIA_ALERTING
(Triggered by external
conversation indication
(RIA) )

configured
RIA
indicates
a
conversation.

RIA
detects
a
detection (RIA) )
conversation.
204/316

Configuration
Name
Value(s) [Default]
Description
RecordStopMode
(Defines how the
which will be OR
combined)

recording start)]
HOST
external
application
(e.g.
user
CONNECT (Conversation The recording will be stopped after
the telephone connection has been
detection)
cut off.
The recording will be stopped if a
DTMF-SEQUENCE
(DTMF sequence)
Server
(see
section
4.1.5
RIA
detects
a
conversation.
detection (RIA) )
StorageMode
NO_STORAGE
(No storage)

(this setting only makes sense for
testing purposes).
[DIRECT_STORAGE
(Storage immediately)]

COMPLETE_CALL_INFO Not available

available)
EXTERN_SAVE
(Keep (on user demand))

except of those the user wants to
EXTERN_DELETE
(DELETE
(on
demand))

user except of those the user wants to
[50:00:00:00:00]
The communication will be stored for

the selected time span (if there is
sufficient
hard
disk
capacity
available). After the defined time span
has run out, the call data will be
deleted but the call information will be
preserved in the database.
205/316

Configuration
Name
Value(s) [Default]
Description
PackageTimeout
0 ms .. 1.000.000 ms
[100 ms]

StorageMode DIRECT_STORAGE is
selected.
AGCEnable
[Disabled]
Enabled (Mono)
Enabled (Stereo)
Enables
control).
InputType1
DYNAMIC_STEREO_
STREAMS
(DYNAMIC_STEREO_
STREAMS)
[STATIC_ / DYNAMIC_
AUDIO_STREAM]
STATIC_ / DYNAMIC_
STEREO_STREAM
INCOMING
Select this value to record all possible

conversations on the defined dynamic
channels.
OUTGOING
AGC
(automatic
gain

channel for audio mixed recording.
channel for stereo recording.
incoming stream, only.
outgoing stream, only.
IP
IP address
Here you can enter the IP address but

for EVOip active you will probably
only configure the extension because
the IP address will usually not change
(e.g. always the IP address of the
conference bridge).
Extension
Extension
Enter the extension (only applies to

static channels).
Availability
Yes
No
This parameter indicates whether the

channel is physically available. The
value is not configurable by the
customer.
PostCompression
[disabled]
G729
Enables post compression.
206/316

Configuration
4.6
Configuration - RIA (Recording Interface Adapter)

Reload
Logout
Fig. 146 - Configuration of the RIA
207/316

Configuration
4.6.1
General Configuration
4.6.1.1
Configuration of a RIA Instance
Fig. 147 - Configuration of a RIA Instance

Name
Value(s) [Default]
Description
NumInstances
[0]
0 .. 30
This value defines the number of

RIAactive, RIApassive and RIAtagger
instances.
[Yes]
No
This value defines if the RIA instance

is enabled or disabled.
Instances
Enabled
Name
This value will be predefined and can

be changed by the user.
LogLevel

208/316

Configuration
Name
Value(s) [Default]
Description
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
will
be
Saves the current RIA configuration
4.6.1.2
Configuration of VirtualRIAactiveChannel
With this settings you can configure the start/stop behavior for recordings controlled by a
RIAactive instance.
209/316

Configuration
Fig. 148 - Configuartion of VirtualRIAActiveChannel

Name
Value(s) [Default]
Description
RecordStartMode
(Defines how the
which will be OR
combined)
[HOST


RIA
detects
a
detection (RIA) )
conversation.
RecordStopMode
(Defines how the
which will be OR
combined)
[- (Use the triggers from

recording start)]
HOST

external
application
(e.g.
user

RIA
detects
a
detection (RIA) )
conversation.
210/316
4.6.1.3

Configuration
Name
Value(s) [Default]
Description
Selective
[Yes]
No
This value defines whether selective

recording will be used or not.
Configuration of a RIA Statemachine

You can configure the RIA statemachine within the tab Protocol-Interface.
Fig. 149 - Configuration of a RIA Statemachine

Name
Value(s) [Default]
Description
Statemachine
[None]
This value defines the state machine

which will be used for interpretation of
the messages from the PBX.
EventBuffer
[No buffering]
1000 .. 10000 Events
It is only necessary to buffer events in

case of problems with the RIA
interface.
PIF-Type
[None]
PIFSiemensTrading
This value defines the protocol

interface for decoding the incoming
messages.
Saves the current RIA statemachine configuration
211/316

Configuration
4.6.1.4
Configuration of a RIA Serial Connection

You can configure the RIA serial connection within the tab Protocol-Interface.
Fig. 150 - Configuration of a RIA Serial Connection

Name
Value(s) [Default]
Description
Connection-Type
Serial
[TCP]
TCP-Listener
This value defines the connection

type of the PIF. Please choose the
value Serial.
COM-Port
0 .. 4294967295
[1]
This value defines the serial port

where the PIF will be connected to.
Baud-rate
9600 bps
19200 bps
38400 bps
57600 bps
[115200 bps]
This value defines the baud rate

which will be used for data transfer.
Data-Bits
5
6
7
[8]
This value defines the data bits which

will be used for data transfer.
Parity
[None]
Even
Odd
Marker
Space
This value defines if a parity should be

used for data transfer.
Stop-Bits
[1]
1.5
2
This value defines the stop bits which

will be used for data transfer.
212/316

Configuration
Name
Value(s) [Default]
Description
Flow-control
[None]
Xon/Xoff
Hardware
This value defines if there should be a

flow control for the data transfer.
Inactivity-Timeout
0 ... 4294967295 seconds This value defines the duration of

inactivity until the connection will be
[0]
closed. The value 0 means no
inactivity timeout.
LogBinaryData
Yes
[No]
This value defines if the incoming

binary data will be written to a log file.
Saves the current RIA serial connection configuration
4.6.1.5
Configuration of a RIA TCP Connection

You can configure the RIA TCP connection within the tab Protocol-Interface.
Fig. 151 - Configuration of a RIA TCP Connection

Name
Value(s) [Default]
Description
Connection-Type
Serial
[TCP]
TCP-Listener

value TCP.
Server-IP
Server-Port

server.
0 .. 4294967295
[0]
Please enter the port for the PIF

connection.
213/316

Configuration
Name
Value(s) [Default]
Description
Inactivity-Timeout

[0]
inactivity timeout.
LogBinaryData
Yes
[No]

Saves the current RIA TCP connection configuration
4.6.1.6
Configuration of a RIA TCP-Listener Connection

You can configure the RIA TCP-Listener connection within the tab Protocol-Interface.
Fig. 152 - Configuration of a RIA TCP-Listener Connection

Name
Value(s) [Default]
Description
Connection-Type
Serial
[TCP]
TCP-Listener

value TCP-Listener.
Listener-Port
0 .. 4294967295
[9000]
Please enter the port for the PIF

listener.
Inactivity-Timeout

[0]
inactivity timeout.
LogBinaryData
Yes
[No]

214/316

Configuration
Saves the current RIA TCP-listener configuration
4.6.1.7
Configuration of a RIA Log Behaviour

You can configure the RIA log behaviour within the tab Protocol-Interface.
Fig. 153 - Configuration of a RIA Log Behaviour

Name
Value(s) [Default]
LogLevel
Description
Off
Minimal

be generated.
[Medium]

be generated.
Extended

Debug
Full debug
generated.
messages
will
be
Saves the current RIA log configuration
4.6.2
Configuration of RIApassive for Siemens HiPath Trading IP

Please refer to the Installation Manual 06_EVOIPactive_for_Unify_OpenScape_Xpert_e_V in
the directory 06_Basic_Configuration\EVOip_Server_Software\Unify.
215/316

Configuration
4.6.3
Configuration of RIApassive for Siemens HiPath Trading

This section describes the required settings for the operation of MARATHON EVOLUTION in
combination with a Siemens HiPath Trading PBX.
1. In the ASC DataManager, open the submenu Configuration in the hierarchical structure on the
left-hand side of the window, and select the item RIA - RIApassive.
2. On the Configuration tab under NumInstances, enter the number of Siemens connections to the
MARATHON EVOLUTION, and click the Save button. Subsequently, a new subsection called
RIApassive_n (n stands for the specific instance) appears under RIApassive. Per instance, one
serial interface connected to a Siemens PBX can be configured.
3. Specify a name for the instance by changing the entry under Name. Subsequently, click the
Save button.
Fig. 154 - Creating a New Siemens Instance

4. In the left directory tree, click the new entry.
5. On the Protocol-Interface tab, under Statemachine, select the required Siemens statemachine,
and under PIF-Type, select PIFSiemensTrading. The following statemachines are available:
SiemensTrading
SiemensTradingMax (default)
SiemensTradingMax_CDR
6. Click the Save button.
Fig. 155 - Assigning the Siemens Properties

7. Open the freshly created subdirectory PIF-Config - Connection and select Serial or TCP under
Connection-Type.
216/316

Configuration
8. Serial Connection: Select 9600 bps under Baud-rate, 8 under Data-Bits, and None under Parity.
9. Enter the IP address of the Master Trade Board under Server-IP, and the port under Server-Port.
10. Click the Save button to store your settings.
Fig. 156 - Configuring the Siemens Connection

11. Go to the Devices tab to assign the phones to the MARATHON EVOLUTION channels.
12. For each phone line, enter the corresponding device number under DeviceNumber1 (trading
turrets in HTE numbering according to the <slmy>.<muxy>.<tt> pattern) and DeviceNumber2
(TAG (turret acces group) <location>.<slmygr>).
13. Under Handset, enter the handset (1, 2, 3, 4) or speach monitoring (A, B, C, D) number.
14. Click the Save button to store your configuration.
Fig. 157 - Assigning the Siemens Phones

4.6.4
Configuration of RIAtagger for IPC

combination with an IPC PBX.
217/316

Configuration
1. In the ADM, open the submenu Configuration in the hierarchical structure on the left-hand side of
the window, and select the item RIA - RIAtagger.
2. On the Configuration tab under NumInstances, enter the number of IPC connections to the
RIAtagger_n (n stands for the specific instance) appears under RIApassive. Per instance, one
serial interface connected to a IPC PBX can be configured.
Save button.
Fig. 158 - Creating a New IPC Instance

5. On the Protocol-Interface tab, under Statemachine, select the IPC statemachine, and under PIFType, select PIFIPC.
Fig. 159 - Assigning the IPC Properties

7. Open the newly created subdirectory PIF-Config - Connection and select Serial under
Connection-Type.
8. Select 19200 bps under Baud-rate, 7 under Data-Bits, and Odd under Parity.
218/316

Configuration
Fig. 160 - Configuring the IPC Connection

11. For each phone line, enter the corresponding channel number under RecordingLine. The system
will automatically assign the correct channel ID.
12. Under StationLAC, enter the number of the device to be recorded on this channel.
13. Under ChannelType enter the name of the device. Possible devices are HS1, HS2, SPK and
ICM.
Fig. 161 - Assigning the IPC Phones
219/316

Configuration
4.6.5
Configuration of RIApassive for DeTeWe OpenCom

combination with a DeTeWe OpenCom.
HINT
Two extensions on one telephone will not be supported!
2. On the Configuration tab under NumInstances, enter the number of DeTeWe connection to the
RIApassive_n (n stands for the specific instance) appears under RIApassive. Per instance, one
network interface connected to a DeTeWe OpenCom PBX can be configured.
Save button.
Fig. 162 - Creating a New DeTeWe OpenCom Instance

5. On the Protocol-Interface tab, under Statemachine, select the DeTeWe OpenCom statemachine,
and under PIF-Type, select PIFDeTeWeOpenCom.
220/316

Configuration
Fig. 163 - Assigning the DeTeWe OpenCom Properties

7. Open the newly created subdirectory PIF-Config - Connection and select TCP under
Connection-Type.
8. Enter the IP address of the DeTeWe OpenCom Server under Server-IP, and the DeTeWe
OpenCom port under Server-Port.
9. Select No under LogBinaryData.
Fig. 164 - Configuring the DeTeWe OpenCom Connection

12. For each phone line, enter the corresponding TeilnehmerNummer.
221/316

Configuration
Fig. 165 - Assigning the DeTeWe OpenCom Phones

4.6.5.1
Checking the Connection

To check if the connection from the MARATHON EVOLUTION to the DeTeWe OpenCom is
working correctly use the OCE application.
Under Applications - Schnittstellen you can see the icon of the connection. If the icon is colored
green the connection works properly. If the icon is colored red the connection failed. In this case
please set the Log level to extended and contact our hotline for further assistance.
Fig. 166 - Checking the DeTeWe OpenCom Connection

4.6.6
Configuration of RIAtagger or RIApassive for Mitel SX2000/ICP2300 SMDR External

combination with a Mitel SX2000/ICP2300 SMDR External. It is possible to configure the RIA as
RIAtagger or RIApassive.
left-hand side of the window, and select the item RIA - RIAtagger/RIApassive.
2. On the Configuration tab under NumInstances, enter the number of Mitel connection to the
RIAtagger_n/RIApassive_n (n stands for the specific instance) appears under
RIAtagger/RIApassive. Per instance, one network interface connected to a Mitel SMDR External
PBX can be configured.
222/316

Configuration
Save button.
Fig. 167 - Creating a New Mitel SMDR External Instance

5. For RIAtagger: On the Protocol-Interface tab, under Statemachine, select the
MitelExternalSMDR statemachine, and under PIF-Type, select PIFMITEL_SMDR_EXTERNAL.
Fig. 168 - Assigning the Mitel SMDR External Properties with RIAtagger
7. For RIApassive: On the Protocol-Interface tab, under Statemachine, select the
MitelExternalSMDR statemachine, under PIF-Type select PIFMITEL_SMDR_EXTERNAL, under
Mode, select Tag only, under TagOnlyCallMappingField, select CHANNELID, and under
StopRecordingsOnPIFDisconnect, select No.
223/316

Configuration
Fig. 169 - Assigning the Mitel SMDR External Properties with RIApassive
9. Open the newly created subdirectory PIF-Config - Connection and select TCP under
Connection-Type.
10. Enter the IP address of the Mitel SMDR External PBX under Server-IP, and the Mitel SMDR
External port under Server-Port.
11. Select Yes under LogBinaryData.
Fig. 170 - Configuring the Mitel SMDR External Connection

13. Open the subdirectory PIF-Config - Log-Behaviour and select Medium under LogLevel.
14. If the SMDRExtendedRecordingLevel1 is configured in the PBX select Yes.
15. If the ExtendedTimeToAnswer is configured in the PBX select Yes.
224/316

Configuration
16. Enter the number of digits from your agents in the field NumOfACDDigits (e. g. if the Agent ID
has 4 digits enter 4 in this field).
17. If the ExtendedStartTime is configured in the PBX, select Yes.
Fig. 171 - Configuring the Mitel SMDR External Protocol Options

19. For RIAtagger: For each tagging line, enter the corresponding recording line and device.
Fig. 172 - Assigning the Mitel SMDR External Phones for RIAtagger
21. For RIApassive: For each PhoneLineID, enter the corresponding DEVICE.
225/316

Configuration
Fig. 173 - Assigning the Mitel SMDR Externall Phones for RIApassive
4.6.7
Configuration of RIApassive for Avaya INDeX

combination with an Avaya INDeX.
2. On the Configuration tab under NumInstances, enter the number of Avaya INDeX connection to
the MARATHON EVOLUTION, and click the Save button. Subsequently, a new subsection
called RIApassive_n (n stands for the specific instance) appears under RIApassive. Per
instance, one network interface connected to a Avaya INDeX PBX can be configured.
Save button.
Fig. 174 - Creating a New Avaya INDeX Instance
226/316

Configuration

5. On the Protocol-Interface tab, under Statemachine, select the AvayaIndex statemachine, and
under PIF-Type, select PIFAvayaIndex.
Fig. 175 - Assigning the Avaya INDeX Properties

7. Open the newly created subdirectory PIF-Config - Connection and select Serial under
Connection-Type.
8. Select 9600 bps under Baud-rate, 8 under Data-Bits.
Fig. 176 - Configuring the Avaya INDeX Connection

12. For each phone line, enter the corresponding trunk device under the SecondParty field.
227/316

Configuration
Fig. 177 - Assigning the Avaya INDeX Phones

4.6.8
Configuration of RIApassive for BT ITSLink

combination with a BT ITSLink. RIApassive can only be used on recording channels without
mixed audio. If multiple handsets or speakers are mixed into one recording channel the
RIAtagger has to be used.
2. On the Configuration tab under NumInstances, enter the number of BT ITSLink connections to
instance, one connection to a BT ITSLink can be configured.
Save button.
5. On the Protocol-Interface tab, under Statemachine, select the required BT_ITSLink
statemachine, and under PIF-Type, select PIFBT_ITSLink.
7. Open the newly created subdirectory PIF-Config - Connection and set the Server-IP to the IP
address of the BT ITSLink server. Set the Server-Port to the port of the BT ITSLink server.
Default port is 3001.
8. The Inactivity-Timeout is the maximum the recorder waits for a message from the BT ITSLink
server before the connection is marked as failed. The heartbeat messages from the BT ITSLink
server must be send at least once in this interval.
228/316

Configuration
10. LogBinaryData defines if the incoming binary data will be written to a log file.
Fig. 178 - Assigning the BT ITSLink Properties

11. Go to the Devices tab to assign the verticals to the MARATHON EVOLUTION channels.
12. For BT ITS Link version 4 do it like this:
For each phone line, enter the corresponding vertical in the following format:
console number followd by a H (for handset) or S (for speaker) and the handset or speaker
number. Console numbers are always 4 digits with leading zeros. Speaker numbers are two
digits with leading zeros. Handset 1 on console 1 is represented as 0001H1. Speaker 5 on
console 3 is represented as 0003S05.
Fig. 179 - Assigning the BT ITSLink Phones (version 4)
229/316

Configuration

console number followed by a H (for handset) or S (for speaker) and the handset or speaker
digits with leading zeros. Handset 1 on console 1 is represented as 0000000001H1. Speaker 5
on console 3 is represented as 0000000003S05. The recording line indicates the actual channel
where the audio is recorded. Enter "1" for "Channel 001".
4.6.9
Configuration of RIAtagger for BT ITSLink

RIAtagger is used on mixed channels. If multiple handsets or speakers are mixed into one
recording channel the RIAtagger has to be used.
2. On the Configuration tab under NumInstances, enter the number of BT ITSLink connections to
instance, one connection to a BT ITSLink can be configured.
Save button.
5. On the Protocol-Interface tab, under Statemachine, select the required BT_ITSLink
statemachine, and under PIF-Type, select PIFBT_ITSLink.
7. Open the newly created subdirectory PIF-Config - Connection and set the Server-IP to the IP
address of the BT ITSLink server. Set the Server-Port to the port of the BT ITSLink server.
Default port is 3001.
8. The Inactivity-Timeout is the maximum the recorder waits for a message from the BT ITSLink
server before the connection is marked as failed. The heartbeat messages from the BT ITSLink
server must be send at least once in this interval.
230/316

Configuration
10. LogBinaryData defines if the incoming binary data will be written to a log file.
Fig. 180 - Assigning the BT ITSLink Properties

11. Go to the Devices tab to assign the verticals to the MARATHON EVOLUTION channels.
For each phone line, enter the corresponding vertical in the following format: console number
followd by a H (for handset) or S (for speaker) and the handset or speaker number. Console
numbers are always 4 digits with leading zeros. Speaker numbers are two digits with leading
zeros. Handset 1 on console 1 is represented as 0001H1. Speaker 5 on console 3 is represented
as 0003S05. The recording line indicates the actual channel where the audio is recorded. Enter
"1" for "Channel 001".
Fig. 181 - Assigning the BT ITSLink Phones (version 4)
231/316

Configuration

console number followed by a H (for handset) or S (for speaker) and the handset or speaker
digits with leading zeros. Handset 1 on console 1 is represented as 0000000001H1. Speaker 5
on console 3 is represented as 0000000003S05. The recording line indicates the actual channel
where the audio is recorded. Enter "1" for "Channel 001".
4.7
Configuration - Auto Tagging

Reload
Logout
Fig. 182 - Configuration of the Auto Tagging

The Auto Tagging function provides the possibility to define additional information that should be
tagged to specific calls. To achieve this, it is first of all required to define the recorded calls that
should be added additional information, and in a second step it is required to enter a new text
that should be tagged to the call and to define the respective database field it should be inserted.
Proceed as follows:
232/316

Configuration
1. Define the recorded calls to which you want to add additional information by selecting a
SourceField of the database from the dropdown menu.
Name
Value(s) [Default]
SourceField
AGENTID
CHANNELID
CHANNELINDEX
Comment
EXT
IP
OWNNUMBER
PARTNERNUMBER
Text01
Text02
...
Text20
For better understanding, please note the following explanations of the terms CHANNELID,
CHANNELINDEX, EXT and IP:
CHANNELID:
The CHANNELID is the specific ID number for a certain channel. You can find that ID in each
channel configuration section in the ADM (see Fig. 183 - ChannelIDs in the ADM / EVOip
channels). This ID is unique for each recorder.
CHANNELINDEX:
The CHANNELINDEX is a general index number for the channels on a MARATHON
EVOLUTION/EVOip. This index is zero-based, i.e. hardware channels begin with
CHANNELINDEX 0, EVOip channels with 5000 and EVOip active channels with 10000.
Fig. 183 - ChannelIDs in the ADM / EVOip channels

Example:
To tag a static value to the EVOip channel 3, you can either use the CHANNELID 4PSI48X3UZ
or the CHANNELINDEX 5002 as SourceField.
EXT and IP will be the information that is obtained by the EVOip or the EVOip active.
233/316

Configuration
EXT:
This information will be obtained by the EVOip or the EVOip active when a new call is detected.
For EVOip active the extension of the endpoint calling the EVOip active will always be displayed
in the EXT field. For EVOip the extension information will only be displayed when decoding
SCCP or SIP protocol or when using MiXML.
IP:
This information will be obtained by the EVOip or the EVOip active when a new call is detected.
The IP address of the endpoint is only useful for EVOip because in EVOip active the IP address
is usually the address of the conference bridge.
2. In the text box Content enter the text that should be included in the already defined
SourceField of the database.
3. Define the field of the database in which the additional information should be written by selecting
a DestinationField from the dropdown menu.
Name
Value(s) [Default]
DestinationField
AGENTID
Comment
OWNNUMBER
PARTNERNUMBER
Text01
Text02
...
Text20
4. In the text box New content enter the text that should be written as new additional information
into the already defined DestinationField of the database.
5. Click Add to save these auto tagging values. They will be added to the above Auto Tagging
table.
To edit the parameters of already defined auto tagging values, select the respective entry from
the Auto Tagging table, change the settings and click Change.
To delete already defined auto tagging values, select the respective entry from the the Auto
Tagging table and click Delete.
Above this list there is a toolbar providing the following buttons for auto tagging:
Reload:
Logout

window
The different buttons at the middle of the screen have the following functions:
Deletes the selected entry
234/316

Configuration
Adds a new new entry to the list

Changes the selected entry
Saves the current configuration of the Auto Tagging
4.8
Configuration - Channel guard

The channel guard function provides the possibility to define an alarm message if the recording
activity on the channel set exceeds the configured time intervals.
4.8.1
Configuration Channel guard
Fig. 184 - Configuration of the Channel guard

Above this list there is a toolbar providing the following buttons for channel guard configuration:
New:
Create a new Channel Guard
Delete:
Delete a Channel Guard
235/316

Configuration
Reload:
Logout

window
Saves the configuration of the Channel guard
In the field Name enter the name for the channel guard. The first checkbox Active time is used to
enable the observation of the active time (that means the recording time). Here you can choose
whether the recordings Longer than or Shorter than the specified time will be observed.
The second checkbox Passive time is used to enable the observation of the passive time (that
means the time with no recording). Here you can choose whether the passive time Longer than
or Shorter than the specified time will be observed.
4.8.2
Configuration Scheduling
The Schedule parameter tab is used to define the time the Channel Guard should be active.
The first checkbox on the left-hand side is used to enable or disable the schedule parameters
defined in this dialog for this recording profile. Uncheck the checkbox Ignore Schedule
parameter to be able to schedule the Channel Guard for daily, weekly or monthly recording.
Fig. 185 - Configuration of the Channel Guard - Scheduling
236/316

Configuration
4.8.3
Configuration Activation
The channel guard can be activated for all channels or for a set of channels. This can be
configured in the activation tab.
Fig. 186 - Configuration of the Channel guard - Activation
237/316

Configuration
4.9
Configuration - Recording Planner

New
profile
Activate / Higher
deactivate priority
profile
Lower
priority
Delete
profile
Reload
Logout
Fig. 187 - The Recording planner screen

The Recording planner function provides the possibility to schedule the recording process
according to specific rules. This is achieved by creating individual recording profiles with various
mathematical and time-related parameters to be defined in the lower part of the screen.
4.9.1
How the Recording Planner works

The number of recording profiles that can be defined and activated in the Recording Planner is
not restricted. The module provides numerous recording parameters like phone numbers, IP
addresses scheduling as well as CTI parameters per recording profile. These criteria are applied
to every call available at the system. The Recording Planner then decides whether the session
will be recorded or not. The order the criteria are applied is determined, above all, by the priority
assigned to the individual recording profiles. The recording profile assigned priority 1 is the first
that will be processed.
Within the recording profiles the criteria are applied in the following order:
1. Profile activation parameters
2. Schedule parameters and recording duration
3. Additional criteria
4. External control trigger
5. Phone number list
238/316

Configuration
6. IP address list
7. CTI parameter
For each recording criterion you can define whether the session will be recorded without
considering the following criteria (forced recording) or will not be recorded at all, without
considering the remaining criteria either.
HINT
Automatic creation of recording profiles after installation/update:
If after the installation/update no recording profiles will be saved, the
APIserver will save after every restart recording profiles depending on
the recording channels configuration. This means if there are only
EXTERN_SAVE Channels the APIserver saves an ESS profile, if there
are only EXTERN_DELETE channels the APIserver saves a Bulk
profile for every channel and if there are EXTERN_SAVE and
EXTERN_DELETE channels the APIserver saves a Bulk profile with
only the EXTERN_DELETE channels.
239/316

Configuration
Fig. 188 - Processing recording criteria
240/316

Configuration
HINT
Bulk profiles should always be at the bottom of the list. Profiles with no
more than Activation parameters and Schedule parameters are bulk
profiles.
4.9.2
Buttons of the Toolbar

The toolbar of this screen provides the following buttons for recording profile configuration:
4.9.3
New profile
Creates a new recording profile.
Activate/deactivate
profile
Activates an already created, inactive profile or deactivates an

already active profile.
Higher priority
Assigns the selected profile a higher priority.
Lower priority
Assigns the selected profile a lower priority.
Delete profile
Deletes the selected profiles. If the profile is still recording, a warning

will be displayed indicating that the recording is still active. The
warning provides the choice to continue deleting the profile or cancel
the delete process.
Reload
Refreshes the data from the database (retrieves current data).
Logout
Logs out the current user and returns to the login window (Internet
Explorer).
Content of the Master Window Table

The Recording planner table lists all currently saved profiles. By default, the list includes the
recording profiles named Bulk profile and ESS KeepDelete with the default settings.
The individual columns of the Recording planner table include the following information:
Profilename
The name of the recording profile as defined by

the user after clicking the Save or Save as button.
Activated on...
Indicates if this profile is restricted to certain

channels or agents or applies to the entire system,
as configured in the Activation tab.
Priority
The priority value (1 - n) that is assigned to the

profile, with value 1 being the highest priority.
New profiles are automatically assigned the
lowest priority of all profiles already available, i.e.
they are added to the bottom of the table and are
assigned the highest number in the column
Priority.
To change the priority of already created profiles
use the Higher priority / Lower priority buttons in
the toolbar.
Starts
The time when active profiles start, as configured

in the Activation tab.
241/316
4.9.4

Configuration
Expires
The time when active profiles will expire, as

configured in the Activation tab.
Status
The current status of the profile, according to the

configuration in the Activation tab. The following
values are possible:
Not activated: The selected profile is currently
not active, i.e. its start date has not yet been
reached or the profile has been deactivated
manually.
Activated: The profile is currently active but its

start date has not yet been reached.
Running: The profile is currently active and its

start date has been reached.
Expired: The profile is no longer active

because its life time, i.e. the time it should be
active, has expired.
Creating New Recording Profiles

To create a new recording profile, click the New profile button in the toolbar.
The Profile Generator in the lower part of the screen, the so-called detail window, will contain
default values that you can adapt to you requirements, thus creating a new recording profile.
Proceed from one tab to the other by clicking the Forward button or stop parameter configuration
within the profile generator by clicking the Finish button.
4.9.5
Deleting Recording Profiles

To delete a selected recording profile with all its parameters, click the Delete profile button in the
toolbar.
242/316

Configuration
It is not possible to delete active profiles. To delete them they have to be deactivated
beforehand.
Fig. 189 - Error message while deleting active profiles
Fig. 190 - Delete dialog box

Click OK to continue or Cancel to abort.
4.9.6
Activating / Deactivating Profiles

Click the Activate/Deactivate profile button to activate an already created, inactive, profile or to
deactivate an already active profile. The actual status is displayed in the Status column of the
master window.
4.9.7
Assigning a Higher / Lower Priority

New profiles are automatically assigned the lowest priority of all profiles already available, i.e.
they are added to the bottom of the table and are assigned the highest number in the column
Priority. To change the priority of already created profiles use the Higher priority / Lower priority
buttons in the toolbar.
4.9.8
Creating New Recording Profiles

To create a new profile, click the New profile button in the toolbar. In the detail window below the
first tab CTI parameter will open with the default settings.
Configure the parameters for the new profile by using the profile creation wizard via the Forward
button and visiting the tabs one after another or select the tabs individually that are relevant for
the specific profile you want to create.
Every single tab, except the Activation tab, provides a Finish button to finish the creation process
either by saving the new profile or by aborting the creation of the new profile. After you have
adapted all parameters to your individual requirements you can display an overview of the
selected parameters in order to verify your settings with the Show summary button.
To finish creating a new profile, click Finish and Save, respectively Save as in the Activation tab.
After you have entered a name for the profile you will have the possibility to assign a priority of
243/316

Configuration
your choice to the new profile which is by default assigned the lowest priority of all already
existing profiles.
4.9.8.1
Configuration - Recording Planner - CTI Parameter

NOTE
The following CTI parameters are not compatible with all available PBX
and ACD facilities. Please contact your system administrator to find out
which parameters have been tested and released with your system.
Fig. 191 - Recording Planner - CTI Parameter

The CTI parameter tab is used to configure CTI parameters for recording control.
The three radio buttons on the left-hand side are used to enable or disable CTI control.
Ignore CTI parameter
CTI parameters are not considered by default for

recording control.
Allow recording
With this option selected, all selected CTI parameters

are considered for recording control. But a call meeting
one of the selected CTI parameters will not immediately
be recorded but the next profile will be checked. Calls
not meeting a configured CTI parameter will not be
recorded.
Force recording
With this option selected, the configured CTI parameters

for recording control will be checked. Any calls meeting
one of the configured CTI parameters will be recorded
without checking further parameters or profiles. Calls not
meeting any of the configured CTI parameters will be
applied to the remaining parameters or profiles.
Deny recording
With this option selected, any previously selected CTI

parameter will be ignored. No call will be recorded, and
the remaining parameters or profiles will not be checked.
244/316

Configuration
The parameters of the section CTI Trigger will be dimmed if CTI is disabled, i.e. the parameter
Ignore CTI parameter is selected. If CTI is enabled (parameter Allow recording or
Force recording selected), configure the following CTI parameters:
Name
Value(s) [Default]
Description
Hold Time (sec)
0 - 99999
[20] seconds
The length of hold times is monitored.

If a session is put on hold for longer
than the number of seconds defined
here, this session will be recorded.
Time in Queue (sec)
0 - 99999
[20]
The duration customers are waiting in

a queue before their call is answered
is monitored. If a customer waits in a
queue for longer than the number of
seconds defined here, this session
will be recorded.
Number of Transfers
0 - 99999
[20]
The number of transfers during a

session is monitored. If this number is
equal to or larger than the number
defined here, this session will be
recorded.
Conference Calls only
Activate / [Deactivate]
Activate this function to record all

conference calls.
The table on the right-hand side of the dialog provides the possibility to define specific CTI fields
with specific values. If a CTI field contains, for example, the customers ID number, it is possible
to configure this value as recording criterion.
To define a CTI field, click the Add button below and edit the CTI Field and Value entries with a
double-click.
NOTE
Your system administrator can provide you with the information on
available CTI parameters and fields.
After you have configured the necessary CTI parameters click Forward to proceed to the next tab
IP addresses or select another tab of your choice or click Finish to save the recording profile with
these settings.
245/316

Configuration
4.9.8.2
Configuration - Recording Planner - IP Addresses
Fig. 192 - Recording Planner - IP Address List

The IP addresses tab is used to configure IP addresses for recording control.
The two radio buttons on the left-hand side are used to enable or disable IP addresses for
recording control.
Ignore IP addresses
IP addresses are ignored by the selected profile.
Select IP addresses
IP addresses can be defined for the actual profile on the

right-hand side of the dialog.
Select MAC addresses
MAC addresses can be defined for the actual profile on

the right-hand side of the dialog.
HINT
The MAC addresses on the right-hand side are displayed automatically
if IP passive is activated and a call was performed by the corresponding
IP phones.
In the parameter box on the right-hand side define the IP addresses and the call direction that
should be monitored as well as the action that should be executed.
Name
Value(s) [Default]
Call direction
Defines the call direction that should

[Ignore direction]
Check only incoming calls be monitored.
Check only outgoing calls
Description
246/316

Configuration
Name
Value(s) [Default]
Description
Action
[Allow recording]
Force recording
Deny recording
Defines the action that should be

executed if one of the IP addresses
defined below are detected.
Allow recording:
If a call on one of the configured IP
addresses is detected, the system
doesnt necessarily record the call
but checks the remaining
parameters or profiles. Calls from
other IP addresses than those
configured here will not be
recorded.
Force recording:
addresses is detected, it will be
recorded without considering any
further parameters or profiles. For
calls from other IP addresses than
those configured here, the
remaining parameters or profiles
will be checked.
Deny recording:
addresses is detected, it will not be
recorded. Not even the remaining
parameters or profiles will be
checked. This setting has the
same effect as a so-called black
list. For calls with IP addresses
which are not included in the list,
the remaining parameters or
profiles will be checked.
247/316

Configuration
In the IP addresses table enter the IP addresses that should trigger the action defined with the
parameter above. To handle the IP addresses use the buttons below:
Add
Click Add to add an IP address entry to the list. Doubleclick this entry to enter the IP address of your choice.
Delete
Click Delete to delete an IP address entry from the list.
Import
Click Import to import IP addresses from a csv file. The

dialog displayed in Fig. 193 - Recording planner configuring IP address import will appear, prompting you
to configure the import. As there is only one column the
separator is not necessary. Each value has to be entered
in a seperate line.
Export
Click Export to export this IP address list to a csv file. A

separate dialog will open prompting you to define
whether the header should also be exported and to
configure characters enclosing and separating the IP
addresses. After you have configured these settings a
separate dialog will open prompting you to define a
folder on your hard disk where this file will be saved.
Fig. 193 - Recording planner - configuring IP address import

After you have configured the necessary IP addresses click Forward to proceed to the next tab
Phone number list or select another tab of your choice or click Finish to save the recording profile
with these settings.
248/316

Configuration
4.9.8.3
Configuration - Recording Planner - Phone Number List
Fig. 194 - Recording Planner - Phone Number List

The Phone number list tab is used to configure phone numbers for recording control.
The two radio buttons on the left-hand side are used to enable or disable this list for recording
control.
Ignore phone number list
The phone number list is ignored by the selected profile.
Select phone number list
Phone numbers can be defined for the actual profile on

the right-hand side of the dialog which must or must not
be recorded, also considering the call direction.
In the parameter box on the right-hand side define the phone numbers, the source of the phone
number and the call direction that should be monitored as well as the action that should be
executed if the defined phone number is detected.
Name
Value(s) [Default]
Call direction
Defines the call direction that should

[Ignore direction]
Check only incoming calls be monitored.
Check only outgoing calls
Description
249/316

Configuration
Name
Value(s) [Default]
Description
Action
[Allow recording]
Force recording
Deny recording
Defines the action that should be

executed if one of the phone numbers
defined below is detected.
Allow recording:
If a call on one of the configured
phone numbers is detected, the
system doesnt necessarily record
the call but checks the remaining
parameters or profiles. Calls from
other phone numbers than those
configured here will not be
recorded.
Force recording:
phone numbers is detected, it will
be recorded without considering
any further parameters or profiles.
For calls from other phone
numbers than those configured
here, the remaining parameters or
profiles will be checked.
Deny recording:
phone numbers is detected, it will
not be recorded. Not even the
remaining parameters or profiles
will be checked. This setting has
the same effect as a so-called
black list. For calls with phone
numbers which are not included in
the list, the remaining parameters
or profiles will be checked.
You can also select which fields shall be used as the source of the phone number (multiple
selection allowed).
In the Numbers table enter the phone numbers that should trigger the action defined with the
parameter above. To handle the phone numbers use the buttons below:
Add
Click Add to add a phone number entry to the list.

Double-click this entry to enter the phone number of your
choice.
Delete
Click Delete to delete a phone number entry from the list.
250/316

Configuration
Import
Click Import to import phone numbers from a csv file. A

dialog similar to the IP address import dialog displayed in
Fig. 193 - Recording planner - configuring IP address
import will appear, prompting you to configure the import.
As there is only one column the separator is not
necessary. Each value has to be entered in a seperate
line.
Export
Click Export to export this phone number list to a csv file.

A separate dialog will open prompting you to define
whether the header should also be exported and to
configure characters enclosing and separating the phone
numbers. After you have configured these settings, a
separate dialog will open prompting you to define a
folder on your hard disk where this file will be saved.
HINT
You may use ? and % as wild cards for the phone numbers.
? replaces a number of characters
% replaces a single character
After you have configured your individual Phone number list click Forward to proceed to the next
tab External trigger or select another tab of your choice or click Finish to save the recording
profile with these settings.
4.9.8.4
Configuration - Recording Planner - External Control Trigger
Fig. 195 - Recording Planner - External Control Trigger

The External control trigger tab is used to define external inputs that should be allowed to control
the recording process.
251/316

Configuration
The two radio buttons on the left-hand side are used to enable or disable recording control by
external applications.
No external control trigger:
Recording control is not allowed by an external

application.
Select external control trigger:
Recording control is allowed by the external application

defined with the parameters on the left-hand side.
In the parameter box on the right-hand side define the external application / Mode_ESS Client
that should be allowed to issue commands for keeping or deleting commands. Check the
respective checkboxes (Can keep or Can delete) if the recording process should be controlled by
ESS Clients, DTMF sequences or specific keys pressed by the user on his/her phone.
After you have configured the external controls click Forward to proceed to the next tab
Additional criteria or select another tab of your choice or click Finish to save the recording profile
HINT
If the partner's phone number is suppressed, the DTMF characters will
be written into the Partner's phone number field. This is continued until
a break takes place. The duration of this break depends on the settings
of the DTMF timeout (see section 4.1.5 - Configuration API Server,
configuration table, parameter DTMF).
4.9.8.5
Configuration - Recording Planner - Additional Criteria
Fig. 196 - Recording Planner - Additional Criteria

The Additional criteria tab is used to configure additional criteria for recording control.
252/316

Configuration
The three radio buttons on the left-hand side are used to enable or disable the additional criteria
defined in the list on the right-hand side for recording control.
Ignore additional criteria:
Additional parameters are not considered by default for

recording control.
Allow additional criteria:
With this option selected, all selected additional criteria

are considered for recording control. But a session
meeting one of the selected additional criteria will not
immediately be recorded but the next profile will be
checked. Sessions not meeting all configured additional
criteria will not be recorded.
Force additional criteria:
With this option selected, the configured additional

criteria for recording control will be checked. Any
sessions meeting one of the configured CTI parameters
will be recorded without checking further parameters or
profiles. Sessions not meeting any of the configured CTI
parameters will be applied to the remaining parameters
or profiles.
In the parameter box on the right-hand side define additional criteria that should be considered
for recording control.
Name
Value(s) [Default]
Description
Record x sessions sequentially
0 - 9999
[5]
Enter the number of calls that should

be sequentially recorded during the
time the profile is active.
Record x sessions evenly spread
0 - 9999
[5]
Enter the number of calls that should

be recorded and that should be
evenly spread over the time the profile
is active.
Record x % of all calls
0 - 100
[10]
Enter a percentage of all calls that

should be recorded during the time
the profile is active.
Record every x th session
0 - 9999
[5]
Records every xth session during the

time the profile is active.
In the box on the outer right side define whether the configured criteria should be applied to each
agent individually or to all agents that are being selected when the profile is activated. You can
select if the calls will be recorded daily, weekly, monthly or quarterly by using the reset counter
pull down menu.
NOTE
The parameters apply to the whole time the profile is running, not to
every particular schedule time.
Example: If you define a profile which should record 10 calls randomly
per agent on a daily basis from 8 AM to 9 AM with the profile runnning
for 2 weeks, the result after two weeks will be: 10 sessions randomly
distributed over the two weeks.
After you have configured the additional criteria, click Forward to proceed to the next tab
Schedule parameter or select another tab of your choice or click Finish to save the recording
profile with these settings.
253/316

Configuration
4.9.8.6
Configuration - Recording Planner - Schedule Parameter
Fig. 197 - Recording Planner - Schedule Parameter

The Schedule parameter tab is used to define the time the recording profiles should be active.
The first checkbox on the left-hand side is used to enable or disable the schedule parameters
defined in this dialog for this recording profile. Uncheck the checkbox Ignore Schedule
parameter to be able to schedule the recording profiles for daily, weekly or monthly recording.
Schedule Parameters for Daily Recording
To define schedule parameters for daily recording, select the option Daily.
Fig. 198 - Schedule parameters for daily recording

After you have checked the option Daily, enter a Start Time and an End Time to define the
time span the recording profile should be active every day. Then click Add to add this time to the
table on the right-hand side. You can define various such time frames by entering several Start
Time and End Time values. Always make sure to add them to the list by clicking the Add button.
254/316

Configuration
Schedule Parameters for Weekly Recording

To define schedule parameters for weekly recording, select the option Weekly.
Fig. 199 - Schedule parameters for weekly recording

After you have checked the option Weekly, select one or more of the days of the week from the
box in the middle and enter a Start Time and an End Time to define the time span the
recording profile should be active on the selected days. Then click Add to add each day selected
to the list on the right-hand side with the respective timeframe. You can repeat these steps to
configure other days/times of the week.
Schedule Parameters for Monthly Recording
To define schedule parameters for monthly recording, select the option Monthly.
Fig. 200 - Schedule parameters for monthly recording

After you have checked the option Monthly, select either the first, second, third, fourth or last of
a specific day within the month from the dropdown menus, e.g. third Monday, or you can select
a particluar date of the month, e.g. 30 th from the spinbox below. Then enter a Start Time and
an End Time to define the time span the recording profile should be active on the selected day
of the month. Make sure to click Add to add the selected day to the list on the right-hand side with
the respective timeframe. You can repeat these steps to configure other days of the month.
255/316

Configuration
Scheduling table
The table on the right-hand side of the Schedule parameter section lists all scheduling tasks
already configured with the respective Date, Start Time and End Time.
Fig. 201 - Scheduling table

To administrate the scheduling tasks, the following buttons are available:
Add
Click Add to add a scheduling task defined with the parameters

on the left-hand side to the list.
Change
Click Change to change the configuration of an already existing

scheduling task.
Delete
Click Delete to delete a scheduling task from the list.
Recording duration
Below the Schedule parameter section there is the Recording duration section that provides the
possibility to record only those calls with a duration longer or shorter than a specific value.
Fig. 202 - Parameters defining the duration of recording
Name
Value(s) [Default]
Description
Calls longer than x seconds
0 - 99999
[20]
Check this option to record only those

calls being longer than the value (in
seconds) entered here.
Calls shorter than x seconds
0 - 99999
[10]
Check this option to record only those

sessions being shorter than the value
(in seconds) entered here.
256/316

Configuration
If you check both options only calls longer than x seconds or calls shorter than x seconds will be
recorded.
After you have configured the Schedule parameters click Forward to proceed to the last tab
Profile activation or select another tab of your choice or click Finish to save the recording profile
4.9.8.7
Configuration - Recording Planner - Activation
Fig. 203 - Recording Planner - Profile Activation

ctivation
The Profile activation tab is used to define the recordings this profile should be valid for as well
as the time the profile should be active. To achieve this, it includes different sections.
The parameter box on the upper left side includes the following parameters:
Fig. 204 - General activation parameters

Name
Value(s) [Default]
Creation Date
Description
The date the recording profile was
created (automatically filled by the
system).
257/316

Configuration
Name
Value(s) [Default]
Comment
Description
Enter a comment of your choice for
this recording profile.
Voice
activate / deactivate
Check the checkbox to activate the

recording profile for recording voice
calls.
Screen
Check the checkbox to activate the

recording profile for recording screen.
Wrap up Time (sec)
0-99999
[10]
This parameter belongs to the screen

recording function. It sets the wrap up
time for the screen recording in
seconds.
Quality tagging
This parameter is only valid for

INSPIRATIONpro.
The parameter box on the upper right side includes the parameter Activate on to restrict this
recording profile to certain channels / channel groups or agents / agent groups.
Fig. 205 - Defining specific channels for the profile

Name
Value(s) [Default]
Description
Activate on
[The whole system]

Channel groups
Specific channels
Agent groups
Specific agents
Defines the configuration area this

recording profile should be applied to.
If you select one of the options
Channel groups, Specific channels,
Agent groups or Specific agents,
select specific channels (as shown in
Fig. 205 - Defining specific channels
for the profile) or enter channel or
agent groups or agent IDs in the
specific tables. Select the respective
entry or entries (by keeping the Ctrl
key pressed) from the list.
258/316

Configuration
The parameter box below includes parameters defining the time the recording profile should be
valid.
Fig. 206 - Defining the time for the profile

By default the radio buttons Starts immediately and Ends never are selected.
To schedule the activation and deactivation of the recording profile, select the options Starts
at and Ends at. It will then be possible to define start and end times and dates with the
following parameters:
Name
Value(s) [Default]
Description
Starts at YYYY-MM-DD
[actual date]
Enter a date the recording profile

should start.
Ends at YYYY-MM-DD
[actual date + one month] Enter a date the recording profile

should end.
Start Time
[00:00]
Enter a time the recording profile

should start.
End Time
[23:59]
Enter a time the recording profile

should end.
To start the recording profile manually later, check the checkbox Activate later. For further
information on activating or deactivating a recording profile later, refer to section 4.9.6 Activating / Deactivating Profiles.
You have now configured all parameters for a recording profile.
259/316

Configuration
You can return to the previous steps of the profile generator by clicking Back. Before saving the
recording profile you can display an overview of the selected parameters with the Show
summary button.
Fig. 207 - Overview of the parameters already configured

4.9.9
Saving a New Recording Profile

After you have created a new recording profile a separate dialog box will be displayed after
hitting the Save as or Save prompting you to enter a name for the new profile.
After it has been saved the new profile will be displayed as lowest entry of the profile table in the
master window with lowest priority. You can now assign a higher priority to the profile by clicking
the Higher priority button.
Fig. 208 - Assigning a Name to the New Profile
260/316

Configuration
4.9.10
Saving an Already Existing Recording Profile

After you have changed an already existing recording profile, it can be saved in two different
ways:
1. Using the Save button:
After you have clicked this button the changed settings will be changed in the existing recording
profile. Please note that this is only possible for inactive profiles.
2. Using the Save as button:
After you have clicked this button a new recording profile with the selected parameter settings
will be created. A separate dialog will open prompting you to enter a name for the new profile.
Before saving the recording profile you can display an overview of the selected parameters with
the Show summary button.
To save the profile click the Save profile button and enter a name for the profile.
After that the new profile will be displayed in the profile table in the upper part of the Recording
planner screen. You can now assign a priority of your choice to the profile, if the lowest priority
that is automatically assigned to new profiles does not suit your needs.
4.10
Configuration - Recording Decision Preview

Reload
Logout
Fig. 209 - The Recording Decision Preview Screen
261/316

Configuration
In this menu you can check your current recording planner settings. You can select different
criterias for a conversation. Afterwards you can check if this conversation would be recorded.
Reload:

current data)
Logout

window
The button at the bottom of the screen has the following function:
Checks the recording decision
4.11
Screen Recording
This area of the hierarchical structure is used to administer the settings for Screen recording. It is
possible to configure several screen recording gateways, but only as many as there are licenses
for INSPIRATION SCREEN CAPTURE available in the dongle.
The following settings can be changed:
Timespan_Until_Deletion Timespan until screen sessions remain on the gateway server.

Screen sessions older than this value will be deleted. The value 00:00:00:00:00 means, as long
as possible.
RecordStartMode - You can choose how the record should start. The following can be select:
External application
Conversation indication
Conversation detection
DTMF sequence
Triggered by external conversation indication (RIA)
Triggered by external conversation detection (RIA)
RecordStopMode - You can select how the record should stop. The following can be choosen:
Use the triggers from recording start
External application
Conversation detection
DTMF sequence
Triggered by external conversation detection (RIA)
Number_Gateways the number of the configurable screen recording gateways. It is only
possible to configure as many gateway as there are licenses for INSPIRATION SCREEN
CAPTURE available in the dongle.
262/316

Configuration
Gateways
- Gateway_0 Gateway_n
IP: IPAddress or Hostname of the server, where the gateway is

installed. If the proxy gateway server runs on the IAS /
INSPIRATIONpro server, the IPAddress must be 127.0.0.1
Login: Gateway Login Name

Password: Gateway Password
Folder: Name fo the shared folder for screen recordings. Recording
folder from ProxyGatewayServer will be used if empty.
HDTreshold: value of diskspace to keep free. If exceeded, screen

sessions will be deleted.
Fig. 210 - Configuration Screen Recording Gateways
263/316

Configuration
4.12
Configuration - Recorder Information

Search
Print
Export
Import
Reload
Logout
Fig. 211 - Recorder Information

In this menu you can see all available channels with their ChannelID. Here you can enter the
recorder description. For each channel you can enter a channel description an Agent ID and a
PC name. You can assign an agent to a channel with the entries Agent ID and PC name.
Search:
Print:

Export:
Import:
Reload:

current data)
Logout

window
Adds a new stereo channel which consists of two mono channels to
the MARATHON EVOLUTION system
264/316

Configuration
Searches for channel IDs in the database and adds them to the list
265/316

Archive Client
Archive Client
This area of the hierarchical structure is used to administer the Archive Manager for the
MARATHON EVOLUTION system. It is used to define archive jobs for archiving the calls.
5.1
Job Configuration
New
Print
Activate/ Import all Export all Delete

deactivate
job
Reload
Logout
Fig. 212 - Job Configuration

Above this list there is a toolbar providing the following buttons for the configuration of the
archiving:
New:
Creates a new job
Print:
Prints the current job configuration list (not

available if ADM is executed on the recorder itself)
Activate/deactivate
job:
Activates/deactivates the current selected job
Import all:
Imports the whole job configuration from a

selected file
Export all:
Exports the whole job configuration to a selected

file
Delete:
Deletes the selected job configuration
266/316

Archive Client
Reload:

current data)
Exit:

Portal
window
Logout:
Enter a job name in the field Job Name and a job description in the field Job Description.
The checkbox Enabled activates/deactivates the job.
For detailed information about the job configuration in the Archive Client please refer to the
Installation
Manual
in
the
directory
5.2
Media Pool
The Media Pool is a list of all archive media of this system. Here you can see the MediaID,
MediaName, MediaStartDate, MediaEndDate and Device.
Print
Reload
Logout
Fig. 213 - Media Pool

Above this list there is a toolbar providing the following buttons for configuration:
Print:

available if ADM is executed on the recorder itself)
Reload:

current data)
Logout

window
267/316

Archive Client
The individual columns of the Media Pool table include the following information:
MediaID
Unique ID for each media. If you have defined a

parallel job you will see a MediaID starting with P-.
If you have created a CCB archive you will see a
MediaID starting with CCB-.
MediaName
Here you can see the name of the archive job.
MediaStartDate
Start time of the first call on the medium.
MediaEndDate
End time of the last call on the medium.
Device
Kind of medium e. g. DVD-RAM or AIT.
268/316

SDDM Client
SDDM Client
This area of the hierarchical structure is used to define SDDM (Selective Data Distribution
Management) jobs. You can transfer data either to an IAS (INTERACTION Software) or another
MARATHON EVOLUTION.
6.1
Overview
New
Search
Print
Import all Export all Delete
Reload
Logout
Fig. 214 - Job Configuration

Above this list there is a toolbar providing the following buttons for SDDM configuration:
New
Creates a new job.
Search
Searches for job entries in the list.
Print

available if ADM is executed on the recorder
itself).
Import all
Imports jobs from a selected file, see also Fig. 215

- Importing jobs.
Export all
Exports all jobs to a selected file.
Delete
Deletes the selected job configuration.
Reload

current data).
Logout

window.
269/316

SDDM Client
When importing files, the check box Overwrite? decides whether already configured jobs should
be overwritten.
Fig. 215 - Importing jobs

The individual columns of the SDDM Client table include the following information:
JobID
ID of the job
Type
Several job types like Call, Quality, Stream and

Rules based
Enabled
Indicates if the job is activated
Job state
Indicates if the job is running
Name
Name of the job
Description
Description of the job
ScheduleStartDate
Start date for the job
ScheduleLastDate
Last execution of the job
ScheduleNextDate
Next date when the job will be executed
TransferSessions
Counter how often the job has been executed
TransferFiles
Counter how many files have been transferred
TransferKBytes
Counter how many KBytes have been transferred
TransferErrors
Counter how many errors have been occured
Skips to the next configuration tab
For further information please refer to Installation Manual 08_SDDM_e_STV in directory

PLEASE NOTE
When using rules based jobs in combination with a time limit for the files
to be transmitted, please monitor the CPU load in order to recognize
when the system's capacities are exceeded.
270/316

Backup
Backup
This area of the hierarchical structure is used to define a database backup job. You can backup
the database to a medium (e. g. USB hard drive, USB stick, DVD RAM, etc.).
HINT
AIT drives can not be used to create database backups.
Reload
Logout
Fig. 216 - Database Backup

Above this list there is a toolbar providing the following buttons for backup configuration:
Reload:

current data)
Logout

window
271/316

Backup
The individual values of the Database backup have the following meaning:
Activated
Checkbox for activating the created job
Job Name
Name of the job
Job Description
Description of the job
Drive
Selection of the connected drives
State
Displays the current job state
Manual only
Checkbox for manual database

(disables the scheduling parameter)
Start Time
Start time for the job
Daily
Starts the job daily
Weekly
Starts with the selected weekday
performing
HINT
The database backup could take a long time and may degrade the
system performance. Therefore the database backup should be
performed outside the working hours.
Executes the database backup directly
HINT
For further information please refer to Installation Manual
08_Database_Backup_e_STV in directory 08_Optional_Functions.
HINT
Please contact an ASC service technician if the database is corrupt and
a database recovery is necessary.
272/316

Registry
Registry
This area of the hierarchical structure is used to administer the following settings of the registry of
the MARATHON EVOLUTION system:
Localization of the different MARATHON EVOLUTION client programs

Date and time formats for different programs
Changing the designations of the text fields
HINT
Only a superuser may administer the Registry.
Fig. 217 - Configuration Tree Registry
Fig. 218 - Change of Date/Time Format
273/316

Registry
For the POWERplay, Portal, INSTANTplay and the WEBplay (MARATHON XML Server) you
can enter names of your choice for the text fields in the list below the submenu Fields. For
INSPIRATIONpro you can enter name of the fields in the list below the submenu AgentFields. In
the registry, the fields will be displayed independent of their visibility. Changes for the ASC
DataManager fields need to be configured within the special country subfolder (e. g. Registry ->
ASC DataManager -> Localization -> en_US).
Fig. 219 - Registry - Fields e. g. POWERplay
HINT
You can only edit the names in the NodeValue column. The text in the
NodeName column must not be changed!
Functions of the buttons in the toolbar of the screen:
Renames the key
Adds a new key
Copies the contents of the key
274/316

Registry
Pastes the contents of the key
Starts the search
Prints the contents of the key
Deletes the key
Exports a key
Imports a key
Reloads the key
Refreshes the configuration tree
Logs out / exit
275/316

Registry
8.1
Registry - Phone Appliance - Config
Fig. 220 - Registry - Phone Appliance - Config

The subfolder Phone Appliance contains the items
Call Statistics
Global
INSTANTplay
VCAM
to configure the Phone Appliance application.

HINT
After you have changed the configuration of the Phone Appliance you
always have to restart your recorder to activate the new settings.
8.1.1
Configuration of Call Statistics
Fig. 221 - Registry - Phone Appliance - Call Statistics

NodeName
NodeValue(s) [Default]
Description
DemoMode
[0]
Activates the demo mode (display of

randomized data).
MaxDisplayCalls
[100]
Amount of statistically evaluated calls.
276/316

Registry
8.1.1.1
Configuration of Chart Channel Total Usage
Fig. 222 - Registry - Phone Appliance - Chart Channel Total Usage

NodeName
Description
SectionCount
1 ... 8
[3]
Amount of different colored diagram

sections.
ShowLegend
[0]
Activating the legend. Use 1 to

activate the legend and 0 to
deactivate the legend.
Title
[Channel Total Usage]
Title of the diagram.
XAxisLabel
[Recording channel count] Lettering of the X axis.
YAxisLabel
[% of total time]
Lettering of the Y axis.
Sublevel Section _n
Fig. 223 - Registry - Phone Appliance - Chart Channel Total Usage

NodeName
AnnotationText
Description
Annotation of diagram section.
Color
Color of the diagram section and the

green, yellow, red, blue,
background.
cyan, magenta, gray,
orange, pink, white, black
[green]
EndPercent
[60.0]
Defines the end of the section

diagram in percent.
277/316
8.1.1.1.1

Registry
NodeName
Description
LegendText
text
[ok]
Text of the legend, if activated.
ShowBackgroundColor
[0]
Activates the background color. Use 1

to activate and 0 to deactivate the
background color.
Configuration of Chart Recording Channel Usage
Fig. 224 - Registry - Phone Appliance - Chart Recording Channel Usage

NodeName
Description
SectionCount
1 ... 8
[3]
Amount of different colored diagram

sections.
ShowLegend
[0]
Activating the legend. Use 1 to

activate the legend and 0 to
deactivate the legend.
Title
[Recording channel
usage]
Title of the diagram.
XAxisLabel
[Recording channel
number]
Lettering of the X axis.
YAxisLabel
[% of total time]
Lettering of the Y axis.
Sublevel Section _n
Fig. 225 - Registry - Phone Appliance - Chart Record Channel Usage
278/316

Registry
NodeName
AnnotationText
8.1.1.1.2
Description
Annotation of diagram section.
Color
Color of the diagram section and the

green, yellow, red, blue,
background.
cyan, magenta, gray,
orange, pink, white, black
[green]
EndPercent
[70.0]
Defines the end of the section

diagram in percent.
LegendText
text
[ok]
Text of the legend, if activated.
ShowBackgroundColor
[0]
Activates the background color. Use 1

to activate and 0 to deactivate the
background color.
Configuration of a Client_n
Fig. 226 - Registry - Phone Appliance - Client

This section has to be configured for every possible client type. A new client type is necessary if
a phone device with a screen resolution is connected that differs from already configured clients.
NodeName
Description
Description
[optiPoint 410 standard]
Enter the name of the configured

client device.
ImageHeight
[185]
Defines the height in pixel of the chart

image.
ImagePath
[/Siemens1/]
Subdirectory in which all graphic

items of the client are stored.
ImageWidth
[240]
Defines the width in pixel of the chart

image.
279/316

Registry
8.1.1.2
Configuration of Global
Fig. 227 - Registry - Phone Appliance - Global

8.1.1.3
NodeName
Description
ChannelCount
[60]
Amount
of
the
recording channels.
DemoCallMaxDelay
[5000]
Max. time interval in milliseconds

between two randomized calls.
DemoCallMaxDuration
[2200000]
Max. duration in milliseconds of a

randomized call.
IpAddress
[127.0.0.1]
IP address of the recorder.
UTCTimeFormat
[0]
This is the format of the UTC time.
contemplated
Configuration of the INSTANTplay
Fig. 228 - Registry - Phone Appliance - INSTANTplay

NodeName
Description
DemoMode
[0]
Activates the demo mode (display of

randomized data).
LCRIp
[000.000.000.000]
Enter the IP Address of the LCR

server.
LCRNumberPrefix
[0]
First part of the LCR number string.
LCRNumberSuffix
[@000.000.000.000]
Last part of the LCR number string.
280/316
8.1.1.3.1

Registry
NodeName
Description
LCRPort
5555
Enter the port of the LCR server.
LCRTimeoutInterval
[90]
Enter the timout in seconds for the

LCR server.
RTPMode
[direct]
Enter the Mode of RTP.
RTPServerIp
[000.000.000.000]
Enter the IP Address fo the RTP

server.
RTPTempPath
[]
Enter here the path of TRP temp.
MaxDisplayCalls
[20]
Enter the maximum amount of calls

provided for the replay.
SessionTimeout
[1800]
Enter the timeout in seconds after the

session of a connected client will be
disconnected.
Fig. 229 - Registry - Phone Appliance - INSTANTplay - Client

a phone device with a screen resolution is connected that differs from already configured clients.
NodeName
Description
Description

client device.
ImagePath
[/Siemens1/]

PlaybackMode
[lcr]
Enter the playback mode.
281/316

Registry
8.1.1.4
Configuration of the Visual Central Alarm Management (VCAM)
Fig. 230 - Registry - Phone Appliance - Visual Central Alarm Management

8.1.1.4.1
NodeName
Description
ModuleNameOrder
[ias,recorder,ctic,pbx]
Order of the components displayed in

a VCAM window.
ModuleStateOrder
[red,yellow,green,grey]
Order of the status icons within the

area of a component.
VCAMProtocolLog
[0]
Enables the VCAM server log. Use 1

to activate and 0 to deactivate the log.
VCAMServerAddress
[127.0.0.1]
Enter the IP address of the VCAM

server.
VCAMServerPort
[60066]
Enter the IP port of the VCAM server.
Fig. 231 - Registry - Phone Appliance - VCAM - Client

a phone device differs from already configured clients.
282/316

Registry
NodeName
Description
Description

client device.
ImagePath
[/Siemens1/]

MidletName
[VCAM]
Application name in the optiPoint

configuration.
PhonePort
[8085]
Enter the phone port of the telephone.
ProgramName
[PAA/VCAMFronted]
Program name on the server in the

optiPoint configuration.
ServerAddress
[000.000.000.000]
Enter the server address in the

optiPoint configuration.
ServerPort
[8080]
Enter the server port in the optiPoint

configuration.
TimeoutInterval
[30]
Timeout in seconds until the client will

be disconnected.
Fig. 232 - Registry - Phone Appliance - VCAM - WEB Client

NodeName
Description
Description
[Web Client ]

client device.
ImagePath
[/Web/]

RefreshInterval
[15]
Timespan in seconds till the display

will be refreshed.
TimeoutInterval
[30]
Timeout in seconds until the client will

be disconnected.
283/316

Registry
8.1.1.5
Registry - VOIP XML SERVICE

The subfolder VOIP XML SERVICE is only relevant for Cisco and Alcatel applications of the
EVOip or EVOip active modules.
Fig. 233 - Registry - VOIP XML SERVICE

The subfolder VOIP XML SERVICE contains the items
Config
Recorders
Language
Alcatel Info
to configure the EVOip or EVOip active module for Cisco applications.

HINT
After you have changed the configuration of the VOIP XML SERVICE
you always have to restart your recorder to activate the new settings.
284/316

Registry
Fig. 234 - Alcatel info
8.1.1.6
Registry - VOIP XML SERVICE - Config
Fig. 235 - Registry - VOIP XML SERVICE - Config
285/316

Registry
NodeName
Description
field-value
max. four user-specific

texts
This parameter is used to predefine

up to four texts which can be selected
at the INFO page of the phone
application to be tagged to the call.
E.g. if this parameter is set as
"Inquiry;Complaint;Reservation;
Other" the INFO page of the phone
applicaton will provide a choice of
those four texts to be tagged to the
current call.
If this parameter starts with a #
character (default) the user can enter
a free form text at the INFO page.
ess-port
50050
This parameter defines the ESS port.
ess-password
[1]
Enter the password configured for the

ESS in the User Administration.
ess-user
[1]
Enter the user name configured with

ESS
rights
in
the
User
Administration.
log-path
[logs]
Enter the path to the logfile.
tag-field
[CALLCOMMENT]
ASCII1-20
LONG1-10
AGENTID
OWNNUMBER
PARTNERNUMBER
THIRDNUMBER
CALLDIRECTION

the additional information for each call
(INFO page) will be saved.
ess-ip
127.0.0.1
Enter the IP address of the ESS

server.
voip-mode
[PASSIVE]
ACTIVE_AUTOMATIC
ACTIVE_MANUAL
This parameter is specific to the

integration used. Please refer to the
corresponding installation manual for
details.
cti-ip
127.0.0.1
Enter the IP address of the CTI

server.
web-home
/usr/asc/bin/tomcat/webap Enter the path to the VoIP XML

ps/
service.
ess-client-port
9900
Enter the port of the ESS client.
cti-path
/usr/asc/bin/CticCisco
Enter the path to the CticCisco

module. Not used yet.
cti-port
1234
Enter the port of the CticCisco

module.
ess-timeout
15
Enter a time value (in seconds) the

system will wait for an answer of the
ESS server. After this time has run out
the system will stop trying to establish
a connection.
286/316

Registry
NodeName
Description
cti-timeout
30

Ctic Cisco module that is responsible
for communication with the Cisco IP
phones. After this time has run out the
system will stop trying to establish a
connection.
redundant-service-url
URL of the redundant

VoIP Service
Leave this field deactived by leaving a

# as first character of this field.
service-ip
[eth0]
eth1
IP address of recorder
Enter the network interface card or

the IP address of the recorder that
should be used for the VoIP service.
ticket-id-field
ASCII0 - ASCII19
Select an ASCII field of the database

where the application will read the
Ticket ID from to display it on the
telefone screen.
If a # is entered as the first character
of this field the Cisco-specific Ticket
ID is displayed instead.
display-update-interval
[8 sec]
Enter the timespan between two

display updates at the terminal. The
default value is 8 seconds.
original-called-number-field ASCII0 - ASCII19
Enter an ASCII field like ASCII1. In

this case, XVOIP tries to tag the
original called number in the field
ASCII1. If a # is entered as the first
character of this field, the value is
comment out.
E.g. Customer (EXT=123) calls agent
A (EXT=456). But the agent is not at
his place at the moment and so, agent
B (EXT=789) takes the call of agent
A. So, the own telephone number is
789, the partner phone number is 123
and the original called number is 456.
Errors and warnings concerning the VOIP XML SERVICE are written in a separate log file
named xvoip.log that is located in the following directory:
/usr/asc/bin/tomcat/logs/
To configure the amount of information written in the logfile open the file server.xml located in the
directory:
/usr/asc/bin/tomcat/conf/
To write all debug messages in the log file replace the word INFO in the line
<Environment
value="INFO"/>
name="DebugLevelXVOIP"
override="false"
type="java.lang.String"
of the file server.xml with the word DEBUG. For additional log information like SQL statements,
etc., replace the word INFO with "DEBUG, DevConsole".
287/316

Registry
8.1.2
Registry - VOIP XML SERVICE - Recorders
Fig. 236 - Registry - VOIP XML SERVICE - Recorders

This dialog box is used for Cisco applications with HTML and JTAPI in order to define the
available EVOip active modules.
Define the extension and the channels of your EVOip active modules according to the following
structure:
In the left column NodeName enter the extension number of the EVOip active after the prefix
phone-.
In the right column NodeValue enter the Recorder ID (see section 4 - Configuration) followed by
a hyphen and the respective channel number (e. g. 4PPGC4X-20).
8.1.3
Registry - VOIP XML SERVICE - Languages

The subfolder Languages is used to switch between the different languages of the XML service
and to define individual texts for the user interface. It contains the item en_EN for the English
288/316

Registry
language and de_DE for German. By default, English is activated as interface language because
in the subfolder en_EN/Config the parameter default is set to true.
Fig. 237 - Registry - VOIP XML SERVICE - Languages - en_EN - Config

To enable a different language as default language, set the parameter default in the VOIP XML
Service registry folder ...Languages/xx_XX/Config to true. E.g. ...Languages/de_DE/Config to
true.
NOTE
Please make sure only one default language is set to true otherwise the
first set default language in alphabetic order is activated.
289/316

Registry
To adapt the texts in the graphical user interface to your individual requirements, open the
Content screen of the respective language and edit the column NodeValue.
Fig. 238 - Registry - VOIP XML SERVICE - Languages - en_EN - Content

8.1.4
Registry - UCVOIP XML SERVICE

The subfolder UCVOIP XML SERVICE is only relevant for Cisco applications of the EVOip active
modules.
Fig. 239 - Registry - UCVOIP XML SERVICE

The subfolder UCVOIP XML SERVICE contains the items
Language
Config
Recorders
290/316

Registry
to configure the EVOip active module for Cisco applications.

HINT
After you have changed the configuration of the UCVOIP XML
SERVICE you always have to restart your recorder to activate the new
settings.
8.1.5
Registry - UCVOIP XML SERVICE - Config
Fig. 240 - Registry - UCVOIP XML SERVICE - Config

NodeName
Description
cti-ip
127.0.0.1
Enter the IP address of the CTI

server.
cti-path
/usr/asc/bin/CticCisco
Enter the path to the CticCisco

module. Not used yet.
cti-port
1234
Enter the port of the CticCisco

module.
cti-timeout
30

Ctic Cisco module that is responsible
for communication with the Cisco IP
phones. After this time has run out the
system will stop trying to establish a
connection.
ess-timeout
15

ESS server. After this time has run out
the system will stop trying to establish
a connection.
291/316

Registry
NodeName
Description
field-value
max. four user-specific

texts
[#Test commentar 1;
Test commentar 2;
Test commentar 3;
Test commentar 4]
This parameter includes four different

values. The texts included in these
values will be tagged to every
recorded call.
If the fields are empty the user can
enter a text of his/her choice that will
be tagged to every recorded call.
log-path
[logs]
Enter the path to the logfile.
service-ip
[eth0]
eth1
IP address of recorder
Enter the network interface card or

the IP address of the recorder that
should be used for the VoIP service.
sync-service-ip
Enter the network address of the

second UCVOIP used in redundancy
scenarios.
sync-service-port
[5995]
Port number used on the second

UCVOIP.
tag-field
[CALLCOMMENT]
ASCII1-20
LONG1-10
AGENTID
OWNNUMBER
PARTNERNUMBER
THIRDNUMBER
CALLDIRECTION

the additional information for each call
will be saved.
ticket-id-field
ASCII0 - ASCII19
[ASCII5]

where the Cisco-specific Ticket ID
number will be saved with every
recorded call.
If you want to tag the MARATHON
EVOLUTION-specific Call ID number
to every call, deactivate this feature
by entering a # as first character in
front of this line.
visibility-id-field
ASCII0 - ASCII19
[ASCII5]

where the Cisco-specific Visibility ID
number will be saved with every
recorded call.
voip-mode
[PASSIVE]
ACTIVE_AUTOMATIC
ACTIVE_MANUAL
This parameter is specific to the

integration used. Please refer to the
corresponding installation manual for
details.
Do not select the value PASSIVE.
web-home
/usr/asc/bin/tomcat/webap Enter the path to the VoIP XML

ps/UCVOIP
service.
292/316

Registry
NodeName
original-called-number-field ASCII0 - ASCII19
Description
Enter an ASCII field like ASCII1. In
this case, XVOIP tries to tag the
original called number in the field
ASCII1. If a # is entered as the first
character of this field, the value is
comment out.
E.g. Customer (EXT=123) calls agent
A (EXT=456). But the agent is not at
his place at the moment and so, agent
B (EXT=789) takes the call of agent
A. So, the own telephone number is
789, the partner phone number is 123
and the original called number is 456.
Errors and warnings concerning the UCVOIP XML SERVICE are written in a separate log file
named ucvoip.log that is located in the following directory:
directory:
<Environment
value="INFO"/>
name="DebugLevelUCVOIP"
override="false"
8.1.6
Registry - UCVOIP XML SERVICE - Recorders
Fig. 241 - Registry - UCVOIP XML SERVICE - Recorders

This dialog box is used for Cisco applications with HTML and JTAPI in order to define the
available EVOip active modules.
293/316

Registry
Define the extension and the channels of your EVOip active modules according to the following
structure:
In the left column NodeName enter the extension number of the EVOip active after the prefix
phone-.
In the right column NodeValue enter the Recorder ID (see section 4 - Configuration) followed by
a hyphen and the respective channel number (e. g. 4PPGC4X-20).
8.1.7
Registry - UCVOIP XML SERVICE - Languages

language and de_DE for German. By default, English is activated as interface language because
in the subfolder en_EN/Config the parameter default is set to true.
Fig. 242 - Registry - UCVOIP XML SERVICE - Languages - en_EN - Config

true.
NOTE
294/316

Registry
Fig. 243 - Registry - UCVOIP XML SERVICE - Languages - en_EN - Content

8.1.8
Registry - MARATHON XML SERVER

The subfolder MARATHON XML SERVER is only relevant for WEBplay and INSTANT WEBplay.
Fig. 244 - Registry - MARATHON XML SERVER
295/316

Registry
The subfolder MARATHON XML SERVER contains the items
Languages
Config
Users
to configure the WEBplay and INSTANT WEBplay.
HINT
After you have changed the configuration of the MARATHON XML
SERVER you always have to restart your recorder to activate the new
settings.
8.1.9
Registry - MARATHON XML SERVER - Language

language and de_DE for German. By default, English is activated as language because in the
subfolder en_EN/Config the parameter default is set to true.
Fig. 245 - Registry - MARATHON XML SERVER - Languages - en_US - Config

true.
NOTE
296/316

Registry
Fig. 246 - Registry - MARATHON XML SERVER - Languages - en_EN - Content

8.1.10
Registry - MARATHON XML SERVER - Config
Fig. 247 - Registry - MARATHON XML SERVER - Config
297/316

Registry
NodeName
Description
alarm-ip
[127.0.0.1]
This parameter defines the IP address

for the alarm management.
Please dont change this value!
alarm-port
[4567]
This parameter defines the port for

the communication between alarm
management and MARATHON XML
SERVER.
dtmf-sequence-enabled
[true]
false
IMPORTANT: Please dont change

this value!
fs-ftp
[false]
true
This parameter defines if the call data

should be replayed from a connected
file server and not from the local
system.
fs-ip
[000.000.000.000]

for the connected file server.
fs-password
[asc1234]
This parameter defines the password

for the connected file server.
fs-path
[/calldata/CallPool]
This parameter defines the path to the

call data on the file server.
fs-user
[db]
This parameter defines the user for

the connected file server.
lcr-ip
[127.0.0.1]

for the LCR server.
lcr-port
[5555]

the communication between the LCR
server
and
MARATHON
XML
SERVER.
log-path
[logs]
This parameter defines the path to the

log files.
logo-flash
[true]
false
This parameter defines if there will be

an animation at the initial screen of
the WEBplay.
ls-ip
[127.0.0.1]

for the license server.
298/316

Registry
NodeName
Description
ls-password
[IASAdmin]
This parameter defines the password

for the license server.
ls-port
[7700]

the communication between the
license server and MARATHON XML
SERVER.
ls-user
[IASAdmin]
This parameter defines the user for

the license server.
password-restrict
[false]
true
This parameter defines if there should

be restricitons for passwords (e.g.
minimal length, not only numbers or
only characters, ...).
save-as-wave-enabled
[true]
false
This parameter defines if the user

should have the possibility to save a
call as wave file.
service-ip
[eth0]
This parameter defines via which

network
connection
the
communication between MARATHON
EVOLUTION
and
WEBplay
/
INSTANT WEBplay will be.
session-timeout
-1 .. 86400
[1800]
This parameter defines the automatic

logout time in seconds. The value -1
means that there will be no automatic
logout.
stereo-method-new
[true]
false
This parameter should be set to true if

the MARATHON EVOLUTION version
will be 5.0 or higher.
stereo-search
[false]
true
This parameter defines if the search

on stereo channels will be available.
type
[EVO]
TDI
VOIP
This parameter defines which kind of

database structure will be used.
web-home
[/usr/asc/bin/tomcat/weba This parameter defines the path to the

pps/XSRS]
MARATHON XML SERVER.
Errors and warnings concerning the MARATHON XML SERVER are written in a separate log file
named xsrs.log that is located in the following directory:
directory:
299/316

Registry
<Environment
value="INFO"/>
name="DebugLevelXSRS"
override="false"
8.1.11
Registry - MARATHON XML SERVER - Users

Fig. 248 - Registry - MARATHON XML SERVER - Users

NodeName
Description
agents
[*]
This parameter defines which agents

(resp. to the user rights) can be
searched for.
This value can be defined with the
WEBplay / INSTANT WEBplay user
interface.
call-count
5 .. 50
[10]
This parameter defines the maximum

number of search results.
interface.
300/316

Registry
NodeName
Description
channels
[*]
This
parameter
defines
which
channels (resp. to the user rights) can
be searched for.
interface.
close-logout
[true]
false
This parameter defines if there should

be an automatic logout if the window
will be closed.
INSTANT WEBplay user interface.
field-name
This parameter defines the database

field which should be used for the
searches.
field-value
This parameter defines which value

has to be entered in the field-name.
language
[en_EN]
This parameter defines the default

language.
interface.
last-calls-access
1 .. x
[-1]
This parameter defines the number of

previous calls of a previous user that
the current user has access to (e. g.
when shift changes). The value -1
means that the functionality has been
deactivated.
last-minutes-access
1 .. 35791 minutes
[-1]
This parameter defines a time period

in minutes previous to the current
users login. The calls during this
period can still be accessed by the
current user. The value -1 means that
the
functionality
has
been
deactivated.
lcr-count
All
5
15
30
[90]
180
360
This parameter defines the number of

days for last call repeat searches. Be
aware that higher values will increase
the search time.
interface.
301/316

Registry
NodeName
Description
linear-pcm-enabled
[false]
true
This parameter defines if a call is

saved as a wave file if it will be in
linear format (=true) or G.711 format
(=false).
mode
[ELCR]
LCR
This parameter defines if the

enhanced LCR mode or the standard
LCR mode will be used.
phone
This parameter defines the phone

number which will be called if replay
via phone has been selected.
interface.
play-LAN
[true]
false
This parameter defines if the replay

should be via LAN (=true) or via
phone (=false).
interface.
play-MODE
[MAX]
MIN
This parameter defines if the

INSTANT WEBplay should be started
in minimized mode (=MIN).
Only relevant for INSTANT WEBplay.
search-for
[channels]
agents
This parameter defines if there will be

searched for channels or for agents.
interface.
timeout
1 .. 144000 minutes
[30]
This parameter defines the automatic

logout time for this user.
interface.
replay-audio-format
[MU_LAW_STEREO]
This defines in which format the audio

data will be replayed.
save-audio-format
[MU_LAW_STEREO]
This defines in which format the audio

data will be saved.
utc
[0]
set-size
[10]
result-table-cols
302/316

Information
Information
9.1
Versions
This window displays the installed versions of the modules. These entries are automatically
created and can not be changed.
ModuleName
Name of the MARATHON EVOLUTION module
CompleteVersionNum
ber
Version number (5 digits)
Check mark is set if a hotfix is installed
Check mark is set if a special is installed
InstallationDate
Day of installation / update
Comment
Name of the module in plain text
For system and dongle updates please refer to the Installation Manual directory
04_Update_Upgrade.
Print
Reload
Logout
Fig. 249 - Versions
303/316

Information
9.2
Update
With the button Update you can start an update of the MARATHON EVOLUTION system.
Therefore all local and FTP locations for an update will be scanned. The first update location
found will be used for updating the system.
9.2.1
Configuration of the FTP update

By clicking the update URLs button the edit update URLs window opens. Here you can type in
the URL of the FTP server where the update file is located.
Please use the following format for the URL:
ftp://username:password@IP address of the FTP server/
e.g. ftp://asc:asc1234@192.168.10.10/.
It is possible to enter more than one address. Click the return key of your keyboard to enter a
new address. All entered addresses will be scanned for the update files.
Fig. 250 - Edit Update URLs
Fig. 251 - Edit Update URLs (example for several addresses)

9.3
Version History
The area Information also contains the sub menu Version History. This screen displays a longer
list of MARATHON EVOLUTION modules with additional information which is similar to the list in
the Versions screen. This list displays all modules that have ever been installed in this
304/316

Information
MARATHON EVOLUTION system which means that this is the long-term memory for the module
versions installed.
Print
Reload
Logout
Fig. 252 - Version History

9.4
License Overview
The area Information also contains the sub menu License overview. This screen displays a list of
all available licences on your MARATHON EVOLUTION indicating whether they are currently in
use or not. Here you can also update the dongle by clicking the dongle update button.
Dongle
update
Print
Reload
Logout
Fig. 253 - License Overview
305/316

Information
9.5
Downloads
Select the sub-item Downloads to display the following screen.
Fig. 254 - ADM: Information / Downloads

The Downloads screen displays new software available for download.
306/316

Troubleshooting
10
Troubleshooting
10.1
Alarm Messages
Module
Code
LogType
API Server
ADM_ARCHIVEJOB_CRE Error
ATED
An archive job could not be Eject the archive medium. Restart the
created
system. If necessary contact the hotline.
API Server
ADM_ARCHIVEJOB_DEL
ETED
Error
An archive job was deleted
API Server
ADM_ARCHIVEJOB_SAV
ED
Error
An archive job could not be Eject the archive medium. Restart the
saved
API Server
ADM_CHANNELGUARDS Error
_SAVED
The configuration of the channel Check the configuration with the

guard could not be saved
installation manual. If necessary contact
the hotline.
API Server
ADM_CHANNEL_SAVED
Error
The configuration of a recording Check the channel configuration.

channel could not be saved
API Server
ADM_CONFIGURATION_
SAVED
Error
The system configuration could Check the system configuration.

not be saved
API Server
ADM_LOGGERCONFIGU
RATION_SAVED
Error
The information about an other Check the configuration.

EVOLUTION could not be
saved
API Server
ADM_PHONENUMBERS_ Error
SAVED
The configuration of a telephone Check the configuration with the

number list could not be saved installation manual. If necessary contact
the hotline.
API Server
ADM_RECORDINGCRITE Error
RIA_SAVED
The
configuration
of
the Check the configuration with the
recording planer could not be installation manual. If necessary contact
saved
the hotline.
API Server
ADM_SDDMJOB_CREAT
ED
Error
A SDDM job could not be Check the configuration with the

created
the hotline.
API Server
ADM_SDDMJOB_DELET
ED
Error
A SDDM job could not be Stop the SDDM job and try again. If
deleted
necessary contact the hotline.
API Server
ADM_SDDMJOB_SAVED
Error
A SDDM job could not be saved Stop the SDDM job and try again. If
API Server
ADM_SENDCONFIG_SAV Error
ED
The configuration of the alarm Check the configuration with the

notifications could not be saved installation manual. If necessary contact
the hotline.
API Server
ADM_TIMEROPERATION
S_SAVED
Error
The configuration of a timer Check the configuration with the

opration list could not be saved installation manual. If necessary contact
the hotline.
API Server
ADM_USER_CREATED
Error
The configuration of an user Check the configuration with the

could not be created
the hotline.
API Server
ADM_USER_DELETED
Error
The configuration of an user Restart the system and try again. If

could not be deleted
API Server
ADM_USER_IMPORTED
Error
The
import
of
configurations failed
API Server
ADM_USER_SAVED
Error
The configuration of an user Check the configuration with the

could not be saved
the hotline.
API Server
ALARM_CALLINFO_FAIL
URE
Error
An error was detected while Contact the hotline.

accessing a call data file
Description
To Do
Eject the archive medium. Restart the

user Restart the system and try again. If

307/316

Troubleshooting
Module
Code
LogType
API Server
ALARM_DB_CONNECTIO Error
N
The connection to the database Restart the system. If necessary contact

could not be established
the hotline.
API Server
ALARM_DB_ERROR
Error
An error was detected while Contact the hotline.

accessing the database
API Server
ALARM_ESS_CLIENT_TI
MEOUT
Error
An ESS client did not answer in Check if the ESS client is running. Check
the expected time
the network connection.
API Server
ALARM_LICENSE_SERV
ER_FAILED
Error
The connection to the license Restart the system. If necessary contact

server could not be established the hotline.
API Server
ALARM_MASTER_MISSI
NG
Error
A master EVOLUTION is not Check the configuration. Check the

connected
network connection to the master.
API Server
ALARM_SLAVE_MISSING Error
A slave EVOLUTION is not Check the configuration. Check the

connected
network connection to the slave.
API Server
ALARM_CHANNELGUAR
D
Warning
A channel guard has detected a Check the channel activity in the Portal.
problem
If there is no change of state on one
channel, check this line. If there are no
changes at all, reboot the system.
API Server
ALARM_MESSAGE_FAIL
URE
Warning
An API client tried to send a Check the ESS client regarding

message in a wrong format.
compatibility. If necessary contact the
hotline.
API Server
ALARM_MASTER_CONN
ECTED
Information A master
connected
API Server
ALARM_SLAVE_CONNEC Information A
slave
TED
connected
API Server
ALARM_UNKNOWN_ESS Information An not configured ESS client An unknown client tried to connect. No
_CLIENT
tried to log in
action necessary.
Description
To Do
EVOLUTION
is A master is connected. No action

necessary.
EVOLUTION
is A slave is
necessary.
connected.
No
action
308/316

Troubleshooting
309/316

Troubleshooting
310/316

Troubleshooting
311/316

Troubleshooting
312/316

Troubleshooting
313/316

Troubleshooting
314/316

Troubleshooting
315/316

Troubleshooting
316/316

06 ASC DataManager e TV

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

06 ASC DataManager e TV

Uploaded by

Copyright:

Available Formats

ASC DataManager

This manual is valid for the following ASC products:

EVOip Server Software

ASC telecom AG - Seibelstr. 2-4 - D-63768 Hsbach - Germany

ASC Data Manager (ADM)

System Requirements .........................................................................................................................................5

ASC DataManager Login................................................................................................................. 9

User Administration - Users ..............................................................................................................................11

Configuration - System ......................................................................................................................................39

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Configuration of RIApassive for Siemens HiPath Trading IP ...........................................................................215

Archive Client............................................................................................................................... 266

Job Configuration ............................................................................................................................................266

SDDM Client ................................................................................................................................. 269

Registry - Phone Appliance - Config ...............................................................................................................276

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Information ................................................................................................................................... 303

Troubleshooting .......................................................................................................................... 307

Alarm Messages .............................................................................................................................................307

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Microsoft Internet Explorer V 10.0 or V 11.0

Hierarchical Structure of the ASC DataManager

Fig. 1 - ASC DataManager window

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Fig. 2 - Hierarchical Structure

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

ModuleName), to the number of the version (column CompleteVersionNumber), to the date of

Fig. 3 - Sorting Lists

Searching within Lists

Part of field content

Search word is somewhere in the text field

Search word must match exactly the content of

Extended search functions which allows the

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

ASC DataManager Login

Fig. 4 - Login screen

To select the language click on the appropriate flag

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Combi user login

Fig. 5 - Combi user login

Fig. 6 - Combi user button

Fig. 7 - Single Sign On button

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

The menu item User Administration in the hierarchical structure

User Administration - Users

Import to Import all Export Export

Fig. 8 - User Administration - Users

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)

Fig. 9 - Registry - ASC DataManager - Configuration

Installation Manual EVOip / EVOLUTION -10.0 Rev. 11

ASC Data Manager (ADM)