Howto:ASC EVOipActive - Testreport
Summary
We tested the new version ASC EVOip Active (only active recording was tested), since it replaces the ASC's "MARATHON VoIP Collector".
The test were successful and all required tests were passed. As a result the ASC EVOip Active recording solution is qualified as a Recommended Product
The phone that records the call (i.e IP240) creates a three party conference call between the caller and ASC EVOip Active recording software. Therefore a "normal"(using only the DSPs of the phone) three party conference between three phones is not possible, since the ASC recorder requires one DSP channel.
The Configuration with ASC DataManager 2.9 is simple (see under related Articles 06_EVOip_active_f_r_Innovaphone_d_V.pdf), but in contrast to this manual we recommend to register phones via H.323 and not SIP. ASC EVOip must be registered via SIP at the PBX where the user-object of ASC EVOip is configured.
The recorded calls are stored with additional call informations. We verified them using ASC Webplay 10.0.
The stored call informations were:
start time, end time, duration, call direction, compression, own phone number, partner phone number and 3rd Party Phone Number (if call forwarding is used) where recorded.
As you can see in the test results, we recommend to update your PBX/phones to v9 Hotfix 11 or later. Otherwise anonymous calls can not be recorded.
Certification Status
The tests for this product have been completed.
Version
- ASC
- EVOip Server Software 10.00.22
- EVOip active 5.20.46
- ASC Datamanager 2.90.24
- WEBplay 10.00.27
- innovaphone Firmware:
- PBX/Phones V9.00 Hotfix7 / Hotfix 11 or newer is strictly recommended! With earlier Hotfixes anonymous calls will not be recorded.
Test Notes
As you can see in the picture below, only ASC EVOip Active Server is registered via SIP at the PBX. All phones are using H.323 (recommended).
Test Setup
PBX: IP800
Phones: IP200A A=Nr.101, IP240 B=Nr.102, IP200A C=Nr.103
ASC EVOip Active on Windows 2003 Enterprise
Test Results
Basic call
Person recorded | Type of call | Own | Partner | Partner Direction | Result |
---|---|---|---|---|---|
1. Basic internal call | A calls B | ||||
A recorded | A | B | outgoing | Ok | |
B recorded | B | A | incomming | Ok | |
2. Basic external call Incoming | Ext. calls A | ||||
A recorded | A | Ext | incomming | Ok | |
3. Basic external call outgoing | A calls ext. | ||||
A recorded | A | Ext | outgoing | Ok |
Internal Conference
Conference Calls with three participants not possible, 1st caller = phone A, 2nd caller = phone B, 3rd caller = Recorder
innovaphone CONF interface is working fine.
Person recorded | Type of call | Result |
---|---|---|
4. Internal conference call | A calls B, A initiates conference to C, C first on-hook | Nok |
Hold / Consultation calls
Person recorded | Type of call | Own | Partner | 3rd Party | Partner Direction | Result | Comment |
---|---|---|---|---|---|---|---|
5. Hold / Consultation Call | A calls B, A consultates C, back to B | ||||||
A recorded | A | B | B,C,B | outgoing | Ok | Complete Consultation (A-B,A-C,AB) recorded | |
B recorded | B | A | A | incomming | Ok | Call between A and B recorded | |
C recorded | C | A | A | incomming | Ok | Call between A and C recorded | |
6. Hold / Consultation and Transfer Call | A calls B, A consultates C, A transfer to B, A first on-hook | ||||||
A recorded | A | B | B,C | outgoing | Ok | Transfered call between B and C could not be recorded because A transfered and on-hook. | |
B recorded | B | A | A,C | incomming | Ok | Complete Consultation recorded. A-B,A-C,B-C | |
C recorded | C | A | A,B | incomming | Ok | Call between A and B not recorded (It couldn't be..). |
Blind Transfer / Deflecting
Person recorded | Type of call | Own | Partner | 3rd Party | Partner Direction | Result | Comment |
---|---|---|---|---|---|---|---|
7. Blind Transfer Call | A calls B, B calls C and transfers without consultation | ||||||
A recorded | A | B | B,C | outgoing | Ok | Complete Consultation recorded | |
C recorded | C | A | A | incomming | Ok | Ruf zwischen A und B wird nicht recorded, Kann auch nicht… | |
7.1 Blind Transfer Call / with recall timer | A calls B, B calls C and transfers without consultation | ||||||
A recorded | A | B | B,C | outgoing | Ok | 2 calls recorded | |
B recorded | B | A | A | incomming | Ok | 2 calls recorded | |
8. Deflect Call | A calls B and B deflects to C | ||||||
A recorded | A | C | C | outgoing | Ok | Das B den call direkt nach C deflected hat wird nicht recorded | |
C recorded | C | A | A | incomming | Ok | Das B den call direkt nach C deflected hat wird nicht recorded |
Pickup and Call forwarding
Person recorded | Type of call | Own | Partner | 3rd Party | Partner Direction | Result | Comment |
---|---|---|---|---|---|---|---|
9. Pickup call | A calls B (member of a Pickup group) and C picks up the call | ||||||
A recorded | A | C | C | outgoing | Ok | ||
C recorded | C | A | A | incomming | Ok | ||
10. Call forwarding immediately | A calls B, call is forwarded to C (C takes the call) | ||||||
A recorded | A | C | C | outgoing | Ok | ||
C recorded | C | A | A | incomming | Ok | 2 calls recorded | |
11. Call forwarding no answer | A calls B, call is forwarded to C (C takes the call) | ||||||
A recorded | A | C | C | outgoing | Ok | ||
C recorded | C | A | A | incomming | Ok | ||
12. Call forwarding busy | A calls B, call is forwarded to C (C takes the call) | ||||||
A recorded | A | C | C | outgoing | Ok | ||
B recorded | B | PSTN | PSTN | outgoing | Ok | busy mit Ruf nach PSTN simmuliert um recording nachzuweisen/CFB A nach C über B funktioniert | |
C recorded | C | A | A | incomming | Ok |
Alternate / Park call
Person recorded | Type of call | Own | Partner | 3rd Party | Partner Direction | Result | Comment |
---|---|---|---|---|---|---|---|
13. Alternate call / makeln | A calls B, B makes a consultation to C, B alternates the call | ||||||
A recorded | A | B | B | outgoing | Ok | Wenn nur A recorded wird, kann auch nur Ruf zwischen A und B recorded werden | |
B recorded | B | A | A-C | incomming | Ok | Kompletter Call wird aufgezeichnet | |
C recorded | C | B | B | incomming | Ok | Call zwischen B und C aufgezeichnet | |
14. Park / unpark call | A calls B, B parks A, B calls C, B unparked A, B calls A | ||||||
A recorded | A | B | B,B | outgoing | Ok | Nur Ruf zwischen A und B recorded | |
B recorded | B | A | A | incomming | Ok | 3 seperate calls recorded | |
B | C | A hear MOH | outgoing | Ok | 3 seperate calls recorded | ||
B | A | A | incomming | Ok | 3 seperate calls recorded | ||
C recorded | C | B | B | incomming | Ok | Nur Ruf zwischen B und C recorded |
Automatic SIP Auth. with password after reboot ASC Server and PBX
Person recorded | Type of call | Own | Partner | 3rd Party | Partner Direction | Result | Comment |
---|---|---|---|---|---|---|---|
15. ASC reboot | A calls B | ||||||
A recorded | A | B | B | outgoing | Ok | Recording starts without login into Windows/ASC | |
15.1. PBX restart | A calls B | ||||||
A recorded | A | B | B | outgoing | Ok | EVOip registered automaticly to PBX |
Phone Recording options (IP200A and IP240)
Person recorded | Type of call | Own | Partner | Result | Comment |
---|---|---|---|---|---|
16. Transparent recording | |||||
Ok | All tests above were made with transparent recording | ||||
16.1 Manuell recording (redial button (standard) to on/off recording) | A calls B | ||||
A recorded | A | B | Ok | If redial button is used for recording, no call transfer will be possible (see 16.3 to solve) | |
B recorded | B | A | Ok | If redial button is used for recording, no call transfer will be possible (see 16.3 to solve) | |
16.2 Optional recording (redial button (standard) to off/on recording) | A calls B (between call on/off rec.) | ||||
B recorded | B | A | Ok | If redial button is used for recording, no call transfer will be possible (see 16.3 to solve) | |
16.3 Manuell recording with Function key to on/off recording) | A calls B, B starts recording, B transfer A to C | ||||
B recorded | B | A | Ok | Recording and call transfer works |
Codecs
Tested feature | Result | Comment |
---|---|---|
Call using g711a | YES | |
Call using g711u | YES | |
Call using g723 | Nok (Not supported from ASC) | It's recorded, but ASC means it's G.729. It could make (still unknown) problems using G.723. |
Call using g729 | YES |
Hide own Number
Person recorded | Type of call | Own | Partner | Result | Comment |
---|---|---|---|---|---|
18. Hide own Number | A hide his own number, A calls B | ||||
A recorded | A | B | Ok | ||
B recorded | Anonymous | B | Ok | Only still V9 Hotfix 11 Anonymous + Time is displayed! With older Hotfixes recorder will crash. |
Long Time Call
Tested feature | Result | Comment |
---|---|---|
Long time call 60 min. | Ok | Tested with G.729, A recorded |
Configuration
This Section describes how to configure Innovaphone PBX and phones to record calls to ASC EVOip Active. For informations how to configure EVOip Active, please read the current ASC manual.
It's highly recommended to register all Innovaphone phones with H.323 at the PBX and only register the EVOip Active Server via SIP at the PBX. Sure, you can also use SIP to register phones, but recording will not working in many cases (i.e. Call forwarding, function keys with Group indications will not work).
So, it's important to understand. If you want to use all Innovaphone features on your phone, register the phone via H.323.
1. Configure an User Object where EVOip Active will be registered
2. There is nothing special to configure normal user objects
3. Activate your prefered recording option on a phone
- manual: recording can be started and stoppen with the redial key or defined function key
- Transparent: recording is always on and can't stopped from the user
- optional: recordings starts automaticly, but it can be stopped and started again with the redial key or defined function key
4. The registered H.323 and SIP Objects should look like this