ASC Call Recording for Siemens HiPath 4000 - Papagayo System, CA

ASC Call Recording 

for Siemens HiPath 4000 

Installation Manual 

for the installation, configuration and administration 

incl. User Manual RIA Server 

Version 20.03.07

ASC Call Recording for Siemens HiPath 4000 

1 Introduction to the Installation Manual.......................................................................................... 3 

2 List of Abbreviations....................................................................................................................... 4 

3 Preliminary Remarks and Restrictions.......................................................................................... 5 

3.1 Copyright .............................................................................................................................................................5 

3.2 Range of Validity .................................................................................................................................................5 

3.3 Limited Warranty .................................................................................................................................................5 

3.4 Disclaimer ...........................................................................................................................................................5 

3.5 Limitation of Liability ............................................................................................................................................5 

3.6 ASC Software License Agreement ......................................................................................................................6 

3.7 Licenses ..............................................................................................................................................................6 

3.8 Restrictions .........................................................................................................................................................6 

4 Classification of Safety Advice and Warning Instructions .......................................................... 7 

5 Description of the Software............................................................................................................ 8 

5.1 Trunk Side Recording .........................................................................................................................................8 

5.2 Extension Side Recording ...................................................................................................................................8 

5.3 Silent Monitoring .................................................................................................................................................9 

5.3.1 Dynamic, Selective Recording .............................................................................................................................9 

5.3.1.1 User-Activated Start and Stop..............................................................................................................................9 

5.3.1.2 Threat Call Recording (KEEP) .............................................................................................................................9 

5.3.1.3 Private Call Elimination (DELETE).......................................................................................................................9 

5.3.2 Centralized Recording........................................................................................................................................10 

5.3.3 Dynamic Assignment of Agents .........................................................................................................................10 

5.3.4 Dynamic Assignment of Recording Channels....................................................................................................10 

5.3.5 Class of Recording (CoR) ..................................................................................................................................10 

5.4 Tagged Call Information ....................................................................................................................................11 

6 System Requirements................................................................................................................... 12 

6.1 System Components by ASC ............................................................................................................................12 

6.1.1 MARATHON EVOLUTION.................................................................................................................................12 

6.1.2 RIA Server Siemens HiPath 4000......................................................................................................................12 

6.2 System Components by Siemens .....................................................................................................................13 

6.2.1 Siemens HiPath 4000 .......................................................................................................................................13 

6.2.2 Siemens CAP Server .........................................................................................................................................13 

7 Installation of the RIA Server........................................................................................................ 15 

7.1 Installing the RIA Server Base Software ...........................................................................................................15 

7.2 Installing the RIA Server for Siemens HiPath 4000 ..........................................................................................19 

8 Configuration of Siemens CAP .................................................................................................... 23 

8.1 CAP Version ......................................................................................................................................................23 

8.2 Service - Switch Connection .............................................................................................................................23 

8.2.1 List of Switch Connections.................................................................................................................................23 

8.2.2 Switch Connection - SCC...................................................................................................................................24 

8.2.3 Switch Connection - CA4000 .............................................................................................................................24 

8.2.4 Switch Connection - Switch................................................................................................................................25 

8.3 Service - Domain Information ............................................................................................................................26 

8.4 Users .................................................................................................................................................................26 

8.4.1 User for CTI Connectivity...................................................................................................................................27 

8.5 Devices .............................................................................................................................................................27 

8.5.1 List of Devices....................................................................................................................................................27 

8.5.2 Device Properties...............................................................................................................................................29 

9 Configuration of Siemens HiPath 4000........................................................................................ 30 

10 Configuration of MARATHON EVOLUTION................................................................................. 32 

10.1 Recording Channels ..........................................................................................................................................32 

10.2 Physical Connection of the Recorder to PBX ....................................................................................................33 

10.2.1 The DIUN Card ..................................................................................................................................................34 

10.2.2 Pin Assignment of the DIU-N2 ...........................................................................................................................34 

10.2.3 Connection Cable...............................................................................................................................................34 

11 Configuration and Administration of the RIA Server ................................................................. 36 

11.1 RIA Server Configurator ....................................................................................................................................36 

11.1.1 Checklist - Required Information........................................................................................................................36 

Installation Manual ASC Call Recording for Siemens HiPath 4000 - 5.0 Rev. 00 1/96


11.1.2 Accessing the RIA Server Configurator .............................................................................................................36 

11.1.3 Login to the RIA Server Configurator.................................................................................................................38 

11.1.4 Creating and Modifying Users............................................................................................................................39 

11.1.5 RIA Connection..................................................................................................................................................39 

11.1.6 PBX....................................................................................................................................................................40 

11.1.7 Extensions..........................................................................................................................................................42 

11.1.8 SiMo Information................................................................................................................................................43 

11.1.9 Buttons...............................................................................................................................................................46 

11.1.10 Class of Recording.............................................................................................................................................47 

11.1.11 Texts for Display ................................................................................................................................................49 

11.1.12 Overview – PBX.................................................................................................................................................49 

11.1.13 Overview – Monitor Points .................................................................................................................................50 

11.1.14 Overview – Check Result...................................................................................................................................50 

12 RIA Client Configuration............................................................................................................... 51 

12.1 Common Configuration .....................................................................................................................................51 

12.2 RIAactive Configuration ....................................................................................................................................52 

12.3 RIApassive Configuration ..................................................................................................................................54 

13 Test Hints ....................................................................................................................................... 57 

13.1 Connection to CAP and HiPath 4000 ................................................................................................................57 

13.2 Setting Monitor Points .......................................................................................................................................57 

13.3 Calling the Recorder (Getting Trunk Numbers) .................................................................................................58 

13.4 Performing Calls Using the RCG Group ...........................................................................................................58 

14 Appendix: AMO Commands ......................................................................................................... 59 

14.1 HOME PBX Settings .........................................................................................................................................59 

14.1.1 CTI Definition .....................................................................................................................................................59 

14.1.2 ACD Settings......................................................................................................................................................60 

14.1.3 Recorder Settings ..............................................................................................................................................61 

14.1.3.1 Configuration of WAML Card (Home PBX)........................................................................................................88 

14.2 Remote PBX Settings .......................................................................................................................................89 

14.2.1 CTI Definition .....................................................................................................................................................89 

14.2.2 RCG Definition ...................................................................................................................................................91 

14.2.3 Configuration of WAML Card .............................................................................................................................91 

14.3 Finding Trunk Numbers for Recorders ..............................................................................................................93 



Introduction to the Installation Manual 

1 Introduction to the Installation Manual 

This document describes the installation of the ASC call recording solution for Siemens HiPath 

4000 and CAP utilizing the ASC RIA Server and MARATHON EVOLUTION including a basic 

user interaction with the system. 



List of Abbreviations 

2 List of Abbreviations 

Abbreviation 

ADM 

CAP 

CTI 

HPCR 

RIA Client 

RIA Server 

Explanation 

ASC DataManager 

Common Application Platforms 

(Siemens CTI Middleware) 

Computer Telephony Integration 

Call recording for HiPath 

(Here used for: Call Recording for Siemens HiPath 

4000) 

Module on the MARATHON EVOLUTION that connects 

to a RIA Server and exchanges the information with the 

recording logic. 

Software that monitors and controls a PBX to obtain call 

information and establish silent monitoring paths. 



Preliminary Remarks and Restrictions 

3 Preliminary Remarks and Restrictions 

The MARATHON EVOLUTION is a digital recording system for communication. The software 

delivered with the system is used for recording and monitoring conversations and for configuring 

all components. 

3.1 Copyright 

The ASC software programs and manuals are protected by copyright laws. All rights are 

reserved on this installation manual, even those of reproduction and/or duplication in any 

conceivable way, either by photocopying, printing on any data recording media or in translated 

form. Duplication of this manual - even in extracts - is only permitted with the written approval of 

ASC telecom. 

The technical standard at the time of delivery of device and installation manual is decisive, if no 

other information is given. Technical changes without advanced notice are reserved, earlier 

installation manuals loose validity. 

The general conditions of sale and delivery of ASC telecom AG are valid. 

3.2 Range of Validity 

This installation manual is valid for the device named MARATHON EVOLUTION including the 

software belonging to the system. 

This installation manual is written for the service personnel but not for system users. Any 

question regarding the contents of this manual can be directed to our service staff. 

3.3 Limited Warranty 

This software is licensed as it is. Refund of the purchase price is not possible if the license is not 

used. ASC warrants the physical medium of the software for a period of 90 days from installation 

or purchase, whichever is later. Defective media cannot be repaired but only exchanged. 

Software compatibility is limited to certain computers and operating systems. Using the software 

with non-compatible systems voids any warranty. For questions on compatibility with computers 

and operating systems contact your ASC Sales Department or the ASC Distributor. 

3.4 Disclaimer 

Except as otherwise restricted by law, ASC makes no warranty, representation or promise not 

expressly set forth in this limited warranty. ASC disclaims and excludes any and all implied 

warranties of merchantability, title or fitness for a particular purpose. ASC does not warrant that 

the software or associated documentation will satisfy your requirements or that the software and 

documentation are without defect or error or that the operation of the software will be 

uninterrupted. 

3.5 Limitation of Liability 

Except as otherwise restricted by law, ASC’s aggregate liability arising from or relating to your 

use of the software, associated documentation or any services provided by ASC and/or its 

agents is limited to the total of all payments made by or for you for the software and 

documentation. Neither ASC nor any of its licensors, employees or agents shall in any case be 

liable for any special, incidental, consequential, indirect or punitive damages even if advised of 

the possibility of those damages. Neither ASC nor any of its licensors, employees or agents is 



Preliminary Remarks and Restrictions 

responsible for lost profits or revenue, loss of use of software, loss of data, costs of re-creating 

lost data or the cost of any substitute equipment or program. 

3.6 ASC Software License Agreement 

ASC software programs and documentation (called "software" and "documentation" in the 

following), for which you have purchased a license, are protected by copyright laws, patent law 

and international treaties. Using them is subject to the terms of license. ASC software programs 

are used in various ways and require different license rights. The type of license applying 

depends on the program for which you purchased a license as shown on your Proof of Purchase 

and the definitions and grants of the license below. If the software is an upgrade version from a 

previous version of an ASC software product, you may either use the current or the previous 

version of the software, but never both at the same time. This license supersedes any prior 

license version. 

You may use the software listed on the Proof of Purchase you have received or will receive, 

subject to and only in the manner described in this license agreement. You may make one 

backup copy per licensed version of this software. 

3.7 Licenses 

You may use the software in the quantity and on the operating system listed on the Proof of 

Purchase. For computers or workstations attached to a network, the quantity of software "in use“ 

is the number of users that you have or intend to have in your network. For computers or 

workstations attached to a public messaging system, the quantity of the software "in use“ is 

considered to be the greater of the maximum number of computers on which the software is 

loaded in memory or virtual memory, or maximum number of computers on which the software is 

stored at any one time. 

3.8 Restrictions 

