Comparison guide

Signals or a direct carrier integration?

A direct carrier relationship gives you a direct network connection. Signals adds a programmable software and operational layer around Nigerian phone numbers, calling, call control, usage and visibility.

Last reviewed: 18 August 2026

Book a technical discovery call Explore SIP Access

Two architectures

Direct carrier integration

Your platform
Carrier SIP or network interface
Phone network

Signals

Your platform
Signals API, SIP or Automations
Provider-backed Nigerian numbers
Phone networks

Signals does not remove your regulatory, KYC or lawful-use responsibilities.

Quick answer

The decision in one minute.

Direct carrier integration may fit better when:

you deliberately want one specific carrier relationship;
you have telecom engineering and operations capacity;
you can build and maintain your own call control, metering, billing reconciliation and monitoring;
your number inventory and route requirements are narrow and stable;
direct commercial control outweighs implementation speed and abstraction.

Signals may fit better when:

you want one managed API or SIP integration;
you need Nigerian numbers from more than one provider in one account;
you want Twilio-compatible programmable call control or Automations;
you need consolidated call records, usage and real-time network visibility;
you want to reuse the same telephony layer across many products, customers or deployments.

What you are buying

Connectivity alone, or connectivity plus a software layer.

A direct carrier integration buys connectivity. Everything above that connection — call control, retries, event handling, recordings, metering, reconciliation and monitoring — is built and operated by your team.

Signals buys connectivity plus a software and operational layer: a programmable Calls API, OneML call control, SIP Access, Automations, consolidated number management, call records, usage and real-time network-performance visibility.

Neither model removes your obligations. Signals customers remain responsible for KYC, lawful use and their own regulatory and consent requirements for the calls they place.

Call path

Direct

Your platform
Carrier SIP or network interface
Phone network

Signals

Your platform
Signals API, SIP or Automations
Provider-backed Nigerian numbers and phone networks

Decision table

Compare what each model asks of your team.

Criterion	Signals	Direct carrier integration
Commercial relationship	One agreement with PressOne covering platform access, numbers and call usage in Naira.	A direct agreement with the carrier. Terms, commitments and account management depend on that carrier.
Number procurement and management	Numbers supplied by multiple Nigerian providers can be purchased and managed in one account, with the customer selecting the originating owned number.	Depends on the carrier and what you negotiate. Inventory and management processes vary by carrier.
API and call-control layer	Twilio-compatible Calls API and OneML, derived from TwiML, with supported behaviour defined by the public compatibility matrix.	Depends on the carrier and what you build. Application-level call control is usually your responsibility.
SIP	Managed SIP Access for contact-centre platforms, PBXs, diallers, BPOs and AI voice systems.	Depends on the carrier’s interconnect options and the SIP infrastructure you operate.
Webhooks and events	Webhooks and call callbacks are part of the documented Programmable Voice surface.	Depends on the carrier and what you build on top of the interface it provides.
Call logs and recordings	Call records in the platform, and recordings within the plan allowance where enabled.	Depends on the carrier and on the recording, storage and retrieval you implement.
Usage and billing visibility	Consolidated usage and billing across numbers and call activity in one account.	Depends on the carrier’s reporting and on the reconciliation process you build and maintain.
Network visibility	Real-time Signals network-performance visibility alongside call records and usage.	Depends on the carrier’s reporting and any monitoring you operate yourself.
Multiple provider-backed numbers	Numbers from more than one Nigerian provider can be held and selected within one Signals account.	Typically requires a separate relationship, integration and reconciliation per carrier.
Internal engineering burden	One managed integration to build against, then maintained as a platform dependency.	Telecom engineering, monitoring, metering and operations capability held in-house.
Fit for repeatable platform deployments	One integration reused across products, customers and deployments.	Depends on how portable your carrier arrangement and internal tooling are across deployments.

Commercial relationship

Signals

One agreement with PressOne covering platform access, numbers and call usage in Naira.

Direct carrier integration

A direct agreement with the carrier. Terms, commitments and account management depend on that carrier.

Number procurement and management

Signals

Numbers supplied by multiple Nigerian providers can be purchased and managed in one account, with the customer selecting the originating owned number.

Direct carrier integration

Depends on the carrier and what you negotiate. Inventory and management processes vary by carrier.

API and call-control layer

Signals

Twilio-compatible Calls API and OneML, derived from TwiML, with supported behaviour defined by the public compatibility matrix.

Direct carrier integration

Depends on the carrier and what you build. Application-level call control is usually your responsibility.

SIP

Signals

Managed SIP Access for contact-centre platforms, PBXs, diallers, BPOs and AI voice systems.

