Topics

1

QueueMetrics installation / Configuring Agents (Elastix 2.2)

« on: December 13, 2011, 12:48:22 »

Hi All,

I am using queuemetrics 1.7.1.13 with Elastix 2.2.0 and I am having issues reporting on indivual agents.

I have noticed in queue_log that the Agent isnt referred to as SIP/XXXX or Agent/XXXX but their full name as specified in their Extension setting i.e.

1315814197|1315814159.8350|6006|Jane Smith|RINGNOANSWER|15000

I have tried to build the Agent in Queuemetrics as

Asterisk Agent Code: Agent/Jane Smith
Agent Description: Jane Smith

But when I run an individual user report I get 0 results.

From my previous work with Queuemetrics/queue_log Asterisk normally logs the agent activity as Agent/XXXX , I havent seen this behaviour before.

Many THanks,

Gavin

2

Lost licences / Lost License

« on: September 07, 2011, 19:50:34 »

Hi,

Is it possible to recover our license , we are migrating back to a server running Queuemetrics and as such are hoping to reuse our license key.

What is the recovery process?

Many Thanks,

Gavin

3

Running QueueMetrics / Display Call lengths in seconds rather than HHMMSS

« on: November 04, 2009, 17:06:07 »

Hi All,

Can the daily reports/weekly reports/30 day reports etc, be modified so all the call lengths are returned in seconds rather than hours/minutes/seconds?

The average call length is reported correctly in seconds, however as below - Min/Max/Total is in Minutes Seconds.

Many Thanks

gavin

Average call length:      256.7 s.
Min call length:    2:00
Max call length:    11:11
Total call length:    38:30

4

Running QueueMetrics / Queuing callers over 30mins drop out of Real Time Monitoring

« on: September 10, 2009, 17:48:53 »

Hi,

I have been doing some testing and found that calls holding for normally longer than 30minutes fail to be displayed on the Real Time monitoring page.

# asterisk -rx 'show queue 200'
200          has 5 calls (max 10) in 'ringall' strategy (0s holdtime), W:0, C:0, A:1, SL:0.0% within 0s
   Members:
      800 (SIP/1000800) (paused) (Not in use) has taken no calls yet
      801 (SIP/1000801) (paused) (Not in use) has taken no calls yet
      802 (SIP/1000802) (Ringing) has taken no calls yet
      803 (SIP/1000803) (paused) (Not in use) has taken no calls yet
      804 (SIP/1000804) (paused) (Not in use) has taken no calls yet
      805 (SIP/1000805) (In use) has taken no calls yet
      806 (SIP/1000806) (paused) (Not in use) has taken no calls yet
      807 (SIP/1000807) (Not in use) has taken no calls yet
      808 (SIP/1000808) (paused) (Not in use) has taken no calls yet
      910 (SIP/1000910) (Not in use) has taken no calls yet
   Callers:
      1. SIP/.net-0881baa0 (wait: 37:33, prio: 0)
      2. SIP/.net-087f5f50 (wait: 35:55, prio: 0)
      3. SIP/.net-087471e8 (wait: 33:03, prio: 0)
      4. SIP/.net-086d62a0 (wait: 13:22, prio: 0)
      5. SIP/.net-087c1788 (wait: 8:23, prio: 0)

Real time monitoring only shows call "4" as the only call waiting in the queue.

The relevant queues.conf context is below

[200]
announce-frequency=105
announce-holdtime=no
autofill=yes
eventmemberstatus=yes
eventwhencalled=yes
joinempty=strict
leavewhenempty=yes
maxlen=10
monitor-type=mixmonitor
monitor-format=wav49
music=classical
periodic-announce-frequency=180
queue-callswaiting=queue-callswaiting
queue-thankyou=queue-thankyou
queue-thereare=queue-thereare
queue-youarenext=queue-youarenext
retry=5
timeoutrestart=yes
strategy=ringall
timeout=20
weight=0
wrapuptime=30
context=ivr-2
periodic-announce=custom/supportqbreakout2
member=>SIP/1000800,,800
member=>SIP/1000801,,801
member=>SIP/1000802,,802
member=>SIP/1000803,,803
member=>SIP/1000804,,804
member=>SIP/1000805,,805
member=>SIP/1000806,,806
member=>SIP/1000807,,807
member=>SIP/1000808,,808
member=>SIP/1000910,,910


Has anyone come across this before?

5

Running QueueMetrics / 1.5.2 - Tracking IVR Activity

« on: April 29, 2009, 21:17:26 »

Hi,

Ive been eager and updated my QM install to 1.5.2, how can I enable IVR activity tracking? Currently all 72 calls that had IVR activity today have been set to Untracked?

Many Thanks,

Gavin

6

General Asterisk configuration / Call Monitor not working since moving to Static Agents

« on: February 12, 2009, 17:33:13 »

