cdr analytics · published

Control Hub notifications and threshold alerts

Verified 2026-09-15 · 12 claims · sources tier 2 · 1 disputed

Also known as Alert Center, Call Quality Drop, Notifications, Trunk certificate expiry alert, webhook callback URL.

Disputed claims: 1 claim below carries conflicting evidence.

Control Hub alerts and notifications cover service monitoring across Webex service families 5. In the field, 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 8.

Alert catalogue and delivery channels

The article includes 19 headings naming an alert across 4 service families, and only 2 of these families have a heading of their own 5. Field reports suggest that Two Webex help addresses with different article identifiers serve this single rendered article, which carries both the alert catalogue and webhook material and links to itself 8.

Sources disagree on delivery channel availability: 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 2. The 4 meeting quality alert types offer email and a Webex space only, meaning a media quality alert cannot be delivered to a webhook or to PagerDuty by its own procedure 4. Furthermore, 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 10.

Thresholds and schedules

In the field, the article's introductory example of a 300 millisecond latency threshold is below the 400 millisecond minimum that every latency field in the article accepts 11. Field reports suggest that the packet loss threshold range is published as 5 to 100 percent for 2 alert types and 5 to 50 percent for a third 9.

Two distinct certificate expiry schedules coexist in the documentation: a trunk certificate alert triggers on the 60th, 30th, 15th, and 7th day before expiry and once only after it, whereas a Control Hub certificate alert triggers 67 days before expiry and every 12 days until renewal 12. Trunk alerts are not triggered on Dedicated Instance based trunks 3.

Webhook integration and data retention

The article publishes no retry behaviour, no rate limit, no HTTP method, and no signature scheme for the webhook, with the terms retry, rate limit, HMAC, signature, and content type each occurring 0 times 6. In addition, 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 7.

Alerts appear in the alerts view for the last 14 days and can be exported for the last 30 days, meaning 16 days of alerts exist only in an export 1.

See also

Applicability

Across the claims in this article, the evidence covers Cisco Webex Control Hub, verified as of 2026-09-15. The deployment model is not covered by any claim in this article. Trunk alerts do not apply to Dedicated Instance based trunks 3.

What remains uncertain

Which delivery channels each alert type actually supports is not covered by any claim in this article. Whether an alert is lost when the webhook endpoint is down is not covered by any claim in this article. The HTTP method, headers, and signature scheme of the alert webhook are not covered by any claim in this article. Why the minimum configurable latency threshold is 400 milliseconds is not covered by any claim in this article.

See also

Excludes

Related to

Referenced by

Claims

#ClaimStatusConfidenceVerified
1Alerts 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
fact0.902026-09-15
2Which 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.
Notifications in Control Hub · Notifications in Control Hub, the introduction against the per-alert delivery channel steps
disputed0.602026-09-15
3Trunk 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
fact0.902026-09-15
4The 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
fact0.902026-09-15
5The 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
fact0.902026-09-15
6The 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
fact0.902026-09-15
7The 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
fact0.902026-09-15
8Two 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.
Notifications in Control Hub · Both addresses retrieved and compared by normalised rendered text
field-pattern0.902026-09-15
9The packet loss threshold range is published as 5 to 100 percent for 2 alert types and 5 to 50 percent for a third.
Notifications in Control Hub · Notifications in Control Hub, the live meeting historical monitoring and device live meeting procedures
field-pattern0.902026-09-15
10Delivery 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
fact0.902026-09-15
11The article's introductory example of a 300 millisecond latency threshold is below the 400 millisecond minimum every latency field in the article accepts.
Notifications in Control Hub · Notifications in Control Hub, introduction against the 6 latency threshold fields
field-pattern0.902026-09-15
12Two 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
fact0.902026-09-15

Sources

tier 2 current vendor documentation

Notifications in Control Hub

Cisco Systems, Inc. (Webex Help Center) · 2026-08-11 · accessed 2026-09-15

Cite this page

APA

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

BibTeX

@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}
}