Compliance Testing is Avaya's approach to providing our customers, channel partner and Avaya support teams with the necessary documentation to successfully deploy and configure third party solutions that interoperate or integrate with Avaya products. We do this through joint testing with members via the Compliance Testing Program, exercising the key APIs and open standards that define the interactions between the systems, and documenting the steps necessary to configure each product or service appropriately. Based on this documentation, Avaya Client Services can then provide basic "triage and fault isolation" to customers who have deployed such joint solutions.

Compliance Testing has three basic phases: Test Planning, Test Execution, and Documentation.

Test Planning encompasses validation of pre-requisites, jointly developing test plans and scheduling a test date.

Test Execution is a joint effort to validate the configuration of Avaya and third party systems to attain the functional integration expected by the third party vendor.

Finally, the Documentation phase focuses on developing DevConnect Application Notes that describe the necessary configuration steps and summarize the scope and results of the Compliance Test.

No. Compliance Testing exercises a subset of functionality, and does not ensure that the third party application will interoperate under any and all conditions. It is primarily an effort centered on obtaining a "known good" configuration that utilizes Avaya products in an appropriate manner. Avaya does not test for compliance with open standards, or necessarily ensure that every API call supported by an Avaya product is being utilized under each and every possible error condition by the third party solution under test.

Compliance Testing is a benefit of enhanced level membership, for Technology Partners and Test-enabled members.

The prerequisites are:

• Your product has completed development and is generally available with all features operational.
• Documentation for the product is completed and available in production quality (including table of Contents and Index).
• All online help and README files are current.
• Production troubleshooting documentation (for internal support personnel) is available.
• Your system level testing has successfully completed.
• Technical and Testing contact information for support and escalation has been provided.
• And your company is current on all membership, procurement, and testing fees.

After you request compliance testing of one of your solutions, a DevConnect test engineer will work with your company's technical contacts to jointly generate a compliance test plan. This test plan will be agreed to by both parties before testing is scheduled. Generally the solution will be tested in a configuration that closely resembles its projected typical use. This may include an environment with load traffic, and firewalls, and may include testing of error conditions and recovery situations.

Compliance testing is not a re-running of a system test, nor is it a complete certification test. Only a carefully selected subset of features and configurations are tested. Compliance testing does not include scalability, reliability or other stress testing components.

Generally, no. Testing is completed using Avaya Solution and Interoperability Lab testbeds.

When you request testing of a specific solution, you can request to do a test in an Avaya facility, or request to do remote lab-to-lab testing over secure VPN. This will be discussed with your assigned Test Engineer.

You will also be asked for a preferred geographic lab location. DevConnect labs, while global, may not be able to handle demand and/or specific system configurations needed for testing, and we apologize if we are unable to schedule your test for a specific lab location.

Service Providers undergoing SIP Trunk testing may be able to arrange for on-site testing by an Avaya engineer under certain specific situations. This testing arrangement may involve additional costs. Your DevConnect BDM will discuss this with you as part of the membership process.

Test time varies by product complexity and scope of effort. Generally, however, testing involves 3 to 5 days of joint testing using one of the Avaya Solution and Interoperability Test Labs around the globe.

Joint testing means that you will provide a one or two person technical team that will be present for the entire testing interval, and available for follow up questions. These resources may be available on-site at the Avaya lab, or remotely, but are required to be available for the entire test execution phase.

The Avaya test engineer assigned to your solution will be able to give you an estimate once the test plan is written.

This also varies based on the complexity of the solution being tested, and our compliance testing queue.

Generally it takes two to three weeks to jointly write and agree to a test plan. Once the test plan is written, firm test days can be scheduled. The minimum gap between the completion of the test plan and start of testing is 2 weeks (test days can not be scheduled less than two weeks after the test plan is written. In most cases, the testing queue is less than 6 weeks. This means that it can typically take between 4 and 8 weeks from request to the start of test execution.

After test execution has complete, results are jointly reviewed. If the test is considered successfully completed, DevConnect Application Notes are then created, reviewed and published. This process may take another 4-6 weeks to complete.

Membership levels affect two parts of compliance testing:

• DevConnect Technology Partners are given higher priority over Test-enabled members in the testing queue when scheduling their compliance testing.
• The cost for purchasing additional testing days may vary by Membership level. Refer to the current DevConnect Program Guide for current pricing information.

Technology Partners and Test-enabled Registered Members can use the link under the Compliance Testing tab to Request Compliance Testing. As part of submitting your request, you will be able to identify which of your approved solutions you wish to test, and the test type (in-lab or remote) as well as preferred test location.

Once a solution has been submitted and completed testing, it cannot be re-tested again. It can, however, be copied as a new solution and the details adjusted to reflect a later release of the Avaya platform or your own solution, or to change associated Avaya platforms entirely. Then the newly created solution record can be submitted as part of a new test request.

Members are responsible for all expenses associated with the installation, configuration and compatibility of their solution, including hardware, software and any external service subscriptions required (e.g. Salesforce.com accounts, SMS service accounts, email services, etc.), including both originating and return shipping of equipment, software and /or documentation to Avaya lab facilities.

Yes it can. Enhanced level DevConnect members can purchase additional testing time in whole day increments. Pricing is identified in the current DevConnect Program Guide. To purchase additional Compliance Test Days, please contact your Devconnect Business Development Manager (BDM).

Yes. Membership in Avaya DevConnect does not provide DevConnect members with authorization to deliver services for Avaya products directly to Avaya customers, or on behalf of Avaya Channel Partners. This includes, but is not limited to, the installation, configuration, maintenance and/or support services for any Avaya product. Furthermore, the creation and/or publication of any DevConnect Application Notes detailing configuration steps for Avaya products using any compliance-tested DevConnect partner product(s) do not provide support authorization.  

Only companies authorized through the Avaya Connect channel partner program or other Avaya programs, e.g., Services-Only Installation Program (SOIP), are recognized by Avaya Client Services as eligible to provide support services for Avaya products. Any company misrepresenting its authorization, based solely on DevConnect membership, may be subject to penalties including suspension of marketing benefits, restrictions on compliance testing or termination from the DevConnect Program.