asc call recording for siemens hipath 4000 call recording for siemens hipath 4000 installation...

ASC Call Recordingfor Siemens HiPath 4000

Installation Manualfor the installation, configuration and administrationincl. User Manual RIA Server

Version 20.03.07

ASC Call Recording for Siemens HiPath 4000ASC Call Recording for Siemens HiPath 4000

1 Introduction to the Installation Manual.......................................................................................... 32 List of Abbreviations....................................................................................................................... 43 Preliminary Remarks and Restrictions.......................................................................................... 53.1 Copyright .............................................................................................................................................................53.2 Range of Validity .................................................................................................................................................53.3 Limited Warranty .................................................................................................................................................53.4 Disclaimer ...........................................................................................................................................................53.5 Limitation of Liability ............................................................................................................................................53.6 ASC Software License Agreement ......................................................................................................................63.7 Licenses ..............................................................................................................................................................63.8 Restrictions .........................................................................................................................................................64 Classification of Safety Advice and Warning Instructions .......................................................... 75 Description of the Software............................................................................................................ 85.1 Trunk Side Recording .........................................................................................................................................85.2 Extension Side Recording ...................................................................................................................................85.3 Silent Monitoring .................................................................................................................................................95.3.1 Dynamic, Selective Recording .............................................................................................................................95.3.1.1 User-Activated Start and Stop..............................................................................................................................95.3.1.2 Threat Call Recording (KEEP) .............................................................................................................................95.3.1.3 Private Call Elimination (DELETE).......................................................................................................................95.3.2 Centralized Recording........................................................................................................................................105.3.3 Dynamic Assignment of Agents .........................................................................................................................105.3.4 Dynamic Assignment of Recording Channels....................................................................................................105.3.5 Class of Recording (CoR) ..................................................................................................................................105.4 Tagged Call Information ....................................................................................................................................116 System Requirements................................................................................................................... 126.1 System Components by ASC ............................................................................................................................126.1.1 MARATHON EVOLUTION.................................................................................................................................126.1.2 RIA Server Siemens HiPath 4000......................................................................................................................126.2 System Components by Siemens .....................................................................................................................136.2.1 Siemens HiPath 4000 .......................................................................................................................................136.2.2 Siemens CAP Server .........................................................................................................................................137 Installation of the RIA Server........................................................................................................ 157.1 Installing the RIA Server Base Software ...........................................................................................................157.2 Installing the RIA Server for Siemens HiPath 4000 ..........................................................................................198 Configuration of Siemens CAP .................................................................................................... 238.1 CAP Version ......................................................................................................................................................238.2 Service - Switch Connection .............................................................................................................................238.2.1 List of Switch Connections.................................................................................................................................238.2.2 Switch Connection - SCC...................................................................................................................................248.2.3 Switch Connection - CA4000 .............................................................................................................................248.2.4 Switch Connection - Switch................................................................................................................................258.3 Service - Domain Information ............................................................................................................................268.4 Users .................................................................................................................................................................268.4.1 User for CTI Connectivity ...................................................................................................................................278.5 Devices .............................................................................................................................................................278.5.1 List of Devices....................................................................................................................................................278.5.2 Device Properties...............................................................................................................................................299 Configuration of Siemens HiPath 4000........................................................................................ 3010 Configuration of MARATHON EVOLUTION................................................................................. 3210.1 Recording Channels ..........................................................................................................................................3210.2 Physical Connection of the Recorder to PBX ....................................................................................................3310.2.1 The DIUN Card ..................................................................................................................................................3410.2.2 Pin Assignment of the DIU-N2 ...........................................................................................................................3410.2.3 Connection Cable...............................................................................................................................................3411 Configuration and Administration of the RIA Server ................................................................. 3611.1 RIA Server Configurator ....................................................................................................................................3611.1.1 Checklist - Required Information........................................................................................................................36

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

ASC Call Recording for Siemens HiPath 4000

