The Telecom Digest | ||
---|---|---|
Copyright © 2022 E. William Horne. All Rights Reserved. |
Message-ID: <Pine.NEB.4.64.2210041337560.24429@panix1.panix.com>
Date: 4 Oct 2022 13:38:12 +0000
From: "danny burstein" <dannyb@panix.com>
Subject: [telecom] FCC threatens telcos with disconnection 'cuz robocalls.
Ummm, they can do this??? Not so sure this is a good idea...
Or good precedent...
[FCC press release]
FCC PLANS TO REMOVE COMPANIES FROM KEY DATABASE FOR …
Companies Removed from Robocall Mitigation Database Can No Longer
Hand Off Call Traffic to Other Networks
Washington, October 3, 2022 - The FCC's Robocall Response Team today announced
first-of-their-kind Enforcement Bureau orders to begin removing seven voice
service providers from the agency's Robocall Mitigation Database. Providers
must take key robocall mitigation steps - including implementing STIR/SHAKEN
throughout their IP networks - and if they fail to demonstrate that they have
met these requirements, they can be removed from the database and other
networks will no longer take their traffic...
rest:
https://www.fcc.gov/document/fcc-remove-companies-robocall-database-non-compliance
_____________________________________________________
Knowledge may be power, but communications is the key
dannyb@panix.com
[to foil spammers, my address has been double rot-13 encoded]
************************** Moderator's Note **************************
I and other T-D regulars were interviewed by the FTC a few years ago,
when they were looking for a way to block robocalls via technical
means.
I told them it couldn't be done: they most CLECs are looking for every
spare penny they can find, and anyone offerng large volumes of traffic
and able to pay cash would always find a backwoods CLEC willing to
take it from VoIP trunks and put it into the PSTN.
I also told them that the problem would remain until real, and
substantial, penalties were imposed for doing it. At least until the
election, Uncle Sam is starting to listen.
Message-ID: <20221004210800.GA471638@telecomdigest.us> Date: Tue, 4 Oct 2022 21:08:00 +0000 From: Bill Horne <malQRMassimilation@gmail.com> Subject: [telecom] Monthly TCPA Digest - September 2022 By Russell H. Fox , Jonathan P. Garvin , Joshua Briones and E. Crystal Lopez We are pleased to present our latest Monthly TCPA Digest, providing insights and news related to the Telephone Consumer Protection Act (TCPA). In this issue's Regulatory Update, we report on an FCC Enforcement Bureau announcement that the USTelecom-led Industry Traceback Group (ITG) would continue as the registered traceback consortium. The announcement cited ITG's "diversity of voice service providers representing all sectors of the telephone calling ecosystem." We also cover Chairwoman Rosenworcel's announcement that the FCC and the Body of European Regulators for Electronic Communications have signed an updated Memorandum of Understanding (MOU). The new MOU, which is not publicly available, includes a focus on combatting unwanted robocalls and the promotion of 5G and other next-generation communications technologies. https://tinyurl.com/4erf7s6d -- (Please remove QRM from my email address to send your reply to my personal mailbox) Message-ID: <20221004164558.GA470276@telecomdigest.us> Date: Tue, 4 Oct 2022 16:45:58 +0000 From: Bill Horne <malQRMassimilation@gmail.com> Subject: [telecom] Ninth Circuit Holds FCC Cell Phone Radiofrequency (RF) Radiation Rules Preempt State-Law Claims Against Apple And Samsung The RF Radiation Issue Over the years, various claims have been made about potential adverse health impacts from the radiofrequency (RF) radiation emissions of cell phones, which in some instances can cause biological effects by increasing the temperature of tissues. Federal Communications Commission (FCC) rules set RF radiation limits (ceilings) that cell phone manufacturers must meet in order to have the FCC authorize their phones for sale. See 47 C.F.R. §§ 12.1093(d)(1) and 2.907. https://tinyurl.com/2p9h2a8d Message-ID: <8672F7A4-BBC5-4F0C-BEA3-A130822C0414@roscom.com> Date: 2 Oct 2022 01:36:39 -0400 From: "Monty Solomon" <monty@roscom.com> Subject: [telecom] The Thorny Problem of Keeping the Internet's Time The Thorny Problem of Keeping the Internet's Time An obscure software system synchronizes the network's clocks. Who will keep it running? In 1977, David Mills, an eccentric engineer and computer scientist, took a job at COMSAT, a satellite corporation headquartered in Washington, D.C. Mills was an inveterate tinkerer: he once built a hearing aid for a girlfriend's uncle, and had consulted for Ford on how paper-tape computers might be put into cars. Now, at COMSAT, Mills became involved in the ARPANET, the computer network that would become the precursor to the Internet. A handful of researchers were already using the network to connect their distant computers and trade information. But the fidelity of that exchanged data was threatened by a distinct deficiency: the machines did not share a single, reliable synchronized time. https://www.newyorker.com/tech/annals-of-technology/the-thorny-problem-of-keeping-the-internets-time ************************** Moderator's Note ************************** I used to work in the same group that handled timing for NYNEX when I was working on SS7. The "Timing" engineer had a favorite joke: whenever anyone asked him what time it was, he'd shrug his shoulders and say "Nobody knows!" |
Helpful Links | |
---|---|
Telecom Digest Archives | The Telecom Digest FAQ |