Interoperability Compliance Testing; General Test Approach; Test Results - Avaya QuesCom 400 Application Notes

5. Interoperability Compliance Testing

The interoperability compliance testing focused on verifying the routing of inbound/outbound
calls to/from the QuesCom 400.

5.1. General Test Approach

The general approach was to place inbound and outbound calls through the QuesCom 400 and
verify successful call completion. The main objectives were to verify that:
• When internal extensions place outbound calls to GSM numbers, the calls are routed to
the QuesCom 400, and the QuesCom 400 decides on the least cost routing and routes the
call to the GSM network.
• When the landline is out of service, all outbound calls can successfully be routed via the
QuesCom 400 if need be.
• If the landline is operational, then Avaya Communication Manager will successfully re-
route calls rejected by the QuesCom 400 to the landline. This can be configured to occur
for various reasons, such as no more free minutes left on the SIM cards.
• Inbound calls from the GSM network to the QuesCom 400 are successfully forwarded to
Avaya Communication Manager using both direct routing (mapping of a SIM card
phone number to an Avaya Communication Manager extension) and post-dialing (SIM
card answers an inbound call and upon a prompt, the external caller enters an Avaya
Communication Manager extension).
• Transfers and conferences between Avaya Communication Manager stations complete
properly on outbound and inbound calls routed through the QuesCom 400.

5.2. Test Results

The test objectives of Section 5.1 were verified. For serviceability testing, outbound and
inbound calls routed through the QuesCom 400 complete successfully after recovering from
failures such as Ethernet cable disconnects, and resets of Avaya Communication Manager and
the QuesCom 400.
The following are observations obtained from testing Avaya Extension to Cellular (EC500) with
QuesCom 400:
• Calls placed to EC500-enabled telephones on Avaya Communication Manager were
successfully extended to EC500-mapped external wireless telephones through the
QuesCom 400.
• EC500-mapped external wireless telephones successfully placed calls to Avaya
Communication Manager telephones through the QuesCom 400, and the displays of the
answering telephones showed the name and extensions of the corresponding EC500-
enabled telephones as the calling party.
• Avaya Extension to Cellular Feature Name Extensions were verified. For example,
EC500-mapped external wireless telephone callers successfully activated the Exclusion,
Idle Appearance Select, and Transfer on Hangup EC500 features through the QuesCom
400 by dialing the corresponding EC500 Feature Name Extensions.
HJP; Reviewed:
SPOC 9/14/2006
Solution & Interoperability Test Lab Application Notes
©2006 Avaya Inc. All Rights Reserved.
23 of 27
QuescomACM_H323