• 1 Post
  • 9 Comments
Joined 4 years ago
cake
Cake day: June 28th, 2022

help-circle
  • It is nobody’s duty to expose anything for the sake of exposing it.

    Bullshit. Exposure is the 1st step.

    It is our duty to expose things for the sake of solving them.

    Of course. But not necessarily directly. There are many ways to solve a problem. Spotlighting an embarrassment is a precursor. You can also travel to a call center and apply to work for them to improve their system. You do you.

    If you have a better solution, we’re ready to hear it.

    It’s not my problem to solve. Do you also demand that testers fix the bugs they report?

    You’re perversely out of step with how volunteer effort is managed. Volunteers choose for themselves how much effort they contribute. You are not their manager. It’s not for you to drive-by task people and bark out orders. When a bug is reported, it’s public for anyone to solve, if they want. It’s a community. Not a corporation.

    I don’t see anything being covered up.

    You don’t know how threadcrap works. It’s designed to suppress the thesis by creating a distraction.


  • I’m confused what you think a better alternative would be? If there was a test number, what if that worked, but you couldn’t call the real 911?

    A test number would suffice in some situations. When an incompetent VOIP provider takes an action to block calls “for security purposes”, they cannot legally block /all/ calls. 911 calls must be permitted. And 911 test calls would obviously require the same status. I do not trust their competency. But if their call blocking allows a 911 test number through, it proves that their blockade is not a simple crude block on /everything/.

    A test number would not be the only solution. With some services you can set the CID to whatever you want. So in principle a CID of 555-1212 could have special meaning to 911 receiptionists. So a tester would set the CID info to that number before calling 911.

    911 is not always instantly answered by humans. When answered by a machine, there could be a cancel code. E.g. dial “119” after connecting to cancel it.

    There’s no way around it: to be absolutely sure your phone can contact 911, you have to… dial 911.

    Sure, if you need that extra level of certainty. In the typical cases that I mentioned (no GSM subscription), a test number would be sufficient. It would show that the dialed number reaches a switch that treats it.






  • First, it’s wrong to assume everyone has multiple phones. Those with multiple phones are also those who least need to test 911.

    But if we can get past that, are you also assuming that the test phone has a phone number? Suppose you call the test center with a friend’s phone (always amusing when a policy imposes having friends, but anyway). The conversation would likely go like this:

    me: I will make a test call from a different phone than the one I am calling from.
    911 center: Okay, what is the phone number of the phone you are testing (so we know which inbound call to disregard)?
    me: The test phone is not subscribed. There is no number.
    911 center: Then we cannot do the test.

    Or do you imagine the 911 center would say: just call us now and we will ignore whatever call we get?

    Of course if a GSM phone has no chip, it also has no number assignment. If the test phone is a VOIP phone, the subscriber may not have a DID. There could be a phony internal number assignment in that case, but the customer does not necessarily know it.

    The next problem is /which/ call center do you call when you are on a voip phone served in a different state than where the call is made from?