stelring wrote:Yeah, that's what we did at the broadcast point and had it tied to ethernet only.
Also, we were monitoring the connection and it had no issues pushing the data, wasn't even near capacity.
So my guess is the church systems were slammed and couldn't hold connections.
@stelring: if you could provide the date and time when you experienced the connection errors, I can have our engineers look at the webcast server logs and see if there was something specific going on.
You should also know that we are just starting several projects to improve the reliability and availability of the webcast servers. There is one particular server load-balancing arrangement in place right now that has given us some occasional problems which we are replacing, which I'm confident will be a good improvement.
I agree with the other suggestions on this thread to also take a look at PVC. The infrastructure is on completely separate hardware; it also offers the advantage of being based on H.264 SVC (Scalable Video Coding), which is a technology that adapts very well to fluctuating Internet bandwidth. In a broadcast scenario, you'll want to simply mute the audio (or better yet, don't even worry about connecting up audio inputs) at the receiving locations, since PVC is set up as a 2-way communications product but you really only need 1-way in the stake conference broadcast scenario.
Sorry to hear of your problems. Trust me, it's painful for those of us here at Church HQ who manage these products to hear of issues that negatively affect the success of meetings. We are working hard to do all we can to provide reliable products. I appreciate the honest comments, and please know we are in the continuous improvement mode.