mANUAl - VOICE RECORDER - Atis-Vc-Mdxv11

Alcatel-Lucent Application Partner Program
Inter-Working Report
Partner: ATIS UHER SA

Application type: Voice Recording Systems
( IP DR-Link )
Application name: VC-MDx v11 VDS-II
Alcatel-Lucent Platform: OmniPCXEnterprise™
The product and version listed have been tested with the Alcatel-Lucent Communication Server and the version specified
hereinafter. The tests concern only the inter-working between the Application Partner product and the Alcatel-Lucent
Communication platforms. The inter-working report is valid until the Application Partner issues a new version of such
product (incorporating new features or functionality), or until Alcatel-Lucent issues a new version of such Alcatel-Lucent
product (incorporating new features or functionality), whichever first occurs.
ALCATEL-LUCENT MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE

APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL-
LUCENT HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF
ANY NATURE WHATSOEVER AS TO THE APPLICATION PARTNER PRODUCT INCLUDING WITHOUT LIMITATION
THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR
PURPOSE AND ALCATEL-LUCENT FURTHER SHALL HAVE NO LIABILITY TO APPLICATION PARTNER OR ANY
OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.
Tests overview
Date of the tests 5th-7th of November
Alcatel-Lucent’s representative Mikael FERELLOC

Partner’s representative Patrick ROTH
Alcatel-Lucent Communication OmniPCX Enterprise

Platform (OmniPCX OmniTouch CCSE
4400/Enterprise, OmniTouch,
OmniPCX Office, ...)
OXE R11 (k1.400.25.f)
Alcatel-Lucent compatibility release
& TSAPI 7.0.5
Partner’s application version VC-MDx v11 VDS-II
Application Category Voice recording
Author(s): Mikaël FERELLOC

Reviewer(s): Rachid HIMMI
Revision History
Edition 1: creation of the document – November 2013
Test results
Passed Refused Postponed
Passed with restrictions
Refer to the section 6 for a summary of the test results.
IWR validity extension

None
Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 2/95

Copyright © 2013 Alcatel-Lucent, All rights reserved
Company Contact Information
Contact name: Thees Frank
Title: CTO
Address : Industrie 7
City: CH-2046 Fontaines
Country: Switzerland
Phone: 0043 328540 117

Fax: 0043 328540 101
Mobil:
Web address: www.voicecollect.net

E-mail: service@voicecollect.net

TABLE OF CONTENTS
1 INTRODUCTION ...................................................................................................................................... 8
2 VALIDITY OF THE INTERWORKING REPORT ............................................................................. 9
3 LIMITS OF THE TECHNICAL SUPPORT ....................................................................................... 10
3.1 CASE OF ADDITIONAL THIRD PARTY APPLICATIONS ........................................................................... 10
4 APPLICATION INFORMATION .......................................................................................................... 11
5 TEST ENVIRONMENT .......................................................................................................................... 13
5.1 HARDWARE CONFIGURATION ............................................................................................................ 14
5.2 SOFTWARE CONFIGURATION .............................................................................................................. 14
6 SUMMARY OF TEST RESULTS ........................................................................................................ 15
6.1 SUMMARY OF MAIN FUNCTIONS SUPPORTED ...................................................................................... 15
6.2 SUMMARY OF PROBLEMS ................................................................................................................... 16
6.3 SUMMARY OF LIMITATIONS ............................................................................................................... 16
6.4 NOTES, REMARKS .............................................................................................................................. 16
7 TEST RESULT TEMPLATE ................................................................................................................ 17
8 TESTS RESULTS FOR IP DR LINK RECORDING ......................................................................... 18
8.1 INBOUND CALLS................................................................................................................................. 18
8.1.1 Test Objectives .......................................................................................................................... 18
8.1.2 Test Results ............................................................................................................................... 18
8.2 INTERNAL CALLS ............................................................................................................................... 19
8.2.1 Test Objectives .......................................................................................................................... 19
8.2.2 Test Results ............................................................................................................................... 19
8.3 OUTBOUND CALLS ............................................................................................................................. 20
8.3.1 Test Objectives .......................................................................................................................... 20
8.3.2 Test Results ............................................................................................................................... 20
8.4 TRANSFER OF AN INBOUND CALL – BLIND TRANSFER........................................................................ 21
8.4.1 Test Objectives .......................................................................................................................... 21
8.4.2 Test Results ............................................................................................................................... 21
8.5 TRANSFER OF AN INBOUND CALL – SUPERVISED TRANSFER .............................................................. 22
8.5.1 Test Objectives .......................................................................................................................... 22
8.5.2 Test Results ............................................................................................................................... 22
Supervised Transfer : The calling number in the supervised transferred record is the user which makes
the enquiry call ( and not the caller of the 1st call ). ................................................................................. 22
8.6 TRANSFER OF AN OUTBOUND CALL – BLIND TRANSFER .................................................................... 23
8.6.1 Test Objectives .......................................................................................................................... 23
8.6.2 Test Results ............................................................................................................................... 23
8.7 TRANSFER OF AN OUTBOUND CALL – SUPERVISED TRANSFER ........................................................... 24
8.7.1 Test Objectives .......................................................................................................................... 24
8.7.2 Test Results ............................................................................................................................... 24
Supervised Transfer : The calling number in the supervised transferred record is the user which makes
the enquiry call ( and not the caller of the 1st call ). ................................................................................. 24
8.8 3 WAY INBOUND CONFERENCE CALL ................................................................................................ 25
8.8.1 Test Objectives .......................................................................................................................... 25
8.8.2 Test Results ............................................................................................................................... 25
8.9 3 WAY INBOUND CONFERENCE CALL – THE THIRD PARTY DROPS OUT FIRST .................................... 26
8.9.1 Test Objectives .......................................................................................................................... 26
8.9.2 Test Results ............................................................................................................................... 26
8.10 3 WAY INBOUND CONFERENCE CALL – THE CONFERENCER DROPS OUT FIRST & SECOND AGENT NOT
RECORDED ..................................................................................................................................................... 27
8.10.1 Test Objectives .......................................................................................................................... 27

8.10.2 Test Results ............................................................................................................................... 27
8.11 3 WAY OUTBOUND CONFERENCE CALL ............................................................................................ 28
8.11.1 Test Objectives .......................................................................................................................... 28
8.11.2 Test Results ............................................................................................................................... 28
8.12 3 WAY OUTBOUND CONFERENCE CALL – THE THIRD PARTY DROPS OUT FIRST................................. 29
8.12.1 Test Objectives .......................................................................................................................... 29
8.12.2 Test Results ............................................................................................................................... 29
8.13 3 WAY OUTBOUND CONFERENCE CALL – THE CONFERENCER DROPS OUT FIRST & SECOND AGENT
NOT RECORDED .............................................................................................................................................. 30
8.13.1 Test Objectives .......................................................................................................................... 30
8.13.2 Test Results ............................................................................................................................... 30
8.14 CONTACT CENTER : SUPERVISED CALLS : NORMAL LISTENING.......................................................... 31
8.14.1 Test Objectives .......................................................................................................................... 31
8.14.2 Test Results ............................................................................................................................... 31
8.15 CONTACT CENTER : SUPERVISED CALLS : RESTRICTED INTRUSION.................................................... 32
8.15.1 Test Objectives .......................................................................................................................... 32
8.15.2 Test Results ............................................................................................................................... 32
8.16 CONTACT CENTER : SUPERVISED CALLS : INTRUSION........................................................................ 33
8.16.1 Test Objectives .......................................................................................................................... 33
8.16.2 Test Results ............................................................................................................................... 33
8.17 CONTACT CENTER : SUPERVISED CALLS : HELP ................................................................................. 34
8.17.1 Test Objectives .......................................................................................................................... 34
8.17.2 Test Results ............................................................................................................................... 34
8.18 CONTACT CENTER : INCOMING PRIVATE CALLS ................................................................................ 35
8.18.1 Test Objectives .......................................................................................................................... 35
8.18.2 Test Results ............................................................................................................................... 35
8.19 CONTACT CENTER : OUTGOING PRIVATE CALLS ............................................................................... 36
8.19.1 Test Objectives .......................................................................................................................... 36
8.19.2 Test Results ............................................................................................................................... 36
8.20 CONTACT CENTER : AGENT WELCOME GUIDE ................................................................................... 37
8.20.1 Test Objectives .......................................................................................................................... 37
8.20.2 Test Results : ............................................................................................................................. 37
8.21 CONTACT CENTER : FREE SEATING ................................................................................................... 38
8.21.1 Test Objectives .......................................................................................................................... 38
8.21.2 Test Results : ............................................................................................................................. 38
8.22 BUSINESS SETS : MULTILINE SETS ..................................................................................................... 39
8.22.1 Test Objectives .......................................................................................................................... 39
8.22.2 Test Results : Record lines with the same number .................................................................... 39
8.22.3 Test procedure: Record lines with several numbers ................................................................. 40
8.22.4 Test procedure: Not record several lines ( inbound calls ) ....................................................... 41
8.23 BUSINESS SETS : MLA FEATURE – SECONDARY MLA SET ANSWERS ................................................ 42
8.23.1 Test Objectives .......................................................................................................................... 42
8.23.2 Test Results : ............................................................................................................................. 42
8.24 BUSINESS SETS : MLA FEATURE – SWAPPING BETWEEN 2 PRIMARY MLA LINES ............................. 43
8.24.1 Test Objectives .......................................................................................................................... 43
8.24.2 Test Results : ............................................................................................................................. 43
8.25 BUSINESS SETS : MLA FEATURE – SWAPPING BETWEEN PRIMARY AND SECONDARY MLA LINES .... 44
8.25.1 Test Objectives .......................................................................................................................... 44
8.25.2 Test Results : ............................................................................................................................. 44
8.26 BUSINESS SETS : TANDEM ................................................................................................................. 45
8.26.1 Test Objectives .......................................................................................................................... 45
8.26.2 Test Results : Inbound call to Main set ..................................................................................... 45
8.26.3 Test Results : Outbound call from the Main set ........................................................................ 45
8.26.4 Test Results : Inbound call to Secondary set ............................................................................. 46
8.26.5 Test Results : Outbound call from the Secondary set ................................................................ 46
8.27 BEEP GENERATION – SINGLE BEEP .................................................................................................... 47
8.27.1 Test Objectives .......................................................................................................................... 47
8.27.2 Test Results : ............................................................................................................................. 47
8.28 BEEP GENERATION – SEVERAL BEEPS ............................................................................................... 47
8.28.1 Test Objectives .......................................................................................................................... 47
8.28.2 Test Results : ............................................................................................................................. 47

