For providers
A bounded integration, and a peering relationship you help govern.
The practical ask is small: one interconnect, a route decision, and controlled media. The practical return is direct delivery to other members’ customers under rules you had a hand in writing.
The ideal founding-member profile
The pilot is deliberately small. These are the characteristics that make a provider a good fit for the first cohort.
- Operates business voice and controls — or can influence — outbound routing.
- Can add a federation SIP peer or a compatible external route decision.
- Serves a meaningful base of business customer numbers or identities.
- Wants a neutral peering relationship with other providers rather than another wholesale supplier.
- Can participate in a limited pilot and help shape the operating rules while they are still being written.
What membership gives you
One relationship, many members
A single authenticated interconnect replaces the overhead of negotiating and maintaining separate bilateral arrangements with each provider.
Known counterparties
Every session that crosses the federation has an identifiable member on each side, operating under the same technical and abuse rules.
A controlled media boundary
Media is proxied where the deployment requires it, so the path is defined rather than inherited from whatever the wholesale chain happened to do.
Usage records both ways
Both members get records for federation traffic, which makes reconciliation and dispute handling tractable.
A vote on the rules
Founding members shape membership criteria, eligibility rules, identity policy, and the dispute process before they are fixed.
No lock-in commitment
Interoperability is a governing principle. Membership should not permanently tie a provider or an identity to one vendor.
Integration expectations
The initial network supports more than one routing pattern, because provider platforms differ substantially in how much routing control they expose.
| Your environment | Likely integration | What we need from you |
|---|---|---|
| Flexible LCR or SBC control | Federated-destination lookup ahead of your ordinary route selection. | A federation SIP peer, and the ability to prefer it for eligible destinations. |
| Platform-constrained routing | External routing-engine integration, or an approved adapter. | A supported hook into route selection, or willingness to work through an adapter with us. |
| Closed or fully hosted platform | May not be integrable in the pilot phase. | An honest look at what your platform exposes. We would rather say so early. |
We do not promise universal compatibility. Some platforms will not be able to make a federated route decision without vendor cooperation. Part of the pilot’s purpose is to establish which patterns actually work in production, and to be specific about which do not.
The Founding Member Pilot
A limited multi-provider interconnect, run with a small cohort, with the explicit goal of producing working technical and governance rules.
The pilot includes
- A federation connection for each participating member.
- An eligibility directory of registered member-served destinations.
- A controlled RTP path.
- Usage records for federation traffic.
- A shared support and escalation process.
The pilot excludes
- General PSTN fallback termination.
- Any commitment about pricing against wholesale minutes.
- Any claim of regulatory exemption for participating providers.
- Universal platform compatibility.