I really don't think that's a huge issue. (Worked at a telco, but small one)
Sure, nobody works for free, but if requests for source become a thing that happens, there will be systems to retrieve it with less work as well. It doesn't need to be a long record - keeping the last couple of days for complaints handling may be painful, but not "too much traffic". If adtech can save all our clicks for analysis, telcos can handle the short term lookups.
> It's only a matter of time before they reach a telco in the chain that says "we don't have those logs sorry".
That's the whole idea - the blame for that specific call falls on them then. Get fined, next time don't lose the logs, sorry.
> Plus, each telco along the way will charge the US telco for retrieving and providing those logs.
Make it a requirement for reporting so they can't - similar to how DMCA safe harbour works. Either you deal with your customer, point at a source peer, or become the responsible party.
> a stolen credit card, at a virtual reseller where no human interaction ever happened to set it up.
That's fine. Close the account and if it repeats too often for the reseller they can get fined until they implement better fraud checks (or prevent large volumes of calls without human interaction). This is not a novel problem - that's why you can't spawn 500 GPU instances on EC2 right after you open an account.
Edit: Back of a napkin - Verizon claimed to handle 800M calls a day some years ago. Logging the 2 source, 1 destination numbers, peer ids and date in binary format, which is all you need for handling complaints, gives you <40GB per day. That's searchable with grep on a laptop. It's definitely not too much data for a telco.