8.29 COMPRESSION TYPE TESTS ................................................................................................................. 48
8.29.1 Test objectives ........................................................................................................................... 48
8.29.2 Test results ................................................................................................................................ 48
9 NETWORK IP DR LINK RECORDING TESTS ................................................................................ 49
9.1 SIMPLE CALLS .................................................................................................................................... 49
9.1.1 Test Objectives .......................................................................................................................... 49
9.1.2 Test Results ............................................................................................................................... 49
9.2 TRANSFER OF AN INBOUND CALL FROM LOCAL TO REMOTE – BLIND TRANSFER ............................... 50
9.2.1 Test Objectives .......................................................................................................................... 50
9.2.2 Test Results ............................................................................................................................... 50
9.3 TRANSFER OF AN INBOUND CALL FROM REMOTE TO LOCAL – BLIND TRANSFER ............................... 51
9.3.1 Test Objectives .......................................................................................................................... 51
9.3.2 Test Results ............................................................................................................................... 51
9.4 TRANSFER OF AN INBOUND CALL BETWEEN 2 NODES – BLIND TRANSFER .......................................... 52
9.4.1 Test Objectives .......................................................................................................................... 52
9.4.2 Test Results ............................................................................................................................... 52
9.5 TRANSFER OF AN INBOUND CALL FROM LOCAL TO REMOTE – SUPERVISED TRANSFER ..................... 53
9.5.1 Test Objectives .......................................................................................................................... 53
9.5.2 Test Results ............................................................................................................................... 53
9.6 TRANSFER OF AN INBOUND CALL FROM REMOTE TO LOCAL – SUPERVISED TRANSFER ..................... 54
9.6.1 Test Objectives .......................................................................................................................... 54
9.6.2 Test Results ............................................................................................................................... 54
9.7 TRANSFER OF AN INBOUND CALL BETWEEN 2 NODES – SUPERVISED TRANSFER ................................ 55
9.7.1 Test Objectives .......................................................................................................................... 55
9.7.2 Test Results ............................................................................................................................... 55
9.8 TRANSFER OF AN OUTBOUND CALL FROM LOCAL TO REMOTE – BLIND TRANSFER ............................ 56
9.8.1 Test Objectives .......................................................................................................................... 56
9.8.2 Test Results ............................................................................................................................... 56
9.9 TRANSFER OF AN OUTBOUND CALL FROM REMOTE TO LOCAL – BLIND TRANSFER ............................ 57
9.9.1 Test Objectives .......................................................................................................................... 57
9.9.2 Test Results ............................................................................................................................... 57
9.10 TRANSFER OF AN OUTBOUND CALL BETWEEN 2 NODES – BLIND TRANSFER ....................................... 58
9.10.1 Test Objectives .......................................................................................................................... 58
9.10.2 Test Results ............................................................................................................................... 58
9.11 TRANSFER OF AN OUTBOUND CALL FROM LOCAL TO REMOTE – SUPERVISED TRANSFER .................. 59
9.11.1 Test Objectives .......................................................................................................................... 59
9.11.2 Test Results ............................................................................................................................... 59
9.12 TRANSFER OF AN OUTBOUND CALL FROM REMOTE TO LOCAL – SUPERVISED TRANSFER .................. 60
9.12.1 Test Objectives .......................................................................................................................... 60
9.12.2 Test Results ............................................................................................................................... 60
9.13 TRANSFER OF AN OUTBOUND CALL BETWEEN 2 NODES – SUPERVISED TRANSFER ............................. 61
9.13.1 Test Objectives .......................................................................................................................... 61
9.13.2 Test Results ............................................................................................................................... 61
9.14 3 WAY INBOUND CONFERENCE CALL – STARTING FROM LOCAL TO REMOTE................................... 62
9.14.1 Test Objectives .......................................................................................................................... 62
9.14.2 Test Results ............................................................................................................................... 62
9.15 3 WAY INBOUND CONFERENCE CALL – STARTING FROM REMOTE TO LOCAL................................... 63
9.15.1 Test Objectives .......................................................................................................................... 63
9.15.2 Test Results ............................................................................................................................... 63
9.16 3 WAY OUTBOUND CONFERENCE CALL – STARTING FROM LOCAL TO REMOTE ............................... 64
9.16.1 Test Objectives .......................................................................................................................... 64
9.16.2 Test Results ............................................................................................................................... 64
9.17 3 WAY OUTBOUND CONFERENCE CALL – STARTING FROM REMOTE TO LOCAL ............................... 65
9.17.1 Test Objectives .......................................................................................................................... 65
9.17.2 Test Results ............................................................................................................................... 65
10 RELIABILITY TESTS ........................................................................................................................ 66
10.1 FAILURE TESTS .................................................................................................................................. 66
10.1.1 Test Objectives .......................................................................................................................... 66
10.1.2 Test Results : IP DR-Link : Bad devices .................................................................................. 66

10.1.3 Test Results : DR-Link & IP DR-Link : Not authorized recording ........................................... 67
10.1.4 Test Results : IP DR-Link : No Recording when the parameter “DR-Link on IP supported” =
FALSE 68
10.1.5 Test Results : DR-Link & IP DR-Link : License not available.................................................. 69
10.1.6 Test Results : DR-Link & IP DR-Link : Max Licenses reached ................................................ 70
10.2 SWITCH FAILURE ............................................................................................................................... 71
10.2.1 Test Objectives .......................................................................................................................... 71
10.2.2 Test Results ............................................................................................................................... 71
10.3 CTI LINK FAILURE - OTS SERVICE FAILURE ..................................................................................... 73
10.3.1 Test Objectives .......................................................................................................................... 73
10.3.2 Test Results : IP DR-Link.......................................................................................................... 73
10.4 REDUNDANCY TESTS ( ALCATEL-LUCENT SIDE ) ............................................................................... 75
10.4.1 Test Objectives .......................................................................................................................... 75
10.4.2 Test Results : OXE in Spatial Redundancy .............................................................................. 75
10.4.3 Test Results : TSAPI Backup .................................................................................................... 77
10.5 PASSIVE CALL SERVER ...................................................................................................................... 79
The test environment :............................................................................................................................... 79
10.5.1 Test Objectives .......................................................................................................................... 80
10.5.2 Test Results : IP DR-Link.......................................................................................................... 80
10.6 UNDERSTANDING OF THE LOGS FILES ................................................................................................ 81
10.6.1 Test Objectives .......................................................................................................................... 81
10.6.2 Test Results ............................................................................................................................... 81
10.7 NOTIFICATIONS & ALARMS ................................................................................................................ 81
10.7.1 Test Objectives .......................................................................................................................... 81
10.7.2 Test Results ............................................................................................................................... 81
11 CTI PARAMETERS ........................................................................................................................... 82
12 APPENDIX B: PARTNER APPLICATION: CONFIGURATION REQUIREMENTS ............. 83
13 APPENDIX C: ALCATEL-LUCENT COMMUNICATION PLATFORM: CONFIGURATION
REQUIREMENTS.......................................................................................................................................... 86
13.1 CONFIGURATION FOR IP DR-LINK ..................................................................................................... 86
13.1.1 CSTA parameters ...................................................................................................................... 86
13.1.2 Phone Facilities Categories parameter .................................................................................... 87
13.1.3 Recording IP Logger................................................................................................................. 87
13.1.4 Quality of service for IP recording parameter (IP / IP Domain) .............................................. 88
13.1.5 IP DR-Link licenses .................................................................................................................. 88
13.2 ADDITIONAL PARAMETER FOR DR-LINK & IP DR-LINK: .................................................................. 88
14 APPENDIX D: PARTNER ESCALATION PROCESS .................................................................. 89
14.1 HEADQUARTER .................................................................................................................................. 89
14.2 GERMAN BRANCH .............................................................................................................................. 89
15 APPENDIX E: AAPP PROGRAM ................................................................................................... 90
15.1 ALCATEL-LUCENT APPLICATION PARTNER PROGRAM (AAPP)......................................................... 90
15.2 ALCATEL-LUCENT.COM ..................................................................................................................... 91
16 APPENDIX F: AAPP ESCALATION PROCESS ........................................................................... 92
16.1 INTRODUCTION .................................................................................................................................. 92
16.2 ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ............................................................. 93
16.3 ESCALATION IN ALL OTHER CASES ..................................................................................................... 94
16.4 TECHNICAL SUPPORT ACCESS ............................................................................................................ 95

1 Introduction
This document is the result of the certification tests performed between the AAPP member’s
application and Alcatel-Lucent’s platform.
It certifies proper inter-working with the AAPP member’s application.
Information contained in this document is believed to be accurate and reliable at the time of printing.
However, due to ongoing product improvements and revisions, Alcatel-Lucent cannot guarantee
accuracy of printed material after the date of certification nor can it accept responsibility for errors or
omissions.
Updates to this document can be viewed on:
- the Technical Support page of the Enterprise Business Portal

