Skip to main content

INDUSTRIES

Telecommunications

Operators, tower companies and internet service providers use us for OSS and BSS integration, site energy monitoring, field workforce systems and the security operations that keep a national network defensible.

Energy, Integration and the Regulator

The economics of a Nigerian mobile network are dominated by an item that has nothing to do with radio: diesel. A base station in an area with poor grid supply may run its generator for eighteen hours a day, and the fuel for it is delivered by third-party contractors to unmanned sites scattered across difficult terrain. Reconciling litres ordered against litres consumed against hours of runtime is genuinely hard, and where it is not done rigorously the losses are large and persistent. Operators and tower companies come to us for instrumentation — fuel level sensors, generator runtime telemetry, door and vibration sensors, geofenced delivery confirmation — and for the analytics that turn thousands of daily readings into an exception list a regional manager can act on before the end of the week.

The second pressure is integration debt. A network that has grown through acquisition and successive vendor projects typically runs several element managers, more than one provisioning stack, a billing system a decade old and a customer relationship platform bought last year, none of which agree on what a subscriber is. Order-to-activation breaks in the gaps; revenue assurance cannot reconcile usage to billing; the contact centre cannot see why a service is down. Our systems integration practice builds the mediation and API layer that lets those platforms exchange consistent records, with message replay and monitored queues so that a failure is visible rather than silent.

Third is the regulator. The Nigerian Communications Commission requires periodic quality-of-service reporting, network availability and performance data, subscriber registration compliance and notification of significant outages. Where those returns are assembled by hand from several systems at the end of each period they are late, inconsistent and painful to defend. We build the reporting pipeline that draws directly from network and business systems, applies the Commission’s definitions consistently, and produces a submission with a traceable audit trail back to the underlying counters.

What We Deliver for Telecoms Operators

Five offerings drawn from work with operators, tower companies and internet service providers across northern Nigeria.

Telecoms Sector Delivery

8

Delivered Systems

Telephony, networking and subscriber platforms

3

Softphone Clients

Flutter, WebRTC and native Android

1

SIP Server Stack

Self-hosted, with push and media relay

1

Video Platform

Self-hostable, with transcoding pipeline

Delivered Communications Systems

Telephony, networking and subscriber platforms we have built and run. Several of these carry our own production traffic, which is the reason they exist.

System Scope Built on
SIP server stack Production telephony: registration, audio and video calling, presence, encrypted one-to-one and group chat, push wake-up on both mobile platforms, media relay for network traversal and self-service account provisioning Flexisip, TURN and STUN relay, FCM and APNs
eSystems Phone Cross-platform SIP softphone with audio and video calling, one-to-one and group chat, presence and call history Flutter
AeroVox WebRTC client Secure SIP client registering over encrypted websockets against an Asterisk cluster, built for stable registration across changing wide-area networks Flutter, Riverpod, Dart WebRTC
TSATVoIP Native Android voice-over-IP client for a dedicated deployment Native Android
BrowsePoint VPN Android client for a self-hosted private network estate, auto-enrolling against the organisation’s own server and routing all traffic through it Self-hosted mesh network server
WiFi voucher platform Multi-tenant hotspot voucher and billing software; each operator gets their own router integration, branding, plans, vouchers and online payment collection MikroTik RouterOS integration on a hosted backend
iTube Self-hostable, mobile-first vertical short-video platform with a dedicated recommendation service and a transcoding pipeline including automated content-safety screening NestJS, React Native Expo, Go, FFmpeg

How We Would Instrument a Base Station Estate

This is a design rather than a delivered reference, and we would rather label it honestly than imply a client. A tower operator can usually see total diesel spend but not where it goes. Fuel arrives from regional contractors against paper waybills, generator hours come back from site attendants on monthly returns, and the two numbers never reconcile. Management may suspect losses of a meaningful size without being able to evidence them site by site, which makes enforcement impossible and contractor disputes unwinnable.

The instrumentation we would propose is capacitive fuel level sensing in the tanks, runtime and load telemetry from the generator controllers, door and vibration sensors on the shelters, and geofenced mobile confirmation that a delivery vehicle was actually at the site when the waybill was signed. Telemetry backhauls over the operator’s own transmission where it exists and over cellular elsewhere.

The analytics matter more than the sensors. Rather than dashboards nobody reads, the system should produce a weekly ranked exception list: sites where litres delivered exceed litres consumed plus expected efficiency, sites where runtime exceeds grid-outage expectation, sites with repeated after-hours door events. Sized so a regional manager can actually work through it. The streaming and geospatial engineering behind this is the same work as our Kano fleet simulation, which models more than five thousand vehicles in real time.

  • Fuel delivery disputes settled from telemetry rather than from argument
  • Unattended site intrusion detected in near real time rather than at the next visit
  • Generator maintenance moved from calendar-based to runtime-based scheduling
  • A weekly ranked exception list sized for one regional manager to action
  • Geofenced delivery confirmation tying a waybill signature to a vehicle at the site
  • Proposed design, not a delivered reference; the streaming engineering is evidenced in our fleet simulation
How We Would Instrument a Base Station Estate

Questions Telecoms Clients Ask

Will your monitoring platform work with our existing site equipment?
In most cases yes. We read from generator controllers over Modbus where they expose it, add our own sensors where they do not, and support the common rectifier and site-controller interfaces. We run a survey across a representative sample of your site types before quoting, because an estate assembled over a decade always contains four or five different equipment generations.
How do you handle sites with no backhaul capacity to spare?
Telemetry is deliberately low bandwidth — a few kilobytes per site per hour under normal conditions, with alarms sent immediately. Where the operator does not want telemetry on the production transmission at all, we backhaul over an independent cellular path with store-and-forward, so readings taken during a connectivity gap are delivered when the link returns rather than lost.
Can you integrate with our existing network management system?
Yes. We prefer to feed alarms into whatever your network operations centre already watches rather than adding another screen. We publish events over SNMP traps, Kafka or REST, whichever suits, and we map our severities onto your existing classification so that operators do not have to learn a second convention.
What does an OSS and BSS integration programme typically cost and take?
An integration programme of this shape is quoted per engagement rather than from a rate card, and we will not publish a band we cannot stand behind. What we will commit to is the shape: delivery in quarterly increments so value appears before the end, and a discovery phase first, typically around six weeks, because integration estimates made without seeing the actual interfaces are worthless.
Do you have engineers who can reach remote sites?
We field maintenance teams from Kano and Abuja covering the North-West and North-Central, with contracted partners elsewhere. Our standard site attendance commitment for the northern estate is 24 hours for a service-affecting fault and 72 hours for a non-affecting one, and we report attainment monthly rather than asking you to take it on trust.
How do you handle the security of operational technology on our sites?
Site telemetry sits on a separate logical network from anything carrying subscriber traffic, communicates outbound only over mutually authenticated channels, and cannot be used to control site equipment unless the client explicitly requests remote control and accepts the additional controls that come with it. The estate is monitored from our security operations centre alongside enterprise IT.

Talk to our telecommunications team

Start with a survey across a representative sample of your sites or a discovery workshop on your integration estate. Both are short, fixed-price and produce a document you can act on.