Messages

2791

Improving QueueMetrics / Re: Queues timeouts report

« on: October 30, 2007, 12:23:36 »

This might be an idea. BTW if you use this setup, did you notice the multi-stint call reporting?

2792

QueueMetrics installation / Re: QM, ATTEMPTS patch and strange statistics

« on: October 30, 2007, 10:00:34 »

I am not sure why this happens, likely the patch went in the wrong place.... would you care to post a sample call with all the attempts logged?

2793

MySQL storage and Qloaderd/Uniloader / Re: Qloaderd 1.7 and Asterisk HEARTBEAT problem

« on: October 29, 2007, 11:36:44 »

Ok, is it fixed now?

2794

MySQL storage and Qloaderd/Uniloader / Re: A question with queue_log rotation.

« on: October 29, 2007, 11:36:03 »

Hello Bluekite,
I am frankly a bit short on Chinese at the moment , but your English is just fine.

The qloaderd will simply use the last "queue_log" file; if you do a rotation of that file, you should restart qloaderd as well (after Asterisk logger rotate) to tell it it is to read the new file.

2795

QueueMetrics installation / Re: QM, ATTEMPTS patch and strange statistics

« on: October 29, 2007, 11:29:46 »

I have a feeling this is not normal - whiuch queue strategy are you running?

2796

Running QueueMetrics / Re: How to delete queue_log records

« on: October 24, 2007, 09:40:41 »

I'd do something like:

Code: [Select]

SELECT DISTINCT call_id FROM `queue_log` WHERE agent = 'agent/101'
and get a list of call_id's to delete.

Then

Code: [Select]

DELETE FROM queue_log WHERE call_id IN ( ...... );
where '....' is your list of call_ids. This should do the trick.

2797

Realtime Live / Re: Problems with Agent pages

« on: October 21, 2007, 13:43:36 »

Lorenzo told me it is working now - do you confirm?

2798

Running QueueMetrics / Re: How to delete queue_log records

« on: October 21, 2007, 13:42:20 »

What you say is pretty rough (what gets written is far subtler than what you say) but... is it okay now?

2799

Improving QueueMetrics / Re: Peak/Average queue length

« on: October 21, 2007, 13:40:43 »

I confirm this is going to be in 1.4.3.

We are really excited about this, as we will be tracking the inital queue position for both taken and lost calls. This will work mostly for Asterisk 1.4, because in 1.2 the support for tracking initial queue position is feeble at best. Even in 1.4 it is far from being perfect, but we see a "real life" coverage of about 80%, enough to draw inferences from.

This is going to be very useful to CC managers - tracking queue lengths and queue turnaround times.

2800

Outbound and QueueMetrics / Re: Quemeterics not recognising remote caller hangup

« on: October 17, 2007, 20:40:16 »

This is strange, as the queuedail.agi was developed for 1.2. You're calling it through DeadAGI, correct?

2801

General Asterisk configuration / Re: Implement a dial-out queue

« on: October 17, 2007, 12:04:18 »

What di d you do so far? did you look at http://queuemetrics.com/download/TrixBox_Outgoing_v10.pdf ?

2802

Improving QueueMetrics / Re: More flexible reporting

« on: October 12, 2007, 09:00:21 »

Ok I can see that. I'll add your comments to the planned activities then. 

2803

Realtime Live / Re: Problems with Agent pages

« on: October 12, 2007, 08:59:25 »

1. are the buttons clickable or d o you immediately get a ne rror message?

2. if you are logged on to the Asterisk CLI when you press a button, do you see any activity?

2804

Running QueueMetrics / Re: How to delete queue_log records

« on: October 12, 2007, 08:58:04 »

Try this:
- look at one of those calls (in QueueMetrics, click on "call detail" and find the caller_id)
- search for that caller_id in the queue_log table (and you'll find one or more call id's)
- select all rows with those call id's

This should make it clear why you're still seeing that agent.

2805

Running QueueMetrics / Re: How to delete queue_log records

« on: October 10, 2007, 15:33:04 »

Deleting them from MySQL will suffice. If QM is still showing those calls, it means you forgot some