(https://businessportal.alcatel-lucent.com) in the Application Partner Interworking Reports
corner (restricted to Business Partners)
- the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free

access.
These tests do not verify the functional achievement of the application as well as they do not
cover load capacity checks, race conditions and generally speaking any real customer's site
conditions.
The first installations are used to complete those tests performed in labs with real customer
conditions (Beta Test process) The Application Partner is invited to inform Alcatel-Lucent
about the results of those fist installations.
Interworking Certification labels:
“Sampling” calls can fit with Quality Management in Contact Center, to record some calls.
Installation, error handling and traces are checked for the Alcatel-Lucent interface. In addition to the
previous requirements,
“Total” means the capability to record all types of calls, for all types of telephone devices, for Contact
Center and Business environments and using all CSTA data. Each of those recording levels can run for the
different types of connection. The Alcatel-Lucent Dedicated Recording Link can be used for a “Stand alone”
site only or for “Networked” in distributed multi-site environment.
2. In addition to the “Sampling” capabilities, “Total” means the call types, for all telephone devices,
within both Contact Center and Business environments, and using all CSTA data.

2 Validity of the InterWorking Report
This InterWorking report specifies the products and releases which have been certified.
This inter-working report is valid unless specified until the AAPP member issues a new major
release of such product (incorporating new features or functionalities), or until Alcatel-Lucent
issues a new major release of such Alcatel-Lucent product (incorporating new features or
functionalities), whichever first occurs.
A new release is identified as following:

 a Major Release” is any x. enumerated release. Example Product 1.0 is a major product
release.
 a “Minor Release” is any x.y enumerated release. Example Product 1.1 is a minor product
release
The validity of the InterWorking report can be extended to upper major releases, if for example the
interface didn’t evolve, or to other products of the same family range. Please refer to the “IWR
validity extension” chapter at the beginning of the report.
Note: The InterWorking report becomes automatically obsolete when the mentioned product
releases are end of life.

3 Limits of the Technical support
Technical support will be provided only in case of a valid InterWorking Report (see chapter 2
“Validity of the InterWorking Report) and in the scope of the features which have been certified.
That scope is defined by the InterWorking report via the tests cases which have been performed,
the conditions and the perimeter of the testing as well as the observed limitations. All this being
documented in the IWR. The certification does not verify the functional achievement of the AAPP
member’s application as well as it does not cover load capacity checks, race conditions and
generally speaking any real customer's site conditions.
Any possible issue will require first to be addressed and analyzed by the AAPP member before
being escalated to Alcatel-Lucent.
For any request outside the scope of this IWR, Alcatel-Lucent offers the “On Demand Diagnostic”
service where assistance will be provided against payment.
For more details, please refer to Appendix F “AAPP Escalation Process”.
3.1 Case of additional Third party applications

In case at a customer site an additional third party application NOT provided by Alcatel-Lucent is
included in the solution between the certified Alcatel-Lucent and AAPP member products such as a
Session Border Controller or a firewall for example, Alcatel-Lucent will consider that situation as to
that where no IWR exists. Alcatel-Lucent will handle this situation accordingly (for more details,
please refer to Appendix F “AAPP Escalation Process”).

4 Application information
Application family : Voice Recording Systems
Application commercial name: VoiceCollect MDx
Application version: v11
Interface type: TSAPI Premium Server
Interface version (if relevant): 7.0.5
Voice logger Features available Features tested in this report

from the recorder side (Supported by Alcatel-Lucent
Technical Support)
Extension side recording No No
Trunk side recording Yes ( without CSTA ) No
DR-Link recording :
- Static mode in DR-Link * No No
- Dynamic mode in DR-Link * Yes No
IP DR-Link recording :
- Static mode in IP DR-link * No No
- Dynamic mode in IP DR-Link * Yes Yes
Remote DR-Link recording * Yes No

IP DR-link Network recording * Yes Yes
Mixed recording * No No
IP sniffing Yes No
Free seating Yes Yes

Selective recording No No
CCD calls Yes Yes
Business calls Yes Yes
Static Mode : The Voice Recording System sends a unique start recording request to the
OmniPCXEnterprise for each recorded user at the CSTA connection.
Dynamic Mode : The Voice Recording System sends a start recording request to the
OmniPCXEnterprise for each conversation of each recorded user.

 TDM DR Link Recording using the Alcatel-Lucent OmniPCX Enterprise and TSAPI. The
Voice TDM logger is connected to PCM2 board on Alcatel-Lucent OmniPCX Enterprise.
 Remote TDM DR Link Recording : The OmniPCX Enterprise(s) are connected with ABC-
F link to central OmniPCX Enterprise. The Active TDM logger is connected to the central
node.
 IP DR-Link Recording using the Alcatel-Lucent OmniPCX Enterprise and TSAPI. The
VoIP-logger is connected directly to Network of the handsets.
 IP DR-Link Network Recording : The OmniPCX Enterprise(s) are connected with ABC-F
link to central OmniPCX Enterprise. The VoIP-logger is connected directly to the central
node.
 Mixed Recording ( Recording between TDM & IP sets ) : selection of the used voice
logger ( DR-link logger or IP DR-link logger )
 Trunk Recording using the Alcatel-Lucent OmniPCX Enterprise and TSAPI. This method
tests Total recording in the Voice Recording Server. The Voice logger is connected on
Alcatel OXE with E1, T2 or T0 trunk.
 Extension Side Recording using the Alcatel-Lucent OmniPCX Enterprise and TSAPI. This
method tests Total recording. Loggers record directly from extensions and are configured to
receive direct parallel inputs to the extensions.

5 Test environment
Tests Configuration :
DATA CENTER 1 DATA CENTER 2
Call Server 1
( Active )
Call Server 2
Primary Link ( Stand By )
Secondary Link
ARMS TSAPI TSAPI

BACKUP
172.27.144.X
Mask : 255.255.255.0 172.27.145.X
Mask : 255.255.255.0
WAN
DOMAIN 0 DOMAIN 1
192.168.6.X 192.168.4.X
Mask : 255.255.255.0 Mask : 255.255.255.0
GA GD
GA GD
T2 T2
T2 T2
PCM-R2
IP Phone
IP Phone
IP Phone
IP Phone

5.1 Hardware configuration
 OmniPCX Entreprise: Appliance servers, T2 and PCM interfaces, UA and Z interfaces,

IP phones, Digital & analog sets
o CS (Call Server Processing Unit)
o GD
o GA
o PCM2 ( MG IVR-Z30 )
o PRA T2 (ISDN Access)
o MIX 2/4/4 (Digital & analog interfaces)
o UA digital and analog sets
o IP Phones
 Phones sets :
o Agents ( TDM sets ) in principal node : A, B, C
o Agents ( IP Phones sets ) in principal node : V1, V2, V3
o Business sets in principal node : M, N
o Agents ( TDM sets ) in remote node : RA, RB, RC
o Agents ( IP Phones sets ) in remote node : RV1, RV2, RV3
 VRS interface:
5.2 Software configuration
 Alcatel Communication Platform: OmniPCX Enterprise R11

 TSAPI Premium Server : 7.0.5
 Partner Application : VC-MDx v11 VDS-II

6 Summary of test results
6.1 Summary of main functions supported
Networking
IP DR-Link
Recording
IP DRLink
Sampling
Total
Features Comments
Basic calls:
Inbound calls OK OK  
Outbound Calls OK OK  
Internal calls OK OK  
Transfer OK OK  
3 Way Conference Call OK OK  
Contact Center :
Supervised Calls NOK   See limitations
Private incoming calls OK 
Private outgoing calls NOK Feature Not Supported

Free seating OK  
Business sets :
Multi lines set NOK   Feature Not Supported
MLA sets NOK  Feature Not Supported
Tandem OK
Codecs : NOK   Feature NOK with G729

Beep generation NOK   Feature Not Supported
Reliability
Basic failure OK  
OXE failure OK  
CTI link failure OK  
Redundancy Tests
Spatial redundancy of the OXE OK 
TSAPI backup OK 
Passive Call Server NOK  Feature Not Supported

6.2 Summary of problems
None
6.3 Summary of limitations
 CCD / Supervisor Calls feature: The voice recording system has no flag which allows to
differentiate a supervisor listening to a supervisor intrusion. So the voice recording system
records a supervisor listening. In CSTA terms, the VRS doesn’t take into account the flag “
silent” or “active” monitor in the Conferenced CSTA event.
 CCD / Private Outgoing calls : Feature not supported
 Multi-lines / MLA sets: Feature not supported.
 Codecs: Feature NOK with G729.
 Beep generation : Feature not supported.
 Passive Call Server : Feature not supported
6.4 Notes, remarks


rd
Conference : The 3 party of the conference is not seen in the records.
 Supervised Transfer : The calling number in the supervised transferred record is the user
st
which makes the enquiry call ( it should be the caller of the 1 call ).
For instance :
1- External caller is in conversation with user A
2- User A makes an enquiry call with user B
3- User A transfers the call
4- User B is in conversation with the external caller
In the record of user B in step 4, the caller is user A ( it should be the external caller )
 Tandem : For the outbound call of the secondary set, the direction in the record is
“incoming” ( it should be outgoing )

7 Test Result Template
The results are presented as indicated in the example below:
Test
Case Test Case N/A OK NOK Comment
Id
Test case 1
 Action
1
 Expected result
Test case 2
The application waits
 Action
2 for PBX timer or
 Expected result
phone set hangs up
Test case 3
Relevant only if the
 Action
3 CTI interface is a
 Expected result
direct CSTA link
Test case 4
 Action No indication, no error
4
 Expected result message
… …
Test Case Id: a feature testing may comprise multiple steps depending on its complexity. Each step
has to be completed successfully in order to conform to the test.
Test Case: describes the test case with the detail of the main steps to be executed the and the
expected result
N/A: when checked, means the test case is not applicable in the scope of the application
OK: when checked, means the test case performs as expected
NOK: when checked, means the test case has failed. In that case, describe in the field “Comment”
the reason for the failure and the reference number of the issue either on Alcatel-Lucent side or on
Application Partner side
Comment: to be filled in with any relevant comment. Mandatory in case a test has failed especially
the reference number of the issue.

8 Tests Results for IP DR Link Recording
8.1 Inbound calls
8.1.1 Test Objectives

This test checks that VRS is able to record inbound calls. In addition, the call-details retrieved from
the CSTA link should be inserted to the VRS calls database. Then, using the Query application, it
should be possible to playback the audio of this call.
8.1.2 Test Results
Test
Id
Inbound call
 Make a PSTN inbound call to Agent V1
1
 Agent V1 answers the call and speaks for at least
10 seconds before hanging-up.
New inbound call
 Make an inbound call to Agent V2 ( call is routed
2 through pilot distribution ).
Check the records in the VRS
 In the VRS application, playback the above
3
conversations

8.2 Internal calls
This test checks that VRS is able to record internal calls. In addition, the call-details retrieved from
the CSTA link should be inserted to the VRS calls database. Then, using the Query application, it
should be possible to playback the audio of this call.
8.2.2 Test Results
Test
Id
Internal call
 Make an internal call from Agent V1 to Agent V2
1
New internal call
 Make an internal call from Agent V1 to Agent V2 (
2 call is routed through pilot distribution ).
3  In the VRS application, check the records

8.3 Outbound calls
This test checks that VRS is able to record outbound calls . In addition, the call-details retrieved
from the CSTA link should be inserted to the VRS calls database. Then, using the Query
application, it should be possible to playback the audio of this call.
8.3.2 Test Results
Test
Id
Outbound call
 Make a PSTN outbound call from Agent V1
1  The external party answers the call and speaks
for at least 10 seconds before hanging-up.


8.4 Transfer of an inbound call – Blind Transfer
This test checks that VRS is able to record blind transferred calls for inbound calls . In addition, the
call-details retrieved from the CSTA link should be inserted to the VRS calls database. Then, using
the Query application, it should be possible to playback the audio of this call.
8.4.2 Test Results
Test
Id
Inbound call
 Make an inbound call to Agent V1
1
10 seconds.
Enquiry and transfer
 Agent V1 makes an internal call to Agent V2 ( the
2 inbound call is automatically put on hold )
 Agent V1 transfers the inbound held call to Agent
V2
Transferred call
3  Agent V2 answers the call and speaks for at least
10 seconds before hanging-up

8.5 Transfer of an inbound call – Supervised Transfer
This test checks that VRS is able to record supervised transferred calls for inbound calls . In
addition, the call-details retrieved from the CSTA link should be inserted to the VRS calls database.
Then, using the Query application, it should be possible to playback the audio of this call.
8.5.2 Test Results
Test
Id
Inbound call
1
10 seconds.
Enquiry call
2
inbound call is automatically put on hold )
 Agent V1 and Agent V2 are in conversation
