SIP-provider classification
3CX classifies providers as Preferred, Supported, or without a dedicated guide. Hosted by 3CX requires a supported SIP provider.
3CX SIP Trunks & SBC
Supported scope depends on SIP-provider classification, hosting model, and branch topology. ECOLOR verifies prerequisites and limitations before design approval without guaranteeing carrier or network outcomes.
Router phone or branch SBC
Cloud-connected phone sites use a supported router phone or SBC. Current 3CX router-phone options include Fanvil, Snom, and Yealink; a dedicated SBC suits larger sites.
HA and recovery limits
SBC high availability uses an active/passive design but does not restore active calls. It is separate from PBX failover, which requires ENT/AI and an eligible deployment model.
Pre-deployment readiness checklist
- • Confirm provider classification and hosting eligibility
- • Document support ownership for any generic/custom provider
- • Choose a router phone or SBC for each site
- • Separate SBC HA, PBX failover, and carrier backup paths
Quick answers
When is an SBC required?
Phone sites connected to a cloud PBX use a supported router phone or SBC. A dedicated SBC is selected according to site size and network design.
Can 3CX use any custom SIP trunk?
A generic/custom trunk can be configured, but the provider must understand and support 3CX. 3CX may not assist with an unsupported provider.
Does SBC HA restore active calls?
No. It restores the SBC service after switchover, not calls already in progress, and it is not the same as PBX failover.
Get an implementation-ready SIP/SBC design
Share the provider classification, hosting model, and branch footprint so ECOLOR can prepare a documented design scope for review.