johnshaw wrote:I'd love to see what use-cases this SP has that is impacting the ability to do his calling that doesn't also apply to members of the wards unable to do their callings.
I'd imagine it has to do with LCR. We haven't heard yet what the ISP bandwidth is. Perhaps this building just shouldn't have WiFi - at least not building wide. I'm pretty close to that with my "problem child" unit running on 4G.
I have no idea what the ideal bandwidth is for the hammering that a typical congregation places on the system each Sunday. I am aware that I can adjust filter strictness to see if it helps. I also don't know if it is possible to request more bandwidth from AT&T; and even if it is possible, how much it would increase the stake's costs. I don't even know what rate the current contract promises, only that I have measured between 8 and 13 Mbps down.
In subsequent emails with stake leadership, I'm now seeing a slightly different picture for the SP's request - it may be more that he is unable to get a wifi connection at all, rather than a question about getting guaranteed bandwidth (and more an issue because his preferred devices have to use wifi because they don't have ports for wired). He reported that even on a Thursday night high council meeting, when there were not lots of members hitting the wifi like on Sundays, they still spent 10 minutes at the start of the meeting figuring out who could get on the wifi. Or quoting from some of the other emails:
"Can not get my computer to connect to the WiFi while sitting in the Stake Clerks office.
Next, move into the High Council Room. Boom, connects right up.
Next, move into the Stake Presidents office. Our Stake President cannot connect to the WiFi. He is forced to use his personal cell phone as a Hot Spot to access the internet."
and a reply from the FM group:
"The Church is in the process of replacing existing wireless APs with newer Meraki APs. The APs at Duncanville were recently changed, but we will need perform adjustments to take care of the issues you identified. This may take a 2-3 weeks to get back to the Duncanville building as we have 13 other buildings in process, but we will do all we can to address the issue as soon as possible."
with instructions that I shouldn't move the Merakis around myself.
And then, today while troubleshooting General Conference (our satellite reception went down, so I had to enable internet streaming as the backup), I purposefully disabled the wifi through tm.lds.org, at least all of the Meraki units listed, but even with that, I was still picking up an LDSAccess hotspot near the stake offices - so it looks like I do get to chase down a rogue AP. I was too busy today to play with a wifi analyzer on my phone to actually try and locate the rogue hotspot or map out the signal strength in various rooms when the Merakis are enabled, but trust that the FM group will eventually get it right, and that hopefully this is just a temporary problem.