Well, carriers would have to block the black boxes and only allow the good networks on. AT&T can peer with Sprint or T-Mobile, but the shady carriers that lets fiber terminate into copper without asking questions have to do due diligence or get cut off.

It wouldn't be evenly distributed. Your carrier could pass on the fine at least a few hops deep, until it reaches whoever connected the shady VoIP company to the real network. In the video's example, it would be Google Voice, the owner of the hacked VoIP systems' uplink provider, or the anonymous online call services. It's rare that the spammers use payphones or prepaid cards.

Even if it's the same situation as with e-mail spam, this would also be a workable solution for that problem.

Say I have a G-Mail account. I get spam from X@hotmail.com. Now G-Mail have to pay me the fine, and Hotmail have to pay GMail the fine, and X has to pay Hotmail the fine. Sure, they can't track down X, but Hotmail have to pay up for letting bad actors on their network.

We could also generalize this to BGP, of course. I get a port 22 brute-force attempt to my server, I contact my ISP, they pay me. They contact whoever peered them, who pays, until we get to China, where some local ISP says that a PC on their network was hacked. Too bad. Either the Chinese ISP pays up, or they get depeered by their CN <-> HK ISP, or they get depeered by their uplink, and so on.

Here is an example traceroute to the Chinese ecommerce site taobao.com from Cogent. In my example, the fine would travel down this list until it finds someone unwilling to pay up, who then gets depeered.

traceroute to 140.205.220.96 (140.205.220.96), 30 hops max, 60 byte packets
1 gi0-1-1-19.5.agr21.jfk02.atlas.cogentco.com (66.28.3.113) 0.693 ms 0.702 ms
2 be2605.ccr41.jfk02.atlas.cogentco.com (154.54.1.153) 0.741 ms 0.759 ms
3 be2806.ccr41.dca01.atlas.cogentco.com (154.54.40.106) 6.397 ms be2807.ccr42.dca01.atlas.cogentco.com (154.54.40.110) 6.538 ms
4 be2113.ccr42.atl01.atlas.cogentco.com (154.54.24.222) 17.340 ms be2112.ccr41.atl01.atlas.cogentco.com (154.54.7.158) 17.461 ms
5 be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 31.636 ms 31.606 ms
6 be2928.ccr21.elp01.atlas.cogentco.com (154.54.30.162) 47.240 ms be2927.ccr21.elp01.atlas.cogentco.com (154.54.29.222) 47.095 ms
7 be2930.ccr32.phx01.atlas.cogentco.com (154.54.42.77) 55.345 ms be2929.ccr31.phx01.atlas.cogentco.com (154.54.42.65) 55.417 ms
8 be2931.ccr41.lax01.atlas.cogentco.com (154.54.44.86) 66.946 ms 67.307 ms
9 be3271.ccr41.lax04.atlas.cogentco.com (154.54.42.102) 67.073 ms 67.072 ms
10 38.142.238.34 (38.142.238.34) 69.608 ms 69.608 ms
11 202.97.50.29 (202.97.50.29) 73.785 ms 73.790 ms
12 202.97.71.193 (202.97.71.193) 206.204 ms 206.594 ms
13 202.97.12.193 (202.97.12.193) 200.253 ms *
14 202.97.24.249 (202.97.24.249) 206.719 ms 202.97.62.61 (202.97.62.61) 202.714 ms
15 101.95.120.105 (101.95.120.105) 224.543 ms 101.95.120.233 (101.95.120.233) 219.260 ms
16 124.74.166.18 (124.74.166.18) 222.636 ms 101.95.206.14 (101.95.206.14) 230.753 ms
17 101.95.208.10 (101.95.208.10) 233.093 ms *
18 114.80.58.82 (114.80.58.82) 237.192 ms 180.163.38.82 (180.163.38.82) 213.441 ms
19 116.251.88.134 (116.251.88.134) 204.868 ms 116.251.88.154 (116.251.88.154) 220.342 ms
20 140.205.58.9 (140.205.58.9) 213.268 ms 116.251.106.190 (116.251.106.190) 197.170 ms
21 * *
22 * *
23 * *
24 * *
25 * *
26 * *
27 * *
28 * *
29 * *
30 * *