11.1.2 Accessing the RIA Server Configurator .............................................................................................................3611.1.3 Login to the RIA Server Configurator .................................................................................................................3811.1.4 Creating and Modifying Users............................................................................................................................3911.1.5 RIA Connection..................................................................................................................................................3911.1.6 PBX....................................................................................................................................................................4011.1.7 Extensions..........................................................................................................................................................4211.1.8 SiMo Information ................................................................................................................................................4311.1.9 Buttons...............................................................................................................................................................4611.1.10 Class of Recording.............................................................................................................................................4711.1.11 Texts for Display ................................................................................................................................................4911.1.12 Overview � PBX.................................................................................................................................................4911.1.13 Overview � Monitor Points .................................................................................................................................5011.1.14 Overview � Check Result...................................................................................................................................5012 RIA Client Configuration............................................................................................................... 5112.1 Common Configuration .....................................................................................................................................5112.2 RIAactive Configuration ....................................................................................................................................5212.3 RIApassive Configuration ..................................................................................................................................5413 Test Hints ....................................................................................................................................... 5713.1 Connection to CAP and HiPath 4000 ................................................................................................................5713.2 Setting Monitor Points .......................................................................................................................................5713.3 Calling the Recorder (Getting Trunk Numbers) .................................................................................................5813.4 Performing Calls Using the RCG Group ...........................................................................................................5814 Appendix: AMO Commands ......................................................................................................... 5914.1 HOME PBX Settings .........................................................................................................................................5914.1.1 CTI Definition .....................................................................................................................................................5914.1.2 ACD Settings......................................................................................................................................................6014.1.3 Recorder Settings ..............................................................................................................................................6114.1.3.1 Configuration of WAML Card (Home PBX) ........................................................................................................8814.2 Remote PBX Settings .......................................................................................................................................8914.2.1 CTI Definition .....................................................................................................................................................8914.2.2 RCG Definition ...................................................................................................................................................9114.2.3 Configuration of WAML Card .............................................................................................................................9114.3 Finding Trunk Numbers for Recorders ..............................................................................................................93


ASC Call Recording for Siemens HiPath 4000Introduction to the Installation Manual

1 Introduction to the Installation Manual

This document describes the installation of the ASC call recording solution for Siemens HiPath4000 and CAP utilizing the ASC RIA Server and MARATHON EVOLUTION including a basicuser interaction with the system.


ASC Call Recording for Siemens HiPath 4000List of Abbreviations

2 List of Abbreviations

Abbreviation Explanation

ADM ASC DataManager

CAP Common Application Platforms(Siemens CTI Middleware)

CTI Computer Telephony Integration

HPCR Call recording for HiPath(Here used for: Call Recording for Siemens HiPath4000)

RIA Client Module on the MARATHON EVOLUTION that connectsto a RIA Server and exchanges the information with therecording logic.

RIA Server Software that monitors and controls a PBX to obtain callinformation and establish silent monitoring paths.


ASC Call Recording for Siemens HiPath 4000Preliminary Remarks and Restrictions

3 Preliminary Remarks and Restrictions

The MARATHON EVOLUTION is a digital recording system for communication. The softwaredelivered with the system is used for recording and monitoring conversations and for configuringall components.

3.1 Copyright

The ASC software programs and manuals are protected by copyright laws. All rights arereserved on this installation manual, even those of reproduction and/or duplication in anyconceivable way, either by photocopying, printing on any data recording media or in translatedform. Duplication of this manual - even in extracts - is only permitted with the written approval ofASC telecom.

The technical standard at the time of delivery of device and installation manual is decisive, if noother information is given. Technical changes without advanced notice are reserved, earlierinstallation 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 thesoftware belonging to the system.

This installation manual is written for the service personnel but not for system users. Anyquestion 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 notused. ASC warrants the physical medium of the software for a period of 90 days from installationor purchase, whichever is later. Defective media cannot be repaired but only exchanged.

Software compatibility is limited to certain computers and operating systems. Using the softwarewith non-compatible systems voids any warranty. For questions on compatibility with computersand 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 notexpressly set forth in this limited warranty. ASC disclaims and excludes any and all impliedwarranties of merchantability, title or fitness for a particular purpose. ASC does not warrant thatthe software or associated documentation will satisfy your requirements or that the software anddocumentation are without defect or error or that the operation of the software will beuninterrupted.

3.5 Limitation of Liability

Except as otherwise restricted by law, ASC�s aggregate liability arising from or relating to youruse of the software, associated documentation or any services provided by ASC and/or itsagents is limited to the total of all payments made by or for you for the software anddocumentation. Neither ASC nor any of its licensors, employees or agents shall in any case beliable for any special, incidental, consequential, indirect or punitive damages even if advised ofthe possibility of those damages. Neither ASC nor any of its licensors, employees or agents is


ASC Call Recording for Siemens HiPath 4000Preliminary Remarks and Restrictions

responsible for lost profits or revenue, loss of use of software, loss of data, costs of re-creatinglost 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 thefollowing), for which you have purchased a license, are protected by copyright laws, patent lawand international treaties. Using them is subject to the terms of license. ASC software programsare used in various ways and require different license rights. The type of license applyingdepends on the program for which you purchased a license as shown on your Proof of Purchaseand the definitions and grants of the license below. If the software is an upgrade version from aprevious version of an ASC software product, you may either use the current or the previousversion of the software, but never both at the same time. This license supersedes any priorlicense 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 onebackup 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 ofPurchase. 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 orworkstations attached to a public messaging system, the quantity of the software "in use� isconsidered to be the greater of the maximum number of computers on which the software isloaded in memory or virtual memory, or maximum number of computers on which the software isstored at any one time.

3.8 Restrictions

