10.4.  Running the Console Demonstration (SCxDemo) Program

The following procedure describes setting up and running the Console Demonstration (SCxDemo) Program. The Console Demonstration Program must be run on the Server node first and then on the Client node.

NOTES:

1. If a clocking event occurs while running the Console Demonstration Program, the program displays the failure and recovery of the SCbus and SCxbus clock (OKAY or FAIL).

NOTES:

2. The only interface type supported is analog. T-1 and E-1 network interfaces are not supported.

3. If not already started, start the Dialogic Service at each node by clicking on the Set Dialogic Service Startup Mode icon.
4. From the Command Prompt:, enter:

scxdemo -n[channel_number] -t[server/client]  
 -s[server_name]

where:

Option	Description
-n	number of D/4x (i.e., voice) channels to use. The minimum 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.
-t	node type - server or client.
-s	server name - alphanumeric name of the server node; enter at client node only.

 
For example:

scxdemo -n4 -tclient -sbigbox


 
starts the demo program with 4 channels on a client node running an analog front-end and the server name is bigbox.

3. A summary screen of the information entered appears on the Server node.

 
Select Y to confirm the choices.
 
Otherwise, select N to exit and repeat procedure from step 1.
 
When Y is selected on the server node, the following message appears:

"Waiting for client connection..."


 
The message indicates that the SCxDemo Program can be started on the client node.
 
The screen in Figure 11.  Console Demonstration (SCxDemo) Program on Server Node illustrates starting the Demonstration Program on a server node with five voice channels, using an Analog network interface, on a machine named KEYBOX.

Figure 11.  Console Demonstration (SCxDemo) Program on Server Node

4. Start the SCxDemo Program on the client node by repeating steps 1 and 2. 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 only use the number of channels that was specified for the server. The maximum number of channels that can be specified is 16. The default is 4.

   NOTE:

   When starting the SCxDemo Program on the client node, ensure that you enter the -s option to identify the server (e.g., -skeybox) as illustrated in Figure 12.  Console Demonstration (SCxDemo) Program on Client Node.

Figure 12.  Console Demonstration (SCxDemo) Program on Client Node

 
After all the channels in the client node are activated, the server node screen displays information such as shown in Figure 13.  Messages Displayed on Server Node.

Figure 13.  Messages Displayed on Server Node

 
Information, such as shown in Figure  14.  Messages Displayed on Client Node, is displayed as each board in the client node is started.

Figure  14.  Messages Displayed on Client Node

NOTE:

The first two digits (e.g., 01) of the 4-digit number (e.g., 0134) that follows the WAIT_RING message is the channel number. The entire number is also used as the access code that can be entered to playback a recorded message (see Step 6).

 
After all channels in both nodes are activated, the Console Demonstration (SCxDemo) Program is ready to handle calls.

5. To continue the Console Demonstration (SCxDemo) Program, generate a ring at the client node by making an inbound call.

 
When a ring is detected, the client node goes off-hook and notifies the server node to play the INTRO.VOX file in the specified time slot. 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 node 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.
 
For example, Figure 15.  Application Status Messages on Client Node, illustrates application status changes that occur when a channel receives a call and records a message:
 
The same status changes are also displayed for the server node.

Figure 15.  Application Status Messages on Client Node

6. To play a previously recorded message on a given channel:
   • Generate a ring on the same channel at the client node by making an inbound call
   • While the introductory message is played, dial the access code for the given channel (e.g., 0134 for Channel 1)

 
The client retrieves the access code digits and sends a socket message to the server node. The server node then plays the recorded message on the given channel. See Figure 16.  Playing Back Recorded Message for an example of the status changes displayed when playing a recorded message on 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.

Figure 16.  Playing Back Recorded Message

7. To terminate the SCxDemo Program at any node, press the Ctrl and C keys.

Click here to contact Dialogic Customer Engineering