VSI VoIP Stack Index Business VoIP comparison tools

Restricted calling classification

FCC's Tin Can Ruling Makes PSTN Restrictions a VoIP Proof Test

A September 30 ruling turns restricted calling into a technical classification question. A contact list alone does not establish that a business phone service qualifies.

Run readiness audit Estimate VoIP cost
Synthetic representative editorial scene of an unbranded corded telephone in a home hallway; not Tin Can's product or a photograph of an FCC event.
Editorial image: synthetic representative telecom scene, not a photo of the named company or news event.

Direct answer

FCC Tin Can non interconnected VoIP Party Line Plan ruling: what buyers need to know

The FCC's Wireline Competition Bureau classified Tin Can's described Party Line Plan as non-interconnected VoIP in DA 26-1057. Its reasoning rests on individually approved contacts and restrictions that users cannot bypass to obtain general PSTN access. A buyer evaluating a restricted-calling service should ask for technical evidence of those boundaries and a written obligations analysis before accepting a classification or changing a compliance budget.

Published 10/5/2026 News event 9/30/2026

This brief cites the source announcement and translates the event into a buyer framework. Verify current vendor terms before changing phone, messaging, or AI routing.

What happened

  • The September 30 ruling addresses Tin Can's specific whitelist service and says its analysis extends to other services only when they share the material characteristics identified in the order.
  • The Bureau distinguishes limited, individually selected PSTN contacts from general access. It also considers whether customers view the service as a replacement for a household phone line.
  • The order identifies continuing applicable obligations, including Robocall Mitigation Database filing and TRS Fund contributions, and records Tin Can's emergency-service commitments.
  • The Bureau leaves the company's CALEA applicability request for a later decision. The order is not a blanket exemption for every whitelist, private network or business VoIP plan.

Why this is trending

  • An actual FCC classification decision gives restricted-contact phone services a concrete regulatory reference, rather than a proposed rule or comment deadline.
  • The CommLaw Group's October 1 advisory highlights consequences beyond the petitioner. The useful buyer question is whether a proposed service can demonstrate the same relevant behavior.
  • This differs from recent number-custody, emergency-outage and robocall-filing coverage: the asset tests the technical facts supporting a service classification.

The VoIP Stack Index take

An illustrative buyer may see a provider advertise a private contact list and assume that normal phone-service obligations disappear. A list can be an interface preference rather than an enforced network boundary. Test incoming and outgoing calls, administration, integrations and alternative clients. Keep that evidence separate from counsel's legal conclusion. This framework is an editorial procurement aid, not a determination that any other provider qualifies.

Restricted PSTN Classification Proof Map

An original evidence map connecting service behavior, bypass testing, emergency exceptions, remaining obligations and change control.

Restricted PSTN Classification Proof Map framework visual
Evidence layerBehavior checkDecision ownerVoIP evidence
PSTN access Document the permitted inbound and outbound contact paths. The service owner approves each permitted contact under the actual design. Network diagram, routing policy and tests showing what happens to an unapproved number.
Bypass resistance Test account controls, APIs, forwarding and alternate clients. A reviewer records whether any path enables general calling. Failed-call traces and a documented assessment of every route, not only app screenshots.
Service positioning Compare the product's behavior with its public sales description. Counsel assesses whether users treat it as basic phone-service replacement. Current terms, marketing copy and a written classification rationale tied to the order.
Emergency exceptions Document the distinct emergency route and callback behavior. An accountable owner confirms implementation with safe test procedures. Emergency-service commitments, registered-location process and provider-approved test evidence.
Remaining obligations List applicable filings, contributions and accessibility requirements. Compliance owners confirm duties rather than infer a broad exemption. Obligations register, filing evidence and explicit treatment of unresolved questions.
Change control Flag a new feature that adds unrestricted calling. Review classification before materially expanding the service. Release approval, revised route tests and updated counsel review.

What buyers should do next

01

Obtain the actual service diagram and a current copy of DA 26-1057, then identify which material facts the provider claims to share.

02

Test unapproved inbound and outbound contacts, administrative bypasses, forwarding and integration paths without placing live emergency calls.

03

Ask for a written classification review and an inventory of the obligations that remain applicable.

04

Review emergency behavior and user disclosures through the provider's approved test process.

05

Require a new classification review before adding features that change PSTN access or service positioning.

Buyer bridge

Do the routing audit before buying the buzz.

The winning AI phone stack is the one that preserves context, controls fallback, and lets humans take over without making the customer repeat the story.

Run the AI-ready VoIP audit