You may not rent, lease, decompile, disassemble, reverse engineer or create derivate works ofthe software. Irrespective of the number of sets of media included with the software, you may usethe software only as provided in this license and the Proof of Purchase. Certain limitations mayapply to the purchase of this license. When present, they are printed on the software packageand are considered as part of the license. Any breach of the terms of license will automaticallyterminate it. All copies of the software and documentation will then have to be destroyed. Youmay 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 tothe terms of this license and has informed ASC about the transfer.


ASC Call Recording for Siemens HiPath 4000Classification 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 clearlyidentified by the following signal words:

All safety advice and warning instructions shall help to avert injuries to the operating personneland damages to the device. Please heed all rules and regulations.

DANGER

Warns of states and possible actions which may lead to injuries of theoperator and severe damage to the device.

ATTENTION

Marks states and possible actions which may cause damage to thedevice.

HINT

Indicates hints that lead to a better understanding of the device and theoperating instructions and useful advice for the daily use of the device.


ASC Call Recording for Siemens HiPath 4000Description of the Software

5 Description of the Software

MARATHON EVOLUTION offers very versatile options of connection to legacy TDM (TimeDivision Multiplexing) and VoIP installations. This chapter describes the various options of how toconnect to a particular configuration. The figure below provides an overview of the recordingmethods.

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 siderecording 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 channelprotocols the MARATHON EVOLUTION is able to "understand".

If D channel information is not provided or does not deliver enough details (like AgentIDs), RIAcomes into play.

5.2 Extension Side Recording

In the case of extension side recording, the recording interface is connected at the extension lineof a subscriber (phone). Both external and internal calls can thus be recorded. By evaluating theD channel of digital terminals, all interactions of a phone like button presses, LED on/off, displaycontents 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 maybe located at the phone (analog handset recording).

If D channel information is not provided or does not deliver enough details (like AgentIDs), RIAcomes into play. RIA is also able to control the exact starting and stopping of recordings wherethis 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 adynamic selective recording which enables the user to manually control the recording.Additionally, the user may obtain information (display message, LED) about the current recordingstatus on the phone (if supplied by the PBX). Silent monitoring requires CTI connectivity with theswitch. A CTI service performs the "monitoring command" driven by definable events, such asAgent_ID, CLI, schedule, etc. The switch creates a "duplicate" of the conversation (to berecorded) and makes a call to the recorder. The recorder takes the call (active PRI required orEVOip for IP solutions) and gathers the "duplicated" audio information. Usually, depending on thetechnology of each vendor, the "duplicated call" may be split into two calls carrying the "talk" andthe "listen" path separately. This option takes twice as much storage capacity, but it allows forstereo 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 ofthe telephone. The dynamic recording mode enables the recording of many extensions with justa few recording channels by setting up channels only when needed. This "dynamic recordingchannel assignment" is essential for start/stop and network-wide recording and frees space forother 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 adifferent group each day and still save on channels per agent and the number of licensesrequired.

5.3.1.1 User-Activated Start and Stop

The recording may be started, stopped or temporarily paused by the agent/user simply bypressing a dedicated button on the telephone. In this way, individual sections of a given call maybe 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 bemonitored to ensure the entire interaction is preserved. Afterwards, the recordings are deletedautomatically, 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 abutton. Agents can also alternate between the keep and delete modes (toggle) at any time duringthe conversation by pressing the button again. The final selection determines how the call will betreated.



5.3.2 Centralized Recording

In a network of PBX systems at multiple locations, MARATHON EVOLUTION recording unitsneed to be deployed just at one site since call recordings are routed back through the networkdriven by the ASC RIA Server. In other words, the server hardware has to be deployed only onone (main) location. All network nodes receive commands from centralized CTI and areinstructed to send audio to the centralized recorder(s). This feature is PBX-dependent and is notsupported by all vendors.

5.3.3 Dynamic Assignment of Agents

Via the graphical user interface, administrators can easily add/delete users from a list forselective recording during runtime.

5.3.4 Dynamic Assignment of Recording Channels

The function Dynamic recording channel assignment makes sure that a channel to the recorderwill only be set up when it is actually needed. This is an essential function which saves channelsin the case of start/stop recording as well as network-wide recording (as network channels wouldotherwise be occupied unnecessarily).

5.3.5 Class of Recording (CoR)

Class of Recording allows the administrator to set up a group of channels with dedicatedfunctionality. In this case, a group of channels can be assigned to a group of users that willoperate 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 8channels (3-10) and 400 users (group C) will share 110 channels (11-120). The calls of group Awill be stored for 5 years, the calls of group B for 3 months and the ones of group C for only 1month.



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


ASC Call Recording for Siemens HiPath 4000System 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. TwoPRI-active channels and one recording channel license PRI-active are required per call to berecorded.

6.1.2 RIA Server Siemens HiPath 4000

Version Version 7.0 or higher is required

Active PRI card For connectivity to the PBX an active PRI card is required

Channel licenses Licenses for the active PRI card and for the 4wire-configuration arerequired

