The Federal Communications Commission (FCC) recently issued their report on Voice Telephone Services: Status as of December 31, 2016, which showed continued growth of VoIP and mobile subscriptions and a decline in subscribership to traditional wired telephone services.
For the three-year period from December 2013 through December 2016, VoIP subscriptions showed annual growth of 10%, while mobile subscriptions grew 3% per year and retail switched access lines declined 12% per year.
On 7 December 2017, the Federal Communications Commission (FCC) asked the North American Numbering Council (NANC) to provide advice on how the Trusted Anchor function should be defined and implemented in the pending STIR/SHAKEN call authentication system for Secure Telephone Identity.
They also asked the NANC to recommend a reasonable timeline for telecommunication service providers (TSPs) to deploy this call authentication system, including incentives or mandates that the FCC can put in place to ensure that the timeline is met.
The FCC asked the NANC to report back within four months of the letter, which would be 7 April 2018.
On 22–23 January 2018, CTIA, a group that represents the U.S. wireless communications industry, met with the Federal Communications Commission (FCC) to discuss how to prevent nuisance robocalls.
After the meeting, the CTIA provided the meeting presentation, which the FCC has posted on their website. We’ve reviewed this information and would like to share the key highlights.
Robocalls are a nuisance for telephone customers. Government regulators have set up Do Not Call lists and rules to keep robocalls at bay, but it isn’t working. There’s money to be made from robocalling, and technology makes it easy to conceal the caller’s true identity.
As long as telemarketers can fake their caller ID, telephone customers can be tempted to answer robocalls. Irate customers are flooding regulators with complaints, and mandates to require telecommunications service providers (TSPs) to implement caller ID authentication have been looming on the horizon. Now, in Canada, it’s happened.
On January 3, 2018, news broke that security flaws had been discovered in computer processor hardware and the low-level code that controls how these processors work.
These flaws have been named Meltdown (CVE-2017-5754) and Spectre (CVE-2017-5753 and CVE-2017-5715). They make it possible for malicious code to access information in other running programs by exploiting a CPU feature called speculative execution, which runs software code in advance of when it might be needed to improve performance.