Note: Since this program is based upon the Microsoft Foundation Classes, it can only be recompiled by Microsoft Visual C++ V5.0. Other compilers cannot be used.

• CT Access is properly installed.

• The file cta.cfg provided in the package (<NMSDIR\Bri\Cfg\ctabri.cfg) is copied into the directory <NMSDIR>\CTAccess\Cfg to be used as the default configuration file.

• The BX 2000 boards are installed and are executing.

• The AG board or the QX board are executing (optional).

• MVIP bus clocks are correctly configured. Refer to the BX 2000 Installation and Developer's Manual for more information.

• The operation of the BRI service for call control on a BX 2000 board.

• The operations across the MVIP bus.

• The play and record operations on a resource board associated to a BX 2000 board.

The BRI Switching Sample window contains the following buttons:

Button	Description
	Initializes the demonstration program (initializes CT Access and creates the CTA queue).
	Exits the demonstration program.

Note: If ctdaemon is started, tracing in CT Access will be enabled. Refer to the CT Access Developer's Reference Manual for more information about ctdaemon.

1. Connect the BX 2000 BRI ports to the PSTN or a PBX.

2. Run the bxmon tool to configure the MVIP bus clocks. For more information about bxmon, refer to the BX 2000 Installation and Developer's Manual.

3. Start agmon.

4. Launch briswi.

1. If you want to test media functions and switching, select the board in the Media Board section of the BRI Switching Sample window.
   If you do not want to test media functions and switching, go to Step 2.

2. briswi does not specify a service or service manager when it calls ctaInitialize. You must specify the services and service managers in the cta.cfg file. The BRI service provides a default cta.cfg file to use where only the BRI service and BRIMGR are declared. If you use a media board, you may also add a line:
   Service = ADI, ADIMGR
   or
   Service = ADI, QDIMGR
   depending upon the media board type.
   Click on the Initialize BRI button to initialize CT Access. The Extended Arguments window appears:
   This window allows you to set extended arguments. If you close the window, no extended arguments will be set. If you leave the window opened, or minimized, each time a BRI call control function is called, briSetExtendedArgs will be called before with the associated values specified in the Extended Arguments window. Some predefined values are set by briswi.
   If you close this window and then want to set extended arguments, click on the Initialize BRI button to reopen the window.

3. By clicking on the Open Context button in the Incoming Call
   and /or Outgoing Call section(s), you create the In and /or Out CTA contexts. ctaCreateContext, ctaOpenServices, briStartProtocol, and optionally, adiStartProtocol are called at that time. briswi determines which services to open depending upon the media board chosen.
   You can choose the BX 2000 board number (by default, briswi uses board # 0), the stream, and the timeslot (according to the channel assignment described in Section 3.3.1, Specifying B Channel CTA Contexts). Enter the appropriate values in the Board, Stream, and Timeslot fields.
   Note: briswi refers only to the AG/QX board # 0 specified in the ag.cfg /qx.cfg file. briswi uses the same stream and timeslots that are specified for the BX 2000 board. Figure 18 and Figure 19 illustrate the creation of the Incoming CTA context and the resulting events.
   
   Figure 18. Incoming CTA Context
   In the Event History section of the window, the events associated to this operation are displayed:
   
   Figure 19. Event History for the Incoming CTA Context
   Note: The line "In 0x12000 ADIEVN_STARTPROTOCOL_DONE Finished(0x1001)" appears only if a media board has been selected.

1. You can now either:

   
   a.	 Place a call. Enter a Called Number in the Outgoing Call section of the BRI Switching Sample window:
   
   

   b. Receive a call. When the BRIEVN_INCOMING_CALL event is displayed in the Event History section of the window, either accept it, answer it, or reject it by pressing the appropriate button in the Incoming Call section of the window. If you first accept the call, you must then answer it or reject it.

2. At any time, you can see the call status of each CTA context by clicking on the Call Status Info... button in the Incoming Call section or the Outgoing Call section of the window.
   The Incoming (or Outgoing) Call Status Information window displays:
   As soon as this window is opened for a CTA context, it is refreshed when an event arrives for the specified CTA context. Click the Close button to return to the BRI Switching Sample window.

3. When a call is established, if you have specified a media board, you can record or play a message depending upon whether the incoming or outgoing CTA context is active. To activate these media functions, click the following buttons on the BRI Switching Sample window:

   If this CTA context is active...	Click on this button...
   Incoming
   Outgoing

4. Either wait for BRIEVN_CALL_DISCONNECTED or release the call by clicking on the Release Call button.
   If you wait for BRIEVN_CALL_DISCONNECTED, you still must release the call afterwards.

5. To exit the demonstration program click on the Exit button .

Note: The choice of MVIP stream 6 and 7 is arbitrary.