Robocall Mitigation

RMD registered. TRACED Act compliant.

SIPNEX maintains an active filing in the FCC Robocall Mitigation Database with complete STIR/SHAKEN implementation. Your calls originate from a carrier that meets every FCC requirement. Downstream carriers accept our traffic. Your calls reach the network. New to the database itself? Start with our FCC Robocall Mitigation Database explainer.

Active RMD Filing

SIPNEX maintains a current, active filing in the FCC Robocall Mitigation Database. Complete STIR/SHAKEN implementation — not just a mitigation program. Updated annually as required.

Complete STIR/SHAKEN

Our RMD filing certifies complete STIR/SHAKEN implementation. We hold our own SP-KI certificate and sign every IP-originated call. This is the highest level of RMD compliance.

Know Your Customer

Every SIPNEX account undergoes KYC verification. We verify business identity, authorized contacts, and intended use before provisioning service. Illegitimate operations are identified and rejected during onboarding.

Traffic Monitoring

Real-time monitoring for calling patterns associated with illegal robocalling — unusual volume spikes, rapid CID rotation through unverified numbers, calls to DNC-heavy area codes. Suspicious patterns trigger investigation.

Traceback Cooperation

Full cooperation with Industry Traceback Group (ITG) requests. When illegal traffic is traced, we identify the source account, investigate, and take enforcement action including service suspension.

AUP Enforcement

Our Acceptable Use Policy explicitly prohibits illegal robocalling, spoofing, and DNC violations. Violations result in investigation and potential service suspension. The AUP protects every customer on our network.

SIPNEX compliance vs minimum requirements.

SIPNEXFCC MINIMUM
RMD registrationActive, current filingRequired
STIR/SHAKENComplete implementation (own cert)Required for IP carriers
Attestation capabilityA-level for verified DIDsAny level
KYC verificationFull business verificationReasonable steps
Traffic monitoringReal-time anomaly detectionProgram required
Traceback cooperationFull ITG cooperationRequired
AUP enforcementActive enforcement + suspensionProgram required
Filing updateAnnually + as neededAnnual

Frequently asked questions.

Is SIPNEX registered in the RMD?
Yes. SIPNEX maintains an active RMD filing with complete STIR/SHAKEN implementation. We hold our own SP-KI certificate and sign every IP-originated call with STIR/SHAKEN attestation. Our filing is publicly verifiable at fccprod.servicenowservices.com/rmd.
What does SIPNEX's robocall mitigation program include?
SIPNEX's program includes: complete STIR/SHAKEN implementation (every IP call signed with our SP-KI certificate), Know Your Customer (KYC) verification for all accounts, real-time traffic monitoring for patterns associated with illegal robocalling, Acceptable Use Policy enforcement with service suspension capability, and cooperation with the Industry Traceback Group (ITG) for traceback requests.
What is traceback and does SIPNEX participate?
Traceback is the process of identifying the source carrier of illegal robocall traffic by tracing the call path from the recipient back to the originator. The Industry Traceback Group (ITG) coordinates traceback efforts across carriers. SIPNEX cooperates with all ITG traceback requests as required by FCC rules. If illegal traffic is traced to our network, we investigate and take enforcement action against the responsible account.
Does RMD registration affect my calls directly?
Your carrier's RMD registration is a prerequisite for your calls reaching the terminating network. Without it, downstream carriers may block your traffic. With it (plus STIR/SHAKEN signing), your calls enter the network as authenticated traffic from a compliant carrier. RMD registration is the network-access layer. STIR/SHAKEN attestation is the per-call trust layer. You need both.

Your calls deserve a compliant carrier.

RMD registered. STIR/SHAKEN certified. Independently verifiable.