Provider certification record
Ip2talk Solutions Inc
Listed- RMD number
- RMD0009186
- FRN
- 0031562515
- OCN
- 044M
Identity
- Legal business name
- Ip2talk Solutions Inc
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 39 Allen St, New Hyde Park NY 11040
- Filing contact
- Ali Asgar
Partner · Sales
ip2talk2022@gmail.com
(929) 344-7900
39 Allen St New Hyde Park NY 11040
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Ali Asgar, CEO
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider Complete Overall Complete - Exemption rules
- Pursuant to 47 C.F.R. § 64.6305(d)(2)(i), IP2Talk Solutions Inc is exempt from the direct obligation to implement STIR/SHAKEN because we do not operate our own switching facilities, acquire numbering resources, or perform SIP header signing. IP2Talk provides VoIP and PBX-based phone services to business clients. However, all of our call origination and termination is provisioned through upstream wholesale providers such as Bandwidth, who maintain full STIR/SHAKEN implementation and perform the authentication of calls on our behalf. Because we do not have the technical ability to independently generate STIR/SHAKEN authentication tokens, manage certificate signing, or obtain an SPC token, our certification properly reflects “No STIR/SHAKEN Implementation.” Instead, our robocall mitigation program focuses on: Vetting and verifying all new and renewing customers, Monitoring call traffic through CDRs and alerts, Blocking suspicious or fraudulent activity, Cooperating with traceback requests within 24 hours, and Relying on our upstream providers’ STIR/SHAKEN authentication and fraud controls. This ensures that while IP2Talk does not directly perform STIR/SHAKEN, all calls traversing our network are subject to effective robocall mitigation and compliance with FCC rules
Prior investigations / actions
- Description
- The Company was subject to an enforcement action by the FCC Enforcement Bureau relating to administrative deficiencies in its Robocall Mitigation Database certification. The action was taken solely by the Federal Communications Commission; no other law enforcement or regulatory agencies were involved. The enforcement action commenced on December 10, 2024, when the Enforcement Bureau issued a Show Cause Order (File No. EB-TCD-24-00036891, later reassigned as EB-TCD-25-00038590) identifying deficiencies in the Company’s RMD certification and robocall mitigation plan and providing the Company an opportunity to cure the deficiencies or explain why its certification should not be removed from the RMD. After the deficiencies were not timely cured, the Enforcement Bureau issued a removal order on August 25, 2025, under File No. EB-TCD-25-000385901 (DA 25-737), removing the Company’s certification from the RMD. The action was based solely on administrative deficiencies in the Company’s RMD certification and robocall mitigation plan. No findings of intentional wrongdoing, illegal robocalling, or spoofing activity were made. The Company has since cured the identified deficiencies, has been reinstated to the Robocall Mitigation Database, and the enforcement matter is closed.IP2Talk Solutions Inc. discloses that, within the prior two years, it was subject to a formal FCC action involving the Wireline Competition Bureau and Enforcement Bureau regarding deficiencies in its RMD certification and robocall mitigation plan. The FCC issued DA 25-737 on August 25, 2025, removing the Company’s RMD certification. The Company has submitted an updated RMD filing and mitigation plan intended to address the identified deficiencies. Additional details, including the agencies involved, commencement date, findings, final determination, and current status, are provided in Section 6 of the Company’s robocall mitigation plan. Upload the revised PDF Certify and submit notify RMD team that you have made the requested revisions.
Robocall mitigation plan
Declaration
- By
- Ali Asgar
- Date
- 2026-05-14No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-05-14 | New | Initial certification filed and added to database. |