BeeTest active service testing

Active service testing BeeTest

Passive probes tell you what the network did. BeeTest tells you what the subscriber got. It drives real and emulated terminals through complete service journeys on a schedule, and puts the results on the same timeline as your ProBee data — so a failure is immediately either a network problem or a service problem.

  • End-to-end journeys: SMS, MMS, RCS, VoLTE, VoWiFi, data attach, TS.43 entitlement
  • Real handsets in a device farm, or emulated terminals at scale
  • Regression packs run automatically on every release and every configuration change
  • Roaming and interconnect testing against each partner, continuously
  • Results correlated with passive probe data in one dashboard
See a test pack
Pair it with ProBee

Real device farm

Emulated terminals

SMS · MMS · RCS

VoLTE · VoWiFi

TS.43 entitlement

Roaming journeys

CI/CD hooks

Regression packs

Scheduled and on-demand

Correlated with ProBee

Active and passive are not alternatives

Buying one without the other leaves a gap that shows up in the worst way. Passive probing sees everything that happens but nothing that should have happened and did not — the subscriber who gave up before the registration retried. Active testing sees the subscriber journey but only on the handful of paths you thought to test.

Together they are a closed question. If BeeTest fails and ProBee shows a protocol anomaly on the same path in the same minute, you have the network fault and the trace. If BeeTest fails and the signalling is clean, the problem is in the device, the client or the configuration — and you have just saved a day of core-network investigation.

That correlation is the reason we sell them as one assurance product line rather than two tools.

Test packs

Messaging

  • SMS MO/MT, on-net, off-net, international and roaming
  • MMS send, retrieve, transcode and MM4 interworking
  • RCS capability discovery, registration, chat, file transfer and groups
  • A2P delivery and delivery-receipt integrity per aggregator

Voice and IMS

  • VoLTE and VoWiFi registration, call setup, hold, transfer and handover
  • Emergency call routing and location delivery
  • Supplementary services and call-forwarding behaviour
  • Media quality sampling alongside signalling outcome

Entitlement and device

  • GSMA TS.43 flows end to end: RCS, VoWiFi, VoLTE, eSIM transfer
  • Watch and companion-device pairing journeys
  • ODSA subscription activation from the device
  • Per-OS-version behaviour, tracked across handset releases

Data and roaming

  • Attach, PDN/PDU session establishment and APN behaviour
  • Throughput and latency sampling per APN and per slice
  • Per-partner roaming journeys, run continuously
  • Steering-of-roaming and network-selection verification

Where it earns its place

Release gating

Every core or IMS change runs the regression pack before it reaches production. Hooked into your CI/CD, results as a pass/fail gate.

Launch verification

New service, new partner, new device: prove the journey works on real hardware before marketing commits to a date.

SLA evidence

Continuous synthetic measurement you can put in front of a customer or a regulator, independent of the elements being measured.

Partner management

Per-interconnect and per-aggregator journey success, tracked over time, with the data to back a commercial conversation.

How it is built

Test controller. Schedules, distributes and correlates. Runs on Kubernetes alongside the rest of your assurance stack.

Device agents. Real handsets in a rack, driven over ADB or vendor automation, with SIMs from the networks under test.

Protocol emulators. Terminal and network-side emulation where a real device is unnecessary or would not scale — the same protocol modules that power our network functions.

Result store and correlator. Every journey step timestamped and joined against ProBee dialogue records, so a failed step links straight to the signalling that caused it.

Service Assurance overview
BeeTest logical architecture

What our customers say

References are anonymised at the customer’s request. Named references and written reference letters are available under NDA.

Core network operations, Tier-1 MNO (DT group)

„We were finding signalling degradations from the complaint queue. ProBee moved that left by roughly forty minutes — we now see the retransmission pattern build before the first customer calls. It is the same Grafana our NOC already lives in, so nobody had to learn a new console.”

Head of Platforms, MVNE serving 300k+ subscribers

„Our BSS was complete and our network layer was not. Mobees dropped in the messaging core and the TS.43 entitlement server behind our existing provisioning, per tenant. We stopped referring those deals out.”

Delivery director, systems integrator, CEE

„They are the people we call when a transformation programme hits SS7 or CAMEL and the schedule is already tight. Small team, no layers, an answer the same week.”

Pick one journey that keeps breaking.

We will automate it, run it for a month and show you the correlation with what the signalling was doing at the time.

Contact us
See ProBee