RIA licenses RIAactive or RIApassive license for Siemens HiPath 4000 required.The number of required RIA seat licenses corresponds to thenumber of recording channels.

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

6.2.2 Siemens CAP Server

Installing Patch MSC14783 (svcstart.jar)

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

2. Rename the former svcstart.jar in <INSTALLDIR>\HipathCTI\lib directory to backup this version (e.g. svcstart.jar_last).

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

4. Edit the S02service_ctrl.proc in <INSTALLDIR>\HipathCTI\config\<HOST_NAME>\systemdb directory as follows:

5. Insert the line restart:1 after the line restartdayly:<?x $USERS_BACKUP_TIME ?>

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

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.)

� 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).

DIUN card Required for connectivity to the Recorder. 2 Ports per 30 recordingchannels.

Version The Siemens CAP Server must have version 3.0 (recommendedminimum version I915 with the patches described below).

Licenses for all monitored devices

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 HiPath4000, the following patches need to be applied to the Siemens CAPServer installation. These patches are valid for CAP V3.0 I915 only.



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.


ASC Call Recording for Siemens HiPath 4000Installation 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 locatedunder: 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 thesetup process. If you prefer all ASC related files in one directory, enter the path to the installationdirectory you have selected for the RIA Server Base Software above, usually C:\ProgramFiles\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 theRIA 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 thissetup 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 theMARATHON EVOLUTION. An ASC service technician should use the user "service" for thispurpose. 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 theMARATHON 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 therequest 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 willlead to a reboot of the PC.

Select No, I will restart my computer later if you have to install more applications and do not wantto reboot after each setup. Do not forget to reboot the PC by yourself to make the RIA ServerBase Software available.

Click Finish to finish the installation process.


ASC Call Recording for Siemens HiPath 4000Configuration 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.0that 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 ofSiemens CAP in June 2006.

With changing subversion numbers, some pages in the CAP administration may look slightlydifferent 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 SingleDomain 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 forSiemens HiPath 4000 connects to the PBX through these switch connections. For each PBX itestablishes 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/sub-app-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. Thisuser does not need an assigned license.

Fig. 22 - Users



8.4.1 User for CTI Connectivity

Fig. 23 - Modify User - CTI

You have to create a CTI user with a user name and password. Please check the CTI Usercheckbox under Roles.

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

8.5 Devices

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


ASC Call Recording for Siemens HiPath 4000Configuration 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 configurationof the PBX.

Refer to chapter 14 - Appendix: AMO Commands for a description of the required AMOcommands 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, likemanual 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 buttonsas 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 withthe 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:


ASC Call Recording for Siemens HiPath 4000Configuration 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 13you have to enter c13013.

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

Where gg = type of device (GrundGeraet), c13006 = Ziel-Rufnummer fuer Namenstaste (targetnumber for name button) and c13 is a special code which is always used as a prefix before theapplication Id (006) in this command.

Check configuration with

ab-ziel:na,301,;

Output similar to the following can be observed.


ASC Call Recording for Siemens HiPath 4000Configuration 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 theactive PRI for the recording of one call. The required settings can be seen in Fig. 26 - Settings forRecording Channel.

Example:

HINT

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

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 connectionand the DIUN must be configured as described above. The Communication Recorder must havethe 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 channelseach. 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 samefor both front ports.

10.2.3 Connection Cable

For the connection, a cable must be manufactured on the basis of the following drawing. Youneed to connect the recorder�s active PRI card to the front side connectors of the Siemens DIUN

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



card. It is also possible to connect to the rear-side of the DIU card. An adaptor with 15-pinconnectors is therefore required to fit to the cable mentioned below.

Fig. 27 - Connection Cable for DIUN2 - ACTIVE PRI


ASC Call Recording for Siemens HiPath 4000Configuration 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

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 WEBPortal.

Access to CAP Each PBX is represented by a Switch Connection in the CAPAdministration. Please refer to chapter 8.2.1 - List of SwitchConnections.

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

Monitored devices Get a list of all devices to be monitored. Those numbers have beenentered during the CAP configuration. Please refer to chapter 8.5.1- List of Devices.

DIUN channel numbers Get a list of all DIUN channels numbers (recorder-extensions), which are used to build the recording path to the recorder.

Trunk numbers for DIUN channel numbers

Each DIUN channel has an associated trunk number (LODEN) thatis used to clean up the DIUN channels on RIA Server startup.

DIU exists At the central PBX, at least one DIU hardware group must exist for connection of the ASC Communication Recorder.

DIU configuration The DIUN hardware group must be configured by a Siemens service technician. Please refer to chapter 14 - Appendix: AMO Commands.

RCG configuration One RCG per PBX must be configured to allow outgoing calls to therecorder channels. The RCG group number needs to be enteredinto the RIA Server configuration.



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

Fig. 29 - RIA Server WEB Portal

HINT