You may not rent, lease, decompile, disassemble, reverse engineer or create derivate works of 

the software. Irrespective of the number of sets of media included with the software, you may use 

the software only as provided in this license and the Proof of Purchase. Certain limitations may 

apply to the purchase of this license. When present, they are printed on the software package 

and are considered as part of the license. Any breach of the terms of license will automatically 

terminate it. All copies of the software and documentation will then have to be destroyed. You 

may permanently transfer the software and documentation to a third party only if all copies, 

including prior and updated versions, are transferred together, and if the third party has agreed to 

the terms of this license and has informed ASC about the transfer. 



Classification of Safety Advice and Warning 

4 Classification of Safety Advice and Warning Instructions 

In this installation manual, three different types of instructions are used, which can be clearly 

identified by the following signal words: 

DANGER 

Warns of states and possible actions which may lead to injuries of the 

operator and severe damage to the device. 

ATTENTION 

Marks states and possible actions which may cause damage to the 

device. 

HINT 

Indicates hints that lead to a better understanding of the device and the 

operating instructions and useful advice for the daily use of the device. 

All safety advice and warning instructions shall help to avert injuries to the operating personnel 

and damages to the device. Please heed all rules and regulations. 



Description of the Software 

5 Description of the Software 

MARATHON EVOLUTION offers very versatile options of connection to legacy TDM (Time 

Division Multiplexing) and VoIP installations. This chapter describes the various options of how to 

connect to a particular configuration. The figure below provides an overview of the recording 

methods. 

Fig. 1 - Overview of Recording Methods 

The numbers in this figure classify each method. Please refer to the appropriate section below. 

1. Trunk side recording 

2. Extension side recording 

3. Silent monitoring 

5.1 Trunk Side Recording 

Trunk side recording is a very common method of recording external conversations. Trunk side 

recording means that the MARATHON EVOLUTION taps the trunk line(s). It gathers audio 

(speech) as well as D channel (call index data) information. There are several D channel 

protocols the MARATHON EVOLUTION is able to "understand". 

If D channel information is not provided or does not deliver enough details (like AgentIDs), RIA 

comes into play. 

5.2 Extension Side Recording 

In the case of extension side recording, the recording interface is connected at the extension line 

of a subscriber (phone). Both external and internal calls can thus be recorded. By evaluating the 

D channel of digital terminals, all interactions of a phone like button presses, LED on/off, display 

contents etc. can be recorded. Usually, the recording interface is connected at the main 




distribution frame (MDF) quite close to the PBX. In certain cases, however, the tapping point may 

be located at the phone (analog handset recording). 

If D channel information is not provided or does not deliver enough details (like AgentIDs), RIA 

comes into play. RIA is also able to control the exact starting and stopping of recordings where 

this would not be possible otherwise (analog phones). 

5.3 Silent Monitoring 

Silent monitoring is the most advanced and sophisticated recording method today. It allows for a 

dynamic selective recording which enables the user to manually control the recording. 

Additionally, the user may obtain information (display message, LED) about the current recording 

status on the phone (if supplied by the PBX). Silent monitoring requires CTI connectivity with the 

switch. A CTI service performs the "monitoring command" driven by definable events, such as 

Agent_ID, CLI, schedule, etc. The switch creates a "duplicate" of the conversation (to be 

recorded) and makes a call to the recorder. The recorder takes the call (active PRI required or 

EVOip for IP solutions) and gathers the "duplicated" audio information. Usually, depending on the 

technology of each vendor, the "duplicated call" may be split into two calls carrying the "talk" and 

the "listen" path separately. This option takes twice as much storage capacity, but it allows for 

stereo recording/replay. 

5.3.1 Dynamic, Selective Recording 

The status of the recording may be shown in the display or with a LED on the function button of 

the telephone. The dynamic recording mode enables the recording of many extensions with just 

a few recording channels by setting up channels only when needed. This "dynamic recording 

channel assignment" is essential for start/stop and network-wide recording and frees space for 

other uses. It also saves on hardware and ownership costs by using fewer channels per agent. 

Large organizations may choose a group of agents to be recorded. Thus, they can monitor a 

different group each day and still save on channels per agent and the number of licenses 

required. 

5.3.1.1 User-Activated Start and Stop 

The recording may be started, stopped or temporarily paused by the agent/user simply by 

pressing a dedicated button on the telephone. In this way, individual sections of a given call may 

be recorded or suppressed to maintain confidentiality. 

5.3.1.2 Threat Call Recording (KEEP) 

Since the user might not recognize a possible threat call at the beginning, all calls need to be 

monitored to ensure the entire interaction is preserved. Afterwards, the recordings are deleted 

automatically, unless the user presses the keep button to save it. 

5.3.1.3 Private Call Elimination (DELETE) 

Depending on the PBX, private calls can be deleted easily by the agent/user at the push of a 

button. Agents can also alternate between the keep and delete modes (toggle) at any time during 

the conversation by pressing the button again. The final selection determines how the call will be 

treated. 




5.3.2 Centralized Recording 

In a network of PBX systems at multiple locations, MARATHON EVOLUTION recording units 

need to be deployed just at one site since call recordings are routed back through the network 

driven by the ASC RIA Server. In other words, the server hardware has to be deployed only on 

one (main) location. All network nodes receive commands from centralized CTI and are 

instructed to send audio to the centralized recorder(s). This feature is PBX-dependent and is not 

supported by all vendors. 

5.3.3 Dynamic Assignment of Agents 

Via the graphical user interface, administrators can easily add/delete users from a list for 

selective recording during runtime. 

5.3.4 Dynamic Assignment of Recording Channels 

The function Dynamic recording channel assignment makes sure that a channel to the recorder 

will only be set up when it is actually needed. This is an essential function which saves channels 

in the case of start/stop recording as well as network-wide recording (as network channels would 

otherwise be occupied unnecessarily). 

5.3.5 Class of Recording (CoR) 

Class of Recording allows the administrator to set up a group of channels with dedicated 

functionality. In this case, a group of channels can be assigned to a group of users that will 

operate in: 

• Start/stop mode 

• Keep/delete mode (i.e. threat call) 

• No compression, high compression 

• Storage term, etc. 

Furthermore, a group of users can be dynamically assigned to a dedicated group of channels: 

Example: 2 users (group A) will share 2 recording channels (1-2), 30 users (group B) will share 8 

channels (3-10) and 400 users (group C) will share 110 channels (11-120). The calls of group A 

will be stored for 5 years, the calls of group B for 3 months and the ones of group C for only 1 

month. 




5.4 Tagged Call Information 

Usually, the following information is provided along with the recordings (PBX-dependant): 

• Own phone number 

• Partner phone number 

• Other phone number 

• Call direction 

• Channel number 

• Agent ID 

• Call start date and time 

• Call end date and time 

• Duration 



System Requirements 

6 System Requirements 

6.1 System Components by ASC 

The system usually consists of the following main ASC devices: 

6.1.1 MARATHON EVOLUTION 

One or several Recorder(s) MARATHON EVOLUTION or XXL with PRI interface active. Two 

PRI-active channels and one recording channel license PRI-active are required per call to be 

recorded. 

Version 

Active PRI card 

Channel licenses 

RIA licenses 

Version 7.0 or higher is required 

For connectivity to the PBX an active PRI card is required 

Licenses for the active PRI card and for the 4wire-configuration are 

required 

RIAactive or RIApassive license for Siemens HiPath 4000 required. 

The number of required RIA seat licenses corresponds to the 

number of recording channels. 

6.1.2 RIA Server Siemens HiPath 4000 

Minimum equipment of 

the PC for the RIA Server 

• Pentium IV with at least 2 GHz CPU 

• At least 512 MB RAM 

• Min. 500 MB free hard disk space 

• Network card – Ethernet 10/100 Mbps 

• VGA graphics card (resolution: min. 800 x 600 pixels) 

• CD-ROM drive 

• Windows XP Professional, Windows 2003 Server 




6.2 System Components by Siemens 

6.2.1 Siemens HiPath 4000 

Version 

Version 2.0 and Version 3.0 are supported 

Patches for Version 2.0 • Patch number PS20t77 is required for error correction in the 

behavior of the ConnectTimeslot Command. 

• Patch number PS20Y72 is required (fixes missing event 

reporting on some transfer scenarios). 

Patches for Version 3.0 • Patch number PS10696 with release number MSC13690 of 

KMOSS archive system of Siemens AG is required. (Error 

correction concerning soft restart in Siemens HiPath 4000 3.0 

with ASC recording solution.) 

DIUN card 

• Patch number PS10899 is required for error correction in the 

behavior of the ConnectTimeslot Command. 

• Patch number PS10D76 with release number MSC15379 is 

required (fixes missing event reporting on some transfer 

scenarios). 

Required for connectivity to the Recorder. 2 Ports per 30 recording 

channels. 

6.2.2 Siemens CAP Server 

Version 

Licenses for all monitored 

devices 

The Siemens CAP Server must have version 3.0 (recommended 

minimum version I915 with the patches described below). 

At least 1 CAP-S License is required per device to be recorded. 

For receiving AgentIDs, a CAP-A License is required instead. 

HINT 

If the route optimization feature is activated in the Siemens HiPath 

4000, the following patches need to be applied to the Siemens CAP 

Server installation. These patches are valid for CAP V3.0 I915 only. 

Installing Patch MSC14783 (svcstart.jar) 

1. Stop the Siemens HiPathCTI service in the Services application. 

2. Rename the former svcstart.jar in \HipathCTI\lib directory to backup this version 

(e.g. svcstart.jar_last). 

3. Copy the provided svcstart.jar file into the same directory \HipathCTI\lib. 

4. Edit the S02service_ctrl.proc in \HipathCTI\config\\systemdb 

directory as follows: 

5. Insert the line restart:1 after the line restartdayly: 

6. Start the Siemens HiPathCTI service in the Services application. 




Installing Patch MSC15126 (tadmin.jar) 

1. Stop the Siemens HiPathCTI service in the Services application. 

2. Rename the folder INSTALLDIR\HiPathCTI\data to backup your configured data. 

3. Rename the former tadmin.jar in INSTALLDIR\HipathCTI\lib directory to backup this version (e.g. 

tadmin.jar_last). 

4. Copy the provided tadmin.jar file into the same directory INSTALLDIR\HipathCTI\lib 

5. Start the Siemens HiPathCTI service in the Services application. 

Installing Patch MSC15353 (cbdriver4000.exe V9.0.15.31) 

1. Stop CA4000 in Diagnostic Agent on the Processes tab. 

2. Rename the former cbdriver4000.exe in INSTALLDIR\HipathCti\bin directory to backup this 

version (e.g. cbdriver4000_last.exe). 

3. Unzip the provided executable AND pdb file into the same directory INSTALLDIR\HipathCti\bin 

4. Start CA4000 in Diagnostic Agent. 

How to check whether the correct version is running: 

• Choose snapshot on the CA4000 in Diagnostic Agent on the Processes tab. 

• Click on status and check the Version value. It has to be 9.0.15.31. 