Direct carrier integration

Depends on the carrier’s interconnect options and the SIP infrastructure you operate.

Webhooks and events

Signals

Webhooks and call callbacks are part of the documented Programmable Voice surface.

Direct carrier integration

Depends on the carrier and what you build on top of the interface it provides.

Call logs and recordings

Signals

Call records in the platform, and recordings within the plan allowance where enabled.

Direct carrier integration

Depends on the carrier and on the recording, storage and retrieval you implement.

Usage and billing visibility

Signals

Consolidated usage and billing across numbers and call activity in one account.

Direct carrier integration

Depends on the carrier’s reporting and on the reconciliation process you build and maintain.

Network visibility

Signals

Real-time Signals network-performance visibility alongside call records and usage.

Direct carrier integration

Depends on the carrier’s reporting and any monitoring you operate yourself.

Multiple provider-backed numbers

Signals

Numbers from more than one Nigerian provider can be held and selected within one Signals account.

Direct carrier integration

Typically requires a separate relationship, integration and reconciliation per carrier.

Internal engineering burden

Signals

One managed integration to build against, then maintained as a platform dependency.

Direct carrier integration

Telecom engineering, monitoring, metering and operations capability held in-house.

Fit for repeatable platform deployments

Signals

One integration reused across products, customers and deployments.

Direct carrier integration

Depends on how portable your carrier arrangement and internal tooling are across deployments.

Carrier capabilities vary. Each direct-carrier statement above depends on the carrier you are considering and on what your team chooses to build; verify both with that carrier.

Stated accurately

Provider diversity without an automatic-failover claim.

Signals customers can purchase and manage numbers supplied by different Nigerian providers.

The customer chooses which owned number an outbound call uses.

This reduces dependence on a single number provider and simplifies account management, because the inventory sits in one place with one billing relationship.

It is not automatic carrier failover, dynamic route selection or carrier redundancy for every number. Signals does not select providers on your behalf.

Number selection

What Signals does

Numbers from multiple Nigerian providers in one account
Customer selects the originating owned number
One place for records, usage and billing

What Signals does not claim

Automatic carrier failover
Dynamic route selection
Automatic provider selection per call

When direct makes sense

Cases where owning the relationship is the right call.

A large telecom team with tailored infrastructure

You already employ the engineering and operations capability to run interconnect, monitoring and metering for a single carrier arrangement built around your needs.

A unique commercial or regulatory need

Your commercial terms, licensing position or regulatory obligations require a direct relationship with a named carrier.

An existing direct integration that works

You already run a direct integration with tooling and economics your team is satisfied with, and the switching cost is not justified.

A deliberate decision to own every layer

You want full control of the stack, and you accept the operational responsibility that comes with it.

When Signals makes sense

Cases where the software layer is the point.

A platform that needs a repeatable integration

A contact-centre, software or PBX platform that must connect once and then deploy the same telephony layer for many customers.

Developers who want programmable call control

A team that wants a Twilio-compatible Calls API and OneML rather than building call control from primitives.

Teams that need shared visibility

Numbers, call records, usage and real-time network-performance visibility available to the same team in one place.

Workloads needing multiple provider-backed numbers

Number inventory supplied by more than one Nigerian provider, held and selected within a single account.

Infrastructure that must be productised

Where telephony is resold or embedded for downstream customers, and the layer must be stable, documented and repeatable.

Build versus buy

Work through this before committing either way.

Who on your team owns telecom engineering, and what else are they responsible for?
How long can you allocate to integration before the workload must be in production?
What call-control behaviour must the application implement itself?
What monitoring and alerting will you build for call quality and delivery?
How will call usage be metered and reconciled against invoices?
What support path applies when something degrades in production, and at what hours?
How many number providers do you need, and who manages that inventory?
What operational risk sits with your team if a single relationship is interrupted?
Which additional markets may be required in the next 24 months?
What happens to this arrangement if the people who built it leave?

This checklist deliberately contains no cost or timeline estimates. Build your own figures from your team’s rates, your carrier’s terms and your workload.

Sources

What this page is based on.

Last reviewed: 18 August 2026

This page compares operating models rather than named carriers. Carrier-specific capabilities, terms and reporting must be verified directly with the carrier under consideration.

Signals pricing →Why Signals →

Decide which parts of the telecom layer you want to own.

Path 01

Walk through your architecture with our team and identify which layers you should own and which you should consume.

Book a technical discovery call

Path 02

Create a PressOne account, complete KYC, enable Developer Mode and test the managed layer against your own workload.

Subscribe and build