Global Lists

Global Lists administration tasks.

Admin CDRs

Review call history across tenants.

Use Admin > Admin CDRs to manage admin cdrs.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

Typical Workflow

  1. Open the menu entry and confirm whether the record already exists.
  2. Create or edit the record with a descriptive name and only the required options first.
  3. Save the record and reopen it to verify the stored values.
  4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

Documentation Example

For documentation and testing, use names prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

DIDs List

Review DID assignments across tenants.

Use Admin > DIDs List to manage dids list.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

Typical Workflow

  1. Open the menu entry and confirm whether the record already exists.
  2. Create or edit the record with a descriptive name and only the required options first.
  3. Save the record and reopen it to verify the stored values.
  4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

Documentation Example

For documentation and testing, use names prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

Extensions List

Review extension assignments across tenants.

Use Admin > Extensions List to manage extensions list.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

Typical Workflow

  1. Open the menu entry and confirm whether the record already exists.
  2. Create or edit the record with a descriptive name and only the required options first.
  3. Save the record and reopen it to verify the stored values.
  4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

Documentation Example

For documentation and testing, use names prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

Media Files List

Review tenant media files from a global view.

Use Admin > Media Files List to manage media files list.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

Typical Workflow

  1. Open the menu entry and confirm whether the record already exists.
  2. Create or edit the record with a descriptive name and only the required options first.
  3. Save the record and reopen it to verify the stored values.
  4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

Documentation Example

For documentation and testing, use names prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

External Agents List

Review external queue agents from a global view.

Use Admin > External Agents List to manage external agents list.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

Typical Workflow

  1. Open the menu entry and confirm whether the record already exists.
  2. Create or edit the record with a descriptive name and only the required options first.
  3. Save the record and reopen it to verify the stored values.
  4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

Documentation Example

For documentation and testing, use names prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.