Provider certification record
S.V. Enterprises
Listed- RMD number
- RMD0007118
- FRN
- 0024821894
- OCN
Identity
- Legal business name
- S.V. Enterprises
- Doing-business-as
- Micro-Tech U.S.A.; Minnow Talk; Minnow Systems
- Foreign Voice Service Provider
- No
- Business address
- 5 N Wabash Ave, Suite 802, Chicago IL 60602
- Filing contact
- Ethan Gillani
CEO · Executive
ethan.gillani@mtusa.com
(312) 357-0023
5 N Wabash Ave Suite 802 Chicago IL 60602
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Ethan Gillani – Chief Executive Officer
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- 47 CFR § 64.6304(b) provides an implementation extension for a voice service provider that is incapable of obtaining an SPC token due to the applicable Governance Authority token access requirements. S.V. Enterprises is currently completing the industry registration and credentialing process necessary to establish eligibility for SPC token access and is actively pursuing the required steps toward its own STIR/SHAKEN implementation. The Company will proceed with its own STIR/SHAKEN implementation once the necessary credentials are obtained. Until that process is completed, the Company relies on its upstream voice service providers for applicable STIR/SHAKEN authentication; S.V. Enterprises certifies that it does not implement STIR/SHAKEN authentication in its role as a non-gateway intermediate provider and therefore selects “No STIR/SHAKEN Implementation” in its Robocall Mitigation Database filing. Pursuant to 47 CFR § 64.6304(b), non-gateway intermediate providers that are incapable of obtaining an SPC token due to Governance Authority policy are exempt from the call authentication requirements applicable to non-gateway intermediate providers until they are capable of obtaining an SPC token. S.V. Enterprises is currently incapable of obtaining an SPC token under Governance Authority policy because it does not possess an Operating Company Number (OCN) and is not a Resp Org, and therefore does not sign calls using STIR/SHAKEN certificates. Consistent with FCC guidance, non-gateway intermediate providers that do not have a STIR/SHAKEN implementation obligation may certify accordingly. STIR/SHAKEN authentication for outbound traffic is performed by upstream voice service providers. The Company maintains and applies a robocall mitigation program consistent with 47 CFR § 64.6305(c), including reasonable steps to prevent illegal robocall traffic and a commitment to respond fully within 24 hours to traceback requests.
Prior investigations / actions
- Description
- S.V. Enterprises was the subject of a formal action by the Federal Communications Commission (FCC), specifically through its Enforcement Bureau. No other law enforcement or regulatory agencies were involved. The Company was specifically named in the FCC Enforcement Bureau Robocall Mitigation Database removal order issued on August 25, 2025 (DA-25-737). The findings concerned deficiencies in the Company’s Robocall Mitigation Database (RMD) certification and robocall mitigation program description, including failure to provide required information and certifications in the filing. The action did not include a finding that S.V. Enterprises intentionally originated or transmitted illegal robocall traffic. Following the FCC’s action, the Company updated its RMD filing and Robocall Mitigation Plan and was provisionally reinstated on September 2, 2025. The Company has continued to update its filing and is currently addressing the remaining deficiencies identified by Commission staff. Commission staff review remains ongoing. The FCC issued the August 25, 2025 removal order, and the Company was subsequently provisionally reinstated; no separate final determination finding that the Company intentionally transmitted illegal robocall traffic has been issued.
Robocall mitigation plan
Declaration
- By
- Ethan Gillani
- Date
- 2026-09-01No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-09-01 | Plan updated | Mitigation plan document replaced. |
| 2026-09-01 | Field change | roleVoice false→true +5 more |
| 2026-05-04 | New | Initial certification filed and added to database. |