4 ms·
https://datatracker.ietf.org/wg/stir/documents/ https://datatracker.ietf.org/wg/stir/documents/ its not exactly ELI5. The CLI (Caller Line ID) field of a "inc
by ggm 5y ago
https://datatracker.ietf.org/wg/stir/documents/ https://datatracker.ietf.org/wg/stir/documents/
its not exactly ELI5.
The CLI (Caller Line ID) field of a "incoming call" message isn't adequately policed. This is sort-of baked into how telephony works. It's stupid, and it should have been thought about more. The CLI field isn't how the call routes, its just how the caller announces who you are. Telephone call routing uses other data fields, its part of SS7 and the other signalling systems the phone network uses. The field which comes up a mobile call, inside "payload" isn't how it routed.
Imagine some company has the indial range 667 2200 to 667 2299.
If you dialled from your assigned handset 667 2241 the CLI can say 667 2200 so it looks like you come from the switch (in this example we assume the company's PBX operator is on 2200, and you publish 2200 as the incoming call number) so people don't learn your office handset: thats why they permitted it.
I have no idea why they allow to to "lie" above your indial group range. But they do.
STIR is how in a VOIP world people are approaching the fix. But really? the FCC and other national regulators have to tell the telco to stomp on the fakeout, when people inject calls into their system.
This has parallels with "envelope sender vs RFC822 header" in email. Or spoofed source if your ISP doesn't do BCP38. Guess what: SPAM is a problem in email (duh) and spoofed source is how DDoS can happen. "telling lies" in end-to-end communications is not helpful.
- marcus_holmes 5y agoIf this is baked into telephony, why we don't have this problem in Europe? (genuinely curious why this happens in the USA but not here)
- ggm 5y agoWe do have it in Australia fwiw
- marcus_holmes 5y agoI used to live in Perth, and never had this problem this bad. I got the occasional spam text, but it was usually from some company I'd given my number to. Are you getting that many spam texts?
- ggm 5y agoI get 2-3 spam texts and calls per month. About 1/2 fake my mobile # off by 1 digit near the end, a trick to make me "think its a number I know" I'm on ALDI which is an MVNO overlay on Telstra wholesale. Maybe ALDI do worse for source detect? (there is no difference between SMS and calls in regard to CLI faking. I don't know about RCS, its possible RCS gets rid of this problem. ALDI doesn't have RCS, its not ubiquitous, has to be enabled in the phone profile by the provider)
- willis936 5y agoIt sounds like it shouldn't even be happening in USA. It's a trivial bit of code in the routing software to check if CLI matches SS7. If it doesn't: don't connect. You don't even need to correct it. There's no legitimate reason to connect a spoofed number.
- riskable 5y agoIt is trivial to implement. They don't do it because they make a ton of money every year selling origin spoofing to businesses and charging customers for incoming texts (they never asked for). Spoofing is a service that the telcoms offer. Not a weakness! At least, that's how they see it.
- pjerem 5y agoThank you for explaining me :)