Skip to content
SIPXCloud
esen
SIPX SBC

SIPX SBC: a Session Border Controller for Microsoft Teams, SIP trunks and PBXs

SIPX SBC is your own voice network, sitting between your company’s telephony and external networks. It connects your PBX and Microsoft Teams to carriers, registers local and remote extensions, protects signaling and media, and records every call. It runs in the SIPX Cloud or on your own server, private cloud or Microsoft Azure.

Request a demo See it in action
  • Microsoft Teams Direct Routing template proven in production.
  • SIP trunks with Colombian carriers, by IP or by registration.
  • SIP firewall, country blocking and anti-fraud per extension, trunk and company.
  • Offline installers for Linux and Windows.

What is SIPX SBC?

SIPX SBC is the SIPX Session Border Controller: SIP registrar, proxy and B2BUA in a single system. It registers extensions, connects to one or more carriers, applies least-cost routing with automatic failover, translates between vendors and protects your voice network. Media always flows through the SBC, so it can hide your internal network, solve NAT and diagnose every call.

It brings the browser (WebRTC), IP phones, SIPX Phone, PBXs, Microsoft Teams, the IVR and the contact center onto one network. It is managed from a web console in Spanish and English and through a REST API. It is multi-tenant: one SBC serves several isolated companies, each with its own domains, extensions, limits, rates and reports. It runs inside SIPX Cloud or as a standalone product.

Who is it for?

  • Companies that want to connect Microsoft Teams with their carriers and PBX on a single voice network.
  • Companies with their own PBX (OpenScape, Asterisk/Issabel, Cisco, Avaya, Mitel, 3CX and others) that need secure SIP trunks.
  • Organizations with remote or mobile staff using SIP phones and SIPX Phone over the Internet.
  • Carriers, integrators and partners serving several customers from one SBC, with rates and minute bundles per customer.

Key features

Microsoft Teams Direct Routing

The SBC ships with the “Microsoft Teams Direct Routing” template, proven in production. With it, Teams calls landlines and mobiles through your carriers, your PBX extensions and SIPX Connect and SIPX Phone users over the same network. The SBC handles FQDN contact, the X-MS-SBC header, transfers (REFER) and transcoding from SILK and Opus to G.711.

SIP trunks, routing and interoperability

  • Trunks by IP or by registration, including carriers behind NAT.
  • Trunk groups with least-cost routing and priority failover (up to 5 destinations per route): if a trunk fails, is full or runs out of minutes, the call moves to the next one.
  • Colombia and Venezuela dial plans included, E.164 rules and rules for the presented number.
  • Templates for OpenScape, HiPath, Cisco, Avaya, Alcatel, Mitel, 3CX, Asterisk, Yeastar, Grandstream and Colombian SIP carriers; SIP AutoFix identifies the far-end device and suggests its template.
  • G.711, G.722, Opus, G.729, GSM and SILK codecs, with transcoding to G.711.

Security and anti-fraud

  • SIP firewall against brute force, extension scanning and INVITE floods.
  • Country and reputation blocking (for example, “Colombia only”) and permanent blocking of repeat offenders.
  • Anti-fraud per extension, trunk or company: maximum duration, hourly calls, cost per hour, schedules and high-risk prefixes.
  • Topology hiding, TLS signaling and SRTP media; certificates from an internal CA, imported or from Let’s Encrypt.
  • Emergency calls are never blocked.

Extensions and minute bundles

Bulk extension creation from CSV or Excel, ring and pickup groups, and minute bundles per company, trunk or extension with balance alerts. Per-destination rates calculate the billable amount per customer.

CDRs, quality and monitoring

A record of every call including who hung up and why, reports exportable to Excel and PDF, per-call voice quality (MOS, loss, jitter), a live operations center, alerts by email, Teams, Slack and Telegram, and SNMP with its own MIB.

High availability and updates

In an active-standby pair with a virtual IP, failover has been measured at about four seconds and requires no changes on the PBX or carriers; calls in progress at the moment of the failure are lost. Updates are applied from the console, signed, with a prior backup and automatic rollback if something fails.

Integrations

  • Microsoft Teams Direct Routing and any SIP PBX or carrier.
  • SIPX Connect, SIPX IVR, SIPX Contact Center and SIPX Phone on the same network, with configuration published from SIPX Admin.
  • REST API (OpenAPI 3), webhooks and WebSocket events for n8n, Make, Zapier or in-house systems.
  • SIPX AI Engineer, which checks trunk health, including the Teams trunk.

Capacity and server requirements

Reference tiers for a server running the whole SBC, assuming a 3-minute average call duration. They are guidance only: they are confirmed with a load test on the actual hardware, and a specialist does the final sizing.

