Events in Advanced Alerts

info

This page summarizes the main event types used in the Alerts & Automation system, including Frafos telephony events, system events, and alert system events. Understanding these events is key to building effective alerting and automation workflows.

---

What Are Events?

Events are JSON documents generated by Frafos equipment and the alerting system to report on various situations in SIP-based telephony environments. They describe actions such as calls starting or ending, registrations, system health, and more. Most events share common attributes, making them easy to filter, group, and evaluate.

---

Frafos Telephony Events

These events are generated by Frafos equipment to describe SIP call and registration activity.

Common Telephony Event Types

• Call-End: Generated when a call is successfully terminated using a SIP BYE transaction. Includes call duration and QoS statistics.
• Call-attempt: Generated when a SIP INVITE transaction completes with a non-200 status (3xx, 4xx, 5xx, 6xx). Failed authentication (401/407) is handled separately.
• Call-start: Generated when a SIP call begins (SIP INVITE with 200 OK response).

tip

All call-related events include URIs of calling/called party, SIP Call ID, and User Agent details. Only call-end events include call duration and QoS stats.

---

frafos SBC System Events

System events are generated by the alerting system to measure and report on its own performance.

• call_agent_counters: Provides periodic updates on traffic passing through the SBC from/to respective Call Agents.

---

Alert System Events

• ingest_redishealth: Periodically generated to report on REDIS memory usage. See Redis memory-stats documentation for details on the event content.

---

Example Event Structure

Call-End

{
  "event_type": "call-end",
  "attrs": {
    "from": "sip:userA@example.com",
    "to": "sip:userB@example.com",
    "call-id": "abc123",
    "duration": 360,
    "qos": { "mos": 4.2 }
  }
}

Call-Attempt

{
  "event_type": "call-attempt",
  "attrs": {
    "from": "sip:userA@example.com",
    "to": "sip:userB@example.com",
    "call-id": "def456",
    "sip-code": 486
  }
}

Call-Start

{
  "event_type": "call-start",
  "attrs": {
    "from": "sip:userA@example.com",
    "to": "sip:userB@example.com",
    "call-id": "ghi789"
  }
}

Call Agent Counters

{
  "event_type": "call_agent_counters",
  "attrs": {
    "agent": "SBC1",
    "calls_in": 120,
    "calls_out": 115
  }
}

Ingest RedisHealth

{
  "event_type": "ingest_redishealth",
  "attrs": {
    "used_memory": 1048576,
    "maxmemory": 8388608
  }
}

---

Additional Resources

• Events Documentation
• Redis Memory Stats

---

tip

Use event attributes to filter, group, and trigger alerts tailored to your environment.