Problem with reflector/mbone

Michael Benson (mbenson@davinci.gmu.edu)
Sat, 25 Feb 1995 00:32:19 -0500 (EST)


I am setting up the reflector on an SGI connecting to the mbone.
Currently I:
1) Have successfully compiled the reflector
2) Have been unable to get it to rebroadcast a VAT session. (I have
not tried NV).

When I connect to the reflector with a MAC IICi, I get a very short
pop on the MAC but no sound. I look in participants window and can see
the VAT session. What am I doing wrong?

Below is my reflect.conf and my reflect.log files.

Michael
(P.S. The Mac can hook to other reflectors and get audio and video.

--------------------------------------------------------------------------------

; Cornell Reflector Version 3.0B1

; CHANGES SINCE LAST VERSION:
; added new 3.0 commands, fixed some spelling errors.
;
; DESCRIPTION:
;
; Sample CUSM Reflector configuration file created by Paul Troutman
; (ai456@yfn.ysu.edu), 12/17/94 5:37am, for private administrative and public
; video conferencing. I created this file for my own personal ease and use, but
; it may be helpful to you and other users to in the process of setting up
; your reflector. You can use it anyway you need to.
;
; Excerpts from Reflector 3.0B1 README file by John Lynn (jal7@cornell.edu)
; and the CUSM Team from Cornell University, that I do not represent.
;
; If you wish to use this config file, first make a backup copy of your old
; reflect.conf. Then rename sample-reflect.conf to reflect.conf, uncomment
; whatever you need, and edit the file to add your site-specific information.
;
; SUGGESTIONS (for the CUSM team):
;
; Reflector team:
;
; Would you consider using this config file, or one like it, in the next
; Reflector software release? It saves time.
;
; PC team:
;
; Would it be possible to implement a "Mac-like" reflector file for the PC?
; Clearily, more than five reflectors are active at one time. :-)
;
; Michael Sattler's reflector list is great asset for CUSM on the Macintosh.
;
; If standardizing the same format for the PC, we could all have the benefit's
; from Michael's list, and we would have the bonus of reflector file
; compatibilty with the Mac.
;
; If you looking for some ideas on audio over TCP/IP and Winsock,
; take a look at IVC10.ZIP (Internet Voice Chat), availble from these and
; other FTP sites:
;
; ftp.execpc.com /pub/win-stuff/winsock
; freebsd.cdrom.com /.2/SimTel/msdos/winsock
; ftp.cyberspace.com /pub/ppp/windows/utils
; ftp.clark.net /pub/muddy/bandwith_theatre
; ftp.ibp.fr /pub3/pc/win3/winsock

;DEBUG
; [useage: uncomment to enable]
;
; Specifying DEBUG causes the reflector to print out a
; large amount of debugging information. This information
; is probably not particularly meaningful to anyone but
; the reflector programmer and will slow down the
; operation of the reflector, so DEBUG in general should
; not be added to the configuration.

;SELF-REFLECT
; [useage: uncomment to enable]
;
; SELF-REFLECT causes the reflector to send your own
; CU-SeeMe stream back to you. This also is a sort of
; debugging aid, allowing you to make sure your reflector
; is up and running.

;REFMON
; [useage: REMFON ip-addr ]
;
; REFMON is used to specify the IP address of the UNIX
; workstation that is allowed to access the reflector
; using the refmon application. If no REFMON is specified
; in the configuration, then a refmon application running
; on any workstation will be allowed access to your
; reflector. If the IP address is specified as 0.0.0.0,
; then no refmon anywhere will be granted access. The
; refmon application is documented later on As refmon
; can be used to kill the reflector, it's probably best
; to include this parameter in all configuration files.

