Tell Me What’s Stuck

Application modernisation Case study

Reliable telecom billing, rebuilt from the server up.

Modernising PABX infrastructure and recovering critical billing data with Raspberry Pi, Ansible and Azure.

Client Kuji Consulting

Explore the work
Focus PABX infrastructure
Work Modernisation & automation
Technology Laravel · Ansible · Docker · Azure
Outcome Repeatable, recoverable operations
01

The brief

The phone system was doing its job. The infrastructure around it was becoming harder to trust.

Kuji needed to move PABX workloads onto smaller, more manageable hardware, standardise deployments across offices, and recover billing data from systems that offered no usable API.

The answer was not a single rebuild. It was a practical operating system for the whole estate: repeatable images, central automation, containerised management software, and a reliable path to the call data.

02

The system

One connected workflow, from office hardware to billing records.

  1. 01

    Standardise

    Packer and Ansible created repeatable Raspberry Pi images for new offices and gradual migration.

  2. 02

    Control

    AWX centralised server information and maintenance, with Laravel providing a usable management layer.

  3. 03

    Deploy

    Docker and Azure DevOps made ARM and x86 builds consistent and moved legacy workloads into Azure.

  4. 04

    Recover

    Puppeteer retrieved call files and scraped the remaining records the billing workflow depended on.

03

The intervention

Modernise what matters. Keep the operation moving.

Hardware & deployment

A repeatable Raspberry Pi foundation

New offices became the first deployment target, creating a low-risk path for moving existing PABX server workloads. Management software was containerised for both ARM and x86 environments, avoiding a second operational fork.

Operations

Server management without the manual chase

AWX and Ansible collected server information and handled maintenance tasks. A Laravel application stored and reported on the estate, and made each server’s automation straightforward to configure.

Data recovery

A way through the systems with no API

The phone systems exposed no supported integration. A focused Puppeteer workflow downloaded call-information files and captured the remaining records needed to keep billing complete.

04

The result

Less fragile infrastructure.
More control over every office.

  • 01Legacy billing applications maintained and replaced without interrupting the operation.
  • 02Repeatable Raspberry Pi images made new deployments consistent and recoverable.
  • 03AWX brought maintenance and server visibility into one central workflow.
  • 04Automated container builds created a dependable path from code to deployment.