appendix a installation test plan

CONTEX Summit™ Implementation Plan

compunetixCommunications Systems DivisionConfidential and Proprietary 08/07

Appendix AInstallation Acceptance Test Plan

CONTEX Summit™ Implementation PlanInstallation Test PlanPage A-1


System ComponentsThe customer’s system consists of the following components:

Required Test EquipmentT1 Sunset with Voice and Signaling Options

DB-15 to dual Bantam Test Cable

Fluke 77 DMM (or equivalent)

Acceptance CriteriaEach test shall be marked as accepted or pending (with comments). Within the comments section three grades of failure will be used to quantify the severity of the failure.

• CriticalA Critical is a fault that prevents the system from performing tasks that are mutually considered critical to the daily business operations.

• SeriousA serious failure is a fault that constitutes major inconvenience for multi-ple users in getting access to the system.

• MinorA minor failure is a fault that does not affect the customer’s customers.

The installation shall be accepted when there are no critical, serious or minor failures present in the system, and none which prevent further installation testing activities.

The total delivery shall be accepted when there are no critical, serious or minor failures present in the system, and documentation is accepted.

All test results shall be documented and agreed upon by the respective project managers of the customer and Compunetix.

Both the customer and Compunetix will maintain a log of all faults. Minor faults will be corrected as appropriate in a future software release, following their identification.

IntroductionThis document describes the Installa-tion Test plan to be performed by Com-punetix to verify functionality of the customer’s CONTEX Summit installa-tion. This outlines tests to ensure that:

•All system components necessary for correct operation have been shipped to the customer’s site.

•All system components necessary for standard operation are functioning cor-rectly.

•All standard features of the system are working correctly.

CONTEX Summit™ Implementation PlanInstallation Test Plan

Page A-2


CONTEX Summit™

Installation Test Procedures

FEATURE RESULT

1 Conference Types1.1 Unattended Passcode Meet-Me

Create an unattended passcode meet-me and ensure both hosts and guests are able to join the conference.

Comments:

Accepted

Pending (see comment)

1.2 Unattended Passcode Progressive

Create an unattended passcode progressive and ensure that the host can dial out to additional participants. Also ensure that guests can join using the guest code.

Comments:

Accepted




1.3 Attended Meet-Me

Create an attended progressive conference, dial-into the bridge and ensure that the operator can add callers to the conference.

Comments:

Accepted


1.4 Attended Progressive (Dial-Out)

Create an attended progressive conference and ensure that the operator can dial out to parties and join each to the conference.

Comments:

Accepted


1.5 Attended Preset

Create an attended preset conference and ensure that it can be saved. Activate the preset and ensure that the operator can dial-out parties and join each to the confer-ence.

Comments:

Accepted


FEATURE RESULT


Page A-4


1.6 Combination Dial-in and Dial-out

Create an attended progressive conference and ensure that the operator can join incoming callers to the conference. Add a few dial out parties and ensure that the operator can dial-out and join the parties.

Comments:

Accepted


2 Conference Features2.1 Q&A Session

Create a conference, ensure that the chair-person is in T/L and all other parties are in Mon. Start a Q&A. Add a few parties to the question queue and promote each party. End the Q&A.

Comments:

Accepted


2.2 Voting Session

Create a conference, ensure that the chair-person is in T/L and all other parties are in Mon. Start a Voting session. End the voting session and save the results. Verify that the report is created.

Comments:

Accepted


FEATURE RESULT



2.3 Sub-conferences

Create two conferences on the bridge. Drag and drop parties from one conference into the other one (thereby creating a sub-con-ference).

Comments:

Accepted


2.4 Conference Details window

Create both an attended and an unattended conference on the bridge. From within each conference open the Conference Details widow and verify that the correct informa-tion is displayed.

]

Comments:

Accepted


2.5 Manual Gain Control

From within an active conference, highlight a connected party and click the Gain but-ton. Ensure that the Gain window opens. Adjust the gain, click the Set Gain button, and ensure that the gain is changed.

Comments:

Accepted


FEATURE RESULT


Page A-6


2.6 Entrance/Exit Tones

For a conference that has entrance and exit tones specified join a party to the confer-ence and verify that the tones (if config-ured) play accordingly. Disconnect a party and verify that the exit tones play accord-ingly.

Comments:

Accepted


2.7 Filter Incoming Calls

From the Answer Calls window, set up an answer filter. Generate a few calls using the number within the filter. Verify calls are dis-played. Generate a few calls using a number not within the filter. Verify the calls are not displayed. Uncheck the Filter On option and verify the calls are now displayed.