;CONF-ID
; [useage: CONF-ID conference-id msg-string //]
;
; Specifying CONF-ID allows you to have a measure of
; privacy on a public reflector. In any Mac version of
; CU-SeeMe above 0.70 or any PC version above 0.34,
; the application will allow the user to optionally
; specify a conference id when opening a connection. The
; default conference id is 0 which is also the reflector's
; default conference id. When the reflector is
; configured, defaulted, or set to zero all user
; configuration ID's are accepted. If the reflector is
; configured with a conference ID other then 0, then any
; incoming CU-SeeMe conference id must match the
; conference id in the reflector. If the conference ids
; do not match, then that participant is not added to the
; conference. To have a private conference, without
; uninvited participants, you would pick a random
; conference id, add it to the configuration file,
; make this number known to all of your invited guests,
; and ask them to specify this conference id when
; connecting to the reflector. The conference id is in
; the range from 0 to 65536. The msg string is an ascii
; string terminated by a carriage return followed by two
; back slashes. This is the string that will appear on a
; participant's screen if he tries to connect with the
; wrong conference ID. Also see CONF-MGR below.

;CONF-MGR
; [useage: CONF-MGR ip-addr]
;
; The CONF-MGR ip address, is the ip address of a
; participant that is permitted to set the conference id
; when he connects. This allows a designated participant
; to dynamically establish a restricted conference
; without having to manually reconfigure the reflector.
; When the conference manager connects to a reflector he
; can specify a non-zero conference ID number. All
; participants currently connected with this correct ID
; number will remain connected. All participants
; currently connected with the wrong conference ID or
; zero will be disconnected and the message string that
; was specified in the CONF-ID configuration parameter
; will appear on their screen (or they will have their
; sending halted, for ID > 32768). All future connection
; attempts will also have to contain the correct
; conference ID The conference ID remains in effect until
; the conference manager resets it to another number or
; perhaps 0 to make it an unrestricted conference.

;CAP
; [useage: CAP cap hold-down-time msg-string //]
;
; CAP is used to enforce transmission rate limits for
; those participants that connect to your reflector.
; If a participant sets his maximum transmission
; rate above the cap that you specified he will
; automatically be disconnected from the reflector and
; prohibited to reconnect for the specified hold-down-time.
; Cap is specified in kilo bits per second and hold-down
; time is specified in minutes. The default value for
; cap is 80 kilo bits per second and the default
; value for hold-down-time is 1 minute.

;ADMIT
; [useage: ADMIT ip-addr msg-string //]
;
; ADMIT is another mechanism you can use to limit the
; participants in a conference. By adding an ADMIT IP
; address line for each invited participant, the
; reflector will restrict the conference to only those
; participants who have an IP address which matches one
; of the IP addresses specified by an ADMIT line.
; The msg string is an ascii string terminated by a
; carriage return followed by two back slashes. This
; is the string that will appear on a participant's
; screen if he tries to connect but he is not on the
; admit list. Currently, there must be a message string
; specified with each ADMIT in the configuration file, but
; only the message string associated with the last ADMIT
; in the configuration file will be used. For now, that
; means you should just enter in some dummy string for
; each ADMIT in the configuration file except the last
; one. In some future version of the reflector all the
; message strings will be optional so that this nuisance
; will go away.

;DENY
; [useage: DENY ip-address msg-string //]
;
; Deny causes the reflector to deny access to the client
; at the specified IP address.

;MAX-PARTICIPANTS
; [useage: MAX-PARTICPANTS maxallowed msg-string //]
;
; MAX-PARTICIPANTS allows you to limit the load on your
; reflector to the specified number of participants. The
; maxallowed range is 0 to 40, with the default equal to
; 20. The msg string is an ascii string terminated by
; a carriage return followed by two back slashes. This
; is the string that will appear on a participant's
; screen if he tries to connect but the maximum number
; of allowed participants has been exceeded.

;MAX-SENDERS
; [useage: MAX-SENDERS maxsendersallowed msg-string //]
;
; MAX-SENDERS allows you to limit the number of video
; senders on your reflector to the specified number of
; participants. The maxsendersallowed range is 0 to 40,
; with the default equal to 20. The msg string is an
; ascii string terminated by a carriage return followed
; by two back slashes. This is the string that will
; appear on a participant's screen if he tries to connect
; as a sender but the maximum number of video sending
; participants has been exceeded.

;MAX-LURKERS
; [useage: MAX-LURKERS maxlurkersallowed msg-string //]
;
; MAX-LURKERS allows you to limit the number of receive
; only participants on your reflector to the specified
; number of participants. The maxlurkersallowed range
; is 0 to 40, with the default equal to 20. The msg
; string is an ascii string terminated by a carriage
; return followed by two back slashes. This is the
; string that will appear on a participant's screen
; if he tries to connect as a non video sender but the
; maximum number of lurkers has been exceeded.

;LOG
; [useage: LOG filename]
;
; The reflector logs a small amount of information such
; as each participants arrival and departure from the
; conference in a log file. The default name for this
; file is reflect.log. To change the name of this file
; specify the LOG parameter with a different file name.

;LOG-LIMIT
; [useage: LOG-LIMIT log-file-line-limit]
;
; If you have a busy reflector running for several days
; the log file can grow quite large. Use LOG-LIMIT to
; limit the number of lines in the log file. The default
; is 10,000 lines of log information. After the log file
; line limit is reached the reflector will erase the log
; file and start a new one with the same name. If you
; specify a log file line limit of 0, no log file will
; be created.

MOTD

C3I test reflector site.
Broadcasting Mbone sessions.
//
; [useage: MOTD ASCII motd-string //]
;
; MOTD is used to specify the message of the day. In any
; Mac version of CU-SeeMe above 0.70, or an PC version
; above 0.34 the application will display any motd
; messages when a user first connects to a reflector. The
; motd can be up to 800 characters in length. The
; message of the day string is an ascii string terminated
; by a carriage return followed by two back slashes.

;MAVEN
; [useage: MAVEN maven-port]
;
; Use MAVEN to allow the reflector to process Maven audio
; packets. The argument, Maven port, (the default Maven
; port is 3456) is the same port that is used when
; starting up the Maven application. When the reflector
; is configured with MAVEN, all Maven clients that
; connect to the reflector will automatically have their
; audio sent to all of the other Maven clients connected
; to the reflector. In addition any CU-SeeMe audio
; capable participants will have their audio sent to all
; of the Maven clients and any Maven clients that are
; also connected with a non-audio capable version of
; CU-SeeMe will have their audio sent to the CU-SeeMe
; audio capable clients.

;ADMIT-BCC-CLIENT
; [useage: ADMIT-BCC-CLIENT ip-address]