Hi All,

After a number of problems with silent calls/not receiving calls using Dynamic Agents, I have moved to Static Agents, however this seems to of broken my ability to monitor calls.

My queue configuration now looks like ;

[200]
announce-frequency=105
announce-holdtime=no
autofill=yes
eventmemberstatus=yes
eventwhencalled=yes
joinempty=strict
leavewhenempty=yes
maxlen=10
monitor-type=mixmonitor
monitor-format=wav49
music=moh
periodic-announce-frequency=180
queue-callswaiting=queue-callswaiting
queue-thankyou=queue-thankyou
queue-thereare=queue-thereare
queue-youarenext=queue-youarenext
retry=5
timeoutrestart=yes
strategy=ringall
timeout=20
weight=0
wrapuptime=30
context=ivr-2
periodic-announce=custom/supportqbreakout2
member=>SIP/1000800,,800
member=>SIP/1000801,,801
member=>SIP/1000802,,802
member=>SIP/1000803,,803
member=>SIP/1000804,,804
member=>SIP/1000805,,805
member=>SIP/1000806,,806
member=>SIP/1000807,,807
member=>SIP/1000910,,910

I still see the Call Monitor icon , against my agents in Realtime monitoring , however clicking on the user and entering my extension 1000800 results in the call being connected but no audio passing.

The following is seen in the Tomcat log ;

$Id: PluggableRTListener.java,v 1.3 2008/09/23 11:20:06 lenz Exp $
$Id: ClassicQMListenerRT.java,v 1.3 2008/09/23 11:20:07 lenz Exp $
Extenal dialling
  Server ID: ''
  Inbound  ?  true
  Agent    : 'agent/807'
  AgentExt : '-'
  Extension: '1000800'
  -> Chan : 'Local/1000800@from-internal/n'
  -> Dial : '11@queuemetrics'
Stato finale:2 - 'The extension you requested was dialed. You should receive the call in a few seconds.' URL: w:0 h:0

2009-02-12 16:12:08 StandardContext[/queuemetrics][523EE9BFA9C0D649A1BDDDEB99E4993B] Fine classe it.loway.app.queuemetrics.callListen.remoteAudioMonitor
2009-02-12 16:12:08 StandardContext[/queuemetrics]LowayTransactionController: [523EE9BFA9C0D649A1BDDDEB99E4993B] Tempo totale esecuzione verbo 'qm_popup_audiomon_phase2': 3058 ms


Any ideas on how to resolve this situation would be appreciated.

Many Thanks,

7

QueueMetrics installation / Live Monitoring Problems

« on: December 12, 2008, 12:45:42 »

Hi,

I'm trying to setup Queuemetrics 1.5.0 (FreePBX 2.5.0) to enable call monitoring.

I have set up the configuration file to enable monitoring, and also added #include extensions_queuemetrics.conf to /etc/asterisk/extensions_custom.conf

I have the telephone icon appear when I enter live overview.

Clicking on the telephone icon , brings up a box asking for my extension (800), then I get an error - Errors occurred trying to perform action after clicking on Monitor Now.

I'm unsure about the following lines, and how you implement these in FreePBX ;

Make sure that the channel is set to Local/$EM@queuemetrics/n if your current telephones call on context queuemetrics.

Make sure that the extension/context are set to 11/queuemetrics ( the unattended audio monitoring endpoint).

8

Realtime Live / Live Monitoring - Waiting/Duration Times

« on: October 02, 2008, 20:32:23 »

Hi,

I am migrating away from a Trixbox solution to my own custom installation using Asterisk/FreePBX 2.5.0/Queuemetrics 1.4.7.1 (Licensed)

Everything is up and running apart from , during Live Monitoring, the Waiting/Duration Times for a call do not appear to get updated , the fields are always blank.

9

QueueMetrics installation / JDBC Error - The SAX XML parser is not installed.

« on: September 29, 2008, 13:59:14 »

Hi All,
I'm in the middle of reinstalling Queuemetrics onto a new Ubuntu(Debian) based installation (Im having problems with Trixbox inside VMware)

I'm receiving an error when I try to perform the Queuemetrics installation test - The SAX XML parser is not installed.

This error is not mentioned in the FAQ and my Java JDK still's are not upto much - does anyone have any hints or tips? I'm using tomcat 5.5 as well.

Many thanks.

10

Running QueueMetrics / Automatically logging in/out of agents using SNOM handsets

« on: July 11, 2008, 16:23:59 »

Hi,

I have a network of SNOM 360 handsets and I am planning to make Queuemetrics live on Monday.

Currently in order to log in/log out of the Queue we have to dial the access number, then enter the agent ID, then the extension

Has any one found a way to automate this using the Speed Dial keys on the SNOM range of phones?

I can get the Speed Dial setup, but cannot insert a pause into the string, so the SNOM just tries to call the full number.