Admin Stats

• Call Stats
• Admin Reports
• Call Performance
• Peer Status
• Transcripts Status

Call Stats

Review global call statistics.

Use Admin > Call Stats to manage call stats.

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.

Admin Reports

Create and run global reports.

Use Admin > Admin Reports to manage admin reports.

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. The source form exposes these main blocks or fields: Date start, Date end.

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.

Main Fields

Field or block	Purpose
Date start	Review this value in relation to the object being configured and the tenant or system scope where it is used.
Date end	Review this value in relation to the object being configured and the tenant or system scope where it is used.

Call Performance

Analyze call performance and related metrics.

Use Admin > Call Performance to manage call performance.

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.

Peer Status

Review peer status across the system.

Use Admin > Peer Status to manage peer status.

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.

Transcripts Status

Review transcript processing state.

Use Admin > Transcripts Status to manage transcripts status.

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.