SCR; Reviewed:
WCH 7/7/2004
Solution & Interoperability Test Lab Application Notes
©2004 Avaya Inc. All Rights Reserved.
32 of 39
oaisys-ipoffice.doc
functionality, routing based on incoming CallerID, and desktop control of end-user extensions
for placing and receiving calls. Performance load tests verified the configuration continued
operating under load.
5.1. General Test Approach
Feature and functionality testing was performed manually. Inbound calls were made to the IP
Office system from analog, T1, and PRI trunks as well as internal extensions. The IP Office
routed all calls to the CallRouteHunt hunt group. The CTS OAISYS Call Router, monitoring
CallRouteHunt via TAPILink and DevLink, took over calls and routed them according to
previously defined rules and/or caller DTMF input to OAISYS Voice Assistant scripts run by
Call Router. Analog loop start trunks and PRI trunks from the central office were connected to
the IP Office. The configuration was changed to T1 for the T1 test cases.
Performance testing was accomplished by utilizing call generation tools for placing and
receiving calls from PRI to analog station ports. Analog station ports on the call generation tool
were connected to analog station ports on the IP Office Phone Expansion Module of the IP
Office. Call generation tool scripts were written to place calls to the CTS configured hunt group
on the IP Office. The first script would place a call from a PRI channel with a defined CallerID.
The OAISYS Call Router would intercept the call and route the call to one of the analog station
ports connected to the call generator based on previously defined rules. The call generation
script on the destination extension answered the call, played an audio file, and then the call
generation script would drop the call on both sides. The second script would place a call from a
PRI channel with a defined CallerID as well. However, the OAISYS Call Router would
intercept that call and on not finding a match in its database, it would launch an OAISYS Voice
Assistant script to prompt the caller for the desired extension. The call generation script would
send DTMF tones for the desired extension, the OAISYS Voice Assistant would collect the
information and pass it to Call Router, which would then divert the call to the desired extension.
The call generation script on the destination extension answered the call, played an audio file,
and then the call generation script would drop the call on both sides. Both scripts were run
simultaneously. Throughout the performance test run, OAISYS Tracer was configured to record
all calls to 2 of the 8 PRI channels used for testing. Due to time constraints, performance testing
on OAISYS Net Phone was passive and thus limited to maintaining the Net Phone client of each
analog station port used for performance testing open on the end-user desktops. Outlook
contacts list look ups were set up so the Net Phone clients would look up the CallerID of
incoming calls and display matched names.
5.2. Test Results
Most feature, functionality, and performance test cases passed successfully. All issues and/or
observations noted during testing were presented in Section 1.1 of these Application Notes.
Overnight performance testing at a rate of 1060 BHCA was conducted on the CTS PC provided
for compliance testing. Performance statistics were captured on the CTS PC to ensure that it was
able to handle the call volume.
