Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Communications IT Technology

T-Mobile, Comcast Turn on Call Verification Between Networks in Latest Robocall Fight (usatoday.com) 58

pgmrdlm shares a report: Calls between T-Mobile users and Comcast's Xfinity Voice home subscribers will now be "verified," the latest move in the ongoing fight against robocalls. The two companies announced Wednesday that they have launched cross-network verification, allowing users to know that the calls they are receiving is from an actual person and not a spammer or robocaller.

They use a handoff system recommended by the FCC where the caller's network verifies that a legitimate call is being made with a "digital signature." The recipient's network then confirms the signature on its side. A number of major wireless and traditional home voice providers have pledged support for the verification method, including Verizon, AT&T, Sprint, Charter, Cox and Vonage, with several announcing plans to roll out or test the feature in 2019.

This discussion has been archived. No new comments can be posted.

T-Mobile, Comcast Turn on Call Verification Between Networks in Latest Robocall Fight

Comments Filter:
  • by Anonymous Coward on Wednesday April 17, 2019 @01:04PM (#58449994)

    This seems like something that should have been done...forever?

    • by Anonymous Coward

      Except what constitutes a "legitimate call?" All it would take for this to be rendered ineffective is an agreement that certain calls be considered "legitimate."

      Plus who verifies these signatures? It's completely useless to the public if it's just between the companies involved behind closed doors. Hell it may not even exist, and be just yet another PR stunt so they can still claim they are "improving" their infrastructure and get more money from their subscribers / taxpayers.

      Yet more proof that slapping a

      • by XXongo ( 3986865 )
        You know, yes, you can come up with problems, but the existing system has totally failed due to robocalls spoofing phone numbers.

        Pretty much all my friends now tell me that they never answer their phone unless the calling number is on their contacts list, simply because the number of fake calls so outnumbers the real calls that it's worth the fact that sometimes you miss calls from somebody who actually does need to get hold of you.

        (but... I did manage to keep the Microsoft repair guy, who cold called me

        • by dj245 ( 732906 )

          You know, yes, you can come up with problems, but the existing system has totally failed due to robocalls spoofing phone numbers.

          Pretty much all my friends now tell me that they never answer their phone unless the calling number is on their contacts list, simply because the number of fake calls so outnumbers the real calls that it's worth the fact that sometimes you miss calls from somebody who actually does need to get hold of you.

          (but... I did manage to keep the Microsoft repair guy, who cold called me at about 2:30 today, on the phone for 17 minutes. I think that's a record for me.)

          It's not that difficult for me. I have a Wisconsin area code but live in Texas. I don't know anyone in Wisconsin anymore so any Wisconsin area code calling me might as well be screaming "I am definitely a robocall!"

  • by Lab Rat Jason ( 2495638 ) on Wednesday April 17, 2019 @01:12PM (#58450030)

    How many robocalls were transiting between these two networks? Personally, I'd prefer if Verison would simply verify calls that were supposedly coming from their OWN network.

    • Exactly. Also, does every network need to add call verification between each network separately? This will take forever. The spammers will just use a network that doesn't have call verification setup.

      • by dissy ( 172727 )

        Also, does every network need to add call verification between each network separately?

        Of course not.
        Networks can choose to send verification certificates or not.
        Your phone, eventually, will gain the ability to see if the originating network sent a certificate or not.
        Your phone - ok, hopefully - should eventually gain the ability to act on that information.

        This will take forever. The spammers will just use a network that doesn't have call verification setup.

        Apple and Google both have stated they will be implementing the shaken/stirprotocols in their OSes.
        For Apple and Google made or stock Android using phones, which they claimed last month would be within a year.

        After that you can choose what

        • Of course there is a much easier fix. A simple option to send all callers not in my contact list directly to voice mail. I don't need to talk to strangers. I've made this happen with a 'hack'. I have a blank ring tone that is my default, each contact list user has a real ring tone. I might get a half dozen spam calls a day, but I never notice.

      • The spammers will just use a network that doesn't have call verification setup.

        Ideally, software will evolve to let us 100% ignore calls from networks that don't have call verification setup. Just like you can choose to only allow mail into your system that passes DMARC. It doesn't require everyone have DMARC setup for it to be useful. What makes you think this is has to be 100% participation to become effective? I don't you didn't come out and say that outright, but can see that is where you are going w

    • by Anonymous Coward

      I suspect it has nothing to do with calls being made from the networks, rather it's about explicitly marking calls as verified. As they prove the system works, they can increase the scope of the effort so that it verifies calls between all of the major networks.

      Until, one day, you'll be able to reasonably assume any call that lacks the "verified" tag is a robocall and autoblock it.

      • They already *know* which numbers belong to which networks, it's a necessary database that allows number portability so when someone calls a number they know which destination network to switch the call to.

        All they need to do is use this database in reverse on calls entering their network to see if the ANI info for the call matches the network it's *supposed* to be coming from.

        If ANI on an incoming call says it belongs to the ATT network but its entering from some carrier other than ATT, then it should be d

        • > so when someone calls a number they know which destination network to switch the call to

          Yes, and TO is the operative word. A phone number is technically known as a DID number - Direct Inward Dial. A DID (phone number) indicates which service (not station aka phone) a call is being placed to. There is no such thing as a DOD, Direct Outward Dial number. Consider this very simple case:

          You are logging in to your bank web site, Second National Bank.com. Your bank doesn't suck, so it has multifactor commun

          • Then don't fucking spoof your own customer service number into the call.

          • Interesting, the DID vs DOD information. Is email in this same boat? I've always wondered why phone spam couldn't be fixed with a hybrid of things that resemble DMARC for email, and Autonomous systems for networks.
            • Email has from and to addresses, in the envelope as well as the headers. So it doesn't have the same issue in terms of fundamental logic. Emails from from some address, phone calls don't come from a "phone number" (DID). So that's a fundamental difference.

              Note that like the phone system, email addresses can be something like customerservice@acme.com - a role or service, NOT a device, and certainly not a person.

              So you can't identify a particular device as customerservice@acme.com, and similarly you can't s

          • by jon3k ( 691256 )

            Yes, and TO is the operative word. A phone number is technically known as a DID number - Direct Inward Dial. A DID (phone number) indicates which service (not station aka phone) a call is being placed to.

            DID is actually the service, not the individual BTN/WTN being forwarded into a PBX, but a lot of people use the term interchangeably.

            There is no such thing as a DOD, Direct Outward Dial number.

            Actually, there is.

        • by Anonymous Coward

          They do not want to do this because the carrier makes money from terminating calls, no matter where they come from. If they only accept calls where the caller-id matches the ANI and where they perform validate that the incoming call is coming from the network owning the calling number, then they will lose money (by not terminating the call). Therefore there is no interest on behalf of any carrier to ensure the validity of the call.

          This is just snake oil designed for theatrical purposes that will actually

  • by psergiu ( 67614 ) on Wednesday April 17, 2019 @01:46PM (#58450218)

    What if the large carriers all implement FCC's SHAKEN/STIR between them but then refuse to do the same thing for all the small carriers ?
    Then start marking all non-verified calls as SPAM ?
    Don't say it could not happen.

    • It wouldn't identify them as spam, it just wouldn't say they were verified (as this new T-Mobile link up appears to do).

      T-Mobile does also identify scam callers in some cases, but it uses a variety of techniques to do that (and a master list updated every six minutes), so it also would not arbitrary mark all calls from a small carrier as spam.

  • by BrendaEM ( 871664 ) on Wednesday April 17, 2019 @01:52PM (#58450246) Homepage
    We also need make our politicians to be tougher on robocalls.
  • It seems like that if robocalls are a problem, it is too easy to get access to the phone network without anyone to hold accountable?

    Also, it seems like a phone number is becoming more and more irrelevant these days. It's more like a node number, an IP address for your device. :D

  • The FCC should step up and make this MANDATORY!
  • Comment removed based on user account deletion

No spitting on the Bus! Thank you, The Mgt.

Working...