Messages

1

Running QueueMetrics / Agent Count report

« on: July 12, 2018, 18:20:48 »

     Does anyone know of a quick way to get a report on the number of agents online at any given moment?  I need to know the maximum number of agents online at any given time frame so I can make sure we do not hit the license cap.

2

General Asterisk configuration / Asterisk 15 and Queuemetrics with WebRTC phone...

« on: July 11, 2018, 00:08:53 »

     I followed the instructions to set up Queuemetrics to use the integrated WebRTC phone.  Everything is running SSL (Lets Encrypt).  The webphone seems to register but becomes unreachable after a minute or so.  If I dial a number it takes about 30 seconds before I see Asterisk receive the call.  I get no audio on the call no matter is it is MoH or another extension.  The guide was made for regular chan_sip and not for PJSIP so I was wondering if anyone has been able to get the webphone working with Asterisk 13 or 15 and PJSIP.

     I have tried other webrtc webphones with the same configuration and they work with audio both ways.  This is all on a local LAN with no NAT at the moment although JsSIP and SIP5ML both work from outside the local network.  Any pointers?

3

General Asterisk configuration / Queuemetrics and PJSIP

« on: May 30, 2017, 00:08:57 »

     As PJSIP is becoming the defacto standard for Asterisk how is Queuemetrics handling this?  All the dialplan logic and scripts are set up to handle chan_sip.  Will Queuemetrics even work with Asterisk 13 and PJSIP?

4

Running WombatDialer / Alternate numbers in list

« on: June 08, 2015, 02:47:33 »

I saw that the new Wombat supports loading alternate numbers for the same customer.  I need this feature and was wondering how to implement it.  I have looked through the manual and cannot find how to load those numbers.  JUst to check, this is what I need:

On a call list we load the main number for a client and then we want to load an alternate contact number if we are not able to contact the client on the main number.  Obviously if the client is contacted on the main number we do not want to dial the alternate.  If the client is contacted on the alternate number wombat should not retry the main number either. 

Any ideas on how to do this?

5

Running QueueMetrics / No audio on webrtc phone

« on: February 26, 2015, 00:53:12 »

I just did a clean install of Queuemetrics 15.02.01 and everything seems to be working fine except I am getting absolutely no audio on the webrtc phone included in the Icon agent page.  The phone registers and I can answer the call or dial another extension.  There is no incoming or outgoing audio.  I tried to use the latest Firefox and Chrome with the same result.  Last time I tested webrtc (about 4 months ago) was on version 14 and it worked well.  Any recommended versions to make everything run smoothly?  I already configured firefox to let queuemetrics use the mic and not prompt for it every time.

6

Running QueueMetrics / Queuemetrics not detecting agent login to queue

« on: September 19, 2014, 19:20:49 »

I am testing the latest Queuemetrics 14.06 for a new project.  I am now able to use the webrtc softphone with Asterisk 11.12 and Firefox.  The problem I am having is that the agent page is not detecting when an agent is online.  Queuemetrics is reading directly from /var/log/asterisk/queue_log at the moment.  In the agent page I can use the Agent Logon panel, select the queues I want to login to.  The queue moves to the loggedin column with a spinning wheel for about 30 seconds and returns to the available column after.  I can see the agent if I do a "queue show" in the cli but as far as queuemetrics is concerned the agent is still offline.  This is the first Asterisk 11 I am using with Queuemetrics, is there some configuration I missed? 

In the reports I can see the calls I made to the queue but in the agents section there is no information at all.  I guess that queuemetrics is not registering the agent from the queue_log file for some reason.

7

Running WombatDialer / Error after upgrade to 0.7.7

« on: September 17, 2014, 18:44:48 »

We upgraded today to version 0.7.7 from 0.6.4 and now we are getting an error when loading the web interface:

Callback failure:com.google.gwt.user.client.rpc.StatusCodeException: 500
HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: NLIC/0
   it.loway.tpf.transaction.servlets.common.ServletEnvironment.init(ServletEnvironment.java:103)
   ch.loway.tpf.gwt.srv.servlets.LowayGwtController.init(LowayGwtController.java:37)
   javax.servlet.GenericServlet.init(GenericServlet.java:212)
   org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:291)
   org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
   org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
   org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
   java.lang.Thread.run(Thread.java:662)

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.33 logs.

After doing the upgrade it ran once to update the database and it said that is was successful but the error showed up immediately after that.

8

General Asterisk configuration / Re: Transferred calls show extension s instead of extension number

« on: September 27, 2013, 18:41:12 »

They press the transfer button on the phone and then dial a 4 digit extension number.

Extensions are defined in the dialplan as:

exten => 1501,1,Macro(stdexten,1501,SIP/1501)

9

General Asterisk configuration / Re: Transferred calls show extension s instead of extension number

« on: September 26, 2013, 18:45:27 »

Transfers are done using the SIP phones transfer button, not with the Asterisk function.  Here are some log entries for transfers:

