Source record · tier 2 current vendor documentation
Configure a paging group in Control Hub
- Publisher
- Cisco Webex Help Center
- URL
- https://help.webex.com/en-us/article/jqejtd/Configure-a-paging-group-in-Control-Hub
- Published
- 2025-10-07
- Updated
- unknown
- Accessed
- 2026-09-25
- HTTP status
- 200
- License
- Cisco website terms of use; no-redistribution; short excerpts and locators only
Source notes citing this source
- For customers in the Asia-Pacific region, the paging group's Calling Line field is populated automatically with the username and cannot be changed. in context
- On a Cisco ATA 192, paging works only if the page is answered manually within 1 to 2 seconds or an external device with auto-answer is connected to the ATA. in context
- A caller who pages a group that has no registered devices hears a busy signal. in context
- Control Hub offers an option to show the paging group name as the caller ID instead of a custom name. in context
- A custom caller ID name for pages from the group can be up to 128 Unicode characters. in context
- Native Webex Calling group paging (up to 75 targets, no on-premises server) covers more endpoints than UCM's free InformaCast Basic Paging (up to 50 phones), but it does not replace InformaCast Advanced Notification for overhead, text or unlimited-endpoint alerting. inferred in context
- When creating a paging group in Control Hub, the admin can optionally copy the selected targets into the originator list. in context
- The paging group's Dial by Name field accepts ASCII characters. in context
- A paging target with Do Not Disturb enabled is not paged. in context
- A user can be assigned as both a paging target and a paging originator in the same paging group. in context
- An existing paging group's general settings, phone number, paging targets and paging originators can be edited in Control Hub. in context
- The originator ends the page by hanging up. in context
- The extension for a paging group must be available and not already assigned. in context
- A paging group has a language setting chosen from a drop-down during creation. in context
- A paging group is created under a specific location and given a name and a phone number or extension; a location can hold more than one paging group. in context
- A Webex Calling paging group lets a user place a one-way group page to up to 75 targets by dialing the number or extension assigned to the paging group. in context
- A paging group must have more than one member. in context
- Paging groups are created and edited in Control Hub under Services > Calling > Features, on the Paging Group card. in context
- If a paging target has Single Number Reach (Office Anywhere), Call Forwarding or Simultaneous Ring enabled, the page is not sent to those configured destinations. in context
- If a paging target does not answer a page, the page is not forwarded to that target's voicemail. in context
- The paging group admin article says that if a paging target is already on a call, the page is not automatically answered. disputed in context
- A group page is one-way audio: the originator has a talk path to the targets, and targets have no talk path to the originator or to each other during the page. in context
- Paging group originators are chosen by searching for and adding users, workspaces or virtual lines. in context
- Paging groups work only on a member's primary devices and do not work on shared devices (shared line appearances). in context
- Once the page is set up to the targets, the originator hears a 'Paging System Ready' announcement telling them to begin speaking. in context
- Each paging group member must have at least one registered device. in context
- The Group Paging service calls all assigned targets simultaneously. in context
- Paging groups work only with Cisco IP Phone 6800, 7800, 8800, 8875 and 9800 Series and Cisco ATA 191 and ATA 192. in context
- Paging group targets can be users, workspaces or virtual lines. in context
- Because Cisco's paging group article lists only Cisco phones and ATA 191 and 192 as supported, putting a third-party SIP paging adapter such as an Algo 8301 into a paging group as a target is probably not a Cisco-documented configuration; the safer design is to call the adapter directly, for example by its extension. inferred in context
Cite this source record
APA
WarmTransfer. (2025, October 7). Configure a paging group in Control Hub. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-jqejtd-configure-paging-group
BibTeX
@misc{warmtransfer-cisco-help-jqejtd-configure-paging-group,
title = {Configure a paging group in Control Hub},
author = {{WarmTransfer}},
year = {2025},
url = {https://warmtransfer.net/knowledge/sources/cisco-help-jqejtd-configure-paging-group},
note = {Cisco Webex Help Center, accessed 2026-09-25}
}