---
title: "About Ring2All SBC & System Architecture"
description: "Documentation for About Ring2All SBC"
---

## Table of Contents
1. [Overview](#1-overview)
2. [Architectural Significance & Transparency](#2-architectural-significance--transparency)
3. [🎯 User Roles & Key Capabilities](#3--user-roles--key-capabilities)
4. [Visual Interface & Dialog Inspection](#4-visual-interface--dialog-inspection)
5. [System & Subsystems Stack Reference](#5-system--subsystems-stack-reference)
6. [Audit & Compliance Best Practices](#6-audit--compliance-best-practices)
7. [Troubleshooting & Verification](#7-troubleshooting--verification)
8. [Glossary](#9-glossary)

---

## 1. Overview

The **About Ring2All SBC & System Architecture** module in **Ring2All SBC** provides real-time diagnostic visibility into the underlying platform build, operating system kernel, cryptographic environment, and telecom engine subsystems that power the session border controller. Accessible directly from the lower user menu in the primary navigation sidebar, this information modal surfaces core runtime telemetry essential for troubleshooting, patch management, and support escalations.

Rather than relying on static documentation, the dialog actively polls host kernel and service APIs, displaying live version binaries for Kamailio, Node.js, PostgreSQL, and Linux distribution packages.

---

## 2. Architectural Significance & Transparency

* **Rapid Support Triage**: When reporting an incident or requesting upstream engineering assistance, telecom teams can verify the exact kernel build, database minor release, and Kamailio SIP engine version in a single glance.
* **Security & Vulnerability Auditing**: Enables system security auditors to inspect running runtime versions (e.g., Node.js LTS, PostgreSQL 17) against corporate CVE registries.
* **Component Parity Verification**: In multi-node SBC clusters, operators can rapidly confirm that all edge proxies are running matching software builds across the network perimeter.

---

## 3. 🎯 User Roles & Key Capabilities

| Role | Key Capabilities |
| :--- | :--- |
| **SBC Administrator** | Inspect platform runtime stack, verify kernel versions, confirm software release builds, and prepare system reports for technical support. |
| **Security Officer** | Verify running versions of cryptographic libraries, web runtimes, and database engines against corporate patch baselines. |
| **Support Engineer** | Cross-reference Kamailio and Node.js minor versions during interoperability and SIP stack debugging. |

---

## 4. Visual Interface & Dialog Inspection

The About dialog opens as an overlay modal with frosted background blur, showcasing the branded subsystem card and component stack details.

![About Ring2All SBC](/screenshots/sbc/account-menu/about.png)

---

## 5. System & Subsystems Stack Reference

### Platform Metadata

| Attribute | Displayed Value | Description |
| :--- | :--- | :--- |
| **Branding Header** | `Ring2All SBC` | Official product identity and session border controller edition. |
| **Release Stage** | `Production / Stable` | Software release track (e.g., Stable, RC, Beta). |
| **License Type** | `Community Edition` | Active license entitlement class currently operating on the node. |
| **Build Date** | `Build Timestamp` | Exact date and time the running container or host binary was compiled. |
| **Environment** | `Debian GNU/Linux 13 (trixie)` | The underlying operating system distribution and kernel release. |

### System & Subsystems Stack

| Subsystem Component | Active Version | Architectural Function |
| :--- | :--- | :--- |
| **OS / Kernel** | `Debian GNU/Linux 13 (trixie)` <br> `6.12.100+deb13-amd64` | The high-performance Linux kernel providing raw network socket routing, epoll event loops, and iptables/nftables packet filtering. |
| **Node.js Runtime** | `v22.23.2` (LTS) | The asynchronous, event-driven JavaScript engine running the Fastify SBC backend API, WebSocket telemetry, and MCP server. |
| **PostgreSQL Database** | `v17.10` | The enterprise-grade relational database storing SIP subscribers, dispatcher pools, LCR routes, and audit event logs. |
| **Kamailio Core Engine** | `v6.0.1` | The high-throughput carrier-grade SIP proxy engine handling packet inspection, digest authentication, NAT traversal, and transaction routing. |

---

## 6. Audit & Compliance Best Practices

* **Confirm Stack Uniformity Across SBC Pairs**: When operating active-passive or active-active high availability (HA) pairs, always confirm that both nodes run identical Kamailio and OS kernel versions.
* **Document Stack in Maintenance Tickets**: Include the exact versions reported in the About modal in all telecom change management records and vendor support tickets.
* **Monitor Upstream Kernel Updates**: Stay informed of security patches released for Debian 13 and Linux kernel 6.12 LTS to ensure perimeter firewall components remain fortified.

---

## 7. Troubleshooting & Verification

| Issue / Symptom | Root Cause | Resolution |
| :--- | :--- | :--- |
| Modal displays `N/A` for Build Date or Release Stage | Development or unversioned build deployment | Normal in self-compiled development environments; official carrier releases display the tagged semantic version. |
| Kamailio version mismatch with CLI output (`kamailio -V`) | Web API cache holding previous process metadata | Restart the SBC management API service (`systemctl restart softswitch-sbc-api`) to refresh daemon state. |
| Dialog fails to open when clicking user menu | Javascript bundle error in browser cache | Perform a hard refresh (`Cmd+Shift+R` / `Ctrl+Shift+R`) to reload updated frontend bundle assets. |

---

## 8. Glossary

* **Kamailio**: Open-source, carrier-grade SIP server capable of routing thousands of call setups per second.
* **Kernel**: The core interface between a computer's hardware and its operating processes.
* **LTS (Long Term Support)**: Software release track guaranteed to receive critical maintenance and security updates over an extended timeframe.
* **Subsystem**: An independent, specialized service component (e.g. database, SIP engine, web API) operating collaboratively within the SBC architecture.