Regulatory posture & network integrity.
CallONet operates as a US wholesale voice carrier and structures its network practices around FCC robocall-mitigation expectations, caller ID authentication standards, and traceback cooperation. This page summarizes our posture in plain language; it is not legal advice.
STIR/SHAKEN awareness
Our platform is built to recognize and pass through STIR/SHAKEN caller ID attestation signaling on traffic that carries it, and we work with upstream and downstream partners to preserve attestation across the call path where technically supported.
Robocall mitigation
CallONet maintains internal practices consistent with FCC robocall-mitigation expectations for voice service providers, including monitoring for anomalous calling patterns and responding to credible complaints.
Traceback cooperation
We cooperate with industry traceback consortiums, upstream carriers, and law enforcement requests related to suspected illegal robocalling or spoofed traffic traversing our network.
The regulatory landscape we operate inside.
A quick primer on the frameworks that shape how CallONet builds and monitors its network. This is general information, not a substitute for your own legal review.
TRACED Act & STIR/SHAKEN
Federal rules require voice service providers to implement caller ID authentication and to file robocall-mitigation information with the FCC. CallONet structures its interconnection and signaling practices with these expectations in mind.
TCPA & Telemarketing Sales Rule
Customers using CallONet routes or leads for outbound calling or texting remain responsible for their own compliance with consent, Do-Not-Call, and calling-time requirements under applicable federal and state law.
Robocall Mitigation Database (RMD)
Voice service providers are expected to submit robocall-mitigation certifications to the FCC's database. We expect the same of downstream carrier customers who originate or terminate traffic through us.
State telemarketing & privacy law
Several states impose their own telemarketing, robocall, and data-privacy requirements in addition to federal law. Customers are responsible for compliance in every state they call into.
What "bad traffic" enforcement actually looks like day to day.
Policy only matters if it's enforced. Here is a summary of the mechanisms CallONet uses to keep unlawful and abusive traffic off the network. The full contractual policy is in our Terms of Use.
- Volume and pattern monitoring to flag sudden spikes, short-duration call bursts, or sequential dialing patterns typical of robocalling.
- Caller ID integrity checks to identify unauthorized or invalid CLI spoofing.
- Complaint intake from consumers, carriers, and industry traceback groups, reviewed against account traffic logs.
- Graduated enforcement ranging from route throttling to immediate suspension for confirmed violations.
- Cooperation with lawful requests from carriers, regulators, and law enforcement investigating specific numbers or campaigns.
1. Flag & investigate
Automated and manual review of the reported traffic.
2. Warn & require remediation
Account is notified and given a defined window to correct the issue.
3. Throttle or suspend routes
Affected routes are limited or paused pending resolution.
4. Terminate & report
Confirmed bad actors are disconnected and may be reported to carriers or authorities.
This page is informational, not legal advice. Telecom compliance obligations vary by service type, calling pattern, and state, and change over time. Consult qualified legal counsel to confirm your own obligations under the TCPA, TSR, TRACED Act, and applicable state law before launching a calling or texting campaign.
Have a specific compliance question?
Our team can walk through documentation requirements before you sign up.