Transfer
3  Agent V1 transfers the inbound held call to Agent
V2
Transferred call
4  Agent V2 and the external party speak at least
during 10 seconds before hanging-up
Supervised Transfer : The calling number in the supervised transferred record is the user which
st
makes the enquiry call ( and not the caller of the 1 call ).
For instance :

8.6 Transfer of an outbound call – Blind Transfer
This test checks that VRS is able to record blind transferred calls for outbound calls . In addition, the
call-details retrieved from the CSTA link should be inserted to the VRS calls database. Then, using
the Query application, it should be possible to playback the audio of this call.
8.6.2 Test Results
Test
Id
Outbound call
 Make an outbound call from Agent V1
1
 The external party answers the call and speaks
for at least 10 seconds.
Enquiry and transfer
2 outbound call is automatically put on hold )
 Agent V1 transfers the outbound held call to
Agent V2
Transferred call

8.7 Transfer of an outbound call – Supervised Transfer
This test checks that VRS is able to record supervised transferred calls for outbound calls . In
8.7.2 Test Results
Test
Id
Outbound call
1
Enquiry call
2
outbound call is automatically put on hold )
Transfer
3  Agent V1 transfers the outbound held call to
Agent V2
Transferred call
4  Agent V2 and the external party speak at least
during 10 seconds before hanging-up
Supervised Transfer : The calling number in the supervised transferred record is the user which
st
makes the enquiry call ( and not the caller of the 1 call ).
For instance :

8.8 3 Way Inbound Conference Call
This test checks that VRS is able to record conference calls for inbound calls. In addition, the call-
details retrieved from the CSTA link should be inserted to the VRS calls database. Then, using the
Query application, it should be possible to playback the audio of this call.
8.8.2 Test Results
Test
Id
Inbound call
1
10 seconds.
Enquiry call
2
Conference
3  Agent V1 conferences the inbound held call with
Agent V2
Conferenced call
4  Agent V1 & V2 and the external party speak at
least during 10 seconds
The conferencer drops out
 Agent V1 hangs up
5
 Agent V2 and the external party speak at least
during 10 seconds before hanging up
The 3rd party of the conference is not seen in the records

8.9 3 Way Inbound Conference Call – The third party drops out first
8.9.2 Test Results
Test
Id
Inbound call
1
10 seconds.
Enquiry call
2
Conference
Agent V2
Conferenced call
The third party drops out
5

8.10 3 Way Inbound Conference Call – The conferencer drops out first
& second agent not recorded
8.10.2 Test Results
Test
Id
Agent B not monitored
1
 Check that the agent V2 is not monitored
Inbound call
2
10 seconds.
Enquiry call
3
Conference
Agent V2
Conferenced call
6

8.11 3 Way Outbound Conference Call
This test checks that VRS is able to record conference calls for outbound calls. In addition, the call-
8.11.2 Test Results
Test
Id
Outbound call
1
Enquiry call
2
Conference
3  Agent V1 conferences the outbound held call with
Agent V2
Conferenced call
5

8.12 3 Way Outbound Conference Call – The third party drops out first
8.12.2 Test Results
Test
Id
Outbound call
 Make an outbound call to Agent V1
1
10 seconds.
Enquiry call
2
Conference
Agent V2
Conferenced call
The third party drops out
5

8.13 3 Way Outbound Conference Call – The conferencer drops out
first & second agent not recorded
8.13.2 Test Results
Test
Id
Agent B not monitored
1
 Check that the agent V2 is not monitored
Outbound call
 Make an outbound call to Agent V1
2
10 seconds.
Enquiry call
3
Conference
Agent V2
Conferenced call
6

8.14 Contact Center : Supervised Calls : normal listening
General remark regarding the supervised calls :
The supervisor can use ACD listening in permanently or dynamically ways.
The following supervision scenarios are examined :

 Normal listening ( the supervisor listens the conversation between the agent and the
“customer” )
 Restricted Intrusion ( the supervisor can speak to the agent but the “customer” doesn’t
hear the supervisor )
 Intrusion ( the supervisor, the agent & the “customer” are in conference )
 Help of Supervisor ( the agent asks help to the supervisor )
Specific configuration on the PBX :

 Create an agent with supervisor function :
o User/ACD station = Supervisor
o User/Prog keys --> key Number ( 1 for instance ) / function = ACD listening
 Affect the agent to a processing group :
o Application/CCD/Operators /Operators data management/attaching list ---> Affect
the agent to the processing group number.
 Log on the supervisor agent on a Pro-ACD set . The « supervision » tests can be done.
This test checks that VRS is able to record supervised calls. In addition, the call-details retrieved
8.14.2 Test Results
Test
Id
Normal listening
1  A supervisor makes normal listening on Agent V1
in permanent mode.
Inbound call
through a distribution pilot ).
2
 Agent V1 answers the call
 Agent V1 and the external caller speak during at
least 10 second before hanging up
Check the Agent’s record in the VRS
There is a record for the supervisor.
The voice recording system has no flag which allows to differentiate a supervisor listening to a
supervisor intrusion. So the voice recording system records a supervisor listening. In CSTA terms,
the VRS doesn’t take into account the flag “silent” or “active” monitor in the Conferenced CSTA
event.

8.15 Contact Center : Supervised Calls : restricted intrusion
8.15.2 Test Results
Test
Id
Inbound call
1
least 10 second
Restricted intrusion
2  A supervisor makes restricted intrusion on the
agent V1 during the conversation
End of Agent’s call
3
 The Agent V1 releases the call

8.16 Contact Center : Supervised Calls : intrusion
8.16.2 Test Results
Test
Id
Inbound call
1
least 10 second
Intrusion
2  A supervisor makes intrusion on the agent V1
during the conversation
3

8.17 Contact Center : Supervised Calls : help
8.17.2 Test Results
Test
Id
Inbound call
1
least 10 second
Help
2
 The agent presses “help”
Restrictive intrusion of the supervisor
3  The supervisor makes now a restrictive intrusion
during the conversation of the agent V1
4

8.18 Contact Center : Incoming Private Calls
This test checks that VRS is able to selectively not record incoming private calls.
Note: To manage private incoming calls, set the parameter: Application / CCD / CCD users / agent
xxxx / Private agent number
8.18.2 Test Results
Test
Id
Inbound call
 Make an inbound call to the private Agent’s