Reference tiers

Transcoding (for example, Teams ↔ G.711) adds CPU load and is sized separately.

  • Small: up to 500 concurrent sessions, 4 vCPU, 8 GB RAM (16 GB on Windows) and a 100 GB SSD.
  • Medium: up to 1,000 sessions, 8 vCPU, 16 GB RAM and a 250 GB SSD.
  • Large: up to 5,000 sessions, 16 vCPU, 32 GB RAM, 1 TB NVMe and 10 GbE.
  • Very large: up to 10,000 sessions, 32 vCPU, 64 GB RAM, 2 TB NVMe and 2 × 10 GbE.

Operating systems and network

Ubuntu Server 22.04, 24.04 and 26.04; Debian 12 and 13; Red Hat, Rocky Linux and AlmaLinux 9 and 10; Windows 11 (22H2 or later) and Windows Server 2025, for small sites and labs. It runs on VMware ESXi, Hyper-V, Proxmox, KVM, Azure or bare metal; Linux is recommended for production. It uses SIP on 5060 and 5061, TLS on 5067 for Teams and a UDP media range with four ports per call; behind NAT, that whole range must be forwarded.

Licensing for the installed SBC

  • Licensing is by concurrent sessions: 10, 20, 30, 50, 100, 150, 200 or unlimited. Calls that only ring or go unanswered don’t count, and neither do phone registrations.
  • Options: monthly subscription, annual subscription (with Full support) or perpetual license (with support purchased separately), plus an initial installation.
  • Every new installation runs for 20 days with no session limit.
  • At the limit, the next call hears an announcement; emergency calls always go through and calls in progress are never dropped.

How is it deployed?

Timelines and scope for each project are defined by an advisor based on your case.

  • Sizing: peak-hour concurrent calls, average duration, extensions, codecs and calls that need transcoding.
  • Installation: a cloud SBC, or on your server with the Linux or Windows installer (about 5 to 20 minutes, no Internet needed).
  • Carrier trunks from templates and, if you keep your PBX, a SIP trunk to it without touching it.
  • Microsoft Teams, if needed: a public FQDN verified in your tenant, a public CA certificate and a trunk from the template.
  • Extensions, IP phones and SIPX Phone; backups and, if required, high availability.

Frequently asked questions

Is SIPX SBC the same as sipX or sipXecs?

No. SIPX SBC is the Session Border Controller of SIPX Cloud, the cloud communications platform operated in Colombia by Eléctricos y Comunicaciones Electrocom S.A.S. (sipx.co). It is not related to sipX or sipXecs, the open-source PBX project with a similar name.

Does it work with Microsoft Teams?

Yes, with Microsoft Teams Direct Routing through SIPX SBC, which includes a Teams template proven in production. You need a public FQDN verified in your Microsoft 365 tenant, a public CA certificate, TLS and SRTP. The Microsoft-side configuration is reviewed with a specialist.

Can I use a self-signed certificate for Teams?

No. Microsoft only accepts certificates from public CAs it trusts. The SBC can generate the request (CSR), import the certificate or use Let’s Encrypt, and it warns you before it expires.

Can I keep my current PBX?

Yes. It connects to SIPX SBC through a SIP trunk, and the SBC includes templates for the main PBX brands. Compatibility with a specific model is confirmed by a specialist.

Can I buy just the SBC, without SIPX Cloud?

Yes. SIPX SBC is offered as a standalone product to install on your server, private cloud or Microsoft Azure.

How many concurrent calls does it support?

It depends on the server: reference tiers range from 500 to 10,000 sessions. The larger tiers are confirmed with a load test, and a specialist does the final sizing.

How does it protect against fraud?

With a SIP firewall, country and reputation blocking, blocking of repeat offenders, cost, schedule and destination limits per extension, trunk and company, and TLS and SRTP encryption. Emergency calls are never blocked.

What happens if the SBC server goes down?

With high availability, the standby node takes over the virtual address in about four seconds and new calls keep coming in. Calls in progress at that moment are lost.

How is it licensed, and what does it cost?

By concurrent sessions, as a monthly or annual subscription or a perpetual license, plus an initial installation. Pricing is quoted by an advisor based on sessions, license type and installation.

Can I try the SBC before buying?

Yes. Every new installation runs for 20 days with no session limit.

Related products

They all share the same users, numbers and data on SIPX Cloud.

See the whole ecosystem
← Back to home
Book a demo

One platform, one provider, one bill.

We’ll show you Connect, the AI-powered IVR, the contact center and the Service Desk running with your company’s data.

  • Nothing to install: it runs in the browser
  • AI included in every product
  • Pay for what you use: Small, Medium or Full