MCU - Multipoint Conference Unit - Radvision ViaIP 400 Registering to use the MCU -------------------------- It has become necessary to authenticate usage of the MCU now to prevent unauthorised purposes. This is to be done by using your machines IP address and your unique "phone number" code (referred to as an E164 code). I have asked about dynamically assigned IP addresses and what we can do to support them, but at the moment you will have to register them too, so if they are REALLY dynamic and not allocated for a few days at a time they cannot be used effectively, We will use meeting numbers 167 (the 4 screen continuos presence mode) as our default, or 168 (singe screen mode). You should make sure the "phone number" you use to log on to the MCU is likely to be unique number less than 8 digits long and including no spaces or characters other than digits (as that is convenient for other things in the MCU then). Note this number will be your MCU user id number from now on. Its called an E164 number by MCU manufacturers. Please mail the following details (mine in filled in as an example) to vidconf@jvcs.video.ja.net cc it to me a.tate@ed.ac.uk please so I can keep a note of everyone authenticated to date. Do not include any other information in your message please. And try not to quote the information. Cut and Paste rather than doing a REPLY... Your Name: Austin Tate Organisation: AIAI, University of Edinburgh Machine Domain Name (DNS): handa.aiai.ed.ac.uk IP address: 129.215.105.74 E164 number: 502741 Services required: 167 & 168 Setting up Netmeeting to use the MCU ----------------------------------- Set up netmeeting to use the MCU as follows: 1. Go into netmeeting -> Tools -> Options and click Advanced calling 2. Tick the Use the gatekeeper to place calls put in IP address 193.63.106.76 3. Tick the log on using my account name, put in your name. You will conflict with others trying to use the same account name, only the first will be able to connect. 4. Then Untick the log in using account name. 5. Then tick the log on using phone number option and put in a unique number there, a maximum of 8 digits is best as that allows invitations to be issued and the number to IP address mapping to be maintained by the MCU. + does not go in as a symbol but you could use the last 6 or 7 digits of your phone number if its not shared. Note 2 users with the same phone number id cannot log on at the same time. 6. Leave this entry ticked. 7. Then so long as you are set up to log on automatically you can just place a call to address 167 (our normal conference number on the MCU) and join in. Up to 4 video source scan be on screen at the same time in this setup. Note meeting 168 may also be used and is for experiments with a single video screen visible at any one time. 8. You can open a web browser and see who is on-line, etc. via URL: Main board: http://193.63.106.71 Backup board: http://193.63.106.72 Notes: a) These IP numbers differ for obtaining the CU status, but the same IP address applies for the gatekeeeper whichever board is in use). b) A bug possibly still in the web page for the status information means that the meeting ID is not passed through properly in the URL. You can type 167 or 168 on the end of the conf_id= URL that is shown. 9. A conference chairman with an appropriate user name and password can lock who appears on screen at any time, and perform other functions. Otherwise in "continuous presence" mode the first 3 people on line will stay on screen, and the 4th quadrant will switch between other participants as they speak.