Automation rules and Telegram alerts

Panel page: Automation (Ctrl K → automation) · Add-on, from $15 a month

A rule is written in the panel, not in code: when something happens on a port, do something, and tell you.

On every SIM port: when 5 connected calls in a row talk under 10 seconds on average, turn the port off and tell me. Wait 30 minutes before firing again on the same port.

Part	What you choose
Trigger	What to watch (the six triggers below), with its numbers
Scope	Which ports: all SIM ports, one gateway, a routing group, single ports, or ports whose name matches a pattern
Actions	Turn the port off; put it back after a number of minutes; tell you
Cooldown	How long before the same rule may fire again on the same port
Channel	Where the alert goes: a Telegram chat

Trigger	Fires when	Numbers
Fast answer	the last N connected calls in a row averaged under X seconds of talk	calls, seconds
Failure streak	N attempts in a row and not one connected	attempts
ASR floor	ASR fell under X % over the last N attempts, optionally only to one destination prefix	%, attempts, prefix
Registration lost	a port has been unregistered for X minutes	minutes
Silent port	a port is registered but carried no call for X minutes while the others carried N	minutes, calls
Daily minutes	a port passed X connected minutes since midnight	minutes

Under the editor, the panel shows which ports the rule would have caught in the last 24 hours. If it would have turned off half your ports, change the numbers before you save.

1. Create a Telegram chat or group for the alerts. We connect the alert bot to it with you during the onboarding call.
2. In Automation → Channels, add the chat and press Test. A test message should arrive in the chat.
3. Choose the channel in each rule. Without a channel, a rule uses the first enabled one.

• A rule only turns ports off. It never turns on a port you turned off.
• A rule puts a port back only when it turned that port off itself and the rule says to put it back.
• Turning a port back on by hand closes the event.
• Every action a rule takes is written to the audit log.

Problem	Rule
A SIM answers calls but they drop at once	Fast answer: 5 calls, under 10 s → off, tell me
A port stopped working but still looks fine	Failure streak: 10 attempts → off, tell me
A gateway lost power or network	Registration lost: 5 minutes → tell me
A port is up but gets no calls	Silent port: 60 minutes while the others carried 20 → tell me