Skip to content

RBC

Network & Telecom

Precise control over every call you carry.

RBC replaces hand-edited switch configuration with a console built for voice operations: customers and their limits, providers and their routes, the calls in progress and the records they leave behind.

The problem

Voice routing lives in config files

Many VoIP operators still manage customers, trunks and dial plans by editing configuration on each switch. Every new customer, rate-limit change or route adjustment is a manual edit that only a few engineers are trusted to make.

When a route fails or a customer disputes a call, the answers are spread across servers, log files and spreadsheets.

  • Routes and prefixes edited by hand on each server
  • Customer call limits that are not enforced consistently
  • No live view of the calls in progress
  • Call records scattered across nodes

Key capabilities

What RBC does

A self-hosted control console for VoIP operators. Manage SIP customers, termination providers and call routing from one place, watch active calls as they happen and keep a durable record of every completed call.

  • Call routing

    Ordered route groups, customer and global prefix rules, number rewriting and failure policies, with a tester that shows the routing decision before a call is placed.

  • SIP customers

    Customers authenticated by credentials, IP access list or both, each with calls-per-second and concurrent-call limits.

  • Termination accounts

    Provider SIP addresses, authentication, transport, codecs and call limits, assigned to the nodes that carry the traffic.

  • Distributed nodes

    Remote termination nodes enroll with a single activation key over outbound HTTPS, so no inbound ports or private IPs are exposed.

  • Active calls

    A live view of calls in progress with filters and per-call detail, updated in real time.

  • Call detail records

    Durable completed-call history with search, date, disposition and node filters and summary totals.

  • Encrypted credentials

    SIP and provider secrets are encrypted at rest and never returned to the browser or written to logs.

  • Audit trail

    Every configuration change is recorded with who made it and when.

How it works

From setup to steady-state operation

  1. 01

    Install

    Deploy the console on your origination server.

  2. 02

    Enroll nodes

    Add termination nodes with a one-time activation key.

  3. 03

    Add providers

    Create termination accounts for each upstream carrier.

  4. 04

    Define routes

    Build route groups and prefix rules, then test the decision.

  5. 05

    Operate

    Onboard customers, watch live calls and review CDRs.

Architecture

Where RBC sits in your stack

RBC is the control plane for your voice network; calls flow through your own nodes.

  1. Customers

    • SIP trunks
    • IP-authenticated peers
    • Retail endpoints
  2. RBC console

    • Customers & limits
    • Routing engine
    • Active calls
    • CDR & audit
  3. Voice nodes

    • Origination server
    • Termination agents
    • Call admission
  4. Carriers

    • IPTSP providers
    • Wholesale carriers
    • PSTN gateways
Highlighted layers are provided by RBC. Other layers are your existing systems or other E-Net Communication products.

Operational benefits

What changes for your team

  • Routing changes without SSH

    Operators adjust routes and limits in the console instead of editing switch configuration.

  • Limits that are actually enforced

    Per-customer CPS and concurrency are checked on every call admission.

  • One record of every call

    CDRs from all nodes arrive in a single searchable history.

  • Your infrastructure, your data

    RBC is self-hosted: signalling, credentials and call records stay on servers you control.

Who it is for

Target customers

  • VoIP & IPTSP operators

    Providers selling SIP trunks and voice services to businesses.

  • Wholesale carriers

    Carriers routing traffic between customers and multiple upstream providers.

  • ISPs adding voice

    Internet providers extending their offer with voice services.

  • Call centre platforms

    Operators that need controlled, auditable outbound routing.

Deployment

Run it where you need it

RBC is self-hosted. The console runs on your origination server and remote nodes connect to it outbound.

  • On-premise

    Installed in your own data center, under your control.

  • Private cloud

    Dedicated environment in your cloud account or ours.

Get started

See RBC in your environment.

Book a walkthrough with the E-Net Communication team. We will map RBC to your current systems and deployment requirements.