Comments:

Accepted


FEATURE RESULT



2.7 Override Default Greeting Msg

In the DNIS/DID Configuration window, specify the option to override the default greeting message with a custom greeting. Save the entry. Dial in on the DNIS and ver-ify that the custom greeting plays. Edit the DNIS entry and return the option to the default greeting and save the entry. Dial back in on the DNIS and verify that the sys-tem default greeting plays.

Comments:

Accepted


3 Unattended Conference Features3.1 Entrance/Exit Tones

Set up an unattended conference for host entrance tones and host exit tones. Dial in to the conference using the host passcode and verify that the tones play upon entrance then disconnect and verify that the tones play upon host exit.

Repeat for guest tones.

Comments:

Accepted


FEATURE RESULT


Page A-8


3.2 Entrance/Exit Announcements

Set up an unattended conference for host entrance and exit announcements. Dial in to the conference using the host passcode and verify that the announcements play upon entrance then disconnect and verify that the announcements play upon host exit.

Repeat for guest tones.

Comments:

Accepted


3.3 Chairperson Disconnect

Setup an unattended conference with Chairperson Disconnect enabled. Create the conference with a Host and several guests. Disconnect the host and ensure that all other parties are disconnected. Verify that the other parties receive the correct mes-sage.

Comments:

Accepted


FEATURE RESULT



3.4 Conference Quick Start

Setup an unattended conference with Con-ference Quick Start enabled. Create the con-ference by dialing in with 2 Guests. Verify that the Guests join the conference imme-diately.

Comments:

Accepted


3.5 First Party Message

Setup an unattended conference with the First Party Message enabled. Create the conference and verify that the first caller receives the First Caller message.

Comments:

Accepted


3.6 Multiple Language Support (3 full)

Create an unattended conference and verify that you can select between one of three languages.

Verify at the MC that 3 languages are loaded.

Comments:

Accepted


FEATURE RESULT


Page A-10


3.7 Distinguish between Hosts/Guests

Create an unattended conference with both a host and a guest passcode. Dial into the conference and verify that parties dialing in with the Host passcode are displayed as Hosts and that parties dialing in with the Guest passcode are displayed as Guests.

Comments:

Accepted


3.8 Auto Breakdown

Setup an unattended conference with the auto breakdown option selected and a duration of 10 minutes. Create the confer-ence by joining a host and a few guests. Wait for 10 minutes to pass and ensure that conference is disconnected.

Comments:

Accepted


FEATURE RESULT



3.9 Auto Record

Ensure the system is setup to allow Auto Record.Setup an unattended conference with the Auto record option enabled. Cre-ate the conference by connecting a Host and a Guest. Verify that after the Guest is connected that the system automatically dials out and connects the recorder and begins the recording session.

Comments:

Accepted


3.10 Lead Time/Trail Time

Verify the Lead Time/Trail Time settings at the MC.

Setup an unattended conference to begin at a specific time for a specific duration. Dial-in for the conference the number of minutes specified by the Lead Time plus a few min-utes before the start time. Verify you can-not access the conference. Wait until the Lead Time exactly, dial-in to the conference, and verify you can access the conference with the passcodes.

Wait for the duration to expire then verify you can still access the conference with the passcodes. Wait the number of minutes indicated by the trail time and dial back in and verify you cannot use the passcodes.

Comments:

Accepted


FEATURE RESULT


Page A-12


3.11 Internal Recording

Create an unattended conference with Internal Recording enabled. Activate the conference and verify that the conference records internally on the AE.

Comments:

Accepted


3.12 Call Flow Configurable per Conference

Setup an unattended conference and specify CIVR mode 1. Dial-in using the passcodes and verify that CIVR mode 1 is enabled for that conference.

Edit the unattended conference and specify CIVR mode 2. Dial-in and activate the con-ference and verify that CIVR mode 2 is enabled for the conference.

Repeat for CIVR mode 5 and CIVR mode 6.

Comments:

Accepted


3.13 Project Codes

Setup an unattended conference with Project codes enabled. Dial-in and verify that a project code can be entered.

Comments:

Accepted


FEATURE RESULT



4 Operator Console Features4.1 Individual WOC Configurations

Edit the WOC.ini file and start the WOC. Ensure that the WOC is configured inde-pendently of other connected WOCs.

Comments:

Accepted


4.2 DNIS/DID Directory

