Upgraded Idaho Falls 2 codec software to version B7.0 (from version B3.0).

 
Aberdeen codec is back connected to the network. Robert discovered that the IP address on the codec had been changed to match the web IP. Apparently the IP we use to web into the codec is really the IP of the router and the codec has another 'non-routable' IP address. This non-routable address (192.168.0.47) is what had been changed to the web IP address (63.227.132.18). I disabled AutoAnswer to prevent incoming calls while we have billing issues with Aberdeen.

 
Jordan upgraded the Parma codec software to version B7.0 (from version B4.0).
Jordan upgraded the Boise 3 codec software to version B7.0 (from version B6.2).
Jordan upgraded the Moscow Ed 2 codec software to version B7.0 (from version B6.2).

 
Upgraded Moscow Ag 1 codec software to version B7.0 (from version B6.1).

 
Upgraded IF1 codec software to version B7.0 (from version B4.3).
Upgraded MCNR codec software to version B7.0 (from version B6.1).

 
Still no SNMP traffice to Twin Falls codec. This is the checklist TMS generates when it tries to talk to TF codec:
Please Check:
Is the System switched on?
Yes.
Is the System connected to the LAN?
Yes.
Are there more than two Telnet sessions to the system?
No.
Is the SNMP Community Name correct?
Yes.
Is remote administration activated on the system?
I don't know. I can't find any place to turn this on or off.
Has the IP address for the system changed?
No.

 
I have upgraded the Twin Falls codec to software version B7.0 (from version B5.1). One interesting feature of the new software is the Snapshots option. Interesting, but so far useless since I can not figure out how to enable its operation. It may be inoperable until the codec is in a conference. The Snapshots web page incorporates camera source and preset controls so it could be quite useful.

 
Ran some tests yesterday with WSU over the fiber giga link. We had 3 simultaneous 1920 Kbps connections going with no trouble: there was no measured jitter or packet loss or any kind of visible video aberration. We did not get to testing all possible connections but we did connect MAg1, MEd1 and MCNR to three of WSU's codecs: WHETS codec 8, WHETS codec 9 and Holland 24. I think we might want to go farther with load testing. If we include our MCU and WSU's Cleveland 312 codec in a test with the codecs listed above we can run 4 simultaneous links at 1920 Kbps. Then if we can load the circuit with some sort of data traffic we should have a pretty good idea of it's robustness. We should do more testing when we can get data network folks involved who can load and monitor the circuit while we are running the video links. We also need to test cascading MCUs and gateway calls to Engineering Outreach.

 
We are back to manual connections only for all calls until TMS is fixed. I called Eric at Tandberg today but he is on vacation until Monday.

 
TMS appears to be hosed. When I try to schedule or change a meeting I get this useful message: 'You can have a maximum of 0 video participants in this meeting. You have added 3 video participants. Please go back and remove some video participants before you continue'.

 
New dialing instructions per Don/Anita:
For billing reasons, Aberdeen to always dial out to campus.
For technical reasons, off-net calls are not possible from CdA.

 
Frequent freezes from CdA2 in today's meeting. Comment from CdA participant on functionality of meeting by videoconference: 'Next time I'll drive down".

 
Update on ghosting issues in Ed 103. I traded the spare camera for cam 1 then cam 2. The ghosting issue did not change. There was not a camera selected on the camera control box. I selected cam 1 and all the ghosting and blurriness disappeared. I worked with Don on this yesterday, he's thinking! hmmm! Today7/17/03 everything is normal so far.

 
The video from JEB 111 main camera has a 'milky' cast to it.

 
In today's PSES faculty meeting (MAg Ab Par TF2 IF1) we were watching a presentation from Parma. They had selected PC for video source and we were seeing nice SVGA video passed through the MCU. After a few minutes, however, TF reported they were only seeing the main camera. The Parma presenter switched the source so that we were seeing the main cam and moved the shot to the projection screen. This is very confusing to me: how could two sites connected to the MCU be seeing two different video feeds from the same site when Duo Video is not active? Anybody have any clues?

 
Moscow AEE system has an intermittent crackle/click/static problem in the outgoing audio. I noticed it on Tuesday when Anita was setting up the system and I was connected from Ag. It seemed to clear up but Casey in Poky reported that it was a problem in the AEE Internship Review meeting (MAEE ISU(Poc) TF2) yesterday. We will need to check this out, I think.

 
7/10/03, Remember how I said Ed 103 had not had the ghost images for sometime? when I started camera's this 9:10 am they were ghosting, sequence, 2, then 3, then 1. Rebooted cam 1 and 2, shadow still there. Direction of the ghosting on cam 1 is left to right, w/ some ghosting right to left, cam 2's ghosting is right to left.

 
Regarding Blogger:
Don't forget to publish your posts. If they are not published they do not show up on the uovnss blog home page (http://uovnss.blogspot.com).

All control room computers should have http://uovnss.blogspot.com as the home page when you open IE browser.

You may want to set your computer to open this page when you start IE. It is pretty easy to set up: First browse to http://uovnss.blogspot.com. Then click on Tools and choose Internet Options. Under Home Page click on Use Current. Then say Apply and OK and you are done. When you have IE configured this way you can tell at a glance if there is anything you need to respond to. If there is, you can click on the Blogger button and log in and post a response.

 
Thanks Don. Alas, I could not get any video out of the spare camera I swapped for camera 1.