An easy way to carry out the administration from another PC is tosimply enter the IP address of the RIA Server PC to bring up the RIAServer 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 avalid user name and password.

Fig. 30 - Login

HINT

The default User is 1 and the default Password is 1. For securitypurposes, 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 anew 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 onthis port for incoming connections from a RIA Client. The RIA Client that runs on the recordermust be configured to connect to the IP address of the RIA Server and the port configured hereunder RIA Connection.



Fig. 32 - RIA Connection

The default value 9000 should only be changed if you plan to use more than one RIA Serversimultaneously or if this port is already occupied by another application.

11.1.6 PBX

One PBX entry in the configuration represents one link to a PBX. Any changes in this sectionrequire 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 theleft.

Fig. 33 - Creating a New PBX

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

HINT

Please observe that you have to enter the same ServerPort in the RIAClient configuration, as displayed in Fig. 45 - RIAactive -> ProtocolInterface and Fig. 47 - RIApassive -> Protocol Interface.



The SCC details from chapter 8.2.2 - Switch Connection - SCC have the following relation to thefields in the PBX configuration:

Fig. 34 - PBX Configuraton

Finally, click Save to create a new PBX entry with the given configuration. Consequently, it will bedisplayed in the menu tree on the left with the name you have entered into the field PBX Name.

PBX Name A "human readable" name for the PBX. This name will appear inother parts of the RIA Server Configurator and will be displayed inthe Status View of the Alarm Management.

Hostname SCC ip address.

Port SCC port.

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

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

Country code Not interpreted, for display only.

Area code Not interpreted, for display only.

Net code Not interpreted, for display only.

PBX ID Internal identification number of the PBX. This number has to beentered as PhysicalPbxID in the RIA Client configuration, asdisplayed in Fig. 48 - RIApassive -> Devices.

RCG The number of the RCG group that has been configured in theHiPath to make the outgoing calls to the recording channels.



11.1.7 Extensions

The Extensions page shows a list of all configured stations and provides the option to create newextensions for monitoring.

Fig. 35 - Extension Configuration

However, this does not mean that recording for a particular station is active. Therefore, a monitorpoint has to be activated as displayed in the above figure under Monitorpoint Enabled = yes.



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 adate 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 numbersfor the setup, which makes things a lot easier and more efficient. Enter a single extension or arange 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 channelsof the DIUN card.

PBX ID The PBX to which the device belongs.

Extension type Extension: Normal endsetTrunk: A connection to a PSTNAgent: An agent login number

Language You can select the language for display messages. By default, onlyen_GB is predefined. Up to 7 different languages are possible whichcan be defined individually in the Text section of the RIA ServerConfigurator.

Class of recording This is an advanced feature. By default, you can set it for allextensions to the value Class1 provided that all extensions are to berecorded in the same way.This setting allows you to group a set of extensions according totheir behaviour (automatic or manual recording start) and usedchannels when recording actively.See also chapter 5.3.5 - Class of Recording (CoR).

Extension number The phone number of the extension supposed to be recorded. Thenumber must be in short format, without area or net code.

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

Note A note field, can be blank.



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.

Fig. 37 - SiMo Information

HINT

Remember that 30 B channels will result in 15 recording channels (15calls can be recorded simultaneously). The assignment of recorderextensions (B channels) to recording channels will be performed in oneof the subsequent steps.

Recording channel ID This parameter must be identical with the one entered asPhysicalDeviceID in the RIA Client configuration.

Class of channel Can be used to group SiMo Information to be used in a class ofrecording.

Route number 1 The number to be dialled in order to reach a defined B channel onthe DIUN card.

Route number 2 The number to be dialled in order to reach a defined B channel onthe DIUN card.

Trunk number 1 Each B channel has a trunk number (LODEN in HiPath terms)assigned that must be entered here.

Trunk number 2 Each B channel has a trunk number (LODEN in HiPath terms)assigned that must be entered here.

Note Can be used for notes.



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: AMOCommands.

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


*

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

HINT

Please make sure that the value you enter as Recording channel ID isidentical with the parameter PhysicalDeviceID in the RIA Clientconfiguration, as displayed in Fig. 46 - RIAactive -> Devices.



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

11.1.9 Buttons

The Buttons page allows the assignment of function buttons to devices that allow the manualstarting/stopping of recordings and marking ongoing recordings to keep or delete them.

Fig. 38 - Configuration of Buttons

HINT

Please check every second LODEN value and transfer these into theASC RIA Server Configurator for all the route numbers.

HINT

You also have to configure the buttons on the telephone as namebuttons to work with the RIA Server. Please refer to chapter FunctionButtons for Manual Interaction for details.

Extension Select the extension to add a new button.

Button type Start/Stop: For manual start of recording.Keep/Delete: Mark ongoing recording to keep or delete after call isover.

