Current Location ：
Bundled or Unbundled Voice: Choosing a Provider Structure
The choice between one supplier for everything and separate suppliers for platform and connectivity looks like a commercial detail. It shapes what happens on the worst day. A bundled arrangement gives one number to call and one party accountable, at the cost of visibility and leverage. A separated arrangement gives choice and clarity, at the cost of a boundary where faults can be passed back and forth.
What Each Structure Optimises
Bundling optimises for simplicity: one contract, one invoice, one escalation path, one party responsible for end-to-end service. Separating optimises for flexibility: the platform can outlive a carrier relationship, pricing is visible per component, and each element can be replaced on its own terms. Neither is universally correct, and the deciding question is which failure the organisation can tolerate more easily.
| Dimension | Bundled | Unbundled |
|---|---|---|
| Accountability | One party for the whole service | Clear per component, blurred at boundaries |
| Cost visibility | Single figure, allocation is internal | Explicit per component |
| Switching | Difficult; usually a full migration | Component can change independently |
| Fault resolution | One number to call | Diagnosis required before the right call |
| Negotiating position | Limited once committed | Leverage per component |
| Contract risk | Concentrated | Spread |
Accountability Is the Real Currency
The argument for bundling usually rests on accountability, and it is a strong argument. When one party is responsible for the platform and the circuit, a fault cannot be attributed to an unnamed third party. The argument weakens when the bundle is assembled from subcontractors who are invisible to the customer: accountability then exists on paper and not in practice. The question to ask is who actually fixes what, and whether that party is the one you contracted with.
- Ask who performs each function, not only who invoices for it
- Check whether the platform survives a change of carrier
- Confirm exit terms for each component, including numbers
- Compare total cost over the term, not first-year price
- Decide in advance how boundary faults will be diagnosed
A Middle Path That Works
Many organisations end up with a platform they own or license directly, and a carrier relationship they can change. That combination keeps the switching cost low where flexibility matters and keeps the carrier accountable for what it actually controls. It requires the organisation to take responsibility for the boundary, which means either internal capability or a support agreement that covers it explicitly.
Size Changes the Answer
A small organisation with no technical staff usually benefits from a single accountable supplier, because the internal effort of coordinating two is more than the flexibility is worth. A larger organisation with a voice capability can extract real value from separation. The mistake is copying the structure of a different-sized organisation without the capability that made it work.
Redstone Approach
Redstone supplies platforms and gateways directly, which keeps the carrier relationship separate and the platform independent of any single provider. Where customers prefer a managed arrangement, the support boundary is defined in writing so that responsibility for the platform and for the circuit does not become a matter of interpretation during an incident.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
