Control Hub notifications and threshold alerts

See also

Sources

1. 1
   Cisco renamed Alert Center to Notifications in a July 2026 change that also removed the Manage tab, moved the all rules and my rules sub-tabs under the Alerts tab, and renamed Requests to Approvals.

   What's new in Control Hub · What's new in Control Hub, July 2026, Updates to Alert Center · Checked 2026-09-05
2. 2
   2 Cisco documents give different illustrative alert thresholds for the same kind of rule: the notifications article uses more than 300 milliseconds latency or 8 percent packet loss and the technical paper uses more than 800 milliseconds latency or 8 percent packet loss.

   Notifications in Control Hub · Threshold-based alerts opening paragraph; technical paper page 31 Alerts section · Checked 2026-09-05
3. 3
   Call quality drop, trunk status change and trunk concurrent call limit alerts are not triggered on Dedicated Instance based trunks.

   Notifications in Control Hub · Add a call quality drop alert, Add a trunk status change alert and Add a trunk concurrent call limit alert · Checked 2026-09-05
4. 4
   Call quality drop alerts are sent when a call ends and an organisation may create at most 10 of them.

   Notifications in Control Hub · Add a call quality drop alert · Checked 2026-09-05
5. 5
   A separate certificate expiry alert for Dedicated Instance is sent 67 days before expiration and then every 12 days until the certificate is renewed.

   Notifications in Control Hub · Certificate expiry alert, Dedicated Instance section · Checked 2026-09-05
6. 6
   Trunk certificate expiry alerts are sent 60, 30, 15 and 7 days before expiry and once immediately after the certificate expires.

   Notifications in Control Hub · Trunk certificate expiry alert · Checked 2026-09-05
7. 7
   Alerts appear in the alerts view for the last 14 days and can be exported for the last 30 so 16 days of alerts exist only in an export.

   Notifications in Control Hub · Notifications in Control Hub, View alerts and rules · Checked 2026-09-15
8. 8
   Which delivery channels an alert type offers differs per type with no rule stated and the article's own general statement that alerts can be delivered by email webhook PagerDuty or a Webex space is contradicted by its own procedures.disputed

   Notifications in Control Hub · Notifications in Control Hub, the introduction against the per-alert delivery channel steps · Checked 2026-09-15
9. 9
   Trunk alerts are not triggered on Dedicated Instance based trunks.

   Notifications in Control Hub · Notifications in Control Hub, stated 4 times across the Calling alert sections · Checked 2026-09-15
10. 10
    The 4 meeting quality alert types offer email and a Webex space only so a media quality alert cannot be delivered to a webhook or to PagerDuty by its own procedure.

    Notifications in Control Hub · Notifications in Control Hub, the 4 meeting alert procedures · Checked 2026-09-15
11. 11
    The article carries 19 headings naming an alert across 4 service families and only 2 of the families have a heading of their own.

    Notifications in Control Hub · Notifications in Control Hub, heading structure of the rendered article · Checked 2026-09-15
12. 12
    The article publishes no retry behaviour no rate limit no HTTP method and no signature scheme for the webhook: retry rate limit HMAC signature and content type each occur 0 times.

    Notifications in Control Hub · Notifications in Control Hub, the webhook sections, counted against the rendered article · Checked 2026-09-15
13. 13
    The words role and permission occur 0 times in the article and no role is named for setting the organisation-wide webhook callback URL that every webhook-delivered alert uses.

    Notifications in Control Hub · Notifications in Control Hub, Set up a webhook callback URL, counted against the rendered article · Checked 2026-09-15
14. 14
    Two Webex help addresses with different article identifiers serve one rendered article titled Notifications in Control Hub which carries both the alert catalogue and the webhook material and links to itself.field report

    Notifications in Control Hub · Both addresses retrieved and compared by normalised rendered text · Checked 2026-09-15
15. 15
    The packet loss threshold range is published as 5 to 100 percent for 2 alert types and 5 to 50 percent for a third.field report

    Notifications in Control Hub · Notifications in Control Hub, the live meeting historical monitoring and device live meeting procedures · Checked 2026-09-15
16. 16
    Delivery to a Webex space reaches only the recipients added to the email delivery channel so an alert configured for a space with no email recipient reaches nobody.

    Notifications in Control Hub · Notifications in Control Hub, the 4 Calling alert procedures · Checked 2026-09-15
17. 17
    The article's introductory example of a 300 millisecond latency threshold is below the 400 millisecond minimum every latency field in the article accepts.field report

    Notifications in Control Hub · Notifications in Control Hub, introduction against the 6 latency threshold fields · Checked 2026-09-15
18. 18
    Two certificate expiry schedules coexist: a trunk certificate alert on the 60th 30th 15th and 7th day before expiry and once only after it and a Control Hub certificate alert 67 days before expiry and every 12 days until renewal.

    Notifications in Control Hub · Notifications in Control Hub, Trunk certificate expiry alert and Certificate expiry alert · Checked 2026-09-15

Documents

Cite this page

WarmTransfer. (2026, September 15). Control Hub notifications and threshold alerts. WarmTransfer. https://warmtransfer.net/knowledge/control-hub-notifications-alerts

@misc{warmtransfer-control-hub-notifications-alerts,
  title  = {Control Hub notifications and threshold alerts},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/control-hub-notifications-alerts},
  note   = {Verified 2026-09-15}
}