Run 6X's wholesale voice and SMS routing engine on your own dedicated server instead of 6X's shared infrastructure. Your portal, billing, and white-label branding stay exactly where they already work — only the routing engine moves.
No accounts to create beyond your installation key, no separate PBX platform to learn — one script does the rest.
Get the appliance files onto your server — a real tarball, not a document telling you to find it yourself.
One command for a blank Debian 12 box, or a lighter one if you already run a voice engine and Docker your own way.
Your box polls 6X every 30 seconds for vendors, rates, and balances — it won't take its first call until that first sync lands.
Download and extract it on your server before running anything else.
cd /root wget https://softswitch.6xcom.com/download -O 6x-switch-appliance.tar.gz tar xzf 6x-switch-appliance.tar.gz cd appliance
This creates an appliance/ folder with everything the installer needs. Run every command below from inside that folder.
Pick the path that matches your server.
Most customers want this. Installs the voice engine (compiled fresh — the official package needs a separate account elsewhere, so this avoids that step), Docker, and everything else, then finishes the install for you.
sudo ./bootstrap.sh your-real-keyLong — 30-60+ minutes since it builds the voice engine from scratch. That's expected; walk away and check back. Refuses to run if a voice engine is already present, or on anything but Debian 12.
Checks your prerequisites, writes your local config, initializes the local cache, wires the dialplan, starts the SMS engine, and installs the background sync service.
sudo ./install.sh your-real-keyThis is also exactly what bootstrap.sh runs at the end of its own process — both paths end up here.
About your-real-key
Every example above shows a placeholder — replace it entirely with the actual installation key 6X gave you, nothing added, nothing kept from the placeholder itself. If you ever see angle brackets like <your-installation-key> in older docs, those meant the exact same thing: a stand-in to replace, not literal characters to type. Typed them in by mistake anyway? Both scripts now catch this directly and tell you exactly what to fix instead of failing with a confusing error.
journalctl -u 6x-switch-sync -f
The sync service polls 6X every 30 seconds for your vendor list, rates, and customer balances. Your box won't accept its first call until the first successful sync lands — expected, not an error.
Your box checks a customer's balance locally before routing a call — fast, no network round-trip needed. The moment a call ends, it reports back to 6X the same way a centrally-hosted call already does, and that's what actually bills the customer — 6X's records are always the source of truth, your local copy just gets corrected on the next sync.
Your box keeps running normally on its last-known data for 60 minutes — long enough to ride out any realistic network hiccup. Past that window, it stops accepting new calls until the connection recovers. No local override, by design: a short cushion protects your day-to-day service, and the eventual stop protects both sides from billing against numbers that might be badly out of date.
Your 6X Softphone and any Voice Broadcast / Power Dialer / Predictive Dialer campaigns always route through 6X's central servers, not your own box — on purpose, so billing and vendor routing stay correct against your account. Your box reports its session usage every 30 seconds; if it goes quiet for 5+ minutes, centrally-routed sessions pause until it reports in again.
Central 6X updates reach you automatically, same as every customer. Code running directly on your box only changes when you run it yourself:
sudo ./update.sh
Backs up everything it's about to replace first, updates only the routing/sync code, and restarts the sync service — your installation key and live local balance cache are never touched. Safe to run any time.
Check /opt/6x-switch/config.env has your real installation key, not the placeholder value.
Confirm at least one vendor is active on your account and a sync has completed successfully (journalctl -u 6x-switch-sync).
Ask 6X to regenerate it — the old one stops working the instant a new one is issued, so update config.env as soon as you get the replacement.
No. Your login, dashboard, logo, colors, and custom domain are all served from 6X's platform, completely independent of where your call traffic physically runs. A local dashboard also now runs on your own box for managing your downstream customers at your own IP if you prefer - it's additional, not a replacement, and everything it shows still comes from 6X's platform.
Run Step 1 above first — bootstrap.sh and install.sh both expect to run from inside the extracted appliance/ folder. If you're starting from a truly blank server, that folder won't exist until you download and extract the package.
Chat with 6X to get provisioned as a self-hosted Switch partner — pricing, trial, and setup all in one conversation.