Installing Patch MSC15460 (SCCHiPath4000.exe V3.0 R5.3.0) 

1. Stop SccHiPath4000 in Diagnostic Agent on the Processes tab. 

2. Rename the former SccHiPath4000.exe in INSTALLDIR\HipathCTI\bin directory to backup this 

version (e.g. SccHiPath4000.exe_last.exe). 

3. Unzip the provided executable AND pdb file into the same directory INSTALLDIR\HipathCTI\bin 

4. Start SccHiPath4000 in Diagnostic Agent. 

How to check whether the correct version is running: 

• Choose snapshot on the SccHiPath4000 in Diagnostic Agent on the Processes tab. 

• Click on status and check the Version value. It has to be V3.0 R5.3.0. 



Installation of the RIA Server 

7 Installation of the RIA Server 

7.1 Installing the RIA Server Base Software 

To carry out the installation of the RIA Server Base Software, launch the file setup.exe located 

under: CD Drive:\CTIntegration Software\setup.exe. 

A dialog box for selecting the setup language will be displayed: 

Fig. 2 - Selecting the setup language 

Select the suitable setup language (English or Deutsch) and confirm your settings with OK. 

The RIA Server Setup will now prepare the InstallShield Wizard. 

The welcome screen will be displayed: 

Fig. 3 - Welcome Screen 




Click Next to continue. The Choose Destination Location dialog box appears: 

Fig. 4 - Selecting the Destination Folder 

Select the desired installation directory and click Next to continue. 

Fig. 5 - Selecting the Database Files Directory 




The RIA Server stores all configuration settings in a MySQL database that is installed during the 

setup process. If you prefer all ASC related files in one directory, enter the path to the installation 

directory you have selected for the RIA Server Base Software above, usually C:\Program 

Files\ASC\RIA Server Base Software\asc_data. Click Next to continue. 

Fig. 6 - Starting the Installation 




Click Install to start the installation process. 

Fig. 7 - Setup Status 

The Setup Status dialog box shows the status of the setup. 

After the setup has been completed, you will be asked whether you now want to carry out the 

RIA Server for Siemens HiPath 4000 Setup. 

Fig. 8 - Setup Query 

Select Yes to initiate the second setup immediately. If you click No, you can later launch this 

setup manually under: CD Drive:\CTIntegration Software\RIA Server\setup.exe. 




7.2 Installing the RIA Server for Siemens HiPath 4000 

Fig. 9 - Welcome Screen 

Click Next to start the installation. 

Fig. 10 - MARATHON EVOLUTION Information 




Enter the IP address of the MARATHON EVOLUTION the RIA Server is supposed to work with. 

Specify the user name and password of a user with write authorization on the ria directory of the 

MARATHON EVOLUTION. An ASC service technician should use the user "service" for this 

purpose. Click Next to continue. 

Fig. 11 - Starting the Installation 

Click Install to start the installation process. The following screen appears: 

Fig. 12 - Starting ASC RIA Server for Siemens HiPath 4000 

All files will be copied and all services will be started. Afterwards, the PIF will be copied to the 

MARATHON EVOLUTION. You will be asked whether you want to restart the RIA daemon. 

Fig. 13 - Restart RIA Daemon 




Select Yes. 

After successfull installation, the following screen appears: 

Fig. 14 - Installation Complete 




Click Finish to exit the InstallShield Wizard. The final setup dialog will be displayed with the 

request to reboot the machine to finalize the installation procedure. 

Fig. 15 - Restarting the Computer 

Select Yes, I want to restart my computer now if you plan to use the RIA Server at once. This will 

lead to a reboot of the PC. 

Select No, I will restart my computer later if you have to install more applications and do not want 

to reboot after each setup. Do not forget to reboot the PC by yourself to make the RIA Server 

Base Software available. 

Click Finish to finish the installation process. 



Configuration of Siemens CAP 

8 Configuration of Siemens CAP 

8.1 CAP Version 

Version 3.0 of Siemens CAP is required for HPCR. The screenshot shows subversion R4.915.0 

that has been used for development and testing, but any 3.0 Version of Siemens CAP will do. 

RIAactive (formerly known as CTIC) for Siemens was certified on the most recent version of 

Siemens CAP in June 2006. 

With changing subversion numbers, some pages in the CAP administration may look slightly 

different compared to the screenshots in this document. 

Fig. 16 - Product Information 

8.2 Service - Switch Connection 

The RIA Server for Siemens HiPath 4000 connects to a switch connection (SCC) in Single 

Domain Native Mode. Configuration of a proxy is not required and not allowed. 

8.2.1 List of Switch Connections 

As a result, the switch connection list must contain an entry for each PBX. The RIA Server for 

Siemens HiPath 4000 connects to the PBX through these switch connections. For each PBX it 

establishes a TCP/IP connection to the target that is given in the CAP Call Control column. 

Fig. 17 - Switch Connection 




8.2.2 Switch Connection - SCC 

Fig. 18 - Switch Connection - SCC 

8.2.3 Switch Connection - CA4000 

Please note that for each switch connection you have to use a different port/link-number/subapp-number. 

Fig. 19 - Switch Connection - CA4000 




8.2.4 Switch Connection - Switch 

Fig. 20 - Switch Connection - Switch 




8.3 Service - Domain Information 

Fig. 21 - Domain Information 

8.4 Users 

For the connection of the RIA Server to the CAP server, a user with CTI rights is required. This 

user does not need an assigned license. 

Fig. 22 - Users 




8.4.1 User for CTI Connectivity 

Fig. 23 - Modify User - CTI 

8.5 Devices 

You have to create a CTI user with a user name and password. Please check the CTI User 

checkbox under Roles. 

This login data has to be entered in the scope of the configuration of the RIA Server. 

8.5.1 List of Devices 

All telephones that may be monitored need to be configured under Device. 




For each device to be monitored, a CAP-S license has to be assigned. 

Fig. 24 - List of Devices 




8.5.2 Device Properties 

Fig. 25 - Device Properties 



Configuration of Siemens HiPath 4000 

9 Configuration of Siemens HiPath 4000 

In short, the following configurations are necessary: 

1. CTI 

2. ACD (defining a RCG group that allows for CTI (CAP)-driven Make Predictive Call to recorder) 

3. Recorder (PRI connection to DIUN) 

4. Routing LCR and access to the recorder 

5. Check patches 

Refer to chapter 14 - Appendix: AMO Commands for detailed information about the configuration 

of the PBX. 

Refer to chapter 14 - Appendix: AMO Commands for a description of the required AMO 

commands to configure the Siemens HiPath 4000. 

Function Buttons for Manual Interaction 

The RIA Server allows you to assign specific functions to individual buttons of the devices, like 

manual start/stop of recordings. This can be defined in the RIA Server configurator. 

However, to allow the RIA Server to recognize pressed buttons, you have to define those buttons 

as name buttons in the Siemens HiPath Administration for each device. 

In this example, we check whether device 301 has the button 06 configured to work properly with 

the RIA Server. 

Check which buttons at 301 have configuration different to the standard: 

ab-tapro:typ=tln,tlnnu=301; 

-> No buttons have been configured. 

Now set button 06 to be associated with a Namenstaste (NA). 

ae-tapro:tlnnu=301,td06=na; 

na stands for Namenstaste and is a fixed string which is always used in this command. 

Check whether it succeeded: 



Configuration of Siemens HiPath 4000 

ab-tapro:typ=tln,tlnnu=301; 

Now we must associate the application 006 to device's 301 button 06. 

This means: For button 06 you have to enter c13006 as target for the button, for button 13 

you have to enter c13013. 

einr-ziel:na,301,6,c13006,gg,,; 

Where gg = type of device (GrundGeraet), c13006 = Ziel-Rufnummer fuer Namenstaste (target 

number for name button) and c13 is a special code which is always used as a prefix before the 

application Id (006) in this command. 

Check configuration with 

ab-ziel:na,301,; 

Output similar to the following can be observed. 



Configuration of MARATHON EVOLUTION 

10 Configuration of MARATHON EVOLUTION 

The following chapter describes the required settings on the recorder. 

10.1 Recording Channels 

The Silent Monitoring Recorder Connectivity to the HiPath 4000 uses two B channels on the 

active PRI for the recording of one call. The required settings can be seen in Fig. 26 - Settings for 

Recording Channel. 

HINT 

Every 16th time slot is not a B but a D channel. You have to skip those 

numbers. 

Example: 

Channel 1 InputSlot1, InputSlot2 = 1,2 


... ... 


... ... 



... ... 


... ... 




Fig. 26 - Settings for Recording Channel 

10.2 Physical Connection of the Recorder to PBX 

The Recorder is connected to the DIUN hardware device of the HiPath. This is a PRI connection 

and the DIUN must be configured as described above. The Communication Recorder must have 

the digital active PRI card inserted. 




10.2.1 The DIUN Card 

The DIU must be of the type DIU-Nx. These cards provide PRI connections with 30 channels 

each. The card provides connection ports at the front panel and at the backplane of the HiPath. 

10.2.2 Pin Assignment of the DIU-N2 

This table shows only the pins used for connecting the recorder. The pin assignment is the same 

for both front ports. 

Signal Name Connector Pin Signal Description Direction 

RTIP 0 / 8 TIP 120 ohm / 75 ohm Input 

RRING 0 / 15 RING 120 ohm / 75 ohm Input 

TTIP 0 / 1 TIP 120 ohm / 75 ohm Output 

TRING 0 / 9 RING 120 ohm / 75 ohm Output 

10.2.3 Connection Cable 

For the connection, a cable must be manufactured on the basis of the following drawing. You 

need to connect the recorder’s active PRI card to the front side connectors of the Siemens DIUN 




card. It is also possible to connect to the rear-side of the DIU card. An adaptor with 15-pin 

connectors is therefore required to fit to the cable mentioned below. 

Fig. 27 - Connection Cable for DIUN2 - ACTIVE PRI 



Configuration and Administration of the RIA Server 

11 Configuration and Administration of the RIA Server 

11.1 RIA Server Configurator 

11.1.1 Checklist - Required Information 

Access to CAP 

CTI login information 

Monitored devices 

DIUN channel numbers 

Trunk numbers for DIUN 

channel numbers 

DIU exists 

DIU configuration 

RCG configuration 

Each PBX is represented by a Switch Connection in the CAP 

Administration. Please refer to chapter 8.2.1 - List of Switch 

Connections. 

IP address and username/password for the connection to the PBX. 

Get a list of all devices to be monitored. Those numbers have been 

entered during the CAP configuration. Please refer to chapter 8.5.1 

- List of Devices. 

Get a list of all DIUN channels numbers (recorder-extensions), 

which are used to build the recording path to the recorder. 

Each DIUN channel has an associated trunk number (LODEN) that 

is used to clean up the DIUN channels on RIA Server startup. 

At the central PBX, at least one DIU hardware group must exist for 

connection of the ASC Communication Recorder. 

The DIUN hardware group must be configured by a Siemens 

service technician. Please refer to chapter 14 - Appendix: AMO 

