Skip to main content

Telecom service assurance and security · Domain Intelligence Pack

Telecom network DIP

Get dark sites back on air faster, with crews sent to the real fault and signaling fraud shut down as it starts.

Overview

Restore faster. Leak less revenue.

A fiber cut lights up hundreds of alarms, and three teams chase the wrong ones. Generators run dry at sites nobody flagged. Customers complain on social media before the NOC confirms anything. Meanwhile signaling attacks track subscribers, SIM swaps empty mobile money wallets, and SIM boxes bleed interconnect revenue. Because Ollandi reads power, transmission, core, and fraud signals together, the real fault gets one crew and the fraud gets stopped.

  • For any site, route, or core element, Ollandi knows which subscribers, enterprise customers, and mobile money agents depend on it.

    • Cell sites, grid power, generators, and batteries
    • Transmission, backhaul, and fiber routes
    • Core network, signaling, and interconnect
    • USSD, mobile money, and subscriber provisioning
  • Batteries draining after a grid outage leave a window to dispatch, and Ollandi uses it. Signaling and provisioning abuse is cut off in its first attempts.

    • Sites about to go off air as batteries drain after a grid outage
    • Hundreds of site alarms that trace back to one fiber cut
    • Signaling messages used to track subscribers or intercept codes
    • SIM swaps and number ports pushed through a compromised agent account
    • SIM-box bypass and traffic pumping that drain interconnect revenue
  • One case replaces hundreds of alarms. It points to the likely break point, the people waiting on it, and the team that should move.

    • Whether a fault is one site, one route, or one region
    • How many subscribers, enterprises, and mobile money agents are affected
    • Whether power, transmission, configuration, or an attack is the cause
    • Which NOC team, vendor, or field crew should move first
  • Restricting a suspicious signaling source or agent account is reversible. Anything that could affect service across a region goes to a person first.

    • Send one ranked case to the crew that owns the fault
    • Restrict a suspicious signaling source or provisioning account
    • Hold a high-risk SIM swap until the subscriber is verified
    • Confirm service is back, site by site, before the case closes
    How you set the limits

In an incident

A grid failure puts dozens of sites on battery

An illustrative case, step by step, from the first signal to a confirmed result.

  1. Warn

    Grid power fails across a district at dusk. Dozens of sites switch to batteries, and Ollandi ranks which will go dark first.

  2. Explain

    Two sites failed a battery test last month, and both carry traffic for a hospital and a busy market. They have the least time left.

  3. Dispatch

    Generator crews get a ranked list: the least time left and the most subscribers first. No crew is sent to a site that will hold.

  4. Confirm

    Power returns. Ollandi confirms every site and service is back, and the record is ready for your outage report to the NCC.

Connections

What it connects to

Ollandi connects to Ericsson Network Manager, Nokia NetAct, and Huawei iMaster NCE, plus site power systems, USSD gateways, and mobile money platforms. Your NOC and SOC keep their tools and work from the same case.

  • Network management and alarm systems
  • Site power and generator telemetry
  • Transmission topology and route data
  • Signaling and interconnect records
  • Provisioning and agent access logs
  • USSD, mobile money, and care records

Domain Intelligence Packs

Add depth in other domains

Packs check one another’s work. A strange sign-in found in one domain can confirm, or rule out, what another domain found.

See all packs
  • Cloud DIP

    Close the cloud gaps attackers look for first: public storage, open ports, and roles with more access than they use.

  • Identity DIP

    Stolen credentials stop working at the first sign of misuse, whether they came from phishing, a SIM swap, or a leaked key.

  • Network DIP

    An intruder moving between servers is stopped at the next hop, and a failing link is flagged before transactions fail.

  • Endpoint DIP

    Ransomware contained on the first device it lands on, long before it can reach a file server or a backup.

  • On-premises DIP

    The legacy systems the business still depends on stay up and defended, including the ones nobody on the team owns anymore.

  • Applications and code DIP

    Reachable flaws in your code and dependencies come with a fix ready to merge, and bots and account takeovers stop at sign-in.

  • Data DIP

    When a stolen account starts copying customer records, the leak stops early, with evidence ready for your regulator.

  • Operational technology DIP

    Plants keep producing while attacks on controllers and remote access are stopped, and the control room keeps the final say.

  • ATM DIP

    Engineers go out only when a visit will fix the fault, and jackpotting is cut off before the cassettes empty.

FAQ

Frequently asked questions

  1. It stays. Your network management, alarm, and provisioning systems feed Ollandi, which reads them together across sites, routes, core, and customers, so crews go straight to the likely cause.

  2. Yes. Signaling, interconnect, provisioning, and privileged access are judged alongside faults. In the first minutes an outage and an attack can look alike, and reading both together is how they are told apart.

  3. Every outage case records when it started, which areas and subscribers it affected, the cause, and when service returned. Your team starts the NCC report from that record instead of rebuilding it from alarm logs.

Get started

Put the Telecom network pack to work

Walk us through your last regional outage or SIM-swap wave. We will show where Ollandi would have sent the first crew, and where it would have stopped the fraud.