extension V1.
1
least 10 second
2  In the VRS application, check there is no record
Creation of a rule in the VRS to not record the private agent number

8.19 Contact Center : Outgoing Private Calls
The aim of these test is to not record private calls from the agent.
To manage private outgoing calls, set the parameters: Application / CCD / Processing Group /
Outgoing ACD call = False
Note : in withdraw state, the agent makes automatically outgoing private call when he makes
outbound calls.
Note : The “AGENT BUSY” CSTA event ( after the ESTABLISHED event ) is not present for a
private outgoing call
This test checks that VRS is able to selectively not record outgoing private calls.
8.19.2 Test Results
Test
Id
Agent’s state
1
 Check that the agent V1 is in idle state
Outbound call
 Make an outbound call from the Agent V1
2  The external party answers the call
least 10 second
Feature Not
3  In the VRS application, check there is no record
Supported

8.20 Contact Center : Agent Welcome guide
This test is intended to see the behaviour of the Voice Recording System when there is an inbound
call to an agent ( from a pilot distribution ) which has an agent welcome guide. In addition, the call-
The management of an Agent Welcome Guide is below:

 Management of this voice guide :
a. Under mgr--> System --> Dynamic voice guides --> Assignment : Create
 Sub-message number = 4500 ( 4500 is the first sub-message
number used for the agent welcome guide )
 ACT-Coupler : Address of one GD board in common hardware (
GPA2 board in crystal hardware )
b. Assign this voice guide to the agent :

 Mgr --> Applications --> CCD ---> Operators ---> For the agent :
a. Presentation mess. Nb = 4500
b. Presentation mess. File Nb = 1
 With the phone set of the agent :

a. Login the agent
b. Press the “welcome guide” button
c. Record the welcome guide
d. Download this recorded welcome guide
e. Activate this welcome guide
8.20.2 Test Results :
Test
Test Case N/A OK NOK Comment
Case Id
Management of an agent presentation guide
 Login the agent V1 on the proacd P1
1  Make an inbound call to the agent V1 ( from a pilot
distribution )
 Logout the agent V1
Inbound call
 Make an inbound call to the agent V1 ( from a pilot
distribution )
2
 The agent V1 answers the inbound call
 The agent V1 & the external party speak for at least
10 seconds before hanging up.
Check the record in the VRS
3  In the VRS application, check the record
The record ( CSTA + audio ) begins at the “Retrieved” CSTA event.

8.21 Contact Center : Free Seating
This test checks that VRS is able to take into account free seating system. The agents will log on
several stations and the system should be able to selectively recording calls. In addition, the call-
Test
Case Id
Agent V1 on proacd P1
distribution )
Agent V1 on proacd P2
distribution )

8.22 Business Sets : Multiline sets
This test checks that VRS is able to record several calls on the same set. In addition, the call-details
retrieved from the CSTA link should be inserted to the VRS calls database. Then, using the Query
Note:
Several scenarios are possible according to the type of multi-line configuration:

* The multi line set has several lines on the same number
* The multi line set has several lines with several numbers
8.22.2 Test Results : Record lines with the same number
Test
Id
Several lines with the same number
1  Create 2 multiline keys with the same number (
the number = the phone set M )
st
Inbound call : 1 call

st
Make an inbound call to the 1 multiline key
2  M answers the call
 M and the external caller speak during at least 10
seconds
nd
New Inbound call : 2 call

nd

st
M puts on Hold the 1 call

nd
3 M answers the 2 call
seconds

nd
M hangs up the 2 call
st
Retrieve the 1 call

st st
M retrieves the 1 call on the 1 multiline key
4  M and the external party speak during at least 10
seconds
 M hangs up the call
Feature Not
Supported

8.22.3 Test procedure: Record lines with several numbers
Test
Id
Several lines with several numbers
1  Create 2 multiline keys with 2 numbers (numbers
are different from the phone set number)
st

st
seconds
nd
Outbound call : 2 call

st
M puts on Hold the 1 call

nd
Make an outbound call from the 2 multiline key
3  The external caller answers the call
seconds

nd
st
Retrieve the 1 call

st st
seconds
5  In the VRS application, check the records Feature not supported

8.22.4 Test procedure: Not record several lines ( inbound calls )
Test
Id
Several lines with several numbers
1  Create 2 multiline keys with 2 numbers (numbers
are different from the phone set number)
Rule to not record these lines
2  Create a rule in the VRS to not record these 2
numbers
st

st
seconds
nd

nd
 M answers the call
4
seconds

nd
st
Retrieve the 1 call

st st
seconds
Note : The test to not record several lines for outbound calls is not done due to a lack of the
CSTA information in the OXE part

8.23 Business Sets : MLA Feature – secondary MLA set answers
This test checks that VRS is able to record calls with MLA keys. In addition, the call-details retrieved
application, it should be possible to playback the audio of this call
Note : A business set must have a multiline key before the creation of a MLA key
Test
Id
Primary MLA key on set M
1  Create a Primary MLA key ( with Number 1 ) on
the phone set M
Secondary MLA key on set N
2  Create a Secondary MLA key ( with Number 1 )
on the phone set N
Inbound call
 Make an inbound call to the MLA number 1
 N answers the call on the Secondary MLA key (
3
Number 1 )
 N and the external caller speak during at least 10
seconds
On hold
4

st
N puts on Hold the 1 call
Retrieve the call on set M
 M retrieves the call on the Primary MLA key (
number 1 )
5
 M and the external party speak during at least 10
seconds
Feature Not
supported
Primary MLA key Secondary MLA key

Number 1 Number 1
Set M
Set N

8.24 Business Sets : MLA Feature – swapping between 2 Primary
MLA lines
Test
Id
 Create a Primary MLA key ( with Number 1 ) on
1 the phone set M
 Create a Primary MLA key ( with Number 2 ) on
the phone set M
Inbound call
 M answers the call on the Primary MLA key (
2
Number 1 )
seconds
New Inbound call

st
M puts on hold the 1 call

nd
M answers the 2 call on the Primary MLA key (
3
Number 2 )
seconds
 M hangs up
st
Retrieve the 1 call
 M retrieves the call on the Primary MLA key (
Number 1 )
4
 M and the external party speak during at least 10
seconds
Feature Not
supported

8.25 Business Sets : MLA Feature – swapping between Primary and
Secondary MLA lines
Test
Case Id
1  Create a Primary MLA key ( with Number 1 ) on the
phone set M
MLA key on set N
 Create a Secondary MLA key ( with Number 1 ) on
2 the phone set N
 Create a Primary MLA key ( with Number 2 ) on the
phone set N
Inbound call
 N answers the call on the Secondary MLA key (
3
Number 1 )
seconds
New Inbound call

st
N puts on hold the 1 call

nd
N answers the 2 call on the Primary MLA key (
3
Number 2 )
seconds
 N hangs up
st
Retrieve the 1 call
 N retrieves the call on the Primary MLA key (
Number 1 )
4
 N and the external party speak during at least 10
seconds
 N hangs up the call
Check the records in the VRS Feature
5  In the VRS application, check the records Not
supported
Primary MLA key Primary MLA key

Number 1 Set N Number 2
Secondary MLA key

Number 1
Set M

8.26 Business Sets : Tandem
This test checks that VRS is able to record calls with business sets in tandem. In addition, the call-
Query application, it should be possible to playback the audio of this call
Management of the tandem :

1. In the Main & secondary sets, create multiline keys
2. For the Main set, mgr --> users :
a. “Tandem directory Number” = number of the secondary tandem user
b. “Main set in the tandem” = YES
8.26.2 Test Results : Inbound call to Main set
Test
Id
Management of the tandem
 Create Multiline keys on the main & the
1
secondary tandem user
 Manage the tandem
Inbound call
 Make an inbound call to the tandem number
2  The main set answers the call
 The main set and the external caller speak during
at least 10 seconds before hanging up
8.26.3 Test Results : Outbound call from the Main set
Test
Id
1
Outbound call
 Make an outbound call from the main set
 The main set and the external caller speak during
at least 10 seconds before hanging up

8.26.4 Test Results : Inbound call to Secondary set
Test
Id
1
Inbound call
 Make an inbound call to the tandem number
2  The secondary set answers the call
 The secondary set and the external caller speak
during at least 10 seconds before hanging up
8.26.5 Test Results : Outbound call from the Secondary set
Test
Id
1
Outbound call
 Make an outbound call from the secondary set
 The secondary set and the external caller speak
during at least 10 seconds before hanging up
For the outbound call of the secondary set, the direction in the record is “incoming” (it should be
outgoing)

8.27 Beep Generation – Single Beep
This test checks that VRS supports the generation of a single beep.
Test
Case Id
Creation of a single beep
1
 Manage a single beep in the VRS
Call
2
 Make a call including a recorded device
Beep generation
3
 Send a single beep
Supported
8.28 Beep Generation – Several Beeps

This test checks that VRS supports the generation of several beeps.
Test
Case Id
Creation of the generation of several beeps
1
 Manage the generation of several beeps in the VRS
Call
2
 Make a call including a recorded device
Beeps generation
3
 Send several beeps
Supported

8.29 Compression type tests
3 codecs can be managed on the OXE: G711, G729, G723
Specific configuration on the PBX:

 Check the compression type on the system parameter
o System/Other System Param./Compression Parameters
Compression Type: G729 (or G723)
 Modify according to the requested test the compression type linked to the IP Phone and the
GD board
o IP/IP Phones Parameters
 Default Voice Coding Algorithm + Without Compression (or With
Compression)
o INTIP B and GD Parameters
 Default Voice Coding Algorithm + Without Compression (or With
Compression)
 To verify the compression type which is used for an IP call from IP Phone, you have to
