Diagox

SIP and media ingress for modern voice systems
Route, bridge, and connect real-time communications across SIP, RTP, and WebRTC.

Diagox is programmable SIP and media ingress for modern voice systems, built around a purpose-built signaling and media B2BUA with an integrated media proxy. It connects PBXs, SIP providers, WebRTC clients, internal voice services, and other reachable telephony endpoints. Diagox provides selected Session Border Controller (SBC) capabilities—including topology hiding, authentication, rate limiting, and call observability—without positioning itself as a full carrier-grade SBC. It runs as a single Go binary and is built on top of sipgo and diago.

What Diagox provides

• SIP ingress and egress over UDP, TCP, and WebSocket transports
• RTP and WebRTC media ingress, egress, and proxying
• B2BUA call routing and dialog bridging between endpoints
• Browser-friendly SIP/WebSocket connectivity
• Registrar and in-memory contact registry support
• Programmable routes with prefixes, fallback destinations, and hangup rules
• Call recording, media statistics, and VoIP monitoring
• YAML-based configuration suitable for local deployments and containers

Get started

The fastest way to explore Diagox is to start with the minimal configuration:

go install ./cmd/diagox

CONF_FILE=example-configs/diagox-minimal.yaml diagox

The configuration expects an endpoint named bob at sip:internal.network:5080. Update that destination for your environment.

For container-based deployments, build the included image and provide the configuration through the image or a mounted file:

docker build -t diagox .
docker run --rm \
  -p 5060:5060/udp \
  -v "$PWD/example-configs/diagox-minimal.yaml:/app/diagox.yaml:ro" \
  diagox

Diago load test

The repository includes a Diago-based load generator. It runs an in-process UAS on port 5080, originates concurrent calls to the configured Diagox SIP target, and sends/receives PCMU RTP for every answered call. Configure Diagox to route its outbound leg to sip:127.0.0.1:5080, then run:

go run ./cmd/diagox-loadtest \
  -target sip:1000@127.0.0.1:5060 \
  -uas-listen 127.0.0.1:5080 \
  -calls 100 \
  -rate 10 \
  -concurrency 50 \
  -duration 60s

Use -calls 0 to run until interrupted, -media=false for SIP-only load, and -metrics-addr :9091 to expose load-generator metrics at http://localhost:9091/metrics. Diagox exposes its application metrics at http://localhost:6060/metrics.

See the installation guide for runtime configuration, networking, and deployment details.

Example configurations

All example configurations are included in the repository:

Example	Use it for
diagox-minimal.yaml	A small SIP routing and recording setup.
diagox-webrtc.yaml	SIP plus WebRTC/WebSocket endpoints.
diagox_full.yaml	A broader example with route contexts, carrier endpoints, authentication, and header handling.
diagox_docker.yaml	Docker-oriented transports, registry routing, and carrier fallbacks.

The examples contain placeholder addresses and credentials. Replace them before using any configuration outside a local test environment.

Core concepts

Diagox configuration is organized around three pieces:

• Transports define where Diagox listens for SIP traffic, including UDP, TCP, and WebSocket listeners.
• Endpoints identify incoming callers or define destinations such as PBXs, carriers, registered users, and WebRTC clients.
• Routes decide where calls go based on the endpoint, dialed number, prefixes, registration state, and other matching rules.

This keeps the call-routing policy separate from the service process and makes it possible to adapt the same gateway to different networks and providers.

Documentation

• Getting started
• Installation
• WebRTC setup
• Feature overview

Open source and scalable (enterprise)

The open-source Diagox distribution provides a focused, single-instance voice gateway that can be run as a binary or container.

Scalable capabilities are available separately for deployments that need:

• Multiple coordinated Diagox instances
• Kubernetes deployment charts
• External registry caching
• Database-backed call detail records
• Centralized management and remote provisioning of instances and SIP/media ingress configuration

For more information about scalable deployments, contact mail.

Development

Build the server with:

go install ./cmd/diagox

Run the Go test suite with:

go test ./...

Diagox is licensed under the Mozilla Public License 2.0.