Friday, August 29, 2003
Looks like my fault on the Sandpoint dial. I must have got the dial direction wrong in TMS.
- matt.kitterman@gmail.com, 7:38 AM
Thursday, August 28, 2003
Hey Paula, I played with the CG today for about 15 minutes. I didn't have any troubles, but I was not trying to do anything complicated.
Some trouble at Aberdeen:
Jodie reported--and I heard it too--that instructor audio from Aberdeen during the PlSc 4/590 class sounded distant. Perhaps the podium microphone needs adjustment. Also, Kristi reported today that their student camera has been broken for at least a week--it will not pan, tilt or zoom.
- matt.kitterman@gmail.com, 2:08 PM
Hi Mike! When you are up in Ed 103, would you check out the Character Generator? For me it has been freezing and rebooting itself. Let me know if you have problems. I was able to work with it for 15 minutes a few days ago and now it seems I can work for a minute and it reboots itself. It could be impatient operator error! Please let me know if you have success!! Paula
Monday, August 25, 2003
Today's AVS 474 between Ag and TF1 had totally awesome video. The codecs were able to use isif resolution at 768 Kbps. We do, however, still have a bit of trouble with echo from TF.
- matt.kitterman@gmail.com, 3:14 PM
The report from WHETS Network Ops is that today's bandwidth problems between UI and WSU were caused 'mostly' by a denial of service attack. They think it has been cleared.
- matt.kitterman@gmail.com, 3:07 PM
All point to point CV connections will be dialed by Moscow to the Distant Site. Please see exception below!
Any MCU connnections will be connected by TMS, Moscow. Ask Matt if you have questions, 5-7945.
TEMPORARY EXCEPTIONS:
If Aberdeen is involved the meeting/class, they will dial into MCU 1.
If Sandpoint is involved they will dial into the MCU Assigned.
Due to current billing issues do not dial Aberdeen or Sandpoint.
Friday, August 22, 2003
TF is unable to access their codec via web from TF1 podium computer.
- matt.kitterman@gmail.com, 4:06 PM
Tested the connection from TF to Pocatello. Neither was able to direct connect to the other. Poky requests that we route the Wednesday night 6-9 class through the mcu. Jodie will be submitting a request for the mcu.
Yesterday had some trouble connecting to Twin Falls. The best bandwidth that their codec could negotiate was 194 Kbps or 256 Kbps. They were unable to connect at 384 for a time. Today I talked to Kurt Smith about the T1 clog. He looked at the circuit log and said that there was a spike in traffic at the time we were having trouble and that was probably what caused it. He also noted that at this point we are in the 'best effort' phase of videoconferencing on that circuit--we have not implemented any Quality of Service yet. Mark Quigley says that there is to be a new router installed at Twin and that will likely be the time to start setting up QoS. Mark is contacting the TF sysad to confirm duplex and speed settings on the TF router. He is also updating the DNS entry for that codec.
All classes going through JEB 111, we want to try to channel them throught the MCU, even if its a point to point call. One of us will go over to JEB 111 and get the class started and then monitor it here in Ag Sci 6.
Tuesday, August 19, 2003
CNR control room computer has been de-wormed (have to get it to stop hunting mice) and it's port has been re-enabled. I moved the monitor to an unswitched power outlet so that it will be more apparent when the computer is actually turned on. Both CNR computers are now windows and virus scan updated.
- matt.kitterman@gmail.com, 9:41 AM
New wireless mic is now installed in CNR. It works well and is a better design than the old one.
- matt.kitterman@gmail.com, 9:39 AM
Thursday, August 07, 2003
The new IP addresses for Twin Falls are:
Twin Falls 1/2: 129.101.165.106
Twin Falls 3: 129.101.165.126
Please update your address books, directories and favorites lists.
- matt.kitterman@gmail.com, 4:23 PM
PRI to Twin Falls is now disconnected. All calls to Twin are now IP only. Tested with two concurrent calls at 768 Kbps--one to TF2 other to TF3--and it looked solid. There was no measured packet loss or jitter. SNMP traffic (TMS) now passes to TF.
- matt.kitterman@gmail.com, 1:39 PM
Did more stress testing on the UI-WSU gigalink yesterday. Ran 4 calls at 1920 Kbps and one call at 768 Kbps simultaneously with no trouble. Also ran 4 calls into our MCU at 1920 with no trouble.
- matt.kitterman@gmail.com, 1:28 PM
|