shubovich.ru
RUEN
xPBX · IP telephony platform

xPBX
Enterprise IP telephony for distributed organizations and contact centers

xPBX unites branch PBXs into a single cluster, connects carriers through its own SIP border controller and routes calls with JavaScript instructions, free from the limits of off-the-shelf PBXs.

Discuss a project Features
CarriersSIP · 1SIP · 2SIP · 3SIP borderKamailioPBX clusterPBX 1AsteriskPBX 2AsteriskPBX 3AsteriskEmployeesContact centerVoice agents
Carriers → Kamailio → PBX cluster → employees, operators and agents
1000+concurrent calls for large enterprises and high-load operations
Clusterbranch PBXs with a unified numbering plan
JavaScriptcall routing defined by instructions, not settings
On‑prem / Clouddeployment on the customer's premises or in the cloud
Features

Enterprise-grade communications infrastructure

The platform is built on Asterisk and Kamailio, with configuration stored in PostgreSQL. Everything usually configured by hand on each PBX is managed centrally in xPBX.

Cluster

Unified PBX cluster

Every PBX is a cluster node. An extension can be served by several PBXs, and calls between nodes are routed automatically by priority.

Routing

JavaScript instructions

Call logic is written as code: CRM requests, project variables, queues, external lines. Any scenario you can describe can be implemented.

SIP border

Kamailio border controller

Carriers are connected through a border controller: load-balancing pools, line redundancy, registration with the carrier, border call accounting, scan protection.

Parameters

Variables and variable sets

Route parameters are set at project, account and variable-set level with a clear order of precedence.

AI

AI service integration

Speech synthesis directly from the call scenario, handover to a VoiceAI voice agent and back to an operator.

Management

Projects and administration

Independent projects for divisions and clients, a web administration console and an open API for integrations.

Routing

Call logic is code

A short JavaScript instruction replaces dozens of settings screens. The scenario reads the channel data, queries your systems and decides where the call goes.

  • HTTP requests to CRM, ERP and internal services during the call
  • Extensions, queues, external lines and carrier trunks
  • Project and account variables, parameters that survive transfers between PBXs
  • Speech synthesis and handover to a voice agent
route/inbound-sales.js
1// Inbound call to the sales department2const caller = channel.getVariable('CALLERID(num)');3 4// Look the customer up in the CRM by number5const res = http.request({6  url: `${route.vars.CRM_URL}/clients?phone=${caller}`,7});8 9if (res.status === 200) {10  const client = JSON.parse(res.body);11  // A regular customer goes straight to their account manager12  route.callExtension(client.manager);13} else {14  // New callers go to the sales queue15  channel.enterQueue('sales');16}
Contact center

Contact center extensions

xPBX handles the voice side of the contact center, while the xFlow and xDesk extensions handle the operators' work.

Contact center floor by day: a team lead with a colleague at a workstation, rows of operators in headsets behind them
Operator management

xFlow

Workstation server: operator states and pauses, pause policies, request distribution, real-time call events.

Operator workstation

xDesk

The operator application with a built-in softphone. The request handling interface is supplied by us or connected from the company's systems.

Queues

Voice queues

Calls are distributed to queues from JavaScript instructions, including after a dialog with a voice agent.

xDesk open architecture

A clear boundary between the platform and business logic

The platform handles telephony, operator states, request distribution and shift control. The substantive part of the workstation, such as the customer card, handling scenarios and forms, is developed by us for the customer's tasks. If preferred, the company can build it itself using familiar web technologies and its own systems.

  • A request opens in the workstation as a page with the customer data: developed by us or served by your CRM
  • The page talks to the platform through a JavaScript API: call events, transfer, completion of handling
  • Changes to business processes require no platform changes and no workstation updates
  • Critical functions stay with the platform: softphone, states, pauses, working time tracking
xDeskOn line · 02:14Inbound · 00:41TransferPause
crm.company.com/activity/48213
Ivan Petrov
  • Contract No. 2024/118
  • Last request: September 12
  • Open ticket: equipment replacement
Complete handling
⇅ JavaScript API
xDesk platformBusiness logic: our development or your system
Scale

One platform from a single office to a branch network

The architecture stays the same; only the number of nodes and connected systems changes.

Mid-size business

Office and branches, 50–⁠500 employees

Your own telephony instead of a cloud PBX: your numbers and carriers, routing by working hours and departments, CRM integration.

  • One or several PBXs
  • Several carriers connected
  • Inbound routing based on CRM data
  • A front-line voice agent when needed
Enterprise

Branch network and contact center

A regional PBX cluster with a unified numbering plan, carrier line redundancy, a contact center with hundreds of operators and voice agents.

  • PBX cluster with routing between nodes
  • Carrier line pools and redundancy
  • xFlow and xDesk for the contact center
  • Integration with CRM, ERP and industry systems
Contact

Let's discuss your project

We will contact you, clarify the requirements and propose a pilot project format. Pricing is determined individually based on the assessment.

Product of interest