I have moved the small (Marshall) LCD monitor bridge in CNR to a switched outlet. It will now power on and off with the rest of the rack i.e. you no longer have to swing it open and switch it separately.

 
Got a couple of 'temporary network error' disconnects today trying to connect to TFA at 768 while the TFB codec was in a call. After the second disconnect I tried at 384 and it stayed connected. I talked to Mark Q at the time and he saw no explanation. The graph of the traffic looked normal--there was not enough load on the line to cause the problem.

Mark and Kurt S are both aware of this blog now. So is Google. Members are: Michael Costa, Dan Fitzgerald, Matt Kitterman, Daryl Power, Jodie Mink, Don Saraceno, Anita Mackey, Paula Heaton. Don't forget to publish your posts--if you just post them not everyone can see them.

 
Boise continued....Got a call from Anita, Law 215 unable to connect to B3. Ip'd into the B3 codec and attempted it myself. Same problem, not able to dial out from unit. Called Erin and found that the patch cable was into B2, swapped to B3.

 
Matt, I see that we're still having problems with the TF connection. Has there been any recent discussion with ITS regarding this? Are you aware if we're still @ level 3 priority?

 
All connections to WSU went well this week. Yay!

 
Thanks Mike, I'll pass on your post to Dave A at Idaho Falls. There may be some reason he has bandwidth to that codec restricted.

On another Idaho Falls note, I have been seeing reduced frame rate video from IF2. Video from there is extremely jerky. I have not been able to find any reason for this in the codec settings. Has anyone else noticed this? I assume it is not just that people in Idaho Falls are jerky.

About the Twin Falls connection, I fell down on two counts. That connection should have been cancelled but I must of overlooked that, and I should have let you know. Sorry about that. CSI is handling the connection from now on via ISDN so our codec is not involved. Looking at the traffic graph for the UITF T1 line at NMS it looks like there is spike in traffic to TF running from about 1930 to 2100. Perhaps there was someone doing a big download at that time. I am running a class to TF right now at 768 Kbps at isif resolution and it looks awesome.

 
While I was monitoring PLSC 490 tonight, I saw that Idaho Falls was only connecting at 256 kbps. Boise also dropped out early (16:30) but I think this was because there were not students from Boise there.

Later, I again had the problem with Twin Falls of a slow connection speed (192 kbps).

 
I have changed the Echo Control Parameters on the Twin Falls A codec so that the echo problem from the classroom is reduced. I do not know how this will sound when the codec is used in the conference room so please listen carefully to received audio from conference room: We may need to re-adjust the echo control parameters if the new settings don't work in there.

 
More trouble at WSU network this morning. Call bandwidth rapidly became restricted down to 192 Kbps. Class was able to go through even though video quality degraded.

 
Mark Q called this morning about exprimenting with some QoS settings on the UITF circuit. We will be trying some Level 3 settings today starting at around 1300. It should be a good time to stress the system a bit since we will have two concurrent calls to TF going from 1330 to 1430. Usually I run that class at 768 Kbps and I may try that today. My understanding is that we should be able to do that--768 for a class, 384 for a meeting, the rest for regular internet traffic. Is that correct?

 
I had Mark Q on the phone while we were having the bandwidth clog yesterday (up to about 1360 Kbps going to TF). He changed some settings (buffer capacity, I think) while the clog was happening. At about that same time the traffic spike declined, possibly because Jodie was running around pulling the plugs on peoples' computers. :-) For one or both of these reasons the video bandwidth improved and packet loss declined and the meeting was successful from around 1600 Pacific. Last night's class was successful, I think, so we are batting .300 on that one.

 
Mike--No guarantees with babies? Shoot, they don't even come with instruction manuals! I'll let Casey know you'll be monitoring from Ed.

 
Matt--I don't have my mobile phone right now, and I am not sure when I am going to get it back. I gave it to my brother to use until his baby is born (so that his girlfriend can get a hold of him at any time to take her to the hospital). Baby is supposed to be born this weekend, but no guarantees. Instead, we may want to give them a room number (Ed 103) and I can be sure to be there to monitor.

 
Mike/Jodie--It looks like our mcu conference started a little bit too early, before the ISU mcu had built its conference to accept the call. Poky only allows incoming calls at 5 minutes before start time and our clocks may have been off by a bit. I talked to Casey and gave him Mike's mobile phone number--he now knows we are monitoring the mcu (apparently his boss told him we weren't).

 
The sites in MPH 502 are ISU-Pocatello and Twin Falls. I'll forward your post to Casey in Poky to see if he has any thoughts. Jodie--do you know if class ended early?

 
I was monitoring a class running through the MCU tonight (MPH 502 6-9pm) and I noticed that Idaho Falls was again connecting at only 192 kbps. Don't know why, and I am not sure if it messed up the class or not (at least no one called me about it). Could be that no students showed up. The monitoring screen turned black at about 6:20 (I think everyone went home), but TF was still connected.

 
Regarding today's mis-connect to B3 for the ME dept mtg--I had changed the site to B1 in TMS by way of the Conference Control Center but it apparently did not 'stick' in the event database. It seems that this way of modifying an event does not always work. Modifications do seem to work when you go in through Booking and Edit an event. Also, be aware that TMS will always try to connect over LAN first. Something to look out for when adding sites on the fly.

 
The UI-WSU link looks good both directions (for the first time since the semester started). It seems that WSU found the problem on their end.

 
Jodie--The only traffic investigation I can think of is to talk to the TF network sysad and see if she/he can explain it. If you can get me a name I can pass it on to Kurt Smith (the network guy up here).

 
Looking at the graph of traffic on the Twin Falls T1 line I see a spike from about 1420 to about 2020 yesterday. This spike ran at about 90% of line capacity almost that whole time. Really more of a plateau than a spike. This is certainly what clogged the pipe and made the TF connection last night run badly. Does anyone know the name of the TF sysad? I wonder if we should contact him/her and see if it is possible to find out what caused the traffic spike.

 
The audio from TF classroom has always been a problem. The trouble comes mainly from the mic/room configuration. There is little the operator can do to fix it. I also think part of the trouble results from sharing the codec between two dissimilar rooms. I have brought the issue up many times and Don is aware of it. Muting the system whenever possible is the correct short term solution. Another possible short term fix is to schedule as many classes as possible in the TF conference room.

 
Ag 416--TF2 has a problem tonight (M@ knows about it already), they could only connect at 192 kbps. This was a headache, but workable (Paula, they will be calling for a copy of the video). They also have a second problem--their audio stinks. I think the controller in the room has no idea how to mute the mic. So, I mute the system for them. The obvious problem with this is that they cannot ask questions whenever they want to. He needs to be taught/shown how to use the basics of the system--or he needs to be refreshed.

 
The scan converter in Ag is now controllable from the control room computer. Scanned computer video position, size, zoom, pan, etc. can be adjusted via the CORIO Control Panel program, accessible from the desktop or Start Programs list.