Button index Defines which button on the device is used for the selected function.To find out the button number, start counting on the uppermost leftwith 1, going down. Continue counting on the button column to theright, going down.



The button Copy to extension(s) copies the configuration of one button to all the devices thathave been selected in the list field above. You can select multiple entries by holding CTRL whileclicking the entries.

If you want to clean up all the assigned buttons for a range of devices, you can enter a range ofdevices into the input fields to the right and click Remove from extension(s) to delete all buttonsfrom those devices.

11.1.10 Class of Recording

A class of recording bundles a set of extensions sharing the same settings like the recordingmode (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, butcan use the one that is there by default.

Fig. 39 - Class of Recording Configuration

LED feedback yes: Indicate recording status through the LED next to the buttonselected under ButtonIndex.no: LED stays always off.

Display feedback yes: Message in display that tells which function has been activatedthrough the button press.no: No messages in display if button is pressed.



Recording type Available values:� Extension-Side

� Trunk-Side

� Silent Monitoring

RIA Server role Available values:� Active

� Passive

Select Active if you plan to do trunk-side recording with monitorpoints only on the extensions. In this case, the RIA Server decidesabout the recording start and stop.For silent monitoring, extension-side recording and trunk-siderecording with monitorpoints on the trunks, Passive is the rightchoice.

Recording mode Available values:� Automatic: Recording starts at the beginning of a call

� Manual: Recording must be started manually during a call through a button press.

LED feedback Available values:� ON

� OFF

If a button is assigned to an extension with an LED, this switch turnsthe recording status indication through that LED on/off.

Display feedback Available values:� ON

� OFF

If turned on, a display message will be shown on the display of thephone at the start/stop of a recording. These messages can beconfigured as described in chapter 11.1.11 - Texts for Display.

Description 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'sdisplay from a total of 7 languages. You can individually define these messages in the Textsection.

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

HINT

If you have activated the display of the recording status in the phone�sdisplay, but want only a message when a recording starts but not whenit ends, then all you have to do is to blank the NodeValue of the STOPNodeName.



11.1.13 Overview � Monitor Points

This page shows the status of the set monitor points. Green check signs mean status OK. Readyto record. Red crossed lines show stations that are not ready to be recorded due to the fact thatthe extension either does not exist or is offline. In this case, you might also want to check therelated 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 bemonitored), 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-4seconds one device from the Extension list.

If you have 100 devices in total defined in the section Extensions, it will take approximately 5 - 6minutes until all devices have been checked.

Fig. 43 - Overview: Check Result


ASC Call Recording for Siemens HiPath 4000RIA 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.

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

12.1 Common Configuration

Fig. 44 - Common RIAactive Configuration

Check all Click this button to check whether there are any conflictingconfigurations.

Reset Resets your settings to the default values.

Save Saves your configuration.

Licensed Indicates whether you have a license for RIAactive.

NumInstances Enter the number of instances and click on Save. Afterwards, thecorresponding number of instances will be displayed in thenavigation bar and under Instances.

Enabled Enables the RIAactive instance.



12.2 RIAactive Configuration

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

Fig. 45 - RIAactive -> Protocol Interface

Name Enter a characteristic name for the RIAactive instance.

LogLevel Specify the depth of the log files. Usually, the level Medium issufficient. A higher log level can be selected for troubleshootingpurposes.

Statemachine Select the grammar to be used for this RIAactive connection.Available grammars are RIAExtnRecExtnMonitor andRIATrunkRecExtnMonitor.

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

PIF-Type Select the appropriate PIF, i.e. the vendor-specific protocol to beused for the communication with the PBX. For example, if you havea Siemens PBX, select PIFSiemensCAP.

PIF-Config Appears as soon as you have selected the PIF type and serves toconfigure the PIF.

Connection Type For CTI connections, always select the connection type TCP.

Server-IP Enter the IP address of the server on which the RIA application isinstalled.



After the configuration of the protocol interface, select the Devices tab to map the names of thechannels on the recorder to the names of the channels on the RIA Client.

Fig. 46 - RIAactive -> Devices

Server-Port Enter the port number for the RIA connection. This number must beidentical with the one entered as parameter ServerPort in the RIAServer configuration. The default value is 9000.

Inactivity-Timeout Specify the time interval (in seconds) of inactivity after which theconnections are to be terminated. By default, this value is set to 0,which means that there is no inactivity timeout.

LogBinaryData Here, you can specify whether you want to save the incoming binarydata. This is usually not required, because the incoming data isidentical with the outgoing data.

HINT

To make sure that the value you enter as Server-Port is identical withthe one in the RIA Server configuration, please check this value asdisplayed in Fig. 32 - RIA Connection.

PhonelineID Name of the channel on the recorder.

PhysicalPbxID To enable the individual channel mapping, enter active.

PhysicalDeviceID Name of the channel on the RIA Client. This name must be identicalwith the one entered on the RIA Server as Recording channel ID.

