Provider certification record

Crown Enterprises

Listed

Identity

Legal business name: Crown Enterprises
Doing-business-as
Foreign Voice Service Provider: No
Business address: 1201 N El Dorado Street, Stockton CA 95202
Filing contact: Mark Williams
CEO · Operations
support@ce-technology.com
(209) 390-4670
1201 N El Dorado Street Stockton CA 95202
United States of America
Principals, Affiliates, Subsidiaries, and Parent Companies: Mark Williams, Inc.

Provider role(s): Voice service provider
STIR/SHAKEN implementation: Role Implementation
Voice service provider None
Overall None
Exemption rules: Our organization originates calls using Bandwidth.com, a fully STIR/SHAKEN-compliant Voice Service Provider (VSP). Under 47 CFR § 64.6304(a) and FCC Orders associated with WC Docket No. 17-97, a provider is exempt from implementing STIR/SHAKEN within its own network when: The provider’s calls are transmitted through an upstream VSP that already performs STIR/SHAKEN authentication, and The upstream VSP is the provider that inserts the STIR/SHAKEN attestation headers into the SIP signaling, The upstream VSP is themselves certified in the Robocall Mitigation Database, and The filer does not have direct access to the underlying IP interconnection points where STIR/SHAKEN can be technically implemented. Our organization meets all of these conditions. We originate calls exclusively through Bandwidth.com, who performs full STIR/SHAKEN A/B/C attestation and signs calls on our behalf. As a result, we cannot technically apply STIR/SHAKEN ourselves at the interconnection level, and therefore we fall under the “reliance on an upstream provider” exemption in 47 CFR § 64.6304(a).

Role	Implementation
Voice service provider	None
Overall	None

Description: There was no law enforcement action or regulatory investigation initiated against our organization. The only activity related to our filing was administrative in nature. On August 6, 2025, we were notified that our Robocall Mitigation Database (RMD) submission required updates under the FCC’s latest filing requirements, but unfortunately this email was not seen until August 25, 2025. We promptly updated our filing on August 26 2025 with our updated contact information, and provided all required supporting documentation. Following the update, the FCC provisionally restored our status in the Robocall Mitigation Database. There has been no finding of wrongdoing, no allegation of misconduct, and no action taken by any law enforcement or regulatory agency. No final determinations were necessary or issued, as the matter was limited solely to updating our documentation to comply with the revised RMD requirements.

Date	Event	Detail / diff
2026-02-17	New	Initial certification filed and added to database.