mirror the IP Phone. From wireshark software, the RTP event will show you the
compression type.
8.29.1 Test objectives

This test checks that VRS is able to record in different codecs (G711, G729 or G723).
8.29.2 Test results
Test
Case Id
G711
1
 Make a call in G711
G723
2
G729
3
Issue with
G729

9 Network IP DR Link Recording Tests
The following test cases intend to record calls over the WAN ( Network OXE in full IP ).
9.1 Simple calls
This test checks that VRS is able to record simple calls through ABC-F2 link. In addition, the call-
9.1.2 Test Results
Test
Id
Network call : OXE1 --> OXE2
 Make a call from Agent V1 to Remote Agent RV1
1
 Remote Agent RV1 answers the call and speaks
for at least 10 seconds before hanging-up.
Network call : OXE2 --> OXE1
 Make a call from Remote Agent RV1 to local
2 Agent V1

9.2 Transfer of an inbound call from Local to Remote – Blind transfer
This test checks that VRS is able to record transfer inbound calls through ABC-F2 link. In addition,
the call-details retrieved from the CSTA link should be inserted to the VRS calls database. Then,
using the Query application, it should be possible to playback the audio of this call.
9.2.2 Test Results
Test
Id
Inbound call to local node
1
10 seconds
Enquiry and transfer to remote node
 Agent V1 makes a network call to Remote Agent
RV1 ( the inbound call is automatically put on
2
hold )
 Agent RV1 transfers the inbound held call to
Remote Agent RV1
Transferred call
3  Remote Agent RV1 answers the call and speaks
for at least 10 seconds
Internal transfer
 Remote Agent RV1 makes an internal call to
Remote Agent RV2 ( the inbound call is
4
automatically put on hold )
 Remote Agent RV1 transfers the inbound held
call to Remote Agent RV2
Transferred call
for at least 10 seconds before hanging-up

9.3 Transfer of an inbound call from Remote to Local – Blind transfer
9.3.2 Test Results
Test
Id
Inbound call to remote node
 Make an inbound call to Remote Agent RV1
1
Enquiry and transfer to local node
 Remote Agent RV1 makes a network call to
Agent V1 ( the inbound call is automatically put
2
on hold )
call to Agent V1
Transferred call
10 seconds
Internal transfer
 Agent V1 transfers the inbound held call to Agent
V2
Transferred call

9.4 Transfer of an inbound call between 2 nodes – Blind transfer
9.4.2 Test Results
Test
Id
1
10 seconds
2
hold )
 Agent V1 transfers the inbound held call to
Remote Agent RV1
Transferred call
Transfer to local node
4
on hold )
call to Agent V2
Transferred call

9.5 Transfer of an inbound call from Local to Remote – Supervised
Transfer
9.5.2 Test Results
Test
Id
1
10 seconds
Enquiry to remote node
2
hold )
 Agent V1 and Remote Agent RV1 speak at least
10 seconds
Transfer
3
 Agent V1 transfers the enquiry call
Transferred call
4  Remote Agent RV1 and the external party speak
Internal Enquiry
Remote Agent RV2 ( the inbound call is
5
 Remote Agent RV1 and Remote Agent RV2
speak at least 10 seconds
Transfer
6
 Remote Agent RV1 transfers the enquiry call
Transferred call
The calling number in the supervised transferred record is the user which makes the enquiry call (
st
and not the caller of the 1 call ).
For instance :

9.6 Transfer of an inbound call from Remote to Local – Supervised
Transfer
9.6.2 Test Results
Test
Id
Inbound call to Remote node
1
Enquiry to local node
2
on hold )
10 seconds
Transfer
3
Transferred call
4  Agent V1 and the external party speak for at least
10 seconds
Internal Enquiry
 Agent V1 and Agent V2 speak at least 10
seconds
Transfer
6
Transferred call
st
For instance :

9.7 Transfer of an inbound call between 2 nodes – Supervised
Transfer
9.7.2 Test Results
Test
Id
Inbound call to Local node
1
10 seconds
Enquiry to Remote node
2
hold )
10 seconds
Transfer
3
Transferred call
Enquiry to Local node
5
on hold )
 Remote Agent RV1 and Agent V2 speak at least
10 seconds
Transfer
6
Transferred call
st
For instance :

9.8 Transfer of an outbound call from Local to Remote – Blind transfer
This test checks that VRS is able to record transfer outbound calls through ABC-F2 link. In addition,
9.8.2 Test Results
Test
Id
Outbound call from local node
1
 External caller answers the call and speaks for at
least 10 seconds
RV1 ( the outbound call is automatically put on
2
hold )
 Agent RV1 transfers the outbound held call to
Remote Agent RV1
Transferred call
Internal transfer
Remote Agent RV2 ( the outbound call is
4
 Remote Agent RV1 transfers the outbound held
call to Remote Agent RV2
Transferred call

9.9 Transfer of an outbound call from Remote to Local – Blind transfer
9.9.2 Test Results
Test
Id
Outbound call from remote node
 Make an outbound call from Remote Agent RV1
1
least 10 seconds
Enquiry and transfer to local node
Agent V1 ( the outbound call is automatically put
2
on hold )
call to Agent V1
Transferred call
10 seconds
Internal transfer
Agent V2
Transferred call

9.10 Transfer of an outbound call between 2 nodes – Blind transfer
9.10.2 Test Results
Test
Id
1
least 10 seconds
RV1( the outbound call is automatically put on
2
hold )
Remote Agent RV1
Transferred call
Transfer ro local node
4
on hold )
call to Agent V2
Transferred call

9.11 Transfer of an outbound call from Local to Remote – Supervised
Transfer
9.11.2 Test Results
Test
Id
1
least 10 seconds
2
hold )
10 seconds
Transfer
3
Transferred call
Internal Enquiry
Remote Agent RV2 ( the outbound call is
5
 Remote Agent RV1 and Remote Agent RV2
speak at least 10 seconds
Transfer
6
Transferred call
st
For instance :

9.12 Transfer of an outbound call from Remote to Local – Supervised
Transfer
9.12.2 Test Results
Test
Id
Outbound call from Remote node
1
least 10 seconds
Enquiry to local node
2
on hold )
10 seconds
Transfer
3
Transferred call
10 seconds
Internal Enquiry
 Agent V1 and Agent V2 speak at least 10
seconds
Transfer
6
Transferred call
st
For instance :

9.13 Transfer of an outbound call between 2 nodes – Supervised
Transfer
9.13.2 Test Results
Test
Id
Outbound call from Local node
1
least 10 seconds
Enquiry to Remote node
2
hold )
10 seconds
Transfer
3
Transferred call
5
on hold )
 Remote Agent RV1 and Agent V2 speak at least
10 seconds
Transfer
6
Transferred call
st
For instance :

9.14 3 Way Inbound Conference Call – Starting From Local to Remote
This test checks that VRS is able to record inbound conference calls through ABC-F2 link. In
9.14.2 Test Results
Test
Id
1
10 seconds
2
hold )
10 seconds
Conference
 Agent V1 presses the “conference” button
3  Agent V1, Remote Agent RV1 and the external
party speak for at least 10 seconds before Agent
V1 hangs up

9.15 3 Way Inbound Conference Call – Starting From Remote to Local
This test checks that VRS is able to record inbound conference calls through ABC-F2 link. In
9.15.2 Test Results
Test
Id
Inbound call to Remote node
1
2
on hold )
10 seconds
Conference
 Remote Agent RV1 presses the “conference”
button
3
 Agent V1, Remote Agent RV1 and the external
RV1 hangs up

9.16 3 Way Outbound Conference Call – Starting From Local to
Remote
This test checks that VRS is able to record outbound conference calls through ABC-F2 link. In
9.16.2 Test Results
Test
Id
1
least 10 seconds
2
hold )
10 seconds
Conference
 Agent V1 presses the “conference” button
3  Agent V1, Remote Agent RV1 and the external
V1 hangs up

9.17 3 Way Outbound Conference Call – Starting From Remote to
Local
This test checks that VRS is able to record outbound conference calls through ABC-F2 link. In
9.17.2 Test Results
Test
Id
Outbound call from Remote node
1
least 10 seconds
2
on hold )
10 seconds
Conference
 Remote Agent RV1 presses the “conference”
button
3
 Agent V1, Remote Agent RV1 and the external
RV1 hangs up

10 Reliability tests
10.1 Failure Tests

The list of tests below intends to check the behaviour of VRS in case of failure or wrong
configuration. More especially if the notification messages (or alarms) are relevant for administrator
to help investigate the possible issues
10.1.2 Test Results : IP DR-Link : Bad devices

This test is intended to check the behaviour of the VRS to not record in IP DR-link a non IP device
Test
Id
Management of the recording of a TDM set in the VRS
1  Declare the recording of a set which is not a serie
8 ( UA, Z, serie 9… )
Record in IP DR-link
2  Try to record in IP DR-link ( send a “Start IP
Recording” event from the VRS ) the set
 In the VRS application, check there is no record
3
 In the VRS application, check the logs…

10.1.3 Test Results : DR-Link & IP DR-Link : Not authorized recording
This test is intended to check the behaviour of VRS to not record a device which is not authorized
Test
Id
Record authorization = False
1  In the Phone Features Category of the set, put
the “Record Authorization” = False
Try to Record
2  Make a call with the set
 Try to record the set
3
In VDS-II-DR-Link-IP.log :

10.1.4 Test Results : IP DR-Link : No Recording when the parameter “DR-Link on
IP supported” = FALSE
This test is intended to check the behaviour of the VRS to not record a VoIP when DR-Link on IP is
not supported.
This boolean is in mgr --> Applications --> CSTA -->“DR-link on IP supported”
Test
Id
“DR-link on IP supported” = FALSE
1  Manage the parameter “DR-Link on IP
supported” = False
Record in IP DR-link
 Try to record in IP DR-link ( send a “Start IP
2
Recording” event from the VRS ) a monitored
VoIP set
3

