EXAMPLE OF A TYPICAL MTEACH SESSION
 
 

Setting Up the Session Parameters

 
There are three types of users in MTEACH:

 
Before the server is run for the first time, the administrator has to make two files which will reside in the same directory as MSERVER.

The first file is Adm.dat which is a file containing the administrative password. It is created by using a ASCII text editor and typing in one word, the password. For example, the file Adm.dat would contain one line of ASCII as follows:

 
secret_password

 
The second file is Types.dat (click here for the explanation of its format). For example, Types.dat would contain:

 .Audio
vat
rat
.Video
vic
.Whiteboard
wb
.3D Video
3dvideo

This file creates Audio, Video, Whiteboard and 3D Video media types for VAT and RAT tools used for audio, VIC for video and 3dvideo for 3D video media.

Once these files are created, the MSERVER can be started (with or without the extra parameters - see here). An example of starting the server:

MServer.tk port 12067 log 1

This would start the server listening on port 12067 and logging the events (default log file name is Log.dat). If the port and log parameters are not specified, port defaults to 23232 and log to 0 (no logging). Note that in order to run a TCL/TK script file, you have to have TCL and TK installed on the computer running MSERVER (only TCL is sufficient for running MSERVER).The server is now ready to receive requests from the client tools.

The administrator can now execute the MADMIN tool to set up new sessions. An example of starting the MADMIN:

 MAdmin.tk foo.ecn.purdue.edu/12067

This would connect MADMIN to the server running on the machine foo.ecn.purdue.edu listening on port 12067. If no parameters are given, MADMIN tries to open the file Servers.dat which contains the server machine names and ports. An example of Servers.dat would contain the following lines and should be created manually:

foo.ecn.purdue.edu 12067
boo.cc.purdue.edu 23000
fee.ecn.purdue.edu 56790

If Servers.dat is found, the user is presented with a list of these servers to choose from. If not, the user is prompted for the server name and the port number. To actually connect to the server, "Click here to connect" button should be invoked.
The administrator is then prompted for the username and the password. The administrator should enter "administator" as the username and the password should be the one previously entered in the file Adm.dat. If the password is correct, the bottom main window entry (a button) turns into "Connected to foo.ecn.purdue.edu."
A new session is now created with MADMIN by clicking on the Add button, selecting Session and then providing the necessary session information. Here is a sample list of actions which would create a test session named "Test Session":
 

             -m 2 -C "Test Session" -r -Xmoderator=user@host 224.22.22.22/57593          This session is running every day from 13:00 - 14:30. Session moderator is John Doe. Once everything is set, Ok button should be invoked which uploads the information to the server. A similar procedure should be used for entering new users (moderators or students). First click on Add, then select Moderator or User, and enter in the data (see here). For example, click Add/Moderator and then enter the moderator's username (does not have to be the same as the user's email address), password and the names of the sessions he/she moderates. If the moderator is moderating "Test Session" and "EE207" session, one would enter:

 
Test Session, EE207

 
in the Sessions entry field. In the case of students, this field should be filled with the list of the sessions that he/she is allowed to attend. Note that the passwords and the session names are case sensitive, whereas usernames are not.

For reviewing the entered sessions or users, List Sessions (and then Get Global sessions or Get Restricted sessions) or List Users (and then Get User List or Get Moderator List) should be invoked. You can then double click on the session or user name for information (right click to remove the information window).

The session now has the proper information set up, along with the accompanying users and the moderator.


Starting or Joining the Session

 

The difference between starting and joining a session is that when starting a session, the multimedia applications are invoked with the moderator command line arguments by the moderator and when joining a session, they are invoked with the user command line arguments by the users.

When the moderator or the administrator wishes to start a session, he/she can start the MADMIN tool in the same way as described in the previous section, select the server where the session information is located and log in.

To join the session select Session/Join Session instead of Session/Start Session. Students would invoke MSTUDENT first:

 
MStudent.tk foo.ecn.purdue.edu/12067

 
This would automatically connect them to the server running on the machine foo.ecn.purdue.edu. If no arguments are supplied, MSTUDENT attempts to open the file Servers.dat which serves the same purpose as described above. The rest of the student login procedure is similar to the administrator or the moderator login, with the difference being that after the password is accepted, the global session and restricted session lists are downloaded automatically (only restricted session to which the student is permitted to enter are downloaded).

The student can then select the session to join and click on the Join Session button. This will start all the necessary multimedia applications.



 

Asking Questions with the modified VAT and VIC

 
To ask a question, one should press the Question? button located at the bottom of the main VAT window. To enable or disable a student's transmission the moderator should select the appropriate student by clicking on the student's name.

For detailed information on how to ask questions or how to enable a student to ask a question, follow this link.

 



 Click here to go back to the main page