Notifications in Control Hub

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/article/nlxh072/Manage-Alerts-for-Advanced-Diagnostics-and-Troubleshooting-in-Control-Hub

Published

2026-08-11

Updated

unknown

Accessed

2026-09-15

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• 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. fact in context
• The Control Hub call quality drop alert defines good as both video and audio streams below 150 milliseconds jitter, 400 milliseconds latency and 5 percent packet loss, and poor as both streams above all 3. fact in context
• Call quality drop, trunk status change and trunk concurrent call limit alerts are not triggered on Dedicated Instance based trunks. fact in context
• Call quality drop alerts are sent when a call ends and an organisation may create at most 10 of them. fact in context
• A separate certificate expiry alert for Dedicated Instance is sent 67 days before expiration and then every 12 days until the certificate is renewed. fact in context
• When concurrent calls exceed the route list calls licence limit up to 20 percent additional capacity is allowed, and off-net calls beyond that bursting limit are blocked. fact in context
• Trunk certificate expiry alerts are sent 60, 30, 15 and 7 days before expiry and once immediately after the certificate expires. fact in context
• Webhook delivery is offered for some alert types and not others: 5 of about 12 named types offer it, at least 5 do not, and one type is described with no delivery channel at all. fact in context
• The steps that set the organisation-wide webhook callback URL name no administrator role, and the word role occurs 0 times in the notifications article, while other alert categories in the same article do name a required role. fact in context
• The article reached as Enable webhooks for alerts in Control Hub is served as Notifications in Control Hub, has no heading of that name, and uses the word alert 234 times against 40 for webhook. field-pattern in context
• None of the 3 webhook payload examples in the notifications article can be parsed: the introductory one ends with a trailing comma and the 2 per-alert examples open on a bare data key with no enclosing brace. field-pattern in context
• The proactive alerts section says notifications are delivered by email, Webex App spaces or both, and its own procedure three sentences later says a webhook may be selected if webhooks are enabled at organisation level. disputed in context
• A secret token is optional on both webhooks, and both articles send the reader elsewhere for how it works rather than documenting it. fact in context
• The notifications article points at a Cisco devices webhook field reference in a separate article, which is a third webhook surface beside the alert webhook and the detailed call records webhook. fact in context
• The notifications article publishes 2 incompatible webhook payload schemas that share 5 field names, and they differ even in the casing of the subtype field. disputed in context
• The Control Hub notifications webhook and the Webex Calling detailed call records webhook are different mechanisms: different setup surfaces, different configuration models and different payloads, and neither article names the other. fact in context
• 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. fact in context
• 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 in context
• Trunk alerts are not triggered on Dedicated Instance based trunks. fact in context
• 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. fact in context
• The article carries 19 headings naming an alert across 4 service families and only 2 of the families have a heading of their own. fact in context
• 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. fact in context
• 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. fact in context
• 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-pattern in context
• 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-pattern in context
• 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. fact in context
• 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-pattern in context
• 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. fact in context

Cite this source record

APA

WarmTransfer. (2026, August 11). Notifications in Control Hub. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-nlxh072-control-hub-notifications

BibTeX

@misc{warmtransfer-cisco-help-nlxh072-control-hub-notifications,
  title  = {Notifications in Control Hub},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-nlxh072-control-hub-notifications},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-15}
}