10.1.5 Test Results : DR-Link & IP DR-Link : License not available
This test is intended to check the behaviour of VRS to not record a device when the licenses are not
available
Test
Id
License file with no recording licenses
1  Put a new license file with no recording ( lock 334
=0)
Try to Record
2  Make a call with the set
 Try to record the set
3

10.1.6 Test Results : DR-Link & IP DR-Link : Max Licenses reached
This test is intended to check the behaviour of VRS to not record a device when the licences are
reached
Test
Id
License file with limited recording licenses
1  Put a new license file with limited recording ( lock
334 with limited value )
Try to Record
2  Try to record the set when the limited recording
license is reached
3

10.2 Switch Failure
This test is intended to check the recovering of the VRS after a Switch failure.
The switch has only one CPU.
10.2.2 Test Results
Test
Id
Inbound call
 Make an inbound call to A
1
 A and the external party speak for at least 10
seconds
Outbound call
 Make an outbound call from B
2
 B and the External party speak for at least 10
seconds
Internal call
3  Make an internal call from C to D
 C and D speak for at least 10 seconds
Switch failure
4
 Reboot the OXE
 In the VRS application, check the records
5
New calls after the reboot

 Perform new calls ( internal, inbound & outbound
6
calls )

 In the VRS application, check the new records
7

10.3 CTI Link Failure - OTS Service Failure
This test is intended to check the recovering of the VRS after a CTI Link failure with an OTS service
failure.
10.3.2 Test Results : IP DR-Link

For this test, the parameter : mgr --> Applications --> CSTA --> “End of recording on end of call” is
used and has to modify the behaviour of the Voice Recording System.
This parameter is only available in IP DR-Link.
Test
Id
Management of “End Of Recording on end of calls”
1  Manage the parameter “End of Recording on end
of calls” = YES
Internal call
2  Make an internal call from V1 to V2
 V1 and V2 speak for at least 10 seconds
Stop the OTS service
3
 Stop the OTS service of the VRS
Check if there are the records in the VRS
4
End of calls
5  Stop the current calls
Start the OTS service

6  Start the OTS service of the VRS

7
New calls
8  Perform a new call between V1 & V2

9

10.4 Redundancy Tests ( Alcatel-Lucent side )
These tests are intended to check the recovering of the Voice Recording System using redundancy
elements.
10.4.2 Test Results : OXE in Spatial Redundancy

This test is intended to check the recovering of VRS after a CPU switchover.
In this test, both CPUs are used in spatial redundancy ( in different IP sub networks ).
Test
Id
Management of the CPUs
1  Manage both CPUs in two IP sub networks
 Check that the spatial redundancy is managed
Internal call
Inbound call
3
 A and the External party speak for at least 10
seconds
Outbound call
4
 B and the external party speak for at least 10
seconds
Switchover of the OXE
 Switchover the Main CPU
5
 Check the new Main CPU is coming up
 Check the new CTI link
End of calls

7
New calls
 Perform a new internal call between V1 & V2
8  Perform a new inbound call to A
 Perform a new outbound call from B

9


10.4.3 Test Results : TSAPI Backup
This test is intended to check the recovering of the Voice Recording System with a TSAPI server
backup installed on a dedicated machine.
Test
Id
Management of the TSAPI server Backup
 Check that the TSAPI server Backup is installed (
1
on a dedicated machine ), configured and
running
Internal call
Inbound call
3
 A and the External party speak for at least 10
seconds
Outbound call
4
 B and the external party speak for at least 10
seconds
Stop the Main Alcatel Open Telephony service
 Stop the main Alcatel-Lucent’s service
5
(Alcatel Open Telephony).
 Wait until TSAPI Backup is Up
End of calls

7
New calls
 Perform a new internal call between V1 & V2
8  Perform a new inbound call to A
 Perform a new outbound call from B

9

10.5 Passive Call Server
The test environment :
DATA CENTER 1
DATA CENTER 2
Call Server 1
Call Server 2
( Active )
( Stand By )
IC GeoCluster TSAPI TSAPI

BACKUP
VoIP Logger
172.27.144.X
Mask : 255.255.255.0 172.27.145.X
Mask : 255.255.255.0
WAN
DOMAIN 0
192.168.6.X
Mask : 255.255.255.0
GA GD
T2 T2
PCM-R2 PCS
VoIP Logger TSAPI
IP Phone
IP Phone

This test is intended to check the recovering of the Voice Recording System in case of network
failure when the Main& StandBy CPU become not available. In this case the Passive Call Server is
started and ensure basic telephonic services.
In this case, the Logger ( for IP DR-Link or DR-Link ) must follow several conditions :
 is located with the remote media gateway
 embeds a TSAPI server which is connected to the Passive Call Server
 is configured with a second CTI link connected to embedded TSAPI
10.5.2 Test Results : IP DR-Link
Test
Id
Management of the Logger
1  Manage a Passive Call Server in the OXE
 Manage the Passive Call Server in the Logger
Network failure
 Unplug the IP cables of the Main & the Standby
CPU
2  The Passive Call Server is isolated and the
remote media gateway reboots automatically
 The Passive Call Server is now linked to the
TSAPI of the “ remote” Logger
Internal calls
 Make an internal call between V1 & V2
3
 V1 & V2 speak for at least 10 seconds before
hanging up
Inbound calls
 Make an inbound call to V1
4
 V1 & the external party speak for at least 10
seconds before hanging up
Outbound calls
 Make an outbound call from V1
5
 V1 & the external party speak for at least 10
seconds before hanging up
Check if there are the records in the logger
 Check the records in the logger
6
Network reconnection
 Plug the IP cable of the Main & the Standby CPU
 The remote media gateway reboots automatically
7
 The Logger is now reconnected with the Voice
Recording System
Synchronization – Retrieving data

8  Check that the Voice Recording Server retrieve
these records
New calls
 Perform new calls : internal, oubound & inbound
9
calls

 In the VRS application, check the records Feature Not
10
 In the VRS application, check the logs… supported

10.6 Understanding of the logs files
This test is intended to check the understanding of the log files of the VRS. We consider three
levels or notes : Poor, Good, Very Good.
Alcatel-Lucent has to add a comment in order to justify the note.
10.6.2 Test Results
Test Case Note Comments
Understanding of the log files of the Recording System Good
10.7 Notifications & alarms

This test is intended to check the notifications & alarms of the Voice Recording System. We
consider three levels or notes : Poor, Good, Very Good.
Alcatel-Lucent has to add a comment in order to justify the note.
10.7.2 Test Results
Test Case Note Comments
No notification
Notifications & Alarms of the Voice Recording System
or alarm

11 CTI parameters
Following CTI information (extracted from CSTA events) are stored in the VRS database
Type Information N/A OK NOK
Calculated
Duration
CSTA Standard Events
Start Time
Stop Time
DNIS
ANI
Direction ( In / Out )
Agent ID
Call ID
Alcatel-Lucent
private CSTA
Agent Name
Agent Group
Pilot Name
Associate Data
Associate station
Global Callid

12 Appendix B: Partner Application: configuration
requirements
1. Open ATIS UHER VDS-II GUI for IP DR LINK
It will run a small command line window and open the GUI itself.
2. Overview of screen with configured settings

 Row explanation :
Device == phone to be monitored
Exchange == TSAPI link
Recorder == link between MDx recorder and VDS-II
Curr. State == current state of the marked target (active == recording)
New State == If you activate & deactivate target first the "new state" changes &
after successful marking the "curr state" changes as well.
Message == gives a hint about potential feedbacks (during creation of
screenshot the TSAPI server was not connected)
3. Functional buttoms
 green phone
activate a marking
you can activate devices or entire groups
 red phone
deactivate a marking
you can deactivate devises or entire groups
 plus
add marking or group
depends on whether selected in "markings" or "marking groups" -drop down
function is not available.

i. Device: the "device ID" i.e. the phone number of the monitored set/agent
ii. Exchange: TSAPI node describer as configured during setup of VDS-II and
TSAPI server
iii. Recorder: an ID which links a VC-MDx to a specific VDS-II. The first recorder for
VDS-II is usually R0001.
iv. Name: only the name of the marking groups. Choose a name which describes
the group properly
 gearwheel
edit group or marking
 minus
remove marking or group
deactivate markings before deleting something!
4. Exit GUI if not needed - make sure to exit it using the "x" in the gui.

13 Appendix C: Alcatel-Lucent Communication
Platform: configuration requirements
13.1 Configuration for IP DR-Link
13.1.1 CSTA parameters
 Parameter 1 : Set to TRUE the “DR-Link on IP supported” parameter.
 Parameter 2 : “End of recording on end of call” :
According to the behaviour requested by the customer, modify the value of this
parameter to stop ( or not ) the recording of a device before the end of call.
This parameter is only available in IP DR-Link ( not in DR-Link )
Remark :The recording stays active until the “Stop IP Recording” is requested even
if the device becomes out of service.

13.1.2 Phone Facilities Categories parameter
The configuration parameter “Record Authorization” in Categories / Phone Facilities

Categories inside the menu ‘Rights’ is affected to allow the System administrator to
authorize the recording of a category of users.
13.1.3 Recording IP Logger
Declare all IP loggers thanks this menu.

13.1.4 Quality of service for IP recording parameter (IP / IP Domain)
If necessary, configure the “Quality of service for IP recording” to have a different

