This has to have been the most frustrating and stressful day I have had since starting with videoconferencing. I had five different connections scheduled for today, involving 15 different schools. All of them involved connections outside the district. And if you have kept up with this blog at all, you know that’s where I have problems.
The first two conferences happened at the same time. The first one involved three schools connected with a content provider, all connected through my MCU. This was the first real multi-site call that we had attempted. And it was the first of 4 set up for the day. The second event was a Connect 2 Texas event and also involved three schools. Because I was already using the bridge and we still have bandwidth issues within the district as well, I had Region 10 connect each school directly. This used 4 out of my 5 available calls on my border controller.
We made it through the 30 minute Connect 2 Texas connection just fine. We did have a few bandwidth issues, but no dropped calls. The other conference lasted a bit longer. During the last 20 minutes the call dropped twice. But the teachers still seemed to be happy with the experience.
After that it all went down hill.
The third conference was set up just like the first one. Three schools and one outside content provider connected through the MCU. From the time it connected, I knew we were in trouble. Before the conference even started, I disconnected the content provider to try to get a better connection. I thought we had, until the presenter actually started. The audio kept dropping and it was hard to follow the conversation. And when the conference is a Q & A session, that’s a problem. I tried everything I knew, and tried reconnecting a couple of different ways and nothing seemed to work. Finally, we gave up and decided to reschedule.
Because I had two more conferences that were set up the exact same way, with the same content provider AND because 4 out of the 6 schools were brand new to videoconferencing, I made the tough decision to cancel them as well. I didn’t want the school’s first experience to be a bad one.
To say that I was frustrated and stressed out was an understatement. To say that I need to figure out what is going on is a bigger understatement!
So, I went to lunch to regain a sense of calm, then came back to tackle the problem.
I set up everything to pull the syslog from the border controller, gatekeeper, and endpoint, and launched a call. The plan was to send the syslogs to Tandberg and have them help me figure out the problem. And par for the course, or Murphy’s Law, or something, the call stayed up for over an hour with no problems. I tired a couple of other calls, and again, not one disconnect.
This was just not my day. To top it all off, I’m posting this at 6:30 on a Friday night, because I couldn’t log in at work! Again, network issues. At that point I had had enough, and here I am.
Next week has got to be better.