Skip to main content

Create Paging Groups

A Paging Group is a reusable set of Cisco IP phones that you can target from one or more Notify Scenarios.

API-First Configuration

Create and maintain Paging Groups through the REST API. A dedicated Notify interface is not currently available in the Call Telemetry web application.

Requirements​

Choose a Group Type​

Group TypeBest For
StaticA controlled list of specific phones that changes infrequently.
DynamicPhones selected from current inventory by attributes such as building, floor, department, or emergency zone.
NestedReusing existing groups inside a larger notification audience.

Use descriptive names that identify both the audience and location, such as Austin Campus - Building A. Avoid names such as Test Group 1 that are difficult to interpret during an incident.

1. Review Existing Groups​

List the organization's Paging Groups:

GET /api/org/{org_id}/paging/groups

See List Paging Groups.

2. Create the Group​

Create a Paging Group:

POST /api/org/{org_id}/paging/groups

Provide a clear name and description, then configure static members, dynamic selection rules, or nested groups. Validate the request against Create a Paging Group.

3. Preview Dynamic Membership​

Preview a dynamic group before using it in a Scenario:

POST /api/org/{org_id}/paging/groups/preview

Review the resolved devices for unexpected omissions or broad matches. A successful preview confirms the current rule result; it does not guarantee that every phone will remain registered or reachable when the Scenario launches.

Missing Phones

If preview results are incomplete, verify the group's selection rules, the phone's inventory attributes, and CUCM registration data before changing the Scenario.

4. Maintain Static Members​

Use the member operations to review or change explicit group membership:

Preview the group again after a substantial inventory or membership change.

5. Add the Group to a Scenario​

When you create or update a paging trigger, add the Paging Group ID to target_group_ids. Use target_recipient_group_ids for unified recipient groups that can route to supported non-phone channels.

Before launching broadly, execute the Scenario against a small controlled group and inspect the delivery results.