Export to CSV Exports the table to a CSV file. A dialog box appears, where youcan specify the export directory.

Import from CSV Allows you to import CSV file which contains a correspondingconfiguration file. A dialog box appears, where you can browse tothe directory of the import file.



12.3 RIApassive Configuration

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

Fig. 47 - RIApassive -> Protocol Interface

HINT

To make sure that the value you enter as PhysicalDeviceID is identicalwith the parameter Recording channel ID in the RIA Serverconfiguration, please check this value as displayed in Fig. 37 - SiMoInformation.

Statemachine Select the grammar to be used for this RIAactive connection. If youuse the extension connection type, select RIAExtnRecExtnMonitorand if you use the trunk connection type, selectRIATrunkRecExtnMonitor.

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

PIF-Type Select the vendor-specific protocol to be used for thecommunication with the PBX.

PIF-Config This section appears as soon as you have selected the PIF typeand serves to configure the PIF.

Connection Type For CTI connections, always select the connection type TCP.



After the configuration of the protocol interface, select the Devices tab to map the telephones ofthe individual PBXs to the individual channels.

Fig. 48 - RIApassive -> Devices

Server-IP Enter the IP address of the server on which the RIA application isinstalled.

Server-Port Enter the port number for the RIA connection. This number must beidentical with the one entered on the RIA Server. The default valueis 9000.

Inactivity-Timeout Specify the time period (in seconds) of inactivity after which theconnections are to be terminated. By default, this value is set to 0,which means that there is no inactivity timeout.

LogBinaryData Here, you can specify whether you want to save the incoming binarydata. This is usually not required, because the incoming data isidentical with the outgoing data.

HINT

To make sure that the value you enter as Server-Port is identical withthe one in the RIA Server configuration, please check this value asdisplayed in Fig. 32 - RIA Connection.

PhonelineID ID of the channel.

PhysicalPbxID Enter the ID of the PBX to which the telephone belongs. Thisnumber must be identical with the one specified as parameter PBXID in the RIA Server configuration.

PhysicalDeviceID Extension number of the telephone to be mapped. This numbermust be identical with the one specified as parameter Extensionnumber in the RIA Server configuration.

Export to CSV Exports the table to a CSV file. A dialog box appears, where youcan specify the directory for the export file.

Import from CSV Allows you to import CSV file which contains a correspondingconfiguration file. A dialog box appears, where you can browse tothe directory of the import file.



HINT

To make sure that the PhysicalPbxID is identical with the parameterPBX ID in the RIA Server configuration and that the PhysicalDeviceID isidentical with the parameter Extension number in the RIA Serverconfiguration, please check these values as displayed in Fig. 35 -Extension Configuration.


ASC Call Recording for Siemens HiPath 4000Test Hints

13 Test Hints

This chapter describes how the configuration of the HiPath 4000 and the CAP-server can bechecked using the csta3host application from Siemens. If any test fails, a technician has to checkthe 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 theconnection 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 inthe 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 withinthe CSTA-tool.

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


ASC Call Recording for Siemens HiPath 4000Test Hints

13.3 Calling the Recorder (Getting Trunk Numbers)

