Howto:ACHAT - Authensis - Call Center Application Testreport: Difference between revisions
m (→Test Results) |
|||
Line 137: | Line 137: | ||
*SOAP is used for call center application functions | *SOAP is used for call center application functions | ||
*H.323 registration of XCAPI for IVR functions | *H.323 registration of XCAPI for IVR functions | ||
====SOAP==== | |||
SOAP configuration of the PBX is performed as usual: User Object placed in PBX group with active flag was used to init SOAP session. All Agents User Objects and Wating Queue objects are placed in this group. | |||
====XCAPI==== | |||
XCAPI was registered on user object on the PBX. No special configuration steps were performed. | |||
=== 3rd party product configuration === | === 3rd party product configuration === |
Revision as of 16:27, 28 August 2008
Summary
Certification Status
This product is being tested right now. The test is not yet completed.
Version
work-route, control-route, admin-route:
8.0.3
CSTA-Adapter:
2.22.0.0
SOAP to CSTA Converter:
1.91.0.1
ACHAT Server:
8.0.2
X-CAPI:
3.3.36.0
Ansagenserver:
1.17.4.6
innovaphone Firmware:
6.00 sr2-hotfix6 08-60900.77
Test Setup
- M1
- Phone on Master PBX
- A1
- Agent 1 Phone
- A2
- Agent 2 Phone
- S1
- Phone on Slave PBX
- E1
- External Phone
Connection to innovaphone PBX
SOAP to CSTA connector is a part of ACHAT and is used by ACHAT to monitor Waiting Queues and Agents.
Media connection to the PBX is handled by X-CAPI and used by IVR module of ACHAT.
Test Results
Basic Call
Tested feature | Result |
---|---|
E1 call service waiting queue, then talk to A1 | OK |
S1 call service waiting queue, then talk to A1 | OK |
M1 call service waiting queue, then talk to A1 | OK |
Call transfer
Tested feature | Result |
---|---|
E1 transfered with consultation by A1 to S1 | OK |
E1 blind transfered by A1 to S1 | OK |
If call in previous test not answered fallback to agent or watingqueue. | N/A |
E1 transferred by A1 to A2 and back to waiting queue | OK |
E1 transferred by A1 to M1 and back to waiting queue | OK |
testphone calls inno1. testphone transfers to inno2. |
Calls to Users with active Call Forward
Tested feature | Result |
---|---|
Agent calls user with call forward to service queue | OK |
CTI Functions of Call agent application
Tested feature | Ok? |
---|---|
Initiate outgoing call | OK |
Accept incoming call | OK |
End call | OK |
Initiate consultation call | OK |
End consultation call and switch back | OK |
Swap between active call and call on hold | NOK |
Put on hold | N/A |
Conference | N/A |
Swap and Conference functions are under construction now and should be available with V7.
Other Features
Directory
LDAP directory as phonebook is not supported.
Configuration
innovaphone configuration
ACHAT server and innovaphone PBX are maintaining two active connections:
- SOAP is used for call center application functions
- H.323 registration of XCAPI for IVR functions
SOAP
SOAP configuration of the PBX is performed as usual: User Object placed in PBX group with active flag was used to init SOAP session. All Agents User Objects and Wating Queue objects are placed in this group.
XCAPI
XCAPI was registered on user object on the PBX. No special configuration steps were performed.
3rd party product configuration
ACHAT is always installed and configured by Authensis technician.