Commands. 

One RCG per PBX must be configured to allow outgoing calls to the 

recorder channels. The RCG group number needs to be entered 

into the RIA Server configuration. 

11.1.2 Accessing the RIA Server Configurator 

The setup process has created several links in the Windows start menu: 

• RIA Server Configurator 

• RIA Server WEB Portal 

Fig. 28 - Start Menu 

Click RIA Server WEB Portal to bring up a browser window that shows the RIA Server WEB 

Portal. 




There, you can click RIA Server Configurator to open the browser-based RIA Server 

administration. 

HINT 

An easy way to carry out the administration from another PC is to 

simply enter the IP address of the RIA Server PC to bring up the RIA 

Server WEB Portal. 

Fig. 29 - RIA Server WEB Portal 




11.1.3 Login to the RIA Server Configurator 

The start page of the RIA Server Configurator shows two input fields where you have to enter a 

valid user name and password. 

Fig. 30 - Login 

HINT 

The default User is 1 and the default Password is 1. For security 

purposes, please change these default values after your first login. 




11.1.4 Creating and Modifying Users 

Under User Administration, a list of all available users is displayed. Select New User to create a 

new user or select a user from the list to change the settings of this user. 

Fig. 31 - User Administration 

11.1.5 RIA Connection 

On the RIA Connection page, you can modify the RIA Server port. The RIA Server will listen on 

this port for incoming connections from a RIA Client. The RIA Client that runs on the recorder 

must be configured to connect to the IP address of the RIA Server and the port configured here 

under RIA Connection. 




HINT 

Please observe that you have to enter the same ServerPort in the RIA 

Client configuration, as displayed in Fig. 45 - RIAactive -> Protocol 

Interface and Fig. 47 - RIApassive -> Protocol Interface. 

Fig. 32 - RIA Connection 

11.1.6 PBX 

The default value 9000 should only be changed if you plan to use more than one RIA Server 

simultaneously or if this port is already occupied by another application. 

One PBX entry in the configuration represents one link to a PBX. Any changes in this section 

require a restart of the RIA Server. 

To create a new PBX in the RIA Server Configurator, select the PBX type in the menu tree on the 

left. 

Fig. 33 - Creating a New PBX 

Enter a name for the new PBX into the input field and click . 




The SCC details from chapter 8.2.2 - Switch Connection - SCC have the following relation to the 

fields in the PBX configuration: 

PBX Name 

Hostname 

Port 

Login 

Password 

Country code 

Area code 

Net code 

PBX ID 

RCG 

A "human readable" name for the PBX. This name will appear in 

other parts of the RIA Server Configurator and will be displayed in 

the Status View of the Alarm Management. 

SCC ip address. 

SCC port. 

User ID: From CAP user details, see Fig. 23 - Modify User - CTI 

Password: From CAP user details, see Fig. 23 - Modify User - CTI. 

Not interpreted, for display only. 



Internal identification number of the PBX. This number has to be 

entered as PhysicalPbxID in the RIA Client configuration, as 

displayed in Fig. 48 - RIApassive -> Devices. 

The number of the RCG group that has been configured in the 

HiPath to make the outgoing calls to the recording channels. 

Fig. 34 - PBX Configuraton 

Finally, click Save to create a new PBX entry with the given configuration. Consequently, it will be 

displayed in the menu tree on the left with the name you have entered into the field PBX Name. 




11.1.7 Extensions 

The Extensions page shows a list of all configured stations and provides the option to create new 

extensions for monitoring. 

Fig. 35 - Extension Configuration 

However, this does not mean that recording for a particular station is active. Therefore, a monitor 

point has to be activated as displayed in the above figure under Monitorpoint Enabled = yes. 




PBX ID 

Extension type 

Language 

Class of recording 

Extension number 

Persi name 

Note 

The PBX to which the device belongs. 

Extension: Normal endset 

Trunk: A connection to a PSTN 

Agent: An agent login number 

You can select the language for display messages. By default, only 

en_GB is predefined. Up to 7 different languages are possible which 

can be defined individually in the Text section of the RIA Server 

Configurator. 

This is an advanced feature. By default, you can set it for all 

extensions to the value Class1 provided that all extensions are to be 

recorded in the same way. 

This setting allows you to group a set of extensions according to 

their behaviour (automatic or manual recording start) and used 

channels when recording actively. 

See also chapter 5.3.5 - Class of Recording (CoR). 

The phone number of the extension supposed to be recorded. The 

number must be in short format, without area or net code. 

A note field for the person who uses the telephone, can be blank. 

A note field, can be blank. 

Fig. 36 - Monitorpoint Enabled 

You have to set Monitorpoint Enabled to yes to enable the monitor for recording. 

If set to yes, you can optionally define a time span in which the monitor will be active. Enter a 

date and time in the From and to fields and activate the Schedule active monitor feature. 

Since in a large network many stations may be defined, it is possible to use a range of numbers 

for the setup, which makes things a lot easier and more efficient. Enter a single extension or a 

range into the fields to the right and click Copy to extension-number(s) to use this feature. 

11.1.8 SiMo Information 

The SiMo information represents the collection of numbers assigned to the individual B channels 

of the DIUN card. 




Example: A DIUN card has 30 B channels with a number range from 9970 to 9999. In this case, 

you have to enter those 30 numbers into this list. 

HINT 

Remember that 30 B channels will result in 15 recording channels (15 

calls can be recorded simultaneously). The assignment of recorder 

extensions (B channels) to recording channels will be performed in one 

of the subsequent steps. 

Fig. 37 - SiMo Information 

Recording channel ID 

Class of channel 

Route number 1 

Route number 2 

Trunk number 1 

Trunk number 2 

Note 

This parameter must be identical with the one entered as 

PhysicalDeviceID in the RIA Client configuration. 

Can be used to group SiMo Information to be used in a class of 

recording. 

The number to be dialled in order to reach a defined B channel on 

the DIUN card. 

The number to be dialled in order to reach a defined B channel on 

the DIUN card. 

Each B channel has a trunk number (LODEN in HiPath terms) 

assigned that must be entered here. 

Each B channel has a trunk number (LODEN in HiPath terms) 

assigned that must be entered here. 

Can be used for notes. 




HINT 

Please make sure that the value you enter as Recording channel ID is 

identical with the parameter PhysicalDeviceID in the RIA Client 

configuration, as displayed in Fig. 46 - RIAactive -> Devices. 

How to find out Trunk Numbers of the Siemens HiPath 4000 

The complete output of the AMO commands used here is listed in chapter 14 - Appendix: AMO 

Commands. 

Step 1: 

Determine the PEN number of the recorder trunk used. This is 1-1-49-1 in our case. 

Step 2: 

Enter the following command: 

EXEC-DISPS:BP; 

The following output is displayed: 

H500: AMO DISPS STARTED 

AMO DISPS VARIANT/VERSION N1/001 OF 2004-04-15 

DISPLAYER VARIANT/VERSION N1/014 OF 2004-07-21 

DISPLAYER-INPUT IN BPB 

PLEASE: 

*lst,sw,loden,cir,1,1,49,1; 

LTG LTU PBC/SLOT CCT L I N E PHYS_LINE SU DI/TSI SI LODEN 

1T 1T 5T 49T 1T 1456T 5B0H 1456T 5B0H 0H 1H 0H 1C5H -> TRUNK NUMBER 453 

1T 1T 5T 49T 1T 1456T 5B0H 1456T 5B0H 1H 1H 0H 1C4H 

1T 1T 5T 49T 1T 1559T 617H 1456T 5B0H 0H 2H 0H 1C7H -> TRUNK NUMBER 455 

1T 1T 5T 49T 1T 1559T 617H 1456T 5B0H 1H 2H 0H 1C6H 


….. 

….. 

1T 1T 5T 49T 1T 1587T 633H 1456T 5B0H 1H 1CH 0H 1FAH 

1T 1T 5T 49T 1T 1588T 634H 1456T 5B0H 0H 1DH 0H 1FDH 

1T 1T 5T 49T 1T 1588T 634H 1456T 5B0H 1H 1DH 0H 1FCH 

1T 1T 5T 49T 1T 1589T 635H 1456T 5B0H 0H 1EH 0H 1FFH 

1T 1T 5T 49T 1T 1589T 635H 1456T 5B0H 1H 1EH 0H 1FEH 


PLEASE: 

* 

-> To quit the DISPS mode, enter the command end. 




The decimal equivalent of the LODEN is the trunk number required for recording. 

HINT 

Please check every second LODEN value and transfer these into the 

ASC RIA Server Configurator for all the route numbers. 

11.1.9 Buttons 

The Buttons page allows the assignment of function buttons to devices that allow the manual 

starting/stopping of recordings and marking ongoing recordings to keep or delete them. 

HINT 

You also have to configure the buttons on the telephone as name 

buttons to work with the RIA Server. Please refer to chapter Function 

Buttons for Manual Interaction for details. 

Fig. 38 - Configuration of Buttons 

Extension 

Button type 

Button index 

Select the extension to add a new button. 

Start/Stop: For manual start of recording. 

Keep/Delete: Mark ongoing recording to keep or delete after call is 

over. 

Defines which button on the device is used for the selected function. 

To find out the button number, start counting on the uppermost left 

with 1, going down. Continue counting on the button column to the 

right, going down. 




LED feedback 

Display feedback 

yes: Indicate recording status through the LED next to the button 

selected under ButtonIndex. 

no: LED stays always off. 

yes: Message in display that tells which function has been activated 

through the button press. 

no: No messages in display if button is pressed. 

The button Copy to extension(s) copies the configuration of one button to all the devices that 

have been selected in the list field above. You can select multiple entries by holding CTRL while 

clicking the entries. 

If you want to clean up all the assigned buttons for a range of devices, you can enter a range of 

devices into the input fields to the right and click Remove from extension(s) to delete all buttons 

from those devices. 

11.1.10 Class of Recording 

A class of recording bundles a set of extensions sharing the same settings like the recording 

mode (trunk-side, extension-side,...) or recording status feedback through display or LED. 

If all devices share the same settings, you do not have to create another class of recording, but 

can use the one that is there by default. 

Fig. 39 - Class of Recording Configuration 




Recording type 

RIA Server role 

Recording mode 

LED feedback 

Display feedback 

Description 

Available values: 

• Extension-Side 

• Trunk-Side 

• Silent Monitoring 


• Active 

• Passive 

Select Active if you plan to do trunk-side recording with monitor 

points only on the extensions. In this case, the RIA Server decides 

about the recording start and stop. 

For silent monitoring, extension-side recording and trunk-side 

recording with monitorpoints on the trunks, Passive is the right 

choice. 


• Automatic: Recording starts at the beginning of a call 

• Manual: Recording must be started manually during a 

call through a button press. 


• ON 

• OFF 

If a button is assigned to an extension with an LED, this switch turns 

the recording status indication through that LED on/off. 


• ON 

• OFF 

If turned on, a display message will be shown on the display of the 

phone at the start/stop of a recording. These messages can be 

