WSU network monkeys seem to have fixed the WHETS H.323 connection issue. WHETS reports that they have straightened the IP path through their building, removing a few hops.

The WHETS connection may still have some issues, however. Occasionally, on a gatekeeper call, their gatekeeper will not be able to find the destination. This typically happens as the second GK call of the day e.g. AVS will go fine at 7:30 but PlSc will sometimes have a problem connecting at 9:00. Restarting our codec and/or their GK clears the problem. Today's calls went through fine. Perhaps the network changes have helped.

I have learned that WHETS changed over to an open-source software gatekeeper last summer. This could be part of the issue.

 
I have a workaround for the TMS-not-seeing-ISDN-capability-for-some-sites problem. This will allow me to schedule Automatic Call Launches for MCU calls for all sites but it may make TMS 'dumber', possibly allowing double booking.

I will start scheduling all MCU calls for Auto Call Launch but we will still need to watch these carefully. I think this will take some of the strain off busy operators at call initiation time.

 
H.323 to WHETS is still bad, the same as Wednesday. WHETS reports that they are looking into it, focusing on their gateway/gatekeeper. Jeff Snell is the investigating WSU network monkey.

WECN had trouble on Wednesday for the INRA class. Apparently Microsoft pushed some upgrades through to their servers which caused multiple reboots. All sites were dropped from their MCU a couple of times.

 
Automatic Call Launch is now partially implemented for MCU calls. TMS does not yet recognize Boise 1, Boise 3 or Moscow sites as having ISDN capability. This is not a problem for the Moscow sites as we normally connect them to the MCU via IP. At this time I am scheduling Automatic Call Launch only for MCU calls that do not involve B1 or B3.

 
Current connection to WSU WECN MCU shows none of the packet loss seen earlier in the connection to WSU WHETS MCU. It seems that the problem seen earlier today is located on the WSU network in the path to WHETS.

 
Chris, the WHETS mcu monkey, reports that WSU network monkeys are investigating errors on their network. My codec is reporting incoming packet loss at 0.5 to 5 percent with occasional spikes much higher. Video quality is K2.0.

 
About the WSU connection issues on Sept. 8: Turns out WSU was under worm attack that day. When I looked at AMP that day everything was flat lined, I assume also due to worms. I don't think they have quite eradicated all the problems over there yet as we still see a few problems in the video, e.g. on the connection going over to WHETS right now it is probably about a 1.8 on the K scale of annoyance (goes up to 5). This connection is normally sub 0.5. WHETS reports losing a switch yesterday so this may be a new issue on their campus, other than last week's attack.

 
Lost ISU-CDA tonight in EdSp 540 just before 7:00. No idea what the cause of the loss was, but the CDA operator said it was happening all day long. I did not call CDA right away, the operator finally called me (she mentioned something about having a hard time finding my number, I don't think they have the numbers in an easily accessible area).

I tried running the meeting through the MCU (no go) and we tried having CDA call Moscow (no go). Apparently ISU @ CDA is having some major issues.

Luckily, I have a tape of the class, so it can be made up by the students.

 
We are having some trouble getting through to WSU today. Rather, it seems that traffic over there is going okay but it is restricted coming this way. At about 9:50 today our connection to WHETS mcu went belly up, with packet loss reported at 70-80%. WHETS operator performed a trace route and saw a problem on WSU campus. A couple of minutes later I did a trace and there was no problem. WHETS operator then did another trace and the problem had cleared. I reconnected and the call was fine.

Connecting to WECN mcu about 10:20 showed 5-8% packet loss. After reboot and reconnect, packet loss is at 1-3%. My last trace shows some packet loss at the gigalink and severe loss at WSU side of link.

I can find no AMP data for WSU today.

 
I had trouble connecting to WHETS for PlSc 320 today. I found that I could not complete a test IP connection to TF so rebooted the Ag codec. After reboot I was able to connect to WHETS. Connection was 7 minutes late.

 
Grip router control software is operational in Ag control room. MS Office is no longer available on this machine. I am still working with Sierra Video and hope to get Office back on this machine in a way that it doesn't get messed with by Grip(e). In the mean time Office programs are available on the other computer (radish).