Business Automation

Problem

VoIP operators often split day-to-day work across a PBX, a billing tool, and separate support processes. That makes provisioning slow, billing easy to get wrong, and customer self-service hard to offer.

Solution

Built a role-based operations panel that lets staff and resellers manage telephony configuration, usage, billing, and support in one product, with a customer-facing portal and a browser softphone.

Key Features

• • Multi-tenant account structure with super-admin, admin, reseller, and client roles
• • Provisioning for extensions, DIDs, carriers, trunks, routes, queues, and ring groups
• • Call detail records, call recordings access, and operational dashboards

Problem

Teams that need per-machine internet egress usually end up editing proxy and firewall configs by hand. That is slow, easy to break, and hard to audit when several machines need different upstream routes.

Solution

Built a self-hosted gateway product: operators add proxies, onboard machines or VPN peers, assign a route, and the appliance applies the networking change through generated configuration rather than manual server edits.

Key Features

• • Proxy inventory with create, import, connectivity tests, and health checks
• • Virtual-machine discovery and onboarding, including per-machine route assignment
• • WireGuard peer management with config/QR onboarding

Problem

Telephony teams often apply carrier and routing changes by logging into each server and editing config files. That is slow, hard to review, and easy to get wrong when more than one server is involved.

Solution

Built a web application that stores server inventory, generates configuration from templates, deploys over SSH, and streams what happened so operators can see the result without working blind.

Key Features

• • Multi-server inventory from a web interface
• • Template-based configuration generation
• • Remote deployment with command output streamed back to the browser

Problem

If usage lives in the PBX and invoices live in a spreadsheet, operators spend time assembling bills and customers cannot see what they used. Errors show up as disputes, not as a product issue.

Solution

Connected call usage to account balances and payment workflows inside the operations panel, so customers can see usage and pay, and operators can automate invoices instead of building them by hand.

Key Features

• • Account balances with prepaid and postpaid handling
• • Usage import from call detail records
• • Payment collection through Stripe, including webhook processing