FCC Orders Blocking of Digital Solutions Traffic and Removes It From the Robocall Mitigation Database

The bottom line: this is the last step of a process that began with an April 2, 2026, notice. The company had two chances to supply the required information and did not.

Here is what happened

According to the order, the Industry Traceback Group (ITG) traced 51 prerecorded calls to wireless numbers, placed between May 6, 2025, and July 8, 2025, to Digital Solutions as the originating provider. The Bureau said the calls delivered prerecorded messages without the consent of the called parties.

• Nineteen calls claimed to be from a "loan processing team" and said the recipient's "application" had been "preapproved for up to 41,000 dollars."
• Four said "we finally have an approval for you" and told recipients to "press 2 now."
• Other recorded calls said the "new administration has introduced updated IRS relief programs."

Digital Solutions confirmed it originated the calls and identified three of its customers as the sources.

The Bureau also found two problems with the company's RMD certification. First, it certified full STIR/SHAKEN implementation while its mitigation plan said otherwise. Second, it certified that it authenticates caller ID for all Session Initiation Protocol (SIP) calls it originates, but evidence from Verizon and the ITG showed ten calls signed with certificates issued to other providers.

The procedural history

1. April 2, 2026: Notice. The Bureau sent a Notification of Suspected Illegal Traffic and RMD deficiency notice. A response was due by April 16, 2026.
2. April 3, 2026: Partial cure. The company revised its mitigation plan, which cured the STIR/SHAKEN contradiction.
3. May 5, 2026: Late response. More than two weeks after the deadline, the company emailed that it had "vacated those customer profiles" and that there had not been more such calls after August 12, 2025. The Bureau said it omitted the required investigation results, blocking certification and plan.
4. June 29, 2026: Initial Determination Order (DA 26-643), giving the company 14 days to respond and a final chance to cure.
5. July 12, 2026: New certification. The company again certified complete STIR/SHAKEN implementation. It also answered "no" when asked whether it had been the subject of a formal Commission investigation with findings of suspected wrongdoing in the prior two years, despite the April Notice and the June order.
6. July 13, 2026: Second response. The company addressed only the ten unauthenticated calls.

The law

Under 47 U.S.C. § 227(b)(1)(A) and 47 C.F.R. § 64.1200(a)(1), calls to wireless numbers using an artificial or prerecorded voice require prior express consent unless made for an emergency purpose.

Section 64.1200(n)(2) sets out a three-step blocking process: a notice requiring the provider to investigate, report and block; an initial determination order if the response is insufficient; and a final determination order requiring downstream blocking if the provider still falls short. Separately, under 47 C.F.R. § 64.6305(g), removal from the RMD requires all intermediate and voice service providers to stop accepting the provider's calls directly.

Why the Bureau was not convinced

Digital Solutions made four arguments about the ten calls. It said it received only a redacted version of the call list, that its downstream carrier "would not have accepted an unauthenticated call," that any missing authentication may be a "technical problem" downstream, and that it could no longer obtain SIP trace records.

The Bureau was not persuaded. It said unredacted copies were sent by email and certified mail. It noted that Digital Solutions holds its own STI certificate and used it to sign other calls in the same period, while these ten calls were signed with other providers' certificates. The company did not claim it used a third party to sign them. The Bureau said a lack of records "rests solely with the Company."

The company also cannot resubmit an RMD certification without the prior approval of the Enforcement Bureau and the Wireline Competition Bureau.

Why it matters

This order shows the full lifecycle of the FCC's blocking rules. A traceback becomes a notice, a notice becomes an initial determination, and an inadequate response ends in mandatory blocking and removal.

It also shows that STIR/SHAKEN certifications are tested against real call data.

What this means for you

1. Respond to every FCC notice on time and answer every item it lists.
2. Retain SIP and authentication records long enough to respond to a traceback months later.
3. Make sure your RMD answers, including prior investigations, are accurate each time you recertify.
4. If a third party signs calls for you, put the arrangement in writing and keep it.

Completing the response the first time is far less expensive than losing access to the network.

Source: FCC, EB Issues Final Determination Order Against Digital Solutions Inc.