HomeAppLitepaperBusinessUser GuideFAQReward Calculator
GET UNETWORK
VERIFY

Telecom Assurance

Verify voice, CLI, SMS, OTP and connectivity at the physical destination, not only what upstream systems say was sent.

Who it is for and what it answers

Who it is for

Carriers, wholesale voice providers, aggregators, CPaaS platforms and telecom assurance teams that need to know what actually arrived at the endpoint.

What it answers

Did the call arrive with the expected CLI? Did the message arrive with the expected Sender ID and content? Did the connection behave as expected at the destination?

How it works

From question to evidence

What was sent is only half the story.Telecom Assurance shows you what arrived.

The route

Origin → carrier path → destination carrier → physical handset → observed evidence

01

Define what must arrive

Specify what you expect the destination endpoint to receive: the expected CLI, an SMS Sender ID, OTP content, call behavior or connectivity outcome.

02

Target the destination

Choose the destination market, carrier and other supported endpoint requirements. Unetwork identifies suitable physical devices on the relevant network.

03

A physical endpoint receives

The call, message or supported verification task reaches a real handset on the destination network. Unetwork observes what actually arrives at that endpoint.

04

Evidence comes back

The result is returned with the available destination context, so the expected outcome can be compared with what was actually observed.

Evidence

What a run returns

By task type:

Voice and CLI

Expected CLI, what should have been presentedObserved CLI, what the destination handset actually displayedDestination context: market, carrier, endpoint and supported network informationResult: matched, mismatched or other supported test state

Messaging and OTP

Expected Sender ID and contentObserved Sender ID and contentDelivery resultDelivery timingDestination network context

Connectivity Verification

Target carrier and marketObserved connectivity outcomeEndpoint contextTimestamp and task result

A concrete run

Example

See an example CLI verification run
Origin

United Kingdom

Destination

Spain

Attestation

Software attested

Expected CLI

+44 XXX XXX XXXX

Observed CLI

+44 XXX XXX XXXX

Result

VERIFIED

Next step

Tell us what must arrive.

Describe the route, the task type and the destination markets, and we will scope a Telecom Assurance test with you.

Provenance

Endpoint attestation

Unetwork supports three endpoint attestation states, allowing the platform to record which attestation state applied to the participating endpoint.

No attestation

A physical Unetwork endpoint without an additional software or hardware attestation result.

Software attested

The endpoint has passed the supported software-based attestation process.

Hardware attested

The endpoint has passed the supported hardware-backed attestation process.

Workloads can target endpoints by attestation state where that requirement is relevant to the task.

  • Any
  • No attestation required
  • Software attested
  • Hardware attested
Telecom Assurance | Unetwork