Registering to a Gatekeeper
-Ok, I am writing up this little outline because I keep seeing problems with our gatekeeper registrations for our connections to WSU. These guidelines will work for any gatekeeper you need to register, but I am going to use ours (129.101.195.222) and WSU's (134.121.239.201) as an illustration. I figure if it is here on Blogger, you can find it even anywhere as long as you have an internet connection...which shouldn't be a problem if you are looking to register to a gatekeeper.

MCU REGISTRATION
-Open the MCU webpage (129.101.195.220) and select "System Configuration" from the main menu and then "H.323" from the sub-menu.
-Make sure Gatekeeper is set to "Manual" in the drop-down menu.
-In the Gatekeeper IP Address line insert the address of the gatekeeper that you want to be registered to (134.121.239.201 in this case) and hit the enter key on the keyboard...then wait 10 seconds and hit "Save" at the bottom of the page.
-The box that shows H.323 Gatekeeper Status should update and show the IP number of the gatekeeper you just registered to. If it does not, wait a few more seconds and hit save again. If it still does not work, double-check the IP address you entered into the address field.
-When your event is done return the bridge registration to it's original settings (129.101.195.222).
NOTE: you cannot change the gatekeeper registration if a conference is going, it will either:
-a) fail outright (which is for the best)
-b) boot everyone from every conference in the bridge (which is really bad)

TANDBERG REGISTRATION
-Open the Tandberg web page and select "System Configuration" from the main menu, then select "Networks" from the sub-menu, then select "H.323 Settings."
-Make sure Gatekeeper is set to "Manual" in the drop-down menu.
-In the boxes next to the line that reads "Manual Gatekeeper IP:" insert the IP address of the gatekeeper you wish to register to (134.121.239.201 in this case) and hit enter on the keyboard.
-Scroll down to the bottom of the page and hit the "Update Settings" button. Within about 10 seconds the bottom of the screen should read:
"GateKeeper Status : Registered to gatekeeper. 134.121.239.201: 1719"
I have no idea why the 1719 is placed in the line, but it is there everytime you register to a gatekeeper, I think it may be some sort of check code.
-If the line reads:
"GateKeeper Status: Registering to gatekeeper."
Then that means there is something wrong, either the system is not happy or the gatekeeper IP address you entered is invalid.
-Once you are done with the conference, return the gatekeeper registration to it's original settings (129.101.195.222).
NOTE: You cannot change the registration while a conference is in session.

 
Ceiling mics in Ag104
-WSU complained about the audio from Ag104 this morning. They were hearing a strange buzzing from our room everytime anyone spoke. After a couple minutes of messing around, I isolated the problem. It seems that the ceiling mics are broadcasting a slight buzz when they pick up audio. The strange part is that I cannot hear the buzz at all from the control room, but as soon as I turned the ceiling mics off, the buzz went away.
-The class on Wednesday went off without a hitch and I have never heard of any other site having problems with our audio from the ceiling mics, so this could either be a new problem, or an isolated incident.

 
TF A-21
-I have been having some problems with the TF A-21 room lately. Twice in the last 3 days I have had to reboot the system because it has stopped talking to the network. I am not sure if this is a symptom of something worse or if we just had a hiccup in the system. Whatever the case may be, TF A-21 had some problems today in the PLSC 302 connection. It dropped in the middle of the conference and after I connected it again, it dropped within 30 seconds. After I connected it a second time, everything seemed to work.
-At the moment the connection seems to be stable once again, but I am writing this so we have a record of some recent problems if everything goes wonky on us over there.

 
PLSC 404, 8/21/06, The instructor, Steve Love is in Aberdeen, the audio has a loud audio hum, the instructor sound like he's speaking from a tunnel. One of the students has hearing problems and cannot totally decipher what the instructor is saying. Steve maybe is standing on the other side of the audio science mic? Is there a podium mic or a lapel mic that he can use, instead of the room mic? ph

 
multipoint test
Mike and I tested calls via the multipoint in Ag104 after testing I think we could put a tandberg
non multipoint in Jeb. but CNR , Ed 103 could use them.

 
Hi all.
Did a test with Hawaii to day, They could not connect to us but we Can Call them with no problem
The ISDN# is (808) 449-0237 James Hamidou (808) 449-0202 cell # (808)3687853
Thank you

 
Alan Odenburg, Interiors shop has ordered matching laminate to repair tables in Ag 104. He said when the laminate comes in he'll plan to come into Ag 104 at 6am to complete the task. ph

 
Testing with WSU.
-I tested connections with WSU on Monday afternoon. I was able to connect Ag104, Ag323, and Ed103 to their system. All of the connections were established with full audio and video, and WSU would prefer it if we could connect at 768 kbps for the courses.
-To connect to WSU, the codec you are using needs to be registered to WSU's gatekeeper and then dial an alias number. The gatekeeper IP address is 134.121.239.201, and they will provide the number we need to dial for each class just before the semester starts (they are working on some last minute changes).

 
Testing with MSU.
-I tested with MSU on Monday afternoon. The connection was stable with a solid video and audio link-up. The connection will be an IP call between MSU, CNR 14, and several other sites; with MSU bridging the call.
-The contacts for MSU are Nadeen (406)994-6553 (she will be the main operator for the course), Bob (406)994-6839 (I believe he is a back-up operator for this class), and the secretary who can find either one of them if you aren't having any luck with their numbers (406)994-6550.

 
Tested with University of Wisconsin today. Dialed IP address 128.104.44.234, connection was fine, video and audio stable.

 
Tested with Boise on the Grove. I worked with Chris and Noah to get the rental unit (Polycom codec) up and running. The current IP address given and used was 207.170.244.25. This is for the event on Thursday broadcasting from Ag104 to Boise. Paula with operate this event, but Daryl should stay close until the connection has been made and is solid.