Use the recently monitored device to manually call the recorder extensions. Check whether thedifferent channels go into light blue/red state (depending on the configuration of the channel). Inthe CSTA events, the used trunk number is displayed (as a decimal number; so you can also usethis 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. calling778000 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. Anew 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 rcggroup number not the rcg number to perform calls!

Fig. 50 - Device#-Mask-Helper


ASC Call Recording for Siemens HiPath 4000Appendix: AMO Commands

14 Appendix: AMO Commands

The following AMO commands were extracted from a running installation that runs in a network-wide configuration. The recorder(s) is/are connected to the HOME PBX. All recordings will besent through the HiPath network from the nodes to this HOME PBX. The configuration of thenetwork nodes can be found in section 14.2 - Remote PBX Settings. Please make sure the callrouting is appropriate.

In this configuration the CAP connects through WAML. That is why you can find the WAMLconfiguration 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="<IP Address of CAP Server>";

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&ABANDON&QUEUED;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=REDIRECT&GRPSEL&LOGON&REC&RCGDISC;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=RCGSEL&ATB&SELECT&QUEUTS&DELIV;

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&PULLBACK;



CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=GRPABAND&GRPDELIV&GRPDIV&GRPFWD&GRPQUED;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DIGDIALD&RCGMPC&TTONGEN&MWI&CALLBACK;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DATARES&DATASUSP&FASTDATA&SENDDATA&STARTDAT;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=STOPDATA&CALLFAIL&MOBILUSR&CALLINFO&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 thesection 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;

















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

CHANGE-LWPAR:TYPE=DIUS2,BLNO=8,LNTYPE=COPPER,VERSION=S2,QUAL=ON,MASTER=Y,DCHAN1=16,DCHAN2=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;



/*** 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 S2QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,DGTPR=00,ISDNIP=0,TRACOUNT=31,SATCOUNT=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,SRCHMODE=ASC,INS=N,DEV=S2CONN,BCHAN=1,BCNEG=N,BCGR=1,LWPAR=8,LWPP=0,LWLT=0,LWPS=0,LWR1=0,LWR2=0;

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 S2QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,DGTPR=00,ISDNIP=0,TRACOUNT=31,SATCOUNT=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=311,SRCHMODE=ASC,INS=N,DEV=S2CONN,BCHAN=2,BCNEG=N,BCGR=2;

HINT

The number of possible BUENDEL is limited to 512. This means that ifyou assign only 1 B-channel per BUENDEL that the number ofsimultaneos recordings would be approximately 240 (480 usableBUENDEL divided by 2). To support up to 480 simultaneous recordingsper PBX, it is possible to assign 2 B channels per BUENDEL, asdisplayed in the screenshot below:










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 S2QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=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=319,SRCHMODE=ASC,INS=N,DEV=S2CONN,BCHAN=10,BCNEG=N,BCGR=10;















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 S2QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,DGTPR=00,ISDNIP=0,TRACOUNT=31,SATCOUNT=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=339,SRCHMODE=ASC,INS=Y,DEV=S2CONN,BCHAN=30,BCNEG=N,BCGR=30;

ADD-TDCSU:OPT=NEW,PEN=1-01-079-1,COTNO=80,COPNO=80,DPLN=0,ITR=1,COS=75,LCOSV=32,LCOSD=32,CCT="ISDN S2QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,DGTPR=00,ISDNIP=0,TRACOUNT=31,SATCOUNT=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=340,SRCHMODE=ASC,INS=N,DEV=S2CONN,BCHAN=1,BCNEG=N,BCGR=1,LWPAR=8,LWPP=0,LWLT=0,LWPS=0,LWR1=0,LWR2=0;









ADD-TDCSU:OPT=NEW,PEN=1-01-079-1,COTNO=80,COPNO=80,DPLN=0,ITR=1,COS=75,LCOSV=32,LCOSD=32,CCT="ISDN S2QUER",DESTNO=0,PROTVAR="EDSS1NET",SEGMENT=1,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,DGTPR=00,ISDNIP=0,TRACOUNT=31,SATCOUNT=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=369,SRCHMODE=ASC,INS=Y,DEV=S2CONN,BCHAN=30,BCNEG=N,BCGR=30;

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

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,CHARCON=NEUTRAL,CONFTONE=NO,RERINGRP=NO,NOPRCFWD=NO,NITO=NO;














/*** 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,LATTR=NONE,VCCYC=4;

















/*** 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",IPNMASK="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.155",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",IPNMASK="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,NEXTROUT="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,INOUTCH1=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 ***/

ADD-TDCSU:OPT=NEW,PEN=1-01-091-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,UUSCCY=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 ***/

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,RERINGRP=NO,NOPRCFWD=NO,NITO=NO;

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

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

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

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

ADD-LDAT:LROUTE=11,LSVC=ALL,LVAL=1,TGRP=11,ODR=11,LAUTH=1,CARRIER=1,ZONE=EMPTY,LATTR=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="<IP Address of CAP Server>";



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&ABANDON&QUEUED;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=REDIRECT&GRPSEL&LOGON&REC&RCGDISC;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=RCGSEL&ATB&SELECT&QUEUTS&DELIV;

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&PULLBACK;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=GRPABAND&GRPDELIV&GRPDIV&GRPFWD&GRPQUED;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DIGDIALD&RCGMPC&TTONGEN&MWI&CALLBACK;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=DATARES&DATASUSP&FASTDATA&SENDDATA&STARTDAT;

CHANGE-XAPPL:CTYPE=SUBAPPL,APPLNO=55,SUBAPPL=D25,ADDEVT=STOPDATA&CALLFAIL&MOBILUSR&CALLINFO&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",IPNMASK="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.151",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",IPNMASK="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,INOUTCH1=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 ***/

ADD-TDCSU:OPT=NEW,PEN=1-02-079-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,FIDX=1,CARRIER=1,ZONE=EMPTY,COTX=11,FWDX=1,CHIMAP=N,UUSCCX=16,UUSCCY=8,FNIDX=1,NWMUXTIM=10,CLASSMRK=EC&G711&G729OPT,TGRP=11,SRCHMODE=CIR,INS=Y,DEV=LAN,BCHAN=1&&7;

/*** 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=NO,RERINGRP=NO,NOPRCFWD=NO,NITO=NO,CLNAMEDL=NO;

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

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

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

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

ADD-LDAT:LROUTE=11,LSVC=ALL,LVAL=1,TGRP=11,ODR=11,LAUTH=1,CARRIER=1,ZONE=EMPTY,LATTR=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


*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


*

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 call recording for siemens hipath 4000 installation...

Documents