TOS/DiffServ for recording ( in order not to disturb voice communications).
13.1.5 IP DR-Link licenses
There are two software locks related to DR-Link on IP :
 lock 130 : to specify the type of voice recording system used.
 "0" if no voice recording system is connected.
 "1" if a Nice Systems recording system is used.
 "2" for other systems (Verint, Witness, Mercom, eTalk, ...).
 lock 334 : gives the maximum IP recording flows available
13.2 Additional parameter for DR-Link & IP DR-Link:
During a system configuration it is possible to precise the quantity of maximum authorized

monitoring. By default this value is set to 1000 but through ACTIS it can be increase to
3000 max

14 Appendix D: Partner escalation process
14.1 Headquarter
ATIS UHER SA address ATIS UHER SA

Industrie 7
CH-2046 Fonaines
telephone CH 0043 328540 100

fax CH 0043 328540 101
14.2 German branch
servicehotline DE 0049 6172 106111

servicemail service@voicecollect.net
generic mail voicecollect@voicecollect.net

15 Appendix E: AAPP program
15.1 Alcatel-Lucent Application Partner Program (AAPP)

The Application Partner Program is designed to support companies that develop communication
applications for the enterprise market, based on Alcatel-Lucent's product family.
The program provides tools and support for developing, verifying and promoting compliant third-
party applications that complement Alcatel-Lucent's product family. Alcatel-Lucent facilitates market
access for compliant applications.
The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives:
 Provide easy interfacing for Alcatel-Lucent communication products:

Alcatel-Lucent's communication products for the enterprise market include infrastructure
elements, platforms and software suites. To ensure easy integration, the AAPP provides a
full array of standards-based application programming interfaces and fully-documented
proprietary interfaces. Together, these enable third-party applications to benefit fully from
the potential of Alcatel-Lucent products.
 Test and verify a comprehensive range of third-party applications:

to ensure proper inter-working, Alcatel-Lucent tests and verifies selected third-party
applications that complement its portfolio. Successful candidates, which are labelled
Alcatel-Lucent Compliant Application, come from every area of voice and data
communications.
The Alcatel-Lucent Application Partner Program covers a wide array of third-party

applications/products designed for voice-centric and data-centric networks in the enterprise market,
including terminals, communication applications, mobility, management, security, etc.

Web site
The Application Partner Portal is a website dedicated to the AAPP program and where the
InterWorking Reports can be consulted. Its access is free at
http://applicationpartner.alcatel-lucent.com
15.2 Alcatel-Lucent.com
You can access the Alcatel-Lucent website at this URL: http://www.Alcatel-Lucent.com/

16 Appendix F: AAPP Escalation process
16.1 Introduction
The purpose of this appendix is to define the escalation process to be applied by the Alcatel-Lucent
Business Partners when facing a problem with the solution certified in this document.
The principle is that Alcatel-Lucent Technical Support will be subject to the existence of a valid
InterWorking Report within the limits defined in the chapter “Limits of the Technical support”.
In case technical support is granted, Alcatel-Lucent and the Application Partner, are engaged as
following:
(*) The Application Partner Business Partner can be a Third-Party company or the Alcatel-Lucent
Business Partner itself

16.2 Escalation in case of a valid Inter-Working Report
The InterWorking Report describes the test cases which have been performed, the conditions of the
testing and the observed limitations.
This defines the scope of what has been certified.
If the issue is in the scope of the IWR, both parties, Alcatel-Lucent and the Application Partner, are
engaged:
Case 1: the responsibility can be established 100% on Alcatel-Lucent side.

In that case, the problem must be escalated by the ALU Business Partner to the Alcatel-Lucent
Support Center using the standard process: open a ticket (eService Request –eSR)
Case 2: the responsibility can be established 100% on Application Partner side.

In that case, the problem must be escalated directly to the Application Partner by opening a
ticket through the Partner Hotline. In general, the process to be applied for the Application
Partner is described in the IWR.
Case 3: the responsibility can not be established.

In that case the following process applies:
 The Application Partner shall be contacted first by the Business Partner (responsible for
the application, see figure in previous page) for an analysis of the problem.
 The Alcatel-Lucent Business Partner will escalate the problem to the Alcatel-Lucent
Support Center only if the Application Partner has demonstrated with traces a problem
on the Alcatel-Lucent side or if the Application Partner (not the Business Partner) needs
the involvement of Alcatel-Lucent.
In that case, the Alcatel-Lucent Business Partner must provide the reference of the Case
Number on the Application Partner side. The Application Partner must provide to Alcatel-
Lucent the results of its investigations, traces, etc, related to this Case Number.
Alcatel-Lucent reserves the right to close the case opened on his side if the investigations
made on the Application Partner side are insufficient or do no exist.
Note: Known problems or remarks mentioned in the IWR will not be taken into account.
For any issue reported by a Business Partner outside the scope of the IWR, Alcatel-Lucent
offers the “On Demand Diagnostic” service where Alcatel-Lucent will provide 8 hours
assistance against payment.
IMPORTANT NOTE 1: The possibility to configure the Alcatel-Lucent PBX with ACTIS quotation tool
in order to interwork with an external application is not the guarantee of the availability and the
support of the solution. The reference remains the existence of a valid InterWorking Report.
Please check the availability of the Inter-Working Report on the AAPP (URL:
https://private.applicationpartner.alcatel-lucent.com) or Enterprise Business Portal (Url: Enterprise
Business Portal) web sites.
IMPORTANT NOTE 2: Involvement of the Alcatel-Lucent Business Partner is mandatory, the access
to the Alcatel-Lucent platform (remote access, login/password) being the Business Partner
responsibility.

16.3 Escalation in all other cases
These cases can cover following situations:
1. An InterWorking Report exist but is not valid (see Chap 2 “Validity of an Interworking Report”)
2. The 3rd party company is referenced as AAPP participant but there is no official InterWorking
Report (no IWR published on the Enterprise Business Portal for Business Partners or on the
Alcatel-Lucent Application Partner web site) ,
3. The 3rd party company is NOT referenced as AAPP participant
In all these cases, Alcatel-Lucent offers the “On Demand Diagnostic” service where Alcatel-
Lucent will provide 8 hours assistance against payment.

16.4 Technical Support access
The Alcatel-Lucent Support Center is open 24 hours a day; 7 days a week:
 e-Support from the Application Partner Web site (if registered Alcatel-Lucent Application Partner):
http://applicationpartner.alcatel-lucent.com
 e-Support from the Alcatel-Lucent Business Partners Web site (if registered Alcatel-Lucent Business
Partners): https://businessportal.alcatel-lucent.com click under “Let us help you” the eService Request
link
 e-mail: Ebg_Global_Supportcenter@alcatel-lucent.com
 Fax number: +33(0)3 69 20 85 85
 Telephone numbers:
Alcatel-Lucent Business Partners Support Center for countries:
Country Supported language Toll free number

France
Belgium French
Luxembourg
Germany
Austria German
Switzerland
United Kingdom
Italy
Australia
Denmark
Ireland
Netherlands +800-00200100
South Africa
Norway
English
Poland
Sweden
Czech Republic
Estonia
Finland
Greece
Slovakia
Portugal
Spain Spanish
For other countries:
English answer: + 1 650 385 2193

French answer: + 1 650 385 2196
German answer: + 1 650 385 2197
Spanish answer: + 1 650 385 2198
END OF DOCUMENT


mANUAl - VOICE RECORDER - Atis-Vc-Mdxv11

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

mANUAl - VOICE RECORDER - Atis-Vc-Mdxv11

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent Application Partner Program

Partner: ATIS UHER SA

ALCATEL-LUCENT MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE

Date of the tests 5th-7th of November

Alcatel-Lucent’s representative Mikael FERELLOC

Alcatel-Lucent Communication OmniPCX Enterprise

Author(s): Mikaël FERELLOC

Edition 1: creation of the document – November 2013

Passed with restrictions

Refer to the section 6 for a summary of the test results.

IWR validity extension

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 2/95

Contact name: Thees Frank

City: CH-2046 Fontaines

Phone: 0043 328540 117

Web address: www.voicecollect.net

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 3/95

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 4/95

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 5/95

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 6/95

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 7/95

It certifies proper inter-working with the AAPP member’s application.

- the Technical Support page of the Enterprise Business Portal

- the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free

Interworking Certification labels:

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 8/95

A new release is identified as following:

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 9/95

For more details, please refer to Appendix F “AAPP Escalation Process”.

3.1 Case of additional Third party applications

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 10/95

Application family : Voice Recording Systems

Application commercial name: VoiceCollect MDx

Application version: v11

Interface type: TSAPI Premium Server

Interface version (if relevant): 7.0.5

Voice logger Features available Features tested in this report

Trunk side recording Yes ( without CSTA ) No

Remote DR-Link recording * Yes No

Free seating Yes Yes

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 11/95

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 12/95

DATA CENTER 1 DATA CENTER 2

ARMS TSAPI TSAPI

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 13/95

 OmniPCX Entreprise: Appliance servers, T2 and PCM interfaces, UA and Z interfaces,

5.2 Software configuration

 Alcatel Communication Platform: OmniPCX Enterprise R11

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 14/95

3 Way Conference Call OK OK  

Private outgoing calls NOK Feature Not Supported

Codecs : NOK   Feature NOK with G729

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 15/95

6.3 Summary of limitations

 CCD / Private Outgoing calls : Feature not supported

 Multi-lines / MLA sets: Feature not supported.

 Codecs: Feature NOK with G729.

 Beep generation : Feature not supported.

 Passive Call Server : Feature not supported

6.4 Notes, remarks

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 16/95

Alcatel-Lucent Application Partner Program – Inter-working report Edition 1 - page 17/95

8.1 Inbound calls