I spoke with Megan at Twin Falls today. Here is a contact name for the evening classes at Twin.
Chris, 308-5191 (Jodies work cel #)

Megan set the audio to the standard levels, the levels were too low, Chris had to turn them up.
With the new mic we may need to have a new set of "standards".

 
I bet everyone already knows this, but the video switcher in Ag 104 is dying (I swear I heard a death rattle this evening). The switcher bar is buggy, and the auto transition key is wierding out on me right now.

 
The box that switches monitor/keyboard/mouse between the two computers in the Ag control room seems to be broken in the mouse section. For now there are two mice for the two computers--the monitor and keyboard are still switched in the old way.

 
There was an apparent spontaneous reboot of the MCU today at approximately 1350. I do not know if there was a power interruption or something else.

 
I ran a couple of test calls with the CAMBR Post Falls site. The first call I ran JEB 28 - MCU - PF at 768 kbps. There was no trouble staying connected. Packet loss was generally around .5%:

I also tested point-to point Ag 3 - PF. In that test the codec was indicating 1-2% packet loss. I was seeing considerable freezing and tiling on the local video from PF. PF user reported that incoming video was perfect, except for the smudges on the our camera lens.

I ran several trace routes to Post Falls during the test. Some of them showed not-too-bad latency throughout the trace while others showed extreme latency at the CAMBR gateway. I don't know how valid a trace is when it traverses a NAT as it does here. I am not even really sure of trace route validity for analyzing H.323 issues, but it is about the only tool I have.

Time of day could influence this connection: one would expect worse performance later in the day when there is more traffic on the net.

 
We heard some retransmit echo from Twin Falls 1 today in PlSc 501. It was not as bad as it was before but it was worse than when we tested on Tuesday.

Also, I think I am hearing some retransmit from B1, though Ryan says the incoming audio volume is not high.

 
H.323 IP connection to B2 seems to be poor. In today's LCSC-bridged Park and Rec meeting the LCSC tech reported that they were only managing 192 kbps on the B2 connection. I tried to bridge B2-Ag1-LCSC but it did not go through. I then bridged it using the UI MCU to connect B2 and Ag1 to the LCSC MCU. While the B2 connection was able to maintain a 384 kbps pipe, the video was poor quality, barely useable. The MCU reports 1478 (sic) ms jitter and about 1.2% packet loss on the incoming video. Outgoing video shows jitter around 30 ms and 0% packet loss. Luckily the audio was not too bad: though there was significant audio artifacting, it remained intelligible.

 
Had a problem with TF A this afternoon. I connected with that IP at noon and had no problems, but a later connection (to a different room, but same IP) lead to some sound problems. I had the audio cranked up to a high level, but the Twin Falls sight said they could barely hear us. I tried a few changes, but nothing seemed to work. I am not sure if they talked to the local tech person or not (I forgot to check), but I tried to call a bunch of the numbers we have on the phone list and I could not get a hold of anyone.

 
Parma was able to dial in this morning following mcu reboot.

 
More apparent PRI trouble: Casey reported he was unable to dial in on ISDN for ME 412 today. He did a test call to his CdA site and it went through okay. I tried to call to the mcu from Parma and the call never even started to come in at the mcu. May be related to the CdA2 green screen thing Mike reported yesterday. I will reboot the mcu at the next opportunity and test again.

 
Had a strange problem in Ag 62 this morning. Throughout the meeting, the audio kept making a strange popping sound. I tried muting all of the sites, but the sound persisted. I did not notice any link between the popping and any other audio phenomenon (ie, did not pop when specific site spoke, when screen changed, etc.). I also could not identify any sound in my room which may be causing a feedback which was popping. The popping was not particularly loud or too distracting, but it may be something to keep an eye on.

CDA was also doing the green screen thing again.