1379433548|1379433498.2515|ventas2|SIP/1527|TRANSFER|s|macro-stdexten|7|42|1
1379438586|1379438459.3325|ventas|SIP/1513|TRANSFER|s|macro-stdexten|1|124|1
1379440824|1379440639.3638|ventas|SIP/1513|TRANSFER|s|macro-stdexten|1|183|1
1379541764|1379541247.14829|ventas5|SIP/1729|TRANSFER|952017800|oficina|4|512|1
1379686450|1379685157.6295|RCI|SIP/1902|TRANSFER|952831111|oficina|35|1249|1

The ones that go to internal phones using the stdexten macro are the ones reporting s, calls to outside phones do have the correct number.

10

General Asterisk configuration / Transferred calls show extension s instead of extension number

« on: September 24, 2013, 23:54:50 »

I am having a problem tracking transferred calls.  They are shown in the reports but only external transfers (outside the call center) show the number dialed.  When the call is transferred to an internal extension I just get "s" as the destination.  Why would this happen?  The only thing I can think of is that my internal extension macro uses s to process the call.  Any idea on how to correct this?  I am using plain Asterisk 1.8 on Centos.  All dialplan logic is coded by hand.

11

Running QueueMetrics / Re: Wait time always 0

« on: August 02, 2013, 00:42:33 »

I found the problem.  When the Queuemetrics installation was done the persona that installed it rand the database init twice and there was some duplicate information in many tables.  If I take the queue_log table to another Queuemetrics server I do get all the proper stats.

12

Running QueueMetrics / Problem with URL pop up

« on: August 02, 2013, 00:26:10 »

I have followed instructions to try and get the agent page to pop up a new browser window.  I gave the queue command the URL parameter:

[2013-08-01 16:01:49] VERBOSE[17209] pbx.c:     -- Executing [20@queue-encuesta:5] Queue("SIP/mcm-000094bb", "20,,http://192.168.11.10/superautos/index.php?referencia=2085677") in new stack

I have realtime.agent_autoopenurl=true

I am using Wombat to dial the call and set up a variable for the number and that is properly set up.  However I cannot get the agent page to open the new url.  What other settings do I need to change in configuration.properties to get this working?

Something I just noticed is that the agent page is not showing any of the calls it has received during the day.  Maybe this is related?  I am using Queuemetrics 13.04.2, Freepbx 2.11, Asterisk 1.8.22.0 and Wombat 0.7.0.1

13

Running QueueMetrics / Re: Wait time always 0

« on: July 05, 2013, 18:41:25 »

I just grabbed the queue_log file and did a new setup on another server and all reports give me the correct wait time.  I am using the same version installed via yum and loway.repo.  I really do not know what the possible reason for the problem is but I need to fix the problem in the production server without nuking everything.

14

Running QueueMetrics / Re: Wait time always 0

« on: July 03, 2013, 17:01:52 »

Here is a queue_log entry for a call:

1372782526|1372782526.403|FEPADE|NONE|ENTERQUEUE||5517924703|1
1372782529|1372782526.403|FEPADE|SIP/103|CONNECT|3|1372782526.404|3
1372782591|1372782526.403|FEPADE|SIP/103|COMPLETECALLER|3|62|1

Here is the call detail from Queuemetrics:

Asterisk Call ID:       1372782526.403
Date and time:       07/02 - 11:28:46
Queue:       FEPADE [fepade]
Caller ID:       5517924703
Handled by:       Agente 3 (103)
Duration:       62 sec.
Time in IVR before queueing:       0 sec.
Waiting time:       0 sec.
Original position       # 1
Disconnection cause:       Caller disconnected
Transferred to:       
Attempts:       1
Last Failed Attempt:       -
Bridged Channel:       1372782526.404
Stints:       1
URL:       
Status code:       
Srv       
DNIS       
IVR selection       
- 1372782526.403.wav

As you can see IVR and Wait time are 0 for the call but the log entry says 3.  As I mentioned before the agent page does have the correct wait time.  Here is the information from the database on the same call:

+-----------+------------+----------------+--------+---------+----------------+-------+----------------+-------+-------+-------+----------+------------------+
| partition | time_id    | call_id        | queue  | agent   | verb           | data1 | data2          | data3 | data4 | data5 | serverid | unique_row_count |
+-----------+------------+----------------+--------+---------+----------------+-------+----------------+-------+-------+-------+----------+------------------+
| P001      | 1372782526 | 1372782526.403 | FEPADE | NONE    | ENTERQUEUE     |       | 5517924703     | 1     |       |       |          |                1 |
| P001      | 1372782529 | 1372782526.403 | FEPADE | SIP/103 | CONNECT        | 3     | 1372782526.404 | 3     |       |       |          |                1 |
| P001      | 1372782591 | 1372782526.403 | FEPADE | SIP/103 | COMPLETECALLER | 3     | 62             | 1     |       |       |          |                1 |
+-----------+------------+----------------+--------+---------+----------------+-------+----------------+-------+-------+-------+----------+------------------+

15

Running QueueMetrics / Wait time always 0

« on: June 28, 2013, 23:39:42 »

I am setting up a new Queuemetrics installation with Asterisk 11.4 and Queuemetrics 13.04.02.  Everything seems to be working fine except that when I go to a report the wait time for all calls is always 0:00.  The duration is correct so I have no idea why wait time is not displayed properly.  Anything I need to tweak in the configuration?  The agent realtime page does show the correct wait time so why the difference?