Order the trunk, channels and access as separate resources
Orange's January 2026 service description says a customer connecting a PBX, SBC, telephony system or supported cloud telephony provider must order a SIP trunk and Voice Channels. One Voice Channel carries one call at a time, and the customer determines the ordered channel count. The trunk, channel quantity and access are therefore separate order lines rather than one generic capacity claim.
Record the contracting entity and country, service version, site, access type, SIP trunk, voice channels, PBX or SBC, demarcation, numbers, emergency owner, support contacts and current portal inventory. Public global coverage language does not establish local serviceability or a completed order.
Bind capacity to the selected access type
Business Talk can use customer-provided Internet access or ordered Orange BVPN, Satellite or SD-WAN access, subject to the current service description. Orange says access bandwidth must match the requested channel count and notes that channels on BVPN Small or Satellite access are not committed or guaranteed.
Preserve access ownership, bandwidth, quality class, diversity, SBC placement and channel commitment from the signed order. One channel per call does not establish calls per second, codec overhead, transcoding, failover headroom or useful audio under load.
Keep Internet-access security and certificate operations explicit
For the documented Internet-access path, the customer maintains the SBC and supplies valid security certificates to Orange, including advance replacement before expiry. That responsibility is narrower than proof that one deployed certificate, TLS session or media-security profile is accepted.
Retain SBC model and software, public identity, certificate chain and dates, private-key owner, peer list, SIP transport, SDP protection, firewall policy, rotation window and rollback. Certified configuration guides are vendor and version evidence, not universal templates for every PBX or cloud provider.
Treat country, number and emergency records as local evidence
The current product page describes global voice, number provisioning or portability, domestic and international breakout and access to emergency services, while stating that offer details vary by country. The service description also says local voice services such as DID, DOD and emergency calling can be limited by legal, regulatory and other constraints.
For each location, retain serviceability, number inventory and port state, allowed calling scope, asserted and delivered identities, emergency zone or address, callback, notification, outage behavior and provider-approved validation. Do not transfer one country's availability or emergency behavior to another.
Use digital management as control evidence, not call proof
Business Talk Digital exposes management of sites, trunks, numbers, emergency zones, portability and product news through portal or API, and Orange describes inventory, reporting, incident and billing functions. A successful API update or green inventory row does not establish that a SIP INVITE reached the intended PBX or that media was usable.
Correlate order, portal or API change, loaded SBC or PBX state, SIP transaction, route, answer, two-way audio, DTMF, fax if ordered, failover and restoration. Preserve API identity, authorization and change history without exposing tokens or customer numbers.
Close commercial and operational boundaries from the current order
Orange publishes a global service description, service-level material, tariff and numbering documents, but the applicable document can depend on contracting region and selected service. Use the signed order and applicable current publication for channels, access, numbers, usage, continuity, emergency service, service levels, support, implementation, taxes, renewal and cancellation.
Messaging is not established by the reviewed Business Talk voice records. Fax, exact codecs, DTMF, encryption, interoperability and continuity must be confirmed for the selected certified design and country. No Orange service, trunk, number, call, media path, emergency workflow, price or support response was validated for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Orange Business Talk ↗
- Business Talk global service description — January 2026 ↗
- Business Talk and Contact Center service documents ↗
- Orange service publication ↗
- Business Talk Digital API overview ↗
- Business Talk Digital API reference ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.