Federal Communications Commission DA 25-694 Before the Federal Communications Commission Washington, D.C. 20554 In the Matter of ) ) ) Robocall Mitigation Database Filers ) EB-TCD-24-00036891 ORDER Adopted: August 6, 2025 Released: August 6, 2025 By the Acting Chief, Enforcement Bureau: I. INTRODUCTION 1. By this Order, the Enforcement Bureau (Bureau) of the Federal Communications Commission (Commission or FCC) removes the Robocall Mitigation Database (RMD) certifications of the companies (each, a Company; collectively, the Companies) identified in Appendix A. Each Company’s RMD certification is deficient because: (a) a robocall mitigation plan was not provided or the plan lacks information required to be submitted by February 26, 2024; and (b) the certification lacks information required by that same date. On December 10, 2024, the Bureau issued an Order affording the Companies a final opportunity to cure the deficiencies in their RMD certifications and notify the Bureau that the deficiencies have been cured; or to file a response with sufficient explanation for why the Bureau should not remove the Company’s certification from the RMD.1 The Companies failed to do either. Removal of a Company’s certification from the RMD requires all intermediate providers and voice service providers to cease accepting all calls directly from the Company.2 The Companies identified in Appendix A shall not re-file an RMD certification without the prior approval of the FCC’s Wireline Competition Bureau (WCB) and the Bureau. II. BACKGROUND 2. The FCC established the RMD in 2020 to promote transparency and effective robocall mitigation.3 On March 16, 2023, the Commission adopted amendments to section 64.6305 of its rules in the Sixth Caller ID Authentication Order that enhanced the information requirements for RMD certifications and expanded the obligation to submit a robocall mitigation plan for new and existing filers.4 On May 18, 2023, the Commission adopted additional amendments to section 64.6305 in the Seventh Call Blocking Order that required all providers to include a commitment to respond fully to 1 See 2,411 Robocall Mitigation Database Filers, 39 FCC Rcd 13318, 13318, para. 1 (EB 2024) (Show Cause Order). 2 See 47 CFR § 64.6305(g). 3 Call Authentication Trust Anchor, WC Docket No. 17-97, Second Report and Order, 36 FCC Rcd 1859, 1902, para. 82 (2020) (Second Caller ID Authentication Order). 4 See Call Authentication Trust Anchor, WC Docket No. 17-97, Sixth Report and Order and Further Notice of Proposed Rulemaking, 38 FCC Rcd 2573, 2592-2601, paras. 36-52 (2023) (Sixth Caller ID Authentication Order). Federal Communications Commission DA 25-694 traceback requests within 24 hours in their RMD certifications.5 Both of these rule amendments took effect on February 26, 2024, and required all existing filers to update their RMD certifications to provide the newly-required information and updated robocall mitigation plans by that same date.6 3. Under the amended rule, voice service providers, gateway providers, and non-gateway intermediate providers7 must submit several pieces of information in their RMD certifications. First, a provider must certify that all calls that it originates on its network are subject to a robocall mitigation program, that any prior certification has not been removed by Commission action and it has not been prohibited from filing in the RMD, and whether it has fully, partially, or not implemented STIR/SHAKEN on the Internet Protocol portions of its network.8 Second, the provider must upload a robocall mitigation plan that describes the specific reasonable steps the provider has taken to avoid originating, carrying, or processing illegal robocall traffic as part of its robocall mitigation program based on the role(s) it serves in the call chain,9 including: (a) a description of the affirmative, effective measures it is taking to prevent new and renewing customers from originating illegal robocalls (if it is a voice service provider); (b) a description of any call analytic system(s) that it utilizes, including those operated by a third-party vendor; and (c) a description of the procedures it is using to know its upstream providers.10 Third, the provider must provide its business name, address, and other identifying information, including contact information for a person responsible for addressing robocall mitigation- related issues, and its principals, affiliates, subsidiaries, and parent companies.11 Fourth, the provider must include certain other information, including: (a) the role it is playing in the call chain; (b) detailed information supporting any claimed STIR/SHAKEN implementation extension or exemption; (c) a statement whether it or any affiliated entity has been subject to a Commission or other law enforcement agency action or investigation in the prior two years due to suspected involvement with illegal robocalling or spoofing, or due to a deficiency in its RMD certification; and (d) the provider’s commitment to respond fully to traceback requests within 24 hours.12 5 Advanced Methods to Target and Eliminate Unlawful Robocalls, Call Authentication Trust Anchor, CG Docket No. 17-59, WC Docket No. 17-97, Seventh Report and Order in CG Docket 17-59 and WC Docket 17-97, Eighth Further Notice of Proposed Rulemaking in CG Docket 17-59, and Third Notice of Inquiry in CG Docket 17-59, 38 FCC Rcd 5404, 5422, para. 52 (2023) (Seventh Report and Order). 6 See Wireline Competition Bureau Announces Robocall Mitigation Database Filing Deadlines and Instructions and Additional Compliance Dates, WC Docket No. 17-97, Public Notice, 39 FCC Rcd 383, 383-87 (WCB 2024) (RMD Public Notice); Advanced Methods to Target and Eliminate Unlawful Robocalls, Call Authentication Trust Anchor, 89 Fed. Reg. 4833, 4833 (Jan. 25, 2024) (establishing February 26, 2024 as the effective date for the amendments to section 64.6305) (Seventh Report and Order Effective Date). 7 The Sixth Caller ID Authentication Order amended section 64.6305 to require non-gateway intermediate providers to file certifications in the RMD for the first time. See 47 CFR § 64.6305(f); Sixth Caller ID Authentication Order, 38 FCC Rcd at 2593, para. 38; RMD Public Notice, 39 FCC Rcd at 384. 8 47 CFR § 64.6305(d)(1), (e)(1), (f)(1); Sixth Caller ID Authentication Order, 38 FCC Rcd at 2595, 2597, paras. 42, 46; RMD Public Notice, 39 FCC Rcd at 385. 9 See Sixth Caller ID Authentication Order, 38 FCC Rcd at 2593, para. 39; RMD Public Notice, 39 FCC Rcd at 385, 388. 10 47 CFR § 64.6305(d)(2)(ii), (e)(2)(ii), (f)(2)(ii); Sixth Caller ID Authentication Order, supra note 4, at 2593-95, paras. 40-41; RMD Public Notice, 39 FCC Rcd at 386-87. 11 47 CFR § 64.6305(d)(4), (e)(4), (f)(4); Sixth Caller ID Authentication Order, supra note 4, at 2595-96, 2597, 2599, paras. 42-43, 46, 48; RMD Public Notice, 39 FCC Rcd at 385-86. 12 47 CFR §§ 64.6305(d)(2)(i), (iii), (iv), 64.6305(e)(2)(i), (iii), (iv), 64.6305(f)(2)(i), (iii), (iv); Sixth Caller ID Authentication Order, supra note 4, at 2596-99, paras. 43-47; RMD Public Notice, 39 FCC Rcd at 385-86. 2 Federal Communications Commission DA 25-694 4. The Bureau may remove a certification from the RMD that is deficient.13 To do so, the Commission first contacts the provider, notifying it that its certification is deficient, explaining the nature of the deficiency, and giving the provider an opportunity to cure the deficiency.14 If the provider fails to cure the deficiency, the Bureau will release an order finding that a provider’s certification is deficient based on the available evidence and direct the provider to cure the deficiency in its certification within 14 days, and notify the Bureau that the deficiency has been cured, or explain why the Bureau should not remove the Company’s certification from the RMD.15 If the provider fails to cure the deficiency or provide a sufficient explanation why its certification is not deficient within that 14-day period, the Bureau will release an order removing the provider’s certification from the RMD.16 5. Following the February 26, 2024 effective date of the amended RMD requirements,17 WCB conducted a review of certifications in the RMD and identified providers that failed to update their RMD certifications (including their robocall mitigation plans) with the required information by the deadline.18 WCB notified each Company on March 29, 2024, that its certification was noncompliant with section 64.6305 because the Company had failed to submit an updated RMD certification and updated robocall mitigation plan by the February 26, 2024 deadline.19 WCB’s notification informed each Company that it “must submit an updated certification and updated robocall mitigation plan in the Robocall Mitigation Database by Monday, April 29, 2024.”20 After this second deadline, the Companies still had not updated their RMD certifications and robocall mitigation plans with the required information; as a result, WCB referred each Company to the Bureau to initiate removal proceedings. 6. On December 10, 2024, the Bureau released an Order requiring the Companies to cure their deficiencies and notify the Bureau of the same, or inform the Bureau why they should not be removed from the RMD within 14 days of publication of a summary of the Order in the Federal Register.21 On December 17, 2024, the summary of the Order was published in the Federal Register.22 Accordingly, the deadline to comply with the Order was December 31, 2024.23 The Bureau and WCB received responses from some of the companies listed in the Order. As of August 4, 2025, the providers in Appendix A are still missing the required information in their certifications. 13 47 CFR § 0.111(a)(28)(i); see Second Caller ID Authentication Order, supra note 3, at 1902-1903, para. 83 (voice service provider certifications); Advanced Methods to Target and Eliminate Unlawful Robocalls, Call Authentication Trust Anchor, CG Docket No. 17-59, WC Docket No. 17-97, Sixth Report and Order in CG Docket No. 17-59, Fifth Report and Order in WC Docket No. 17-97, Order on Reconsideration in WC Docket No. 17-97, Order, Seventh Further Notice of Proposed Rulemaking in CG Docket No. 17-59, and Fifth Further Notice of Proposed Rulemaking in WC Docket No. 17-97, 37 FCC Rcd 6865, 6882, para. 40 (2022) (addressing gateway provider certifications); Sixth Caller ID Authentication Order, supra note 4, 38 FCC Rcd at 2602-2603, paras. 56-57 (addressing non-gateway intermediate provider certifications). 14 Sixth Caller ID Authentication Order, supra note 4, at 2604, para. 60. 15 Id. 16 Id. 17 See Seventh Report and Order Effective Date, supra note 6, at 4833 (establishing February 26, 2024, as the effective date for the amendments to section 64.6305). 18 Id. 19 Email from Robocall Mitigation Database Team (Mar. 29, 2024) (on file in EB-TCD-24-00036891). 20 Id. 21 See Show Cause Order, supra note 1, at 13318, 13321, paras. 1, 8. 22 In the Matter of 2,411 Robocall Mitigation Database Filers, 89 Fed. Reg. 102144 (Dec. 17, 2024). 23 See id. 3 Federal Communications Commission DA 25-694 III. DISCUSSION 7. The Bureau finds that the Companies listed in Appendix A have deficient RMD certifications because they failed to update their certifications with the required information. Despite receiving an email notification from WCB informing the Company that its RMD certification was noncompliant, and an order from the Bureau to cure the deficiency or explain why the Company should not be removed,24 each Company listed in Appendix A failed to take remedial measures. Therefore, the Companies’ RMD filings are deficient and warrant removal. While not a basis for the removal of the Companies listed in Appendix A, we note that the Companies have transmitted suspected illegal robocalls as either an originating or gateway provider.25 Moreover, many of the Companies have failed to respond to traceback requests.26 All voice service providers play a critical role in the call path, and a full and rapid response to traceback requests is required by the Commission’s rules27 and is “essential to identifying both callers placing illegal calls and the voice service providers that facilitate them.”28 8. We remove the certifications of the Companies identified in Appendix A from the RMD as of the release date of this Order. All intermediate providers and voice service providers must cease accepting traffic from the Companies within two business days of the release date of this Order.29 The Companies shall not refile in the RMD unless and until both WCB and the Bureau consent. 9. Additionally, we remind all providers of their RMD obligations. Section 64.6305 requires providers to submit information about their STIR/SHAKEN implementation, robocall mitigation practices, and business information.30 Providers must keep this information up-to-date.31 Failure to comply with the requirements of section 64.6305 of the Commission’s rules may result in the removal of a provider’s certification from the RMD.32 Complete and accurate RMD certifications are essential to ensuring that providers are taking steps to mitigate illegal robocalls. IV. ORDERING CLAUSES 10. Accordingly, IT IS ORDERED that, pursuant to sections 4(i), 4(j), 227b, 251(e), and 403 of the Communications Act of 1934, as amended, 47 U.S.C. §§ 154(i), 154(j), 227b, 251(e), and 403, and sections 0.111, 0.311, 1.1, and 64.6305 of the Commission’s rules, 47 CFR §§ 0.111, 0.311, 1.1, and 64.6305, this Order is ADOPTED. 11. IT IS FURTHER ORDERED that the Companies named in Appendix A are IMMEDIATELY REMOVED from the Robocall Mitigation Database as of the release date of this Order. 24 See supra note 19; Show Cause Order, supra note 1, at 13322, 13323, para. 13 & App. A. 25 See 47 CFR § 64.1200(n)(4) (requiring a voice service provider to take “affirmative, effective measures to prevent new and renewing customers from using its network to originate illegal calls . . .”). 26 See id. § 64.1200(n)(1) (requiring voice service providers to respond to traceback requests within 24 hours); see also ITG Subpoena Response (July 31, 2025) (on file at EB-TCD-24-00036891). 27 47 CFR § 64.1200(n)(1) (requiring all providers to respond to traceback requests within 24 hours). 28 Seventh Report and Order, supra note 5, at 5412, para. 22. 29See 47 CFR § 64.6305(g); Sixth Caller ID Authentication Order, supra note 4, 38 FCC Rcd at 2603, para. 58; Global UC Inc, Removal Order, 37 FCC Rcd 13376, 13379, para. 8 (EB 2022). 30 See 47 CFR §§ 64.6305(d)-(f). 31 See 47 CFR §§ 64.6305(d)(5); (e)(5); (f)(5) (requiring providers to update filings within 10 business days of any change in information). 32 See 47 CFR § 0.111(a)(28)(i); supra note 13. 4 Federal Communications Commission DA 25-694 12. IT IS FURTHER ORDERED that within two business days of the release of this order all intermediate providers and voice service providers MUST CEASE ACCEPTING TRAFFIC FROM THE COMPANIES NAMED IN APPENDIX A. 13. IT IS FURTHER ORDERED that pursuant to section 1.102(b) of the Commission’s rules, 47 CFR § 1.102(b), this Order SHALL BE EFFECTIVE upon release. 14. IT IS FURTHER ORDERED that each Company named in Appendix A shall not refile in the Robocall Mitigation Database unless and until both the Wireline Competition Bureau and the Enforcement Bureau consent. 15. IT IS FURTHER ORDERED that copies of this Order shall be sent by email to the robocall mitigation contact (as certified in the RMD) for each Company listed in Appendix A. FEDERAL COMMUNICATIONS COMMISSION Patrick Webre Acting Chief Enforcement Bureau 5 Federal Communications Commission DA 25-694 RMD0007721 Voltexeo RMD0007827 Nettalk Voice Inc RMD0008017 MS TEL Corp. RMD0008063 Guentha Teknical RMD0008172 Zealous Services LLC RMD0008303 inbound inc RMD0008390 Arctele Communications, Inc. RMD0008420 Nuance Communications, Inc RMD0008435 Onetree LLC RMD0008459 Vultik INC RMD0008467 Next Communications, Inc. RMD0008473 Nexus IT Consultants LLC RMD0009030 gbcbusinessgroup RMD0009072 Dravis Technologies LLC RMD0009087 KNOBLOCH COMMUNICATIONS RMD0009215 One Eye LLC RMD0009252 Trunk Tel LLCC RMD0009360 knoblochcommunications RMD0009369 PrestigeDRVoIP.Com Inc RMD0009377 Peer Voip Services RMD0009436 mancomtec LLC RMD0009475 Technology Brokers Intl Corp RMD0009490 Family Communication Inc. RMD0009506 AKV TECHNOLOGIES LLC RMD0009650 commventures llc RMD0009677 Contravoip LLC RMD0009681 SMARTBIZSOLS INC RMD0009706 Xpertelecom Corporation RMD0009729 Huffman Telcom Corp RMD0009754 Voipvip.net LLC RMD0009761 The Net Calls, LLC RMD0009779 Blue Diamond Communications Inc RMD0009795 DIGICONNECT LLC RMD0009824 Innovative Tech LLC RMD0009869 Jumpsolinc RMD0009874 SKISIP LIMITED RMD0009965 Voip Voice Telecom Inc RMD0009996 AKS Infotech RMD0010490 URTH ACCESS, LLC RMD0010687 SYNDEO NETWORKS, INC RMD0010821 MY BUSINESS VOIP RMD0010876 Onlinecer Solutions LLC RMD0011007 Dial Vista RMD0011088 Legrand Telecom RMD0011165 CallWin LLC RMD0011256 VOXPACE LLC RMD0011309 Voice Fetch RMD0011310 DIGITAL PURVEY LLC RMD0011325 Swift Telco LLC RMD0011352 Astro Telco LLC RMD0011371 Zone-tel 7 Federal Communications Commission DA 25-694 RMD0011390 VacVoip ,llc RMD0011422 Telecom Business Network RMD0011466 Predator Studio LLC RMD0011555 Agnes Sophisticated Hair LLC RMD0011736 TERRA VOIP RMD0011749 Platinum Voice Services RMD0011828 VOIP CITI RMD0011853 BMS Tele LLC RMD0011872 Joonto, Inc. RMD0011890 Transcom Consulting LLC RMD0011995 Voice Radial RMD0012042 Innovation Tel RMD0012062 perfect call RMD0012068 Vos Logic RMD0012106 Dtel Network LLC RMD0012154 FILASCO AMERICA LLC RMD0012250 VAULT SYSTEMS LLC RMD0012266 Solid Double LLC RMD0012301 Techlinkhub LLC RMD0012331 INTELLIVISION TECH RMD0012434 Linphones LLC RMD0012450 TEL X NETWORKS RMD0012486 Atlas Direct Marketing LLC RMD0012511 WHITE OMEN IT CONSULTING, Inc. RMD0012541 Konnect1 RMD0012542 Voip Torque RMD0012561 Tellus 247 RMD0012579 Chatmantics Inc RMD0012595 Bray Telecom LLC RMD0012627 Blue Storm Network RMD0012640 Elmiris LLC RMD0012668 ITD Telecom LLC RMD0012679 Ringless Portal RMD0012879 FROSMO UK LIMITED LLC RMD0012887 Interstellus LLC RMD0012942 Sipdesk RMD0012953 alianznetwork RMD0012958 Neil Wisozk RMD0012993 50 Stars IT Technologies RMD0013015 Wyoming Fiber Phone Inc RMD0013071 directvoicellc RMD0013094 Sigma Solutions Inc. RMD0013344 Mobee Apps, LLC RMD0013358 taconictelcom RMD0013386 Crecer solutions RMD0013400 Zeb Telecom RMD0013512 Zebtelcom RMD0013523 MAGICTEL LLC RMD0013563 VOICEZONE COMMUNICATION RMD0013565 Ran infotech RMD0013581 Tanya David LLC 8 Federal Communications Commission DA 25-694 RMD0013590 Xicomm LLC RMD0013600 Stacy Newsome LNCC RMD0013606 Global Services RMD0013632 Net Speak Pro LLC RMD0013633 AllSeeingConnect LLC RMD0013645 Purple Rose Ltd RMD0013706 Teocommunications RMD0013736 Pleedex LLC RMD0013798 SIP CONNECT RMD0013851 Encoderss RMD0014021 GET DEALS USA LLC RMD0014356 Advanced Financial Help RMD0014358 Expedited Financial Help RMD0014698 CABLE INTERNET BILL LLC RMD0014827 The Telecom Solution RMD0014945 ICOE, LLC RMD0014990 KAZTEL LLC RMD0015047 Peers Global Solutions, LLC RMD0015120 BROWN-FORMAN CORPORATION RMD0015183 Kaiser Telecom LLC RMD0015323 Unified Data Services RMD0015377 DEALSCO RMD0015380 AI TELECOM LLC RMD0015493 Alliant Financial RMD0015516 AMB COMMUNICATIONS LLC RMD0015520 Veriwave Telco, LLC RMD0015583 Confianza Technologies LLC RMD0015625 SIPNVOIP RMD0015627 Voip Studio RMD0015660 Jay Voice LLC RMD0015953 Sims Real Estate RMD0009483 AUM LLC RMD0013350 RMD0013076 RMD0008841 9