Telegram alerts for fibre outages

RadixOLT messages your NOC’s Telegram group when a sweep finds a new line fault or a weak signal, and when an OLT goes down, reboots or comes back. It uses your bot, in your group, and a cut fibre arrives as one message naming the port.

Start 24-hour free trial Talk to sales

What a message looks like

Plain text an engineer can act on from a phone: whose service, what happened, which port and which chassis. The first line is the subscriber, because that is who will call.

telegram A line fault on one ONU

Username : kiran.s
Status : OFFLINE 🔥
Down Reason : LOS
ONU : 0/1/6/3
Serial : HWTC6F21A0C3
Device : olt-hyd-07

telegram Low optical power

Username : sunita.r
Status : Fiber Power High 🔥
Optical Power : -28.64 dBm
ONU : 1/2/3/8
Serial : ZTEGC4A2215E
Device : olt-bom-01

telegram A cut fibre: one summary, not 31 messages

31 ONUs need attention 🔥
Device : olt-hyd-07
31 down with a line fault
0/1/6 : 31 ONU(s)
Too many to list individually — see the Alerts page.

telegram The OLT itself stops answering

Status : OLT DOWN 🔥
Device : olt-ind-05
SNMP : 203.0.113.20:161
Not answering for : 2m

The formats are exactly what RadixOLT sends; the names and numbers in them are an example.

When RadixOLT sends one

Only for something somebody can act on. An ONU that is merely switched off is not news, and a channel that announces it every 15 minutes is a channel people mute.

Sent once, when the condition first appears
Event	Sent when	Not sent when
A line fault on an ONU	A sweep finds the ONU offline with a fibre-type reason the OLT reported: `LOS`, `LOSi`, `Wire Down`, `PON loss` and the rest of a list collected from each vendor.	The reason is a power-off, a dying gasp, a reason nobody has classified, or the ONU was already reported.
Low optical power	An online ONU reads −28 dBm or weaker, the same level the product draws as critical.	The ONU is offline. A down ONU reports no optics, so its level says nothing.
The OLT stops answering	Two once-a-minute SNMP checks in a row go unanswered, on the OLT’s own SNMP port.	It is still down. One outage is announced once.
The OLT answers again	With how long it was down, and “did not reboot” only when that was measured.
The OLT rebooted	Its uptime reset, even if the outage was too short to be called down.

Built so a cut fibre does not become a flood

More than ten at once become one message

A cut fibre drops every ONU on its PON port in the same sweep, and Telegram allows about twenty messages a minute into one group. Past ten new alerts in a sweep, RadixOLT sends one summary grouped by port and by kind instead, so the message says where to go.

An acknowledged alert is not sent again

Acknowledging means somebody has picked the fault up. The next sweep updates the alert in place instead of raising it again, so nobody is told twice.

A resolved fault that is still there comes back

Resolving an alert while the ONU is still down says you are finished with it. If the fault outlives the ticket, the next sweep raises a fresh alert with its own clock.

A failed message never fails the read

Messages are sent after the alert is saved. If Telegram is down, the sweep still succeeds and the alert is still on the Alerts page; the bot token is never written to a log.

Setting it up

Five minutes, most of them in Telegram. Contacts are managed by ISP Admins, because a bot token is a secret.

Create a bot
In Telegram, message @BotFather, send /newbot, and follow the two prompts. It replies with a token that looks like 123456789:AA….
Add the bot to your NOC group
Add it like any member. It has to be in the group before it can post there.
Find the group’s chat ID
Send /start@your_bot_name in the group, then open https://api.telegram.org/bot<token>/getUpdates in a browser and copy the chat id. A group’s id is negative, for example -1001234567890.
Create a contact in RadixOLT
Contacts, then New contact: a name, Telegram as the channel, the token and the chat ID. The token is stored encrypted and never shown again.
Choose what it hears about
Whole ISP, which includes OLTs you add later, or Pick OLTs. Then press Send test; if Telegram refuses, its own reason is shown, such as “chat not found” or “bot was blocked by the user”.

Plans

Telegram delivery is part of the Pro plan, and of the 24-hour trial, which switches every plan feature on. On Basic, the same alerts appear on the Alerts page. WhatsApp delivery is planned and not built.

Alerts are raised by RadixOLT’s own sweep of your OLTs. Nothing needs installing on the OLT, and no SNMP traps have to be configured.