• Passerby6497@lemmy.world
      link
      fedilink
      English
      arrow-up
      35
      ·
      edit-2
      4 hours ago

      Considering our telecons can’t (won’t) even enforce basic fucking origin checking, it’s not surprising.

      These companies have ways of validating calls, it just takes money to setup and enforce, and we can’t waste money on silly things like basic safety when the shareholder value is at stake.

      • Bazoogle@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 hours ago

        Assuming this was in the US, most 911 dispatchers are E911, so the approximate location is automatically included with the call. Smart phones are able to provide a more accurate location, and dispatchers still ask location because they don’t know what floor you’re on if it’s a multi story building.

        • JcbAzPx@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          18 minutes ago

          The E911 location information is not verified. It’s just a field you fill out when you sign up with a voip service. Smart phone location data can also be spoofed, but that’s not quite as easy.

        • Passerby6497@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          39 minutes ago

          Unfortunately, I’m fairly certain e911 isn’t super helpful against people already spoofing their number and location.

          I’m vaguely aware of possible feature rfc to add another layer to prevent spoofing, but given how lazy telecoms are about doing validations MUCH more basic than extending a protocol/schema, I’m not holding my breath.