configured as described in chapter 11.1.11 - Texts for Display. 

Here, you can enter a significant description for your settings. 




11.1.11 Texts for Display 

Chapter Extensions describes the option of selecting a language for messages on the phone's 

display from a total of 7 languages. You can individually define these messages in the Text 

section. 

HINT 

If you have activated the display of the recording status in the phone’s 

display, but want only a message when a recording starts but not when 

it ends, then all you have to do is to blank the NodeValue of the STOP 

NodeName. 

Fig. 40 - Text Configuration 

11.1.12 Overview – PBX 

The overview shows the current status of the RIA Server. Red-crossed PBXs are not connected. 

Lines with a green check sign show PBXs that are connected and ready to record. 

To refresh the page, please click the upper right button or click the PBX link once again. 

Fig. 41 - Overview: PBX 




11.1.13 Overview – Monitor Points 

This page shows the status of the set monitor points. Green check signs mean status OK. Ready 

to record. Red crossed lines show stations that are not ready to be recorded due to the fact that 

the extension either does not exist or is offline. In this case, you might also want to check the 

related PBX connection status. 

Fig. 42 - Overview: Monitor Points 

11.1.14 Overview – Check Result 

In contrast to the Monitor Points page which only shows devices activated for recording (to be 

monitored), this list checks all devices defined in the sections PBX and Extensions. 

For load reasons, this is done in a background process with low priority that checks every 3-4 

seconds one device from the Extension list. 

If you have 100 devices in total defined in the section Extensions, it will take approximately 5 - 6 

minutes until all devices have been checked. 

Fig. 43 - Overview: Check Result 



RIA Client Configuration 

12 RIA Client Configuration 

In the ASC DataManager, select Configuration -> RIA. 

General Buttons in the ASC DataManager 

On the GUI of the ADM, you will frequently find the buttons specified below. 

Check all 

Reset 

Save 

Click this button to check whether there are any conflicting 

configurations. 

Resets your settings to the default values. 

Saves your configuration. 

Changes you have not yet saved are indicated by a checkmark. 

12.1 Common Configuration 

Fig. 44 - Common RIAactive Configuration 

Licensed 

NumInstances 

Enabled 

Indicates whether you have a license for RIAactive. 

Enter the number of instances and click on Save. Afterwards, the 

corresponding number of instances will be displayed in the 

navigation bar and under Instances. 

Enables the RIAactive instance. 




Name 

LogLevel 

Enter a characteristic name for the RIAactive instance. 

Specify the depth of the log files. Usually, the level Medium is 

sufficient. A higher log level can be selected for troubleshooting 

purposes. 

12.2 RIAactive Configuration 

In the navigation bar, select the RIAactive instance you want to configure. Begin with the Protocol 

Interface configuration. 

Fig. 45 - RIAactive -> Protocol Interface 

Statemachine 

Select the grammar to be used for this RIAactive connection. 

Available grammars are RIAExtnRecExtnMonitor and 

RIATrunkRecExtnMonitor. 

EventBuffer Specifies the size of the event buffer. The default value is 1000. 

PIF-Type 

PIF-Config 

Connection Type 

Server-IP 

Select the appropriate PIF, i.e. the vendor-specific protocol to be 

used for the communication with the PBX. For example, if you have 

a Siemens PBX, select PIFSiemensCAP. 

Appears as soon as you have selected the PIF type and serves to 

configure the PIF. 

For CTI connections, always select the connection type TCP. 

Enter the IP address of the server on which the RIA application is 

installed. 




Server-Port 

Inactivity-Timeout 

LogBinaryData 

Enter the port number for the RIA connection. This number must be 

identical with the one entered as parameter ServerPort in the RIA 

Server configuration. The default value is 9000. 

Specify the time interval (in seconds) of inactivity after which the 

connections are to be terminated. By default, this value is set to 0, 

which means that there is no inactivity timeout. 

Here, you can specify whether you want to save the incoming binary 

data. This is usually not required, because the incoming data is 

identical with the outgoing data. 

HINT 

To make sure that the value you enter as Server-Port is identical with 

the one in the RIA Server configuration, please check this value as 

displayed in Fig. 32 - RIA Connection. 

After the configuration of the protocol interface, select the Devices tab to map the names of the 

channels on the recorder to the names of the channels on the RIA Client. 

Fig. 46 - RIAactive -> Devices 

PhonelineID 

PhysicalPbxID 

PhysicalDeviceID 

Export to CSV 

Import from CSV 

Name of the channel on the recorder. 

To enable the individual channel mapping, enter active. 

Name of the channel on the RIA Client. This name must be identical 

with the one entered on the RIA Server as Recording channel ID. 

Exports the table to a CSV file. A dialog box appears, where you 

can specify the export directory. 

Allows you to import CSV file which contains a corresponding 

configuration file. A dialog box appears, where you can browse to 

the directory of the import file. 




HINT 

To make sure that the value you enter as PhysicalDeviceID is identical 

with the parameter Recording channel ID in the RIA Server 

configuration, please check this value as displayed in Fig. 37 - SiMo 

Information. 

12.3 RIApassive Configuration 

In the navigation bar, select the RIApassive instance you want to configure. Begin with the 

Protocol Interface configuration. 

Fig. 47 - RIApassive -> Protocol Interface 

Statemachine 

Select the grammar to be used for this RIAactive connection. If you 

use the extension connection type, select RIAExtnRecExtnMonitor 

and if you use the trunk connection type, select 

RIATrunkRecExtnMonitor. 

EventBuffer Specifies the size of the event buffer. The default value is 1000. 

PIF-Type Select the vendor-specific protocol to be used for the 

communication with the PBX. 

PIF-Config 

Connection Type 

This section appears as soon as you have selected the PIF type 

and serves to configure the PIF. 

For CTI connections, always select the connection type TCP. 




Server-IP 

Server-Port 

Inactivity-Timeout 

LogBinaryData 

Enter the IP address of the server on which the RIA application is 

installed. 

Enter the port number for the RIA connection. This number must be 

identical with the one entered on the RIA Server. The default value 

is 9000. 

Specify the time period (in seconds) of inactivity after which the 

connections are to be terminated. By default, this value is set to 0, 

which means that there is no inactivity timeout. 

Here, you can specify whether you want to save the incoming binary 

data. This is usually not required, because the incoming data is 

identical with the outgoing data. 

HINT 

To make sure that the value you enter as Server-Port is identical with 

the one in the RIA Server configuration, please check this value as 

displayed in Fig. 32 - RIA Connection. 

After the configuration of the protocol interface, select the Devices tab to map the telephones of 

the individual PBXs to the individual channels. 

Fig. 48 - RIApassive -> Devices 

PhonelineID 

PhysicalPbxID 

PhysicalDeviceID 

Export to CSV 

Import from CSV 

ID of the channel. 

Enter the ID of the PBX to which the telephone belongs. This 

number must be identical with the one specified as parameter PBX 

ID in the RIA Server configuration. 

Extension number of the telephone to be mapped. This number 

must be identical with the one specified as parameter Extension 

number in the RIA Server configuration. 

Exports the table to a CSV file. A dialog box appears, where you 

can specify the directory for the export file. 

Allows you to import CSV file which contains a corresponding 

configuration file. A dialog box appears, where you can browse to 

the directory of the import file. 




HINT 

To make sure that the PhysicalPbxID is identical with the parameter 

PBX ID in the RIA Server configuration and that the PhysicalDeviceID is 

identical with the parameter Extension number in the RIA Server 

configuration, please check these values as displayed in Fig. 35 - 

Extension Configuration. 



Test Hints 

13 Test Hints 

This chapter describes how the configuration of the HiPath 4000 and the CAP-server can be 

checked using the csta3host application from Siemens. If any test fails, a technician has to check 

the configuration of the CAP or the HiPath 4000. 

13.1 Connection to CAP and HiPath 4000 

This test will confirm that the CAP link to the HiPath has been configured correctly and the 

connection to the CAP-server is working. 

Step 1: 

Link -> Setup -> insert ip and port of the CAP Server that is used to connect to the HiPath 

(see Fig. 49 - CSTA3 Host Setup). 

Fig. 49 - CSTA3 Host Setup 

Step 2: 

Link -> Connect 

Step 3: 

Forms -> ACSE Request -> Associate -> Version :versionFive 

On failure, check whether the connectivity adapter is running and is receiving events. 

13.2 Setting Monitor Points 

Now, test whether monitor points can be set on the configured devices. 

Step1: 

Forms -> CSTA Request -> Monitoring Services -> StartMonitor -> enter an extension number in 

the dialable-field (the extension must exist in the CAP configuration see section 8.5 - Devices, e. 

g. ext: 100). All other options remain unchanged. 

Step 2: 

Go off-hook, on-hook on the monitored device and check whether events are displayed within 

the CSTA-tool. 

On failure, check whether the device exists within the CAP-configuration and licenses are 

available. 



Test Hints 

13.3 Calling the Recorder (Getting Trunk Numbers) 

Use the recently monitored device to manually call the recorder extensions. Check whether the 

different channels go into light blue/red state (depending on the configuration of the channel). In 

the CSTA events, the used trunk number is displayed (as a decimal number; so you can also use 

this way to get the trunk numbers instead of transforming the LODEN). 

Keep in mind that 2 subsequent extension numbers activate 1 recording channel! (e. g. calling 

778000 and 778010 both activate channel 1) 

On failure, check whether the recorder-extensions are configured within the HiPath. 

13.4 Performing Calls Using the RCG Group 

The last test is to perform a call from the rcg group to a phone or the recorder. 

Step 1: 

Forms -> CSTA Request -> Call Control Services -> MakePredictiveCall 

Switch the combo-box CallingDevice to Device#. Now right-click into the Device# text field. A 

new window Device#-Mask-Helper opens. Select the radio button Route Control Group (RCG) 

and enter the rcg-group number (e. g. 85). 

Enter a extension number into the Called Directory Number - Dialable# text field. 

On failure check whether the rcg has been configured correctly. Make sure you are using the rcg 

group number not the rcg number to perform calls! 

Fig. 50 - Device#-Mask-Helper 



Appendix: AMO Commands 

14 Appendix: AMO Commands 

The following AMO commands were extracted from a running installation that runs in a networkwide 

configuration. The recorder(s) is/are connected to the HOME PBX. All recordings will be 

sent through the HiPath network from the nodes to this HOME PBX. The configuration of the 

network nodes can be found in section 14.2 - Remote PBX Settings. Please make sure the call 

routing is appropriate. 

In this configuration the CAP connects through WAML. That is why you can find the WAML 

configuration as well in the document. 

In short, the following configurations are necessary: 

1. CTI 

2. ACD (defining an RCG group that allows CTI (CAP)-driven Make Predictive Call to recorder) 

3. Recorder (PRI connection to DIUN) 

4. Routing LCR and access to the recorder 

5. Check patches 

14.1 HOME PBX Settings 

14.1.1 CTI Definition 

/*** CTI Application Process Definition ***/ 

