Hey Mike--I have changed the Disconnect Time for Ent 322 to 1025. You should be safe to connect to Boise any time after that without TMS disconnecting your call. Unfortunately TMS still thinks there is no ISDN capability in CNR so I could not set up an Automatic Call Launch for CE 4/522 without utilizing an MCU conference. You will still have to manually connect that class.
Let me know if this setup does not perform as we expect.

 
New board in Model 60 fixed ISDN connectivity for the MCU. We are back to normal connections for multipoint calls.

 
Mike--I bet I know what is going on with your mysterious 10:30 disconnects. It is because our 'standard' scheduling window runs one hour and 10 ten minutes (1:10) e.g. Ent 322 connects at 9:20 and disconnects at 10:30. TMS Automatic Call Launches (like Ent 322) send a Disconnect command according to the call duration set when the event is entered into TMS. I think that TMS is not smart enough to know that you already manually disconnected, probably around 10:20, and sends a Disconnect command to your codec, dropping you from your Boise connection.
Probably the best thing to do in this case is to shorten the Ent 322 connection so that it drops at, say, 10:25. This will work fine as long as Ed doesn't run more than 5 minutes over. At the same time I think we could set the CE 4/522 class to launch automatically at 10:25. Let me know if that seems like a good plan.

 
The MCU has no ISDN connectivity at this time. Probable culprit is a blown board in the Model 60. We should have a new board tomorrow. We are set for all MCU calls to go on IP Only until tomorrow afternoon but please watch automatic call launches carefully as TMS may still be a bit flaky. Also, some connections may be not so good due to IP bandwidth limitations.

 
This is a recurring issue that has not been a problem until today. Every week, after ENT 322 on Tuesdays, I need to call B1. For some reason, the call hangs up at 10:30 exactly every week. My theory is it has something to do with the MCU, but I don't know. Normally, this is not a problem because class has not started and I just reconnect the call. However, today I was unable to connect to B1 for some reason. I called them and they were able to connect to me--actually, it turns out they didn't even need CV today, but that is not the point. My point it automatic call dropping at 10:30 every Tuesday is annoying.
Please, some technical guru (insert Matt or Don's name here), fix this annoying habit.
Thanks.

 
I have started investigating the Boise 2 issue, but have not yet gotten to the bottom of the problem. I believe all connections via the MCU are good, but I will continue to work on this in the morning. Updates to come.
D-

 
Boise 2 seems to be unable to dial out via ISDN, though it could be that the correct dial strings are not in the B2 directory. What is the correct ISDN dialing protocol for calls from B2?

 
I have turned off Duo Video and People+Content in the MCU Conference Template. If you want Duo Video & P+C to happen in an ad-hoc MCU conference you will need to re-enable it in the Conference Configuration.

 
I have run a few test calls and TMS seems to working fine for automatic call launches at this time. We do seem to be able to edit meetings now as well. Perhaps the upgrade solved some of the troubles we were having. The Monitoring section is improved in new version.
However, since we did have some call-launch problems yesterday, we should keep a close watch on automatic connects and disconnects.

 
A couple of devices have required restarts this week. Yesterday I had to hot boot the gatekeeper because it was not responding to the network. Today Don had to restart the MCU to restore ISDN connectivity.

 
Matt, we pulled the 7350 and found that it had a stretched loading belt. Did not have a new one stock, so we used rubber restorer to bring it back to life until new parts arrive. Working fine at this time, cleaned and lubricated while on the bench. New parts will be order today, replaced as soon as they arrive. On to the VHS deck!

 
Videotape machine trouble in Ag: SVHS 2 will not play back a locked picture. SVHS 1 returns an 'E-4' error when Play is pushed and an 'E-3' error--and a loud noise--when the tape is ejected. Possibly a broken belt. There is no VHS playback capability in Ag at this time.