Tech Forum

brholman wrote:It was for that reason in our stake that we called an STS for each ward.

We have one for each ward. Those just happen to be the four that decided not to connect to the Church webcast system today.

craiggsmith wrote:Still, other bishoprics might want wifi while another ward is broadcasting.

But look at your options:
- Spending time and money on something where it's likely at some point you'll be told to remove it, leaving users unhappy.
- While it does mitigate the issue, it doesn't solve it. What happens to the webcast if the bishopric decides to hold a zoom meeting to include some people at the same time?
- Things like passwords to the "privileged" WIFI will circulate. You'd probably have to change the password every 1-2 months to keep it under control.

Perhaps a better solution would be to discuss with the stake president about discouraging meetings that require internet access during a sacrament time block.

We added a separate router to the building just for the purpose of the broadcasting. You would still need to contend with the members on overall bandwidth, but at least you will have your own direct connection to the network. WiFi bottlenecks are often in the individual connections to the router itself, so doing this might help you.

Couple thoughts -

1- Can prioritized WiFi QoS be turned on for the livestream resource?

2- Do all meeting houses have an Ethernet drop near the pulpit for a livestream resource?

I don’t see “turning off” WiFi as practical.

rklindquist wrote:1- Can prioritized WiFi QoS be turned on for the livestream resource?

Not a the level of control that local units have.

rklindquist wrote:2- Do all meeting houses have an Ethernet drop near the pulpit for a livestream resource?

All of mine do, but I'm sure there's exceptions when we start talking "all".

I recently received information about a Hidden SSIS: Lehi. See below:

Technology Manager Changes
Two changes have recently been made to Technology Manager (TM; tm.ChurchofJesusChrist.org):

New "Lehi" wireless network (SSID)
"Central Network Log" tab

Lehi Wireless Network (SSID)
You now have the option to enable the Lehi wireless network (SSID). This will allow you to disable the Liahona SSID during the webcast of sacrament meeting or other important meetings but still provide a wireless network (Lehi) for other local unit leaders who are meeting in the same meetinghouse.
The Lehi and Liahona wireless networks (SSIDs) will be broadcast from the same Meraki wireless access points (APs).
The Lehi SSID will be disabled by default. To enable it, simply change the Lehi default passphrase from "2Nephi2526" to a passphrase that will be managed by each stake technology specialist.
The passphrase must be updated for each meetinghouse where the Lehi SSID will be used. The passphrase should be shared only with unit leaders who are approved by the stake president. It must be updated every 90 days or it will automatically be disabled.
The Lehi SSID will not display a "Terms of Use" splash page and cannot be scheduled like the Liahona SSID. It is recommended that you create a schedule for the Liahona SSID. Individual AP management will no longer be an option. See the example in the screen capture below from TM.
Central "Network Log" Tab
This provides a single log history of any changes to the meetinghouse network, such as who made the change, the date, and the details of the change. See the screen capture below from TM.
For support questions, please contact the Global Services Department (GSD).

1. Ask everyone who enters the building to put their devices into Airplane mode until they leave. This should disable wi-fi for everyone. And children can use coloring books and crayons, no need for an electronic device during sacrament services.
2. Encourage everyone to plan ahead. Share the agenda with your council/presidency/bishopric the night before. Print out the agenda or other paper work - say the paperwork for a tithing interview. Print out the roster, even a full directory if needed. Update your apps before leaving home. Download whatever you need, and save it to your device.
3. Sell the STS on the idea that you need an ethernet jack at this or that location. Russellhltn is correct - one size fits all does not. Our church was built for our branch back in the mid 90s, and while it has the cultural hall (overflow, guy) wired for speakers, the pulpit does not have an ethernet jack.
4. Have them meet in the clerk's office, and use the clerk's computer. The clerk's computer most likely is tethered to the wall with an ethernet cord, so no wi-fi is needed. I understand that it is a small office compared to the bishop's or president's office. Also, the clerk gets top priority in the clerk's office for clerking.
5. Schedule the meetings at a time that does not interfere with the broadcast. Sorry, it is a bit obvious, yet ignored a lot.
6. Hold the meetings from home using Zoom, FaceTime, or the tech of their choice.
7. Move the bishopric only, no group presidencies, to the new Lehi network, then disable the Liahona SSID during regular church hours. Set up streaming to use the Lehi network as well.
8. I don't know if it is possible or not, yet speak to your STS about vlan, QoS, and what ever else is available in his toolkit to shape traffic.
9. and 10. I am sure I missed something or two, so I'll leave these empty for now, with the understanding that I might come back and edit this in the future.

Just my two cents before taxes, inflation, and other fees - you will be lucky to see .01352 of a cent at the end. All refunds will be charged a $20 processing fee.

awev wrote:I don't know if it is possible or not, yet speak to your STS about vlan, QoS, and what ever else is available in his toolkit to shape traffic.

There isn't any. Disabling wifi and setting filtering levels is about it.