ADD-CPTP:TYPE=DPCON,NO=55,DPPROC="PROCID5",IPNO=""; 

ADD- 

CPTP:TYPE=APPL,NO=55,EMSAPPL="ACM55",DPPROC="PROCID5",DPAPPL="APPL55",MSGBASED 

=YES,LOCPORT=102,FARPORT=102,LOCTSAP="ACM55",FARTSAP="APPL55"; 

/*** Definition of CTI Events Filter ***/ 

ADD-XAPPL:APPLNO=55,APPLDP="APPL55 

",TSKA=Y; 

",NAME="APPLICATION_55 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=ACCOUNT&AGASSIGN&AGENT&ABANDO 

N&QUEUED; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=REDIRECT&GRPSEL&LOGON&REC&RCG 

DISC; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=RCGSEL&ATB&SELECT&QUEUTS&DELI 

V; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=RTD&ASSOC&DISCON&RET&REMOV; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=ROUTD&GRP&CONNECT&GENDGTS&PUL 

LBACK; 




CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=GRPABAND&GRPDELIV&GRPDIV&GRPF 

WD&GRPQUED; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DIGDIALD&RCGMPC&TTONGEN&MWI&C 

ALLBACK; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DATARES&DATASUSP&FASTDATA&SEN 

DDATA&STARTDAT; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=STOPDATA&CALLFAIL&MOBILUSR&CA 

LLINFO&APPINFO; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=APPOOS&APPBIS&APPCLEAR&CFWDED 

; 

CHANGE-XAPPL:CTYPE=MONCB,APPLNO=55,SUBAPPL=D25,GLOBAL=RCG; 

/*** Definition of ACL Manager Link for CTI ***/ 

ADD- 

ACMSM:APPLNO=55,TYPE=ACLAPPL,ACLAPPL="APPL55",PBXAPPL="ACM55",PROCID="PROCID5" 

,ACCESS=CB,PASSWD="CSTAGW",PACKAGE=Y,MAXSBYTE=1020,MAXRBYTE=1020; 

14.1.2 ACD Settings 

ADD-WABE:CD=8815,DAR=RCG,CHECK=N; 

/***** Enabling ACD in the PBX *****/ 

CHANGE- 

ZAND:TYPE=ACD,ACDALLOW=YES,MONTONE=YES,SUPAGTNU=NO,COCONN=NO,TIECONN=NO; 

/**** Call Forwarding of RCG *****/ 

/*** The number 85 in the following line is the one you have to enter as RCG-Name under the 

section 11.1.6 - PBX. 

CHANGE-ACDSD:TYPE=CAFRCG,RCG=85,CAFDN=8815; 

/***** Definition of ACD Route *****/ 

ADD-ACDRT:ART=201,MAXSTEP=5; 

CHANGE-ACDRT:ART=201,TYPE=ARTSTEP,STEP=1,ACT=SKIP; 








/***** Definition of ACD Routing (Shiftsets) *****/ 

ADD-ACDRS:TYPE=DS,DSNUM=1,SHIFT=23-59,ART=201,EOS=YES,ARTDEF=201; 

ADD-ACDRS:TYPE=RS,RCG=85,SUN=1,MON=1,TUE=1,WED=1,THU=1,FRI=1,SAT=1; 

/***** Definition of STN for DNIT *****/ 

ADD-WABE:CD=870,DAR=STN; 

/***** Definition for DNIT *****/ 

ADD-DNIT:TBL=DNI,INTRTDN=870,ROUTING=DRTD,SARULE=0,DISPLAY=" 

",ACD=YES,RCG=85,PRI=64,OVRPRI=0,AUDSRCID=0,THRSHLD=*,REVCHA=FORB; 

14.1.3 Recorder Settings 

/*** Definition of COT Parameters for Recorder Trunks ***/ 

ADD-COT:COTNO=80,PAR=USD&CEBC&TIE&BLOC&LWNC&NLCR&DFNN&NLRD&NTON; 

CHANGE-COT:COTNO=80,COTTYPE=COTADD,DEV=S2CONN,INFO="EDSS1"; 

/*** Definition of COP Parameters for Recorder Trunks ***/ 

ADD-COP:COPNO=80,TRK=TA; 

/*** Definition of Recorder Trunk Groups ***/ 

ADD-BUEND:TGRP=310,NAME="ASC 

REC 

",NO=1,TRACENO=0,ACDTHRH=*,PRIONO=2,TDDRFLAG=ON,GDTRRULE=0,ACDPMGRP=0,CHARCON= 

NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 





REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 





REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 





REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 





REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 


REC 


NEUTRAL; 

/*** Definition of Loadware for Recorder Trunks ***/ 

CHANGE- 

LWPAR:TYPE=DIUS2,BLNO=8,LNTYPE=COPPER,VERSION=S2,QUAL=ON,MASTER=Y,DCHAN1=16,DC 

HAN2=0,PATTERN=D5,QUAL1=10,QUAL2=10,SMD=Y,PERMACT=Y,FCBAB=DF,CDG=N,FIXEDTEI=0, 

CNTRNR=255,TEIVERIF=N,CRC4REP=N,DEV=INDEP; 




HINT 

The number of possible BUENDEL is limited to 512. This means that if 

you assign only 1 B-channel per BUENDEL that the number of 

simultaneos recordings would be approximately 240 (480 usable 

BUENDEL divided by 2). To support up to 480 simultaneous recordings 

per PBX, it is possible to assign 2 B channels per BUENDEL, as 

displayed in the screenshot below: 

/*** Definition of Recorder Trunk Circuits ***/ 

ADD-TDCSU:OPT=NEW,PEN=1-01-049- 

1,COTNO=80,COPNO=80,DPLN=0,ITR=1,COS=75,LCOSV=32,LCOSD=32,CCT="ISDN 

S2 

QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,AT 

NTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,DGTPR=00,ISDNIP=0,TRACOUNT=31,SATCOU 

NT=MANY,NNO=100,ALARMNO=0,FIDX=1,CARRIER=1,ZONE=EMPTY,COTX=80,FWDX=1,CHIMAP=N, 

UUSCCX=16,UUSCCY=8,FNIDX=1,NWMUXTIM=10,CLASSMRK=EC&G711&G729OPT,TGRP=310,SRCHM 

ODE=ASC,INS=N,DEV=S2CONN,BCHAN=1,BCNEG=N,BCGR=1,LWPAR=8,LWPP=0,LWLT=0,LWPS=0,L 

WR1=0,LWR2=0; 



S2 





ODE=ASC,INS=N,DEV=S2CONN,BCHAN=2,BCNEG=N,BCGR=2; 






S2 








S2 








S2 








S2 








S2 








S2 








S2 








S2 











S2 








S2 








S2 








S2 








S2 








S2 








S2 











S2 








S2 








S2 








S2 








S2 








S2 








S2 








S2 











S2 








S2 








S2 








S2 








S2 





ODE=ASC,INS=Y,DEV=S2CONN,BCHAN=30,BCNEG=N,BCGR=30; 



S2 





ODE=ASC,INS=N,DEV=S2CONN,BCHAN=1,BCNEG=N,BCGR=1,LWPAR=8,LWPP=0,LWLT=0,LWPS=0,L 

WR1=0,LWR2=0; 



S2 











S2 








S2 








S2 








S2 








S2 








S2 








S2 








S2 











S2 








S2 








S2 








S2 








S2 








S2 








S2 











S2 








S2 








S2 








S2 








S2 








S2 








S2 








S2 









/*** Definition of Recorder Routes ***/ 



S2 








S2 








S2 








S2 








S2 





ODE=ASC,INS=Y,DEV=S2CONN,BCHAN=30,BCNEG=N,BCGR=30; 

ADD-RICHT:MODE=LRTENEW,LRTE=311,LSVC=ALL,NAME="ASC 

REC 

",TGRP=311,DNNO=1-1- 

110,ROUTOPT=YES,DTMFCNV=FIX,DTMFPULS=PP300,ROUTATT=NO,EMCYRTT=NO,PDNNO=0,CHARC 

ON=NEUTRAL,CONFTONE=NO,RERINGRP=NO,NOPRCFWD=NO,NITO=NO; 


REC 

",TGRP=312,DNNO=1-1- 




REC 

",TGRP=313,DNNO=1-1- 







REC 

",TGRP=317,DNNO=1-1- 




REC 

",TGRP=315,DNNO=1-1- 




REC 

",TGRP=310,DNNO=1-1- 




REC 

",TGRP=316,DNNO=1-1- 




REC 

",TGRP=314,DNNO=1-1- 




REC 

",TGRP=318,DNNO=1-1- 




REC 

",TGRP=319,DNNO=1-1- 




REC 

",TGRP=320,DNNO=1-1- 




REC 

",TGRP=321,DNNO=1-1- 




REC 

",TGRP=322,DNNO=1-1- 




REC 

",TGRP=323,DNNO=1-1- 




REC 

",TGRP=324,DNNO=1-1- 







REC 

",TGRP=325,DNNO=1-1- 




REC 

",TGRP=326,DNNO=1-1- 




REC 

",TGRP=327,DNNO=1-1- 




REC 

",TGRP=328,DNNO=1-1- 




REC 

",TGRP=329,DNNO=1-1- 




REC 

",TGRP=330,DNNO=1-1- 




REC 

",TGRP=331,DNNO=1-1- 




REC 

",TGRP=332,DNNO=1-1- 




REC 

",TGRP=333,DNNO=1-1- 




REC 

",TGRP=334,DNNO=1-1- 




REC 

",TGRP=335,DNNO=1-1- 




REC 

",TGRP=336,DNNO=1-1- 







REC 

",TGRP=337,DNNO=1-1- 




REC 

",TGRP=338,DNNO=1-1- 




REC 

",TGRP=339,DNNO=1-1- 




REC 

",TGRP=340,DNNO=1-1- 




REC 

",TGRP=341,DNNO=1-1- 




REC 

",TGRP=342,DNNO=1-1- 




REC 

",TGRP=343,DNNO=1-1- 




REC 

",TGRP=344,DNNO=1-1- 




REC 

",TGRP=345,DNNO=1-1- 




REC 

",TGRP=346,DNNO=1-1- 




REC 

",TGRP=347,DNNO=1-1- 




REC 

",TGRP=348,DNNO=1-1- 







REC 

",TGRP=349,DNNO=1-1- 




REC 

",TGRP=350,DNNO=1-1- 




REC 

",TGRP=351,DNNO=1-1- 




REC 

",TGRP=352,DNNO=1-1- 




REC 

",TGRP=353,DNNO=1-1- 




REC 

",TGRP=354,DNNO=1-1- 




REC 

",TGRP=355,DNNO=1-1- 




REC 

",TGRP=356,DNNO=1-1- 




REC 

",TGRP=357,DNNO=1-1- 




REC 

",TGRP=358,DNNO=1-1- 




REC 

",TGRP=359,DNNO=1-1- 




REC 

",TGRP=360,DNNO=1-1- 







REC 

",TGRP=361,DNNO=1-1- 




REC 

