Previous Topic

Book Contents

Book Index

Next Topic

Stress Test

Test tries to establish connection to CTI server, one per 1 sec, to monitor each phone listed in the input text file. It is supposed to verify that:

  • CTI servers can handle to monitor all addresses/phones for all Valuemation users which are supposed to use CTI
  • all phones to be monitored are correctly configured at CTI server

Test will produce a log file for each monitored address.

Logs files being longer/shorter than correct logs must be investigated for the problem.

NOTE: This is not a stress test of Valuemation but a stress test of customer CTI servers.

Help Image
Input file with addresses to be monitored

Help Image
VBS program to execute a test each address listed in the input file

Help Image
Batch file to execute java test program

Help Image
Windows opened by the test

Test result evaluation

There will be as many log files created as many addresses. Order them by size and investigate them beginning from the smallest.

Help Image

PASSED result

Each log file, created in CtiStressTestLogs, should contain info that address could be obtained and a plugin was created and connected to CTI server, as are the blue lines in the example below:

08/28 11:09:37.100 11 p1 InitMonitoredAddresses

08/28 11:09:37.100 12 p1 Get Address for 2283

08/28 11:09:37.100 13 p1 Address: 2283

08/28 11:09:37.334 14 p1 Observer added to the address 2283

08/28 11:09:37.334 15 p1 Trace terminals

08/28 11:09:37.334 16 p1 Terminal[0] SEP0011202B8D27 is assigned to addresses 2283

08/28 11:09:37.334 17 Plugin p1 was created and connected to CTI server.

08/28 11:09:37.334 18 OK

FAILED result

If there is any exception (as are the red lines below), the test has failed:

09/02 20:11:19.227 2 p1 setConnectionParams(26535@10.174.32.122;applicationID=CAP-S;login=+49876543210;passwd=123456)

09/02 20:11:19.228 3 p1 setMonitoredAddresses(365)

09/02 20:11:19.228 4 p1 Decoder: de.usu.s3.cti.yaplugin.JTapiDecoder

09/02 20:11:19.233 5 p1 Peer: com.siemens.cti.cstajtapi.JtapiPeerImpl

09/02 20:11:19.233 6 p1 Opening: 26535@10.174.32.122;applicationID=CAP-S;login=+49876543210;passwd=123456

javax.telephony.ProviderUnavailableException: Unable to connect to telephony server.

at com.siemens.cti.cstajtapi.JtapiPeerImpl.getProvider(JtapiPeerImpl.java:128)

at de.usu.s3.cti.yaplugin.siemens.SiemensPlugin.doConnect(SiemensPlugin.java:34)

at de.usu.s3.cti.yaplugin.CtiPlugin.connect(CtiPlugin.java:76)

at de.usu.s3.cti.YaCtiProvider.addPlugin(YaCtiProvider.java:86)

at de.usu.s3.cti.YaCtiTest.testPlugin(YaCtiTest.java:35)

at de.usu.s3.cti.YaCtiTest.main(YaCtiTest.java:56)

09/02 20:11:40.296 7 Monitoring of phone "365" on telephony server "p1" was not initialized. Cause: Unable to connect to telephony server.

See Also

Connection to CTI server

Avaya Aura

Cisco JTrace

Cisco

Siemens

Test of Calls to ACD