> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/operations/analytics/queuemetrics.md).

# QueueMetrics Integration

QueueMetrics is a Call Center Queue (Teams) Analytics software.

## Overview

QueueMetrics is a [Call and Contact Center Software](https://www.pascom.net/en/call-contact-center/) Queues and Agents reporting tool.

## Configuration

### QueueMetrics Interface

QueueMetrics is a Loway product. The QueueMetrics interface transfers data between the PASCOM server and QueueMetrics via Uniloader. The Uniloader is also capable of receiving HTTPs commands from QueueMetrics and passing these on to the Asterisk AMI.

Since the AMI is integrated directly into the PASCOM platform, no additional installation is required on the PASCOM server.

### QueueMetrics Configuration

#### Add API User in QueueMetrics

Log in to the QueueMetrics web UI and select the menu option **Settings** > **User** > **Create New**.

Add the API User with the following values:

| Parameter        | Description                                                                                                                                                                                                                                                                                                     |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Login            | User login name. We recommend "pascom"                                                                                                                                                                                                                                                                          |
| Password         | Password for user authentication                                                                                                                                                                                                                                                                                |
| Confirm Password | Reenter the user password                                                                                                                                                                                                                                                                                       |
| Class            | From the dropdown menu, select the class "WQLOADER"                                                                                                                                                                                                                                                             |
| User keys        | <p>Click the Hat icon and select "User's roles" > "User may launch ROBOT transactions." and "Misc API access" > "The user can upload logs over HTTP". In the text field, "ROBOTS" will be automatically entered.<br><strong>Keys</strong>: USER ROBOT USR\_PCODE USR\_AGENT USRADMIN USR\_QUEUE USR\_SKILLS</p> |

![Queuemetrics Ami User](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-073169eb913d235933f42f9c5baef12c1c87bae4%2Fami-user.jpg?alt=media)

Save the user via **Save**.

### PASCOM Configuration

#### Connect the QueueMetrics Database

Log into the PASCOM web UI and select the menu point **Advanced** > **QueueMetrics**:

| Parameter            | Description                                                                                                     |
| -------------------- | --------------------------------------------------------------------------------------------------------------- |
| QueueMetrics enabled | By selecting Yes, PASCOM will start the service which continually saves queue data to the QueueMetrics database |
| QueueMetrics URL     | The URL of the QueueMetrics server                                                                              |
| API User             | The API user on the QueueMetrics Server (Login-Name)                                                            |
| API Password         | The API users password                                                                                          |

Save the configuration and apply all generator jobs.

#### Configure the Asterisk Manager Interface

In order to communicate with the phone system Server, you will need to allow QueueMetrics access via the Asterisk Manager Interface (AMI).

**Find the AMI Access Credentials**\
The AMI access credentials can be found in the PASCOM web UI under **Advanced** > **QueueMetrics** > **Show AMI credentials**

**Setup AMI Access in QueueMetrics**\
Now enter the access credentials within the QueueMetrics web UI under **Administrative Tools** > **Edit system parameters.** and activate the phone system's access:

```
...
callfile.dir=tcp:USERNAME:PASSWORD@127.0.0.1
...

...
default.webloaderpbx=true
...
```

Replace the USERNAME and PASSWORD with the AMI credentials from the PASCOM Web UI. The IP Address 127.0.0.1 does not need to be updated as the QueueMetrics Uniloader is located on the PASCOM cloud phone system host.

{% hint style="info" %}
The Call Monitor function (listening to live calls) from QueueMetrics is not currently possible with PASCOM 18.
{% endhint %}

### Set up Queuemetrics Live Call Monitoring

Enter the following parameters in the Queuemetrics web interface under **Administrative Tools**> **Edit system parameters.**:

```
callfile.monitoring.enabled=true
callfile.monitoring.channel=Local/10@queuemetrics
callfile.monitoring.extension=11
callfile.monitoring.context=queuemetrics
platform.directami.extension=PJSIP/${num}
platform.directami.localext=PJSIP/${num}
```

In Quemetrics itself, for live call monitoring you need the SIP peer of the end device that wants to monitor the channel:

![SIP Peer setting for live monitoring](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-9b7d861546766b779b578b08fc7e2846da7aac30%2Fsip-peer.jpg?alt=media)

![Live Monitoring](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-f248f6ebe845cc148c7cc20e2632720d7f8828e8%2Fspy-queuemetrics.jpg?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/operations/analytics/queuemetrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