From the WOC, select Directories from the main menu bar then select DNIS/DID. Ensure that the DNIS directory opens. Cre-ate an entry and verify that the entry can be saved. Select an entry and verify that an entry can be deleted. Select an entry and edit the DNIS description, save the entry, and verify that the changes were saved.

Comments:

Accepted


4.3 Remote Capability

Connect a WOC from a location other than near the CONTEX Summit. Verify that the WOC can be connected.

Comments:

Accepted


FEATURE RESULT


Page A-14


4.4 Operator History

Connect the WOC, answer incoming calls, dial-out to a few parties, create a few unat-tended conferences, and activate a preset. Verify that you can view the Operator His-tory file and that events appear in the file.

Comments:

Accepted


4.5 Extract ANI

This applies only to those systems that receive ANI from the network.

In the WOC.ini enable the variable ANSWER_COPY_ANI. Dial-in to the bridge and verify that when the WOC operator answers the incoming call the ANI is auto-matically copied into the Phone field.

Comments:

Accepted


4.6 Group and Super Functions

From the WOC’s Conference Control win-dow select a group of participants and try each Group function and ensure that each is functional.

Repeat for each Super function.

Comments:

Accepted


FEATURE RESULT



4.7 View Schedule

From the WOC’s Answer Calls window, verify that when you select View Sched that the Conference Schedule window opens and reservations are displayed.

From the WOC’s main screen, verify that when you select Conference and then Schedule that the Conference Schedule win-dow opens and reservations are displayed.

Comments:

Accepted


4.8 Drag and Drop Capability

Create two conferences at the WOC. Select two or three parties from the one confer-ence and drag them to the second confer-ence. Verify that they parties are transferred in the same state.

Comments:

Accepted


FEATURE RESULT


Page A-16


5 DTMF Control Features5.1 Conferee Self-Mute

Verify the CIVR mode for the conference before running this test. Outside of the CIVR menu the self-mute key sequence is typically a *6 toggle.

Create an unattended conference. From within the conference press the self-mute key sequence and verify that the party is muted. Also, verify at the WOC that the party is displayed as in Mon.

Comments:

Accepted


5.2 Conference Mute

Create an unattended conference. From within the conference press the Conference mute key sequence and verify that all of the parties are muted. Also, verify at the WOC that all of the parties are displayed as in Mon.

Comments:

Accepted


FEATURE RESULT



5.3 Operator Recall (*0)

From within the conference have both a host and a guest press *0 to signal for assistance. Verify that both are able to do so. Also verify that at the WOC both sig-nals are displayed.

From within an attended conference verify that a party can press *0 to signal for assis-tance and that the WOC displays the request.

If cancel signal requests is enabled, verify that pressing *0 a second time cancels the request.

Comments:

Accepted


5.4 Conference Lock

Create an unattended conference. From within the conference press the conference lock key sequence and verify that the con-ference is locked. Also, verify at the WOC that the conference lock symbol is dis-played to the left of the conference name.

Comments:

Accepted


FEATURE RESULT


Page A-18


5.5 Participant Count

From within an unattended conference enter the DTMF command for participant count and verify that it works correctly.

Comments:

Accepted


5.6 Roll Call

From within an unattended conference enter the DTMF command for a roll call to the Host. Verify that only the Host hears the roll call.

From within the unattended conference enter the DMTF for a conference roll call. Verify that all hear the roll call.

Comments:

Accepted


5.7 Sub-Conferencing (1 at a time)

For an unattended conference using CIVR Mode 1 verify that the Host can access the Participant Management menu and pull a party out of the conference and then put them back.

Comments:

Accepted


FEATURE RESULT



5.8 Conference Extend

From within an unattended conference scheduled for automatic breakdown verify that using the DTMF to extend the confer-ence increases the duration

Comments:

Accepted


5.9 Disconnect Last Joined Conferee (CPDO)

Creating an unattended progressive confer-ence and dial out to a party and join the party to the conference. Press *3 and verify that the last party added to the conference is disconnected.

Comments:

Accepted


5.10 Vetting

Vetting is only available via the CONTEX Access Server currently.

Comments:

Accepted


FEATURE RESULT


Page A-20


6 Maintenance Client Features6.1 Windows-based Interface

Start up the Maintenance Client (MC) and verify that you see a Windows-based inter-face.

Comments:

Accepted


6.2 Graphical “Tree” Structure

From the MC main screen verify that a sys-tem “tree” is displayed along the left side. Verify that the tree can be expanded.

Comments:

Accepted


6.3 MC Not Required for Operations

