Provider certification record
Beneffy Corp.
Listed- RMD number
- RMD0006468
- FRN
- 0031389505
- OCN
Identity
- Legal business name
- Beneffy Corp.
- Doing-business-as
- Beneffy Telecom USVoIP.net
- Foreign Voice Service Provider
- No
- Business address
- 920 Brunswick Ln, Rockledge FL 32955
- Filing contact
- Sergey Kharlamov
CTO · IT
office@beneffy.com
(844) 455-5566
920 Brunswick Ln Rockledge FL 32955
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Sergey Kharlamov
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- The Provider has not implemented the STIR/SHAKEN authentication framework on any portion of its network and all calls originating on its network are subject to the policies and procedures set forth in this Robocall Mitigation Plan which are intended to stop anyone from using the Provider’s service to originate illegal robocalls. Presently, the Provider relies on the continuing extension from STIR-SHAKEN implementation provided under 47 CFR § 64.6304 (d) which exempts from STIR-SHAKEN Caller ID Authentication those portions of a voice service provider network that rely on technology that cannot initiate, maintain, carry, process, and terminate SIP. More specifically, at this time no part of the Provider’s existing network is capable of initiating, maintaining, carrying, processing, or terminating interconnected VoIP calls, with a continued transmission of STIR-SHAKEN attestation data. Beneffy Corp. d/b/a Beneffy Telecom and USVOIP.net is small voice service provider with less than 100,000 subscribers and is exempt from the requirements of full STIR/SHAKEN protocols through June 30, 2023. Beneffy Corp. qualifies under 47 CFR § 64.6305(b)(4) as a voice service provider without a STIR/SHAKEN implementation obligation. The company relies on its upstream carriers (e.g., Telnyx, Vonage, SignalWire) to perform STIR/SHAKEN authentication in compliance with FCC requirements.
Prior investigations / actions
- Description
- The company failed to update its RMD filing by the February 26, 2024, deadline due to a lack of awareness regarding the specific regulatory changes and associated deadlines. While the company regularly monitors FCC rule updates, the recent amendments requiring additional information in RMD filings were not properly disseminated to the appropriate internal teams. Furthermore, the compliance team responsible for RMD maintenance was undergoing restructuring at the time, which contributed to delays in identifying and acting on the new requirements. The company takes full responsibility for this lapse and recognizes the importance of timely compliance with FCC regulations. The Company updated RMD filling and reinstate service. No other findings and no other agency been involved. (1) all law enforcement or regulatory agencies involved - FCC (2) the date that any action or investigation was commenced 02/26/2024 and 08/29/2024(August RMD removal orders) (3) the current status of the action or investigation - NONE (4) a summary of the findings of wrongdoing made in connection with the action or investigation - NONE (5) whether any final determinations have been issued - UNKNOWN All recommendation are fallowed and no feature action require. FCC prior action - Contacted to ask to update FCC Filling with proper data and mitigation plan.
Robocall mitigation plan
Declaration
- By
- Sergey Kharlamov
- Date
- 2026-04-10No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-04-10 | New | Initial certification filed and added to database. |