Supported PBXs

FreePBX Distro

FreePBX Status

2.10

OK

2.11

OK

6.12

OK

14

OK

15

OK

16

OK

Elastix

The following versions of Elastix have been tested with Espresso:

Elastix Status

1.6.0

OK

2.0.4 b4

OK

2.2

OK (Hotdesking, Asterisk 1.8, automated installation)

2.3.0 beta2

OK (Hotdesking, Asterisk 1.8, automated installation)

TrixBox

TrixBox Status

2.6.x.x

OK (Transfer and Call Hangup from the realtime page are not supported)

2.8.x.x

OK

AsteriskNOW

The queue_log file is not automatically rotated daily or weekly by the standard AsteriskNOW distribution. Please note that the queue module has to be installed before installing QueueMetrics with espresso otherwise the qloaderd should be restarted manually after the queue module installation.

(AsteriskNOW is a registered trademark of Digium Inc.)

AsteriskNOW Status

1.7.0

OK (Transfer and Call Hangup from the realtime page are not supported with Asterisk 1.4)

1.7.1

OK (Transfer and Call Hangup from the realtime page are not supported with Asterisk 1.4)

2.0

OK

3.0.0

OK

PBX-in-a-Flash

PIAF Status

1.7.5.7.1

OK (Please note that Tomcat is very slow to start-up and shutdown; Transfer and Hangup call from the realtime page are not supported with Asterisk 1.4)

2.0.6.2.1

Not supported

Thirdlane

Thirdlane is a bit different from FreePBX-based systems. It still can be configured through Espresso but a few things are different. The first is that Thirdlane has the concept of TENANTS - that is everything you do is linked to a tenant. For example, if you create SIP extension 200, it will actually be called SIP/200-t1, where "t1" is your tenant code. A single-tenant instance of Thirdlane will use a defaut tenant called "thirdlane".

So, in order to make QM work, you need to follow the rules below:

  • Tenant codes should be all lowercase. Uppercase ones might not work.

  • When you log in an agent through an extension, the extension should be entered as "200-t1", not just "200".

  • All queues are called "queuename-tenant". So queues "sales-t1" and "sales-t3" are two distinct queues used by two distinct tenants.

  • In order to enable inbound and outbound chanspy from the real-time page, you should define a tenant code for each agent; you will enter this in the "CURRENT TERMINAL" field for the agent. So if Agent/101 works for tenant "t3", you should enter "t3" in the Current Terminal field for Agent/101.

Thirdlane Status

2.2 ST

OK

2.2 MTE

OK (Transfer from the realtime page is not supported)

What if my PBX is not on the list?

If your version of the PBX is not listed on the tables above, and installation fails, QueueMetrics will be configured with a link to a help page on the QueueMetrics website. This way, one of our technicians will get in touch with you and will help you installing a working version of QueueMetrics for your system.

On the help page, we will ask you for the exact model and version of the PBX used, so that if that is possible we will include it in the next release of Espresso.

Once the new version is released, you can re-apply it on your system by issuing the command:

 yum update queuemetrics-espresso

And wait for its completion. This will install a working system overwriting the current configuration.

If you want to remove the link on the QueueMetrics login page pointing to our help page, you can do that by editing the property called layout.splash in the file configuration.properties that is installed under /usr/local/queuemetrics/qm-current/WEB-INF.