",TGRP=362,DNNO=1-1- 




REC 

",TGRP=363,DNNO=1-1- 




REC 

",TGRP=364,DNNO=1-1- 




REC 

",TGRP=365,DNNO=1-1- 




REC 

",TGRP=366,DNNO=1-1- 




REC 

",TGRP=367,DNNO=1-1- 




REC 

",TGRP=368,DNNO=1-1- 




REC 

",TGRP=369,DNNO=1-1- 



/*** Definition of Recorder Channel Outdial Rule ***/ 

ADD-LODR:75,,,,NPI,UNKNOWN,UNKNOWN; 

ADD-LODR:75,,,,END; 

/*** Definition of LCR Routes for Recorder Trunks ***/ 

ADD- 

LDAT:LROUTE=310,LSVC=ALL,LVAL=1,TGRP=310,ODR=75,LAUTH=1,CARRIER=1,ZONE=EMPTY,L 

ATTR=NONE,VCCYC=4; 

ADD- 






ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 






ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 






ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 






ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



ADD- 



/*** Definition of Recorder Access Codes ***/ 

ADD-WABE:CD=330700,DAR=TIE,CHECK=N; 


































































/*** Definition of Recorder Dial Plans ***/ 

ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP="330700",LROUTE=310,LAUTH=1,PINDP=N; 





































































14.1.3.1 Configuration of WAML Card (Home PBX) 

/*** Card Definition of WAML ***/ 

ADD-BCSU:MTYPE=PER,LTG=1,LTU=1,SLOT=91,PARTNO="Q2205-X 

",FCTID=1,LWVAR="0",HWYBDL=A; 

/*** Routing Definition for WAML ***/ 

/*** Global Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=1,SLOT=91,TABTYPE=GLOBAL,STNO=338950,LANHW=WESTERN,ACTNETIF=ALL 

,FIREWALL=ISDN,ADPISDN=PROXY,ADPELAN=PROXY; 

/*** Atlantic LAN Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=1,SLOT=91,TABTYPE=NETWORK,NETNAME=ATLLAN,IPADDR="192.9.55.4",IP 

NMASK="255.255.255.0"; 

/*** Customer LAN Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=1,SLOT=91,TABTYPE=NETWORK,NETNAME=EXTLAN1,IPADDR="192.168.205.1 

55",IPNMASK="255.255.255.0"; 

/*** WAN Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=1,SLOT=91,TABTYPE=NETWORK,NETNAME=ISDN1,IPADDR="192.3.3.55",IPN 

MASK="255.255.255.0"; 

/*** IP Route to ADS of Remote PBX ***/ 

ADD- 

LANC:LTG=1,LTU=1,SLOT=91,TABTYPE=IPROUTE,IPADDR="192.9.51.3",DESTTYPE=HOST,NEX 

TROUT="192.3.3.51"; 

/** ISDN Terminal Settings for Connection to Remote PBX ***/ 

ADD- 

LANC:LTG=1,LTU=1,SLOT=91,TABTYPE=ISDNTERM,IPADDR="192.3.3.51",STNO1=339450,INO 

UTCH1=IN&OUT,STNO2=339450,INOUTCH2=IN,BITRATE="64",CALLBACK=N; 

/*** COT for WAML ***/ 

ADD-COT:COTNO=11,PAR=RCL&ANS&CEBC&CBBN&CBFN&FWDN&FNAN&COTN&IEVT&BSHT&NTON; 

/*** COP for WAML ***/ 

ADD- 

COP:COPNO=11,PAR=DTMF&SDL&EOD&ANS&SACK&ACKF&ACKB&RBLK&RLSA&NTON&WOT2&TIM1&TIM3 

&IDP2&DTM1&AST1,TRK=TA,TOLL=TA; 

/*** Class of Service for WAML ***/ 

ADD-COSSU:NEWCOS=11; 




CHANGE-COSSU:TYPE=COS,COS=11,AVCE=TA&TNOTCR&DATA; 

CHANGE-COSSU:TYPE=COS,COS=11,AFAX=TA&TNOTCR&BASIC; 

CHANGE-COSSU:TYPE=COS,COS=11,ADTE=TA&TNOTCR&BASIC; 

CHANGE-COSSU:TYPE=LCOSV,LCOSV=11,COPIN=0; 

CHANGE-COSSU:TYPE=LCOSD,LCOSD=11,ALAUTH=1&&64; 

/*** Trunk Group for WAML ***/ 

ADD-BUEND:TGRP=11,NAME="WAML 

",NO=30,TRACENO=0,ACDTHRH=*,PRIONO=2,TDDRFLAG=ON,GDTRRULE=0,ACDPMGRP=0,CHARCON 

=NEUTRAL; 

/*** Trunk Circuit for WAML ***/ 


0,COTNO=11,COPNO=11,DPLN=0,ITR=0,COS=11,LCOSV=32,LCOSD=32,CCT="ISS 

WAML 

",DESTNO=0,PROTVAR="CORNV33",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP= 

TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,TRACOUNT=31,SATCOUNT=MANY,NNO=1-1- 

11,ALARMNO=0,FIDX=1,CARRIER=1,ZONE=EMPTY,COTX=11,FWDX=1,CHIMAP=N,UUSCCX=16,UUS 

CCY=8,FNIDX=1,NWMUXTIM=10,CLASSMRK=EC&G711&G729OPT,TGRP=11,SRCHMODE=CIR,INS=Y, 

DEV=LAN,BCHAN=1&&30; 

/*** Access Code Definition for WAML ***/ 


/*** Route for WAML Circuit ***/ 

/*** Outdial Rule for WAML Circuit ***/ 

ADD-LODR:ODR=11,CMD=DTMF; 

ADD-LODR:ODR=11,CMD=END; 

/*** LCR Route for WAML ***/ 

ADD-RICHT:MODE=LRTENEW,LRTE=11,LSVC=ALL,NAME=" WAML 

",TGRP=11,DNNO=1-1- 

11,ROUTOPT=YES,ROUTATT=NO,EMCYRTT=NO,PDNNO=0,CHARCON=NEUTRAL,CONFTONE=NO,RERIN 

GRP=NO,NOPRCFWD=NO,NITO=NO; 

ADD- 

LDAT:LROUTE=11,LSVC=ALL,LVAL=1,TGRP=11,ODR=11,LAUTH=1,CARRIER=1,ZONE=EMPTY,LAT 

TR=NONE,DNNO=1-1-314,VCCYC=4; 

/*** Dialing Plan for WAML ***/ 


14.2 Remote PBX Settings 

14.2.1 CTI Definition 

/*** CTI Application Process Definition ***/ 

ADD-CPTP:TYPE=DPCON,NO=55,DPPROC="PROCID5",IPNO=""; 




ADD- 

CPTP:TYPE=APPL,NO=55,EMSAPPL="ACM55",DPPROC="PROCID5",DPAPPL="APPL55",MSGBASED 

=YES,LOCPORT=102,FARPORT=102,LOCTSAP="ACM55",FARTSAP="APPL55"; 

/*** Definition of CTI Events Filter ***/ 

ADD-XAPPL:APPLNO=55,APPLDP="APPL55",NAME="APPLICATION_55 

",TSKA=Y; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=ACCOUNT&AGASSIGN&AGENT&ABANDO 

N&QUEUED; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=REDIRECT&GRPSEL&LOGON&REC&RCG 

DISC; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=RCGSEL&ATB&SELECT&QUEUTS&DELI 

V; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=RTD&ASSOC&DISCON&RET&REMOV; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=ROUTD&GRP&CONNECT&GENDGTS&PUL 

LBACK; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=GRPABAND&GRPDELIV&GRPDIV&GRPF 

WD&GRPQUED; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DIGDIALD&RCGMPC&TTONGEN&MWI&C 

ALLBACK; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DATARES&DATASUSP&FASTDATA&SEN 

DDATA&STARTDAT; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=STOPDATA&CALLFAIL&MOBILUSR&CA 

LLINFO&APPINFO; 

CHANGE- 

XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=APPOOS&APPBIS&APPCLEAR&CFWDED 

; 

CHANGE-XAPPL:CTYPE=MONCB,APPLNO=55,SUBAPPL=D25,GLOBAL=RCG; 

/*** Definition of ACL Manager Link for CTI ***/ 

ADD- 

ACMSM:APPLNO=55,TYPE=ACLAPPL,ACLAPPL="APPL55",PBXAPPL="ACM55",PROCID="PROCID5" 

,ACCESS=CB,PASSWD="CSTAGW",PACKAGE=Y,MAXSBYTE=1020,MAXRBYTE=1020; 




14.2.2 RCG Definition 

/***** Definition of Route Control Group *****/ 

ADD-WABE:CD=8811,DAR=RCG,CHECK=N; 

/***** Enabling ACD in the PBX *****/ 

CHANGE- 

ZAND:TYPE=ACD,ACDALLOW=YES,MONTONE=YES,SUPAGTNU=NO,COCONN=NO,TIECONN=NO; 

/**** Call Forwarding of RCG *****/ 

CHANGE-ACDSD:TYPE=CAFRCG,RCG=85,CAFDN=8811; 

/***** Definition of ACD Route *****/ 

ADD-ACDRT:ART=201,MAXSTEP=5; 






/***** Definition of ACD Routing (Shiftsets) *****/ 

ADD-ACDRS:TYPE=DS,DSNUM=1,SHIFT=23-59,ART=201,EOS=YES,ARTDEF=201; 

ADD-ACDRS:TYPE=RS,RCG=85,SUN=1,MON=1,TUE=1,WED=1,THU=1,FRI=1,SAT=1; 

/***** Definition of STN for DNIT *****/ 

ADD-WABE:CD=870,DAR=STN; 

/***** Definition for DNIT *****/ 

ADD-DNIT:TBL=DNI,INTRTDN=870,ROUTING=DRTD,SARULE=0,DISPLAY=" 

",ACD=YES,RCG=85,PRI=64,OVRPRI=0,AUDSRCID=0,THRSHLD=*,REVCHA=FORB; 

/***** Recorder Channel Mapping from Remote PBX *****/ 

ADD-WABE:CD=330700&&330759,DAR=STN,CHECK=N; 

CHANGE-WABE:CD=330700&&330759,DESTNO=15; 

14.2.3 Configuration of WAML Card 

/*** Card Definition for WAML ***/ 

ADD-BCSU:MTYPE=PER,LTG=1,LTU=2,SLOT=79,PARTNO="Q2205-X 

",FCTID=1,LWVAR="0",HWYBDL=A; 




/*** Global Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=2,SLOT=79,TABTYPE=GLOBAL,STNO=339450,LANHW=WESTERN,ACTNETIF=ALL 

,FIREWALL=ISDN,ADPISDN=ROUTE,ADPELAN=ROUTE; 

/*** Atlantic LAN Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=2,SLOT=79,TABTYPE=NETWORK,NETNAME=ATLLAN,IPADDR="192.9.51.4",IP 

NMASK="255.255.255.0"; 

/*** Customer LAN Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=2,SLOT=79,TABTYPE=NETWORK,NETNAME=EXTLAN1,IPADDR="192.168.151.1 

51",IPNMASK="255.255.255.0"; 

/*** WAN Settings for WAML ***/ 

