Provider certification record
Sanvoice LLC
Listed- RMD number
- RMD0041628
- FRN
- 0038870309
- OCN
Identity
- Legal business name
- Sanvoice LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 2767 SW Buckhart St, Port St Lucie FL 34953
- Filing contact
- Peterson Pierre
President · Sanvoice
ppierre@sanvoice.com
(866) 675-4775
2767 SW Buckhart St Port St Lucie FL 34953
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Peterson Pierre 100%
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Certified implementation status: No Implementation. Rule relied upon. SanVoice states, pursuant to 47 C.F.R. § 64.6305(d)(2)(i), that it is unable to implement STIR/SHAKEN due to a lack of control over the network infrastructure necessary to implement STIR/SHAKEN. Why the exemption applies to SanVoice. SanVoice's role in the call path is limited to configuring customer telephone features through software VoIP.ms provides. SanVoice owns no switch, media server, or SIP signaling infrastructure, and controls no network element on which a caller identification header could be signed or verified. The infrastructure on which STIR/SHAKEN authentication would have to be performed for SanVoice customer traffic is owned, operated, and controlled exclusively by VoIP.ms. SanVoice therefore cannot implement STIR/SHAKEN on any network, because it has no network on which to implement it. The Commission has twice stated this exemption. In the order first adopting the STIR/SHAKEN implementation rules: "we clarify that the rules we adopt today do not apply to providers that lack control of the network infrastructure necessary to implement STIR/SHAKEN." Call Authentication Trust Anchor, Report and Order, WC Docket No. 17-97, FCC 20-42, ¶ 40 (rel. Mar. 31, 2020). And in the order adopting rules governing third-party call authentication: "Providers that lack control over the network infrastructure necessary to implement STIR/SHAKEN, such as switches for voice service in the IP portion of their network, are exempt from STIR/SHAKEN implementation requirements." Call Authentication Trust Anchor, Eighth Report and Order, WC Docket No. 17-97, FCC 24-120, ¶ 8 (rel. Nov. 22, 2024). SanVoice's administrative access to VoIP.ms's hosted PBX interface does not confer control over network infrastructure. The Commission addressed this directly: a facilities-based provider "cannot give control of its network infrastructure to a non-facilities-based provider ... by, for example, providing the non-facilities-based provider with access to software that enables them to enter attestations and certificate information for the purpose of authentication." Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN, Notice of Proposed Rulemaking, FCC 26-32, 91 Fed. Reg. 42602, 42621 (July 9, 2026).
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Peterson Pierre
- Date
- 2026-09-10No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-09-10 | New | Initial certification filed and added to database. |