{"id":859,"date":"2026-10-12T15:13:56","date_gmt":"2026-10-12T15:13:56","guid":{"rendered":"https:\/\/microtalk.co.uk\/blog\/?p=859"},"modified":"2026-10-12T15:13:56","modified_gmt":"2026-10-12T15:13:56","slug":"compliance-obligations-for-intermediate-providers-and-gateway-carriers","status":"publish","type":"post","link":"https:\/\/microtalk.co.uk\/blog\/compliance-obligations-for-intermediate-providers-and-gateway-carriers\/","title":{"rendered":"Compliance Obligations for Intermediate Providers and Gateway Carriers"},"content":{"rendered":"

Gateway Carrier Compliance<\/span>: Vetting Foreign Partners and Blocking Illegal Traffic<\/h1>\n
\n
\n

The Loophole That No Longer Exists<\/p>\n

For years, the FCC<\/span>‘s STIR\/SHAKEN requirements focused primarily on terminating carriers\u2014the providers that deliver calls to consumers. Intermediate providers\u2014the carriers that help route calls from one network to another\u2014were largely overlooked.<\/p>\n

That loophole has now been closed.<\/p>\n

The FCC<\/span> has expanded STIR\/SHAKEN<\/a> requirements to require intermediate providers that are the first to pick up a call from an originating carrier to use STIR\/SHAKEN. In other words, if you are an intermediate provider and you receive a call from an originating carrier, you must authenticate that call using STIR\/SHAKEN.<\/p>\n

Who Are Intermediate Providers and Gateway Carriers?<\/p>\n

Intermediate Providers: Carriers that sit between originating carriers (which start calls) and terminating carriers (which deliver calls to consumers). They route traffic across networks.<\/p>\n

Gateway Carriers: Carriers that accept traffic from foreign originating providers and bring it into the U.S. telecommunications network. They are the “point of entry” for international calls.<\/p>\n

Both types of carriers now have significant compliance<\/span> obligations under FCC<\/span> rules.<\/p>\n

Intermediate Provider Obligations<\/h2>\n

Intermediate providers must now:<\/p>\n

Implement STIR\/SHAKEN: If you are the first intermediate provider to receive a call from an originating carrier, you must authenticate that call using STIR\/SHAKEN.<\/p>\n

Maintain RMD Certification<\/a>: Like all voice service providers, intermediate providers must be listed in the RMD.<\/p>\n

Respond to Traceback Requests: All carriers, regardless of position in the call path, must respond to traceback requests within 24 hours.<\/p>\n

Block Based on DNO Lists: The FCC<\/span>‘s call blocking requirements apply to all providers in the call path, not just terminating carriers.<\/p>\n

Gateway Carrier Obligations<\/h3>\n

Gateway carriers have additional, specialized obligations:<\/p>\n

Vet Foreign Partners: Gateway providers must take reasonable and effective steps to ensure that foreign originating providers and foreign intermediate providers are not using the gateway to carry high volumes of illegal traffic onto the U.S. network.<\/p>\n

Block Illegal Traffic: If a foreign partner is generating illegal traffic, the gateway provider must block that traffic.<\/p>\n

Mark Foreign-Originated Calls: The FCC<\/span> is proposing to require gateway providers to mark foreign-originated calls, intermediate providers to pass the indicator, and terminating providers to display a foreign-origin indicator to consumers.<\/p>\n

Include Foreign Origin in Analytics: The FCC<\/span> is proposing to require voice service providers to include whether a call originated from outside the United States as a factor in their call blocking analytics.<\/p>\n

The Traceback Obligation<\/h4>\n

All carriers\u2014intermediate providers, gateway carriers, and terminating carriers alike\u2014have a critical traceback obligation.<\/p>\n

The purpose of a traceback is to identify the provider that originated the call (or, for overseas calls, the gateway U.S. provider that first accepted the call).<\/p>\n

The 24-Hour Rule: All domestic voice service providers must respond to traceback requests from the FCC<\/span>, civil and criminal law enforcement, and the industry traceback consortium within 24 hours of receiving the request.<\/p>\n

The Blocking Consequence: If an originating carrier fails to mitigate illegal traffic after being notified by the FCC<\/span>, the FCC<\/span> may require all providers immediately downstream to block all of that provider’s traffic.<\/p>\n

Why This Matters for Your Business<\/h5>\n

If you are an intermediate provider or gateway carrier, the FCC<\/span>‘s expanded rules mean you can no longer operate in the background. You are now on the front lines of the fight against illegal robocalls.<\/p>\n

The Consequences of Non-Compliance<\/span>:<\/p>\n

– RMD Removal: Failure to comply with STIR\/SHAKEN or other obligations can result in removal from the RMD.<\/p>\n

– Traffic Blocking: Other carriers may be required to block your traffic.<\/p>\n

– Fines: The FCC<\/span> can impose significant penalties for non-compliance<\/span>.<\/p>\n

– Reputation Damage: Public enforcement actions can harm your business relationships.<\/p>\n

The Bottom Line<\/pre>\n
Intermediate providers and gateway carriers are no longer exempt from FCC<\/span> compliance<\/span> obligations. The loophole has been closed, and the rules now apply to the entire call path.<\/p>\n
At Microtalk<\/a>, we help all types of carriers\u2014intermediate, gateway, and terminating\u2014navigate FCC<\/span> compliance<\/span> requirements. In today’s regulatory environment, every carrier in the call path is accountable.<\/p>\n
Are you an intermediate provider or gateway carrier? Is your compliance<\/span> up to date?<\/p>\n<\/div>\n<\/div>\n"},"excerpt":{"rendered":"
Gateway Carrier Compliance: Vetting Foreign Partners and Blocking Illegal Traffic The Loophole That No Longer Exists For years, the FCC‘s STIR\/SHAKEN requirements focused primarily on terminating carriers\u2014the providers that deliver calls to consumers. Intermediate providers\u2014the carriers that help route calls from one network to another\u2014were largely overlooked. That loophole has now been closed. The FCC […]<\/p>\n","protected":false},"author":6,"featured_media":860,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[319],"tags":[366,162,322,372,371,4,370,165,368,373,367,301],"class_list":["post-859","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fcc-compliance-for-usa-traffic","tag-carrier-compliance","tag-contact-centre","tag-fcc-compliance","tag-gateway-carriers","tag-intermediate-provider","tag-microtalk","tag-robocall-mitigation","tag-stir-shaken","tag-telecom-regulation","tag-traceback","tag-voice-service-provider","tag-wholesale-voice"],"_links":{"self":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts\/859","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=859"}],"version-history":[{"count":2,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts\/859\/revisions"}],"predecessor-version":[{"id":862,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts\/859\/revisions\/862"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/media\/860"}],"wp:attachment":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=859"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=859"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=859"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}