| |
Friday, August 27, 2004
We can set MCU call duration in the Conference Configuration page. This can be changed on the fly, after the conference is already up. The call duration is in minutes so you will have to do a little arithmetic to get the call to drop at the proper time.
I apologize for not bringing this up sooner.
- matt.kitterman@gmail.com, 8:31 AM
Thursday, August 26, 2004
#^<&***!!! GRIP software is down in Ag control room. It is not finding the com port that lets it talk to the router although the computer thinks the com port is working fine. The only way to control the router is via the control panels.
- matt.kitterman@gmail.com, 3:30 PM
Wednesday, August 25, 2004
I have updated user accounts and settings on the two Ag control room computers. There is now a generic 'operator' account and an account for Mike on both machines. Unfortunately, to use Grip on Carrot, these users still have to fight their way through a MS Office installer malfunction BUT at least Grip will now work after that is done (click Cancel about ten times). I have also added a Codec Control Links Page to the desktops of these accounts. All operators should have commonly used codec links in their Favorites lists. Let me know if these account settings don't work.
Monday, August 23, 2004
The WSU connection issue seems to have been resolved. Trace routes on Thursday indicated that the gigalink was down. ITS reported that the link had been turned off at the WSU side. Friday ITS got them to turn it back on but we were still seeing packet loss. I initiated further testing with WSU, connecting 5 codecs concurrently to UI, while ITS checked the UI network back to the gigalink. UI network to gigalink tested fine. Video testing showed the problem was specific to WHETS codecs in Murrow Hall, since connections to other buildings seemed to be fine. WSU sysad said ping data showed network problems and that they had made some changes that were likely causing the problem. I think these changes were part of the reason that they had turned off the gigalink previously. WSU sysad was able to locate the party that had made the network changes and get them fixed. Testing at 1700 on Friday showed a clean connection.
It has been brought up that this may have been cutting it a bit close to the start of the semester for network testing. That may be true. But if we had tested before the network had been changed, say two weeks ago, then we may have been thinking everything was fine until this morning when classes started. Probably early testing, combined with testing if the network changes, would be a good way to go. As it came out, I am happy that we tested when we did and were able to get resolution prior to classes starting.
- matt.kitterman@gmail.com, 7:48 AM
Thursday, August 19, 2004
TMS is still down, victim of a software upgrade. We have decided to give Todd the server monkey another week to work on it with T-berg before we give up and go back to the previous software version. So: All meetings, including MCU meetings, will have to be manually connected until further notice.
- matt.kitterman@gmail.com, 2:32 PM
Some H.323 issues today:
1) In the meeting with Utah State and Moscow Ag 1 from 0830 to 1000 there were repeated connection drops, even when we forced the meeting down to 192 kbit/S.
2) While testing to WSU from 1200 to 1230 the Moscow Ag 3 codec indicated significant packet loss of 1-5% on receive video, resulting in considerable freezing, tiling, etc on Moscow's incoming video. WSU reported that their incoming video was fine with no packet loss. I am not sure if the Moscow Ag 3 codec is correctly listed for priority video traffic in the packet shaper as I think the IP address may have changed on that codec since I last gave the network monkeys a codec list.
3) I ran a test call to Idaho Falls 1 over IP. The connection was unable to sustain 384 kbit/s and was quite blocky. This is typical of IP connections to IF, including the IP-only rooms IF4 and IF5.
- matt.kitterman@gmail.com, 1:37 PM
Thursday, August 12, 2004
Endpoint software upgrades done today: Twin Falls A and Twin Falls B.
Tuesday, August 10, 2004
Endpoint software upgrades done today: Moscow AEE, Moscow Ag 2 (Ag62), Moscow FCS (Niccols).
A note on software upgrades: The upgrade disables the Web Snapshot feature. This feature can only be enabled at the codec (under >Menu>Utilities). Please check to see that Web Snapshots is turned on when you are operating a codec via the remote.
- matt.kitterman@gmail.com, 8:36 AM
Monday, August 09, 2004
Endpoint software upgrades done today: Moscow Ag 1 (Ag104), Moscow Ag 3 (Ag 6), Moscow CNR (CNR14), Moscow Ed 1 (Ed 103), Moscow Ed 2 (Ed301), Don's.
- matt.kitterman@gmail.com, 1:20 PM
We were unable to connect point-to-point ISDN from Ed 301 to Boise 1. The call would only negotiate at 64 kbit/s on H.221 protocol. I ran the connection through the MCU going IP to Ed and was able to get a normal ISDN connection to Boise.
- matt.kitterman@gmail.com, 9:05 AM
I have upgraded the MCU software. Here is what T-berg says this will do for us:
4. New Features in D3.3
4.1 Web Call List Timeout
It is now possible to enable/disable disconnected participant timeouts from the Web participant list during an ongoing conference. To disable the participant timeout simply uncheck “Timeout Participants from Call List” when creating the conference. If disabled, disconnected participants will remain in the participant list for the duration of the conference. This feature is enabled by default and disconnected participants will be removed from the list after 2 minutes.
4.2 Video Mute Participant
It is now possible to mute incoming video from a participant. When muted the participant will still receive video but will not be visible to other participants in the conference. To use this feature simply press the new action button located in the participant list on the Web page to mute video and the action button to un-mute video.
5. Changes and Improvements in D3.3 from D3.2
· Increased size of Web participant list
· Improved video stability
· Improved audio handling during ISDN disconnection
· Improved handling of long site names
· Improved stability under heavy load
· Improved video robustness to allow for QCIF in CP layouts
· Improved handling of Duo Video
- matt.kitterman@gmail.com, 8:19 AM
Thursday, August 05, 2004
The initial H.323 connections in today's PSES meeting in the MCU showed restricted bandwidth. There was no difference between IP endpoints on or off campus: Moscow, Twin Falls and Idaho Falls initially showed connection speeds at 364 kbit/s, fluctuating and dipping down to about 264 kbit/s before eventually rising to 384 and stabilizing there. Call initiation was at 0720 and fluctuating call rates occured from then until about 0728. Idaho Falls 4, however, never came up to speed, eventually settling at 192 kbit/s. Over the duration of the call (from 0720 to 1100) IF4 packet loss as reported by the MCU was 0.5 to 0.8% for all bitstreams except Video Out which was at 3%.
- matt.kitterman@gmail.com, 9:30 AM
|
|