ADD- 

LANC:LTG=1,LTU=2,SLOT=79,TABTYPE=NETWORK,NETNAME=ISDN1,IPADDR="192.3.3.51",IPN 

MASK="255.255.255.0"; 

/** ISDN Terminal Settings for Connection to Remote PBX ***/ 

ADD- 

LANC:LTG=1,LTU=2,SLOT=79,TABTYPE=ISDNTERM,IPADDR="192.3.3.55",STNO1=338950,INO 

UTCH1=IN&OUT,STNO2=338950,INOUTCH2=IN,BITRATE="64",CALLBACK=N; 

/*** COT for WAML ***/ 

ADD-COT:COTNO=11,PAR=RCL&ANS&CEBC&CBBN&CBFN&FWDN&FNAN&COTN&IEVT&BSHT&NTON; 

/*** COP for WAML ***/ 

ADD- 

COP:COPNO=11,PAR=DTMF&SDL&EOD&ANS&SACK&ACKF&ACKB&RBLK&RLSA&NTON&WOT2&TIM1&TIM3 

&IDP2&DTM1&AST1,TRK=TA,TOLL=TA; 

/*** COS for WAML ***/ 

CHANGE-COSSU:TYPE=COS,COS=111,AVCE=TA&TNOTCR&DATA; 

CHANGE-COSSU:TYPE=COS,COS=111,AFAX=TA&TNOTCR&BASIC; 

CHANGE-COSSU:TYPE=COS,COS=111,ADTE=TA&TNOTCR&BASIC; 

CHANGE-COSSU:TYPE=LCOSV,LCOSV=32,ALAUTH=1&&32; 

CHANGE-COSSU:TYPE=LCOSV,LCOSV=32,COPIN=0; 

CHANGE-COSSU:TYPE=LCOSD,LCOSD=32,ALAUTH=1&&64; 

CHANGE-COSSU:TYPE=LCOSD,LCOSD=32,INFO="DATA CLASS"; 




/*** Trunk Group for WAML ***/ 

ADD-BUEND:TGRP=11,NAME="WAML 

",NO=30,TRACENO=0,ACDTHRH=*,PRIONO=2,TDDRFLAG=ON,GDTRRULE=0,ACDPMGRP=0,CHARCON 

=NEUTRAL; 

/*** Trunk Circuit for WAML ***/ 


0,COTNO=11,COPNO=11,DPLN=0,ITR=0,COS=111,LCOSV=32,LCOSD=32,CCT="WAML 

",DESTNO=0,PROTVAR="CORNV33",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP= 

TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,TRACOUNT=31,SATCOUNT=MANY,ALARMNO=211,FID 

X=1,CARRIER=1,ZONE=EMPTY,COTX=11,FWDX=1,CHIMAP=N,UUSCCX=16,UUSCCY=8,FNIDX=1,NW 

MUXTIM=10,CLASSMRK=EC&G711&G729OPT,TGRP=11,SRCHMODE=CIR,INS=Y,DEV=LAN,BCHAN=1& 

&7; 

/*** Route for WAML ***/ 

/*** Outdial Rule for WAML ***/ 

ADD-LODR:ODR=11,CMD=DTMF; 

ADD-LODR:ODR=11,CMD=END; 

/*** LCR Route for WAML ***/ 

ADD-RICHT:MODE=LRTENEW,LRTE=11,LSVC=ALL,NAME="WAML 

",TGRP=11,DNNO=1- 

1- 

12,ROUTOPT=YES,PLB=NO,ROUTATT=NO,EMCYRTT=NO,PDNNO=0,CHARCON=NEUTRAL,CONFTONE=N 

O,RERINGRP=NO,NOPRCFWD=NO,NITO=NO,CLNAMEDL=NO; 

ADD- 

LDAT:LROUTE=11,LSVC=ALL,LVAL=1,TGRP=11,ODR=11,LAUTH=1,CARRIER=1,ZONE=EMPTY,LAT 

TR=NONE,DNNO=1-1-12,VCCYC=4; 

/*** Access Code for WAML ***/ 


/*** Dialling Pattern for WAML ***/ 


14.3 Finding Trunk Numbers for Recorders 

Step I: 

Determine the PEN number pf the recorder trunk used. This is "1-1-49-1" in our case. 

Step II: 

Enter the following command: 

EXEC-DISPS:BP; 

The following output is displayed: 

H500: AMO DISPS STARTED 




AMO DISPS VARIANT/VERSION N1/001 OF 2004-04-15 

DISPLAYER VARIANT/VERSION N1/014 OF 2004-07-21 


PLEASE: 

*lst,sw,loden,cir,1,1,49,1; 

LTG LTU PBC/SLOT CCT L I N E PHYS_LINE SU DI/TSI SI LODEN 







1T 1T 5T 49T 1T 1561T 619H 1456T 5B0H 0H 4H 0H 1CBH 

1T 1T 5T 49T 1T 1561T 619H 1456T 5B0H 1H 4H 0H 1CAH 

1T 1T 5T 49T 1T 1562T 61AH 1456T 5B0H 0H 5H 0H 1CDH 

1T 1T 5T 49T 1T 1562T 61AH 1456T 5B0H 1H 5H 0H 1CCH 

1T 1T 5T 49T 1T 1563T 61BH 1456T 5B0H 0H 6H 0H 1CFH 

1T 1T 5T 49T 1T 1563T 61BH 1456T 5B0H 1H 6H 0H 1CEH 

1T 1T 5T 49T 1T 1564T 61CH 1456T 5B0H 0H 7H 0H 1D1H 

1T 1T 5T 49T 1T 1564T 61CH 1456T 5B0H 1H 7H 0H 1D0H 

1T 1T 5T 49T 1T 1565T 61DH 1456T 5B0H 0H 8H 0H 1D3H 

1T 1T 5T 49T 1T 1565T 61DH 1456T 5B0H 1H 8H 0H 1D2H 

1T 1T 5T 49T 1T 1568T 620H 1456T 5B0H 0H 9H 0H 1D5H 

1T 1T 5T 49T 1T 1568T 620H 1456T 5B0H 1H 9H 0H 1D4H 

1T 1T 5T 49T 1T 1569T 621H 1456T 5B0H 0H AH 0H 1D7H 

1T 1T 5T 49T 1T 1569T 621H 1456T 5B0H 1H AH 0H 1D6H 

1T 1T 5T 49T 1T 1570T 622H 1456T 5B0H 0H BH 0H 1D9H 

1T 1T 5T 49T 1T 1570T 622H 1456T 5B0H 1H BH 0H 1D8H 

1T 1T 5T 49T 1T 1571T 623H 1456T 5B0H 0H CH 0H 1DBH 

1T 1T 5T 49T 1T 1571T 623H 1456T 5B0H 1H CH 0H 1DAH 

1T 1T 5T 49T 1T 1572T 624H 1456T 5B0H 0H DH 0H 1DDH 




1T 1T 5T 49T 1T 1572T 624H 1456T 5B0H 1H DH 0H 1DCH 

1T 1T 5T 49T 1T 1573T 625H 1456T 5B0H 0H EH 0H 1DFH 

1T 1T 5T 49T 1T 1573T 625H 1456T 5B0H 1H EH 0H 1DEH 

1T 1T 5T 49T 1T 1574T 626H 1456T 5B0H 0H FH 0H 1E1H 

1T 1T 5T 49T 1T 1574T 626H 1456T 5B0H 1H FH 0H 1E0H 

1T 1T 5T 49T 1T 1575T 627H 1456T 5B0H 0H 10H 0H 1E3H 






1T 1T 5T 49T 1T 1578T 62AH 1456T 5B0H 0H 13H 0H 1E9H 

1T 1T 5T 49T 1T 1578T 62AH 1456T 5B0H 1H 13H 0H 1E8H 

1T 1T 5T 49T 1T 1579T 62BH 1456T 5B0H 0H 14H 0H 1EBH 

1T 1T 5T 49T 1T 1579T 62BH 1456T 5B0H 1H 14H 0H 1EAH 

1T 1T 5T 49T 1T 1580T 62CH 1456T 5B0H 0H 15H 0H 1EDH 

1T 1T 5T 49T 1T 1580T 62CH 1456T 5B0H 1H 15H 0H 1ECH 

1T 1T 5T 49T 1T 1581T 62DH 1456T 5B0H 0H 16H 0H 1EFH 

1T 1T 5T 49T 1T 1581T 62DH 1456T 5B0H 1H 16H 0H 1EEH 

1T 1T 5T 49T 1T 1582T 62EH 1456T 5B0H 0H 17H 0H 1F1H 

1T 1T 5T 49T 1T 1582T 62EH 1456T 5B0H 1H 17H 0H 1F0H 

1T 1T 5T 49T 1T 1583T 62FH 1456T 5B0H 0H 18H 0H 1F3H 

1T 1T 5T 49T 1T 1583T 62FH 1456T 5B0H 1H 18H 0H 1F2H 

1T 1T 5T 49T 1T 1584T 630H 1456T 5B0H 0H 19H 0H 1F5H 

1T 1T 5T 49T 1T 1584T 630H 1456T 5B0H 1H 19H 0H 1F4H 

1T 1T 5T 49T 1T 1585T 631H 1456T 5B0H 0H 1AH 0H 1F7H 

1T 1T 5T 49T 1T 1585T 631H 1456T 5B0H 1H 1AH 0H 1F6H 

1T 1T 5T 49T 1T 1586T 632H 1456T 5B0H 0H 1BH 0H 1F9H 

1T 1T 5T 49T 1T 1586T 632H 1456T 5B0H 1H 1BH 0H 1F8H 

1T 1T 5T 49T 1T 1587T 633H 1456T 5B0H 0H 1CH 0H 1FBH 




1T 1T 5T 49T 1T 1587T 633H 1456T 5B0H 1H 1CH 0H 1FAH 

1T 1T 5T 49T 1T 1588T 634H 1456T 5B0H 0H 1DH 0H 1FDH 

1T 1T 5T 49T 1T 1588T 634H 1456T 5B0H 1H 1DH 0H 1FCH 

1T 1T 5T 49T 1T 1589T 635H 1456T 5B0H 0H 1EH 0H 1FFH 

1T 1T 5T 49T 1T 1589T 635H 1456T 5B0H 1H 1EH 0H 1FEH 


PLEASE: 

* 

To quit the DISPS mode, enter the command end. 

The decimal equivalent of the LODEN is the trunk number required for recording. 

Please check every second LODEN value and transfer these into the ASC RIA Server for CTI- 

Server setup.GUI: 

To change language: 

cha-funct:slang=ger; to German, only for the current session 

cha-funct:lang=ger;change forever 

cha-funct:lang=eng;

ASC Call Recording for Siemens HiPath 4000 - Papagayo System, CA

Create successful ePaper yourself

Delete template?

Save as template?