




10.5. Running the GUI Demonstration (WinSCxDemo) Program
The following procedure describes setting up and running the GUI Demonstration (WinSCxDemo) Program. The GUI Demonstration (WinSCxDemo) Program needs to be started on the server node first and then on all client nodes.
- NOTE:
- If a clocking event occurs while running the GUI Demonstration (WinSCxDemo) Program, the program displays the failure and recovery of the SCbus and SCxbus clock (OKAY or FAIL).
- If not already started, start the Dialogic Service at each node by clicking on the Set Dialogic Service Startup Mode icon.
- Click on the WinSCxDemo icon in the Dialogic Development Package or the Dialogic System Software Folder/Program Group. The SCX160 Bus Adapter Demo window, as shown in Figure 17. SCX160 Bus Adapter Demo Window, is displayed.
- NOTE:
- Start the GUI Demonstration (WinSCxDemo) Program at the Server node first and then at each client node.
Figure 17. SCX160 Bus Adapter Demo Window
The machine name of this node is automatically displayed in the Machine Name field. Enter the number of D/4x (i.e., voice) channels you want to use. The minimum number is 1, the maximum is 16, and the default is 4.
- NOTE:
- The number of channels specified for a client node cannot be greater than the number specified for the server node. If a larger number is specified, the client node will use the number of channels specified for the server.
Select the network interface type used in your client node at both the server and client(s) nodes.
Select the Node Type: (Client or Server). If this is the server node, leave the "For a client node enter its server's" field blank. If this is a client node, enter the name of the server node.
- Click the OK button. A summary of the information entered is displayed, such as shown in Figure 18. Starting the Server Node. At the server node, activate the channels by clicking on the Start button shown in Figure 18.
- NOTE:
- The server node must be started first.
Figure 18. Starting the Server Node
- Repeat steps 1 - 3 for the client node. At the client node, activate the channels by clicking on the Start button. Information, such as shown in Figure 19. Starting the Client Node, is displayed as the channels in the node are activated.
Figure 19. Starting the Client Node
- NOTE:
- The first two digits (e.g., 01) of the 4-digit number (e.g., 0134) appearing before the WAIT_RING message is the channel number. The entire number is also used as the access code that can be entered to play a recorded message (see Step 6).
Figure 20. Server Node In WAIT_RING State
After all channels in both nodes are activated, the WinSCxDemo Program is ready to handle calls.
- To continue the WinSCxDemo demonstration, generate a ring at the client node by making an inbound call.
When a ring is detected, the client node goes off-hook, notifies the server node to play the INTRO.VOX file on the specified channel and displays information such as shown in Figure 21. Client Node in PLAY_INTRO State.
Figure 21. Client Node in PLAY_INTRO State
You will hear the messages on the client node as they are played at the server node, and you can record a message when asked to do so.
Both the client and server nodes display the changes in status when the call is answered, when messages are played and recorded, and when the channel goes on-hook or off-hook.
- To play back a previously recorded message on a given channel:
- Generate a ring on the given channel at the client node by making an inbound call
- While the introductory message plays, dial the access code for the given channel (e.g., 0134 for Channel 1)
The client node retrieves the access code digits and sends a socket message to the server. The server node then plays the recorded message on the given channel (e.g., channel 1).
- NOTE:
- If an invalid access code was entered, a "PLAY_INVALID" status message is displayed. Otherwise, the server node is instructed to play the recorded message and the status changes are shown on both nodes. To terminate the WinSCxDemo Program, click on the Exit button.11.





Click here to contact Dialogic Customer Engineering
Copyright 2001, Dialogic Corporation
All rights reserved
This page generated February, 2002