Law 978 - 4:30 to 5:30

B2 kept fluctuating in signal rate, from a high of 384 to a low of 220. I noticed that it stayed around 268 for most of the meeting.

 
Boise circuit update- Mike Rusca just called to inform me that AT&T has identified a problem directly outside the Boise Center. A technician is working on the trouble call now, and we're hopeful that the circuit will be back up by tomorrow morning.

 
Vid Team- As you all know, I've been working with Madge to isolate the problem with the Boise circuit. Though we had not found any one specific problem, we did find that both the model 60 here in Moscow, as well as the model 40 in Boise had experienced a number of ESF framing errors beginning on 1/26/05. These errors are directly relate to clocking/timing, and is most likely the cause of the problem. Kurt Smith has contacted AT&T and is currently waiting for a confirmation from Boise as to when the circuit can be tested.

 
PLSC 547 - 9:30 to 10:20

The Idaho Falls connection this morning came in at 320 kbps (instead of 384) and it never went up from there.

 
WLF 501--Friday 12:30 to 1:20. Connection between CNR 14 and B2.

The connection today with Boise was awful. The video connection was very broken up and grainy today. Of course, with the ISDN problems, we had to go IP for the whole class session. Everything totally fell apart about 1:05. From then on, the video would freeze, tile, and drop...over and over again. All I could do was keep trying to connect, but the connection would only last for a bare minute before dropping us because the network would fail. What it finally boiled down to was a frozen picture and audio for a few minutes at a shot for the last ten minutes of class.

I am betting the problem was the load on the network in Boise.

 
PLSC 547--9:30 to 10:20 on Friday morning.

Just after 9:45, Idaho Falls 2 dropped to 0 (zero) kbps and started making a horrible buzzing noise. I dropped them (which took longer than it should to hang up the call), then called them again and everything worked fine again.

I have no idea what caused the problem.

 
Bad news fellow UOVNSS monkeys (especially head monkey Don). TF (codec A) is having what I like to call "issues". Tonight, they were involved in the EdAd 527 class with B1 and Ed 2. The conference was a disaster from the start. TF's audio never seemed to work right. I keep getting intermittent calls from B1 telling me they can't hear TF. TF called and said everything was correctly routed there and they have no idea what the problem is. I have no real understanding of the TF room, so I had no helpful advice to offer all those marvelous callers.

Apparently Paula tried to work a little with them too, so she may be able to shed more light on the situation.

BUT! TMS fired the meeting correctly, so I am still happy. :-D

Strangely, I never got any calls from Ed 2 saying they had problems, so I am wondering if everything went smoothly there or if no one knew who to call.

 
I have an idea. Stunning, I know.

I think we should ask each professor at the beginning of the year which type of conference he wants (ie: voice switched or enhanced continuous presence). Probably not using those exact terms unless we like getting blank stares. Maybe something along the lines of "Hey, do you want to see all the classes or do you want to see one class at a time very well?" Then we can also pay attention to the class (a real stretch for me) and give the presenter the floor everytime they use the computer or overheads.

So far, here is my running tally: PLSC 547 wants ECP
EDAD 527 wants ECP
Everything in Jeb 26 wants VS

I only mention this because Don had me switched everything to voice switched, and now I have had two specific requests for me to move it back to enhanced continuous presence.

Luckily, I get paid for all this stuff, so I really don't care how often we switch it. All it means is more experience and more work time for me. WOOT! ;-)

PS--do you guys even know what "woot" means? Not really important, just wondering.

 
YAAAY! The first meeting I scheduled in TMS this morning (let's not talk about the 2 I forgot/didn't know about) fired on time and connected all of the right sites the first time. Today is going to be a good day.

 
CE 421, MWF, 10:30 to 11:30 Ed 103 - B1. 1/19/05 and 1/21/05. Both mornings I've received a message saying corrupted data received, please wait, the the Boise video is frozen. 1/19/05 I disconnected and reconnected and all was fine. 1/21/05, audio was choppy from off campus, I dis and reconnected and video froze, so one more time and all was well the rest of the class. Paula

 
Noticed a minor problem in the Idaho Association of FCS meeting today. This was an MCU connection between 5 different sites (Moscow FCS, B1, IF 1, TF 3 codec B, and ISU/Pocatello). I noticed that IF 1 began with a nice 384 connection speed, then immediately dropped lower, and then dropped again until it rested at 192 kbps. It seems to be pretty happy there now.

 
TMS has, once again, failed to set up a point-to-point conference. This time the connection was between CNR and B2. I looked in the log, and the error message says that a password was provided, but not needed. I have no idea what that means...as usual.

 
This morning we had a TMS connection between Ag 104, IF 2, and Aberdeen (PLSC 547). TMS was unable to connect Ab to the conference, so I tried to dial it in manually...also not possible. Gave the folks down in Ab a call and they were able to connect to us from there end.

 
Well Don, no luck tonight. Adding the 9 seemed to have no effect except possibly confusing the system even further.

Also had problems with the EdAd 527 meeting (5 to 8). TMS had a problem connecting Ed 2 into the system. I ended up manually adding it to the group. Once again, this was a system where TMS said it was IP only but we wanted to connect ISDN. I ended up connecting ISDN by going through the MCU and adding Ed 2.