Verify that if you shut down the MC that bridge operations are not affected.

Comments:

Accepted


FEATURE RESULT



6.4 Ability to Configure Circuits/Ports

From the MC’s Ports/Parties window verify that you can configure the ports on the bridge.

Right-click on a span and select Span Con-figuration, Verify that the Span/Trunk Con-figuration window opens and that you are able to configure the span.

Comments:

Accepted


6.5 Ability to View/Acknowledge Alarms

From the MC, click on the Alarm icon or select Alarm from the tool bar then verify you can view the System Alarms window. Also verify that you can acknowledge the alarms displayed in the System Alarms win-dow.

Comments:

Accepted


FEATURE RESULT


Page A-22


6.7 Keyboard Function Keys

From the MC’s Ports/Parties window verify that the following function keys work:

F1 - Displays the Port/Party Operation Shortcut window

F2 - Mute/Unmute

F3 - Pick up party

F4 - Disconnect party

F5 - Join operator

F6 -Release operator

F7 - Set operator

F8 - Exit listen set

F9 - Breakdown set

F10 - Exit all sets

F11 - Probe party

F12 - Configuration

<Enter> - Place call

Also verify the <Shift><function keys> work according to the list displayed in the Port/Party Operation Shortcut window.

Comments:

Accepted


FEATURE RESULT



6.8 Rack Status Window

Right-click the Rack option in the tree and select Status and verify that the Rack Status window opens. Verify that the correct mod-ules are displayed in the correct slot.

Comments:

Accepted


6.9 Remote Connection via Internet

Connect a MC via the Internet (if this is allowed by the customer).

Comments:

Accepted


7 Enhanced Capabilities7.1 Tone Block

From the MC verify that Tone Block is enabled. From within an unattended confer-ence verify that as a party presses any DMTF key sequence that the DTMF is not broadcast into the conference.

Comments:

Accepted


FEATURE RESULT


Page A-24


7.3 Silent Intruder Detection

Join an unattended conference with PNR enabled. Do NOT record your name then verify that the system plays the message “Name Not Recorded.” when the party is added to the conference.

Comments:

Accepted


8 VoIP8.1 VoIP Dial-In

Using a VoIP phone or application, such as SJPhone, dial into the Summit and ensure that a connection is made and prompts are heard.

Comments:

Accepted


8.2 VoIP DTMF Recognition

Create an unattended conference and verify that DTMF is accepted and parties are joined to the conference.

Accepted


8.3 VoIP Dial-Out (Operator)

Create an attended progressive conference and ensure that the operator can dial out to parties and join each to the conference.

Accepted


FEATURE RESULT



CONTEX Web™

Installation Test Procedure

8.4 VoIP Dial-out (Host)

Create an unattended progressive confer-ence, dial in as the Host with a VoIP phone and ensure that the Host can dial out to additional (PSTN) parties.

Accepted


FEATURE RESULT1.1 Creation of Accounts

Create an account using the CONTEXWeb Administration Utility and ensure that set-tings can be saved. (Skin Dependent)

Comments:

Accepted


1.2 Log into CONTEXWeb Session

Depending on current skin, verify that an account or conference is set up properly and ensure that a user is able to log in.

Comments:

Accepted


FEATURE RESULT


Page A-26


1.3 Dial Out to Host Phone

After logging in, ensure that the Host phone can be connected by following the Web instructions.

Comments:

Accepted


1.4 Dial Out to Participants

If available on the skin, ensure that the CONTEXWeb user can dial out and join a participant to the conference.

Comments:

Accepted


1.5 Updated Conferee List (Dial-out)

Add parties to the conference through CONTEXWeb. Ensure that the conferee lists is updated and matches the parties shown at the WOC.

Comments:

Accepted


FEATURE RESULT



SignaturesCompunetix Engineer:________________________________________

Signature Date:_____________________________________________

Customer Witness:__________________________________________

Signature Date:_____________________________________________

By signing this document, the customer witness verifies that CONTEX Summit has been satisfactorily installed and has been demonstrated to successfully meet the criteria of this Installation Test Plan, thereby acknowledging system acceptance.

1.6 Updated Conferee List (Dial-in)

Dial in and add parties to the conference. Ensure that these parties are added and dis-played correctly from the CONTEXWeb skin.

Comments:

Accepted


1.7 Basic Skin Functionality

Test basic conference functions that are available in current skin. Ensure that all options works as expected.

Comments:

Accepted


FEATURE RESULT

appendix a installation test plan

Documents