Messages

2881

Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue

« on: August 22, 2007, 18:54:43 »

I run the following test:

I have a system with many calls on it, but none on "Q Test" (which internal name is queue-test). I run a realtime report for it and I get:

Response block: RealTimeDO.RTRiassunto

Code: [Select]

Queue  N. agents Ready agents On pause Unk Bsy N. Calls waiting On phone inbound On phone outbound
All selected 0 0 0 0 0 0 0 0

(Sorry if it's not really readable - hard to format)
This is correct - I get that All selected queues are zero calls and zero agents.

If I run a call to it, I get:

Response block: RealTimeDO.RTRiassunto

Code: [Select]

Queue  N. agents Ready agents On pause Unk Bsy N. Calls waiting On phone inbound On phone outbound
All selected 0 0 0 0 0 1 0 0
Q Test 0 0 0 0 0 1 0 0   

This looks correct to me as well - I have one call waiting in the queue, and so one waiting as well in "All selected" that is the same as my very queue.

About the problem with agents, Asterisk agents are - generally speaking - not linked to one specific queue, so the agent logon/logoff status is orthogonal to the taken calls system.
If you'd like the "Show members only" button to be pressed for XML-RPC reports, well, you can change the default setting in configuration.properties and Qm will use that setting.

And yes, I agree, it would be nice to be able to override system settings from the XML-RPC interface as well - but this might be for the future releases 

2882

Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue

« on: August 22, 2007, 09:21:24 »

No I think it's by design, as long as you get the same results of the realtime page without pressing any button on it.

2883

Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue

« on: August 21, 2007, 22:13:21 »

This looks correct then - But I'll have the tech people have a look, just in case.

2884

Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue

« on: August 21, 2007, 19:06:24 »

I am filing this as  a possible bug - from what I know of QM's "guts" it seems pretty strange, but anything is possible 

2885

Running QueueMetrics / Re: XML-RPC realtime method does not filter by queue

« on: August 21, 2007, 18:24:25 »

"All Selected" is the same as one single queue, is fyou selected that single queue 

2886

Running QueueMetrics / Re: queue_log problem?

« on: August 21, 2007, 10:04:07 »

No, but Qm does not know anything about the fact the file is shared, so it treats it as if it were a regular file on the filesystem.

My idea is that somehow some caching mechanism kicks in, so that QM ends up not seeing the latest version of the file, so:

- Find some mount option that will make the file readable correctly on the QM machine. I would start by playing with rsize and wsize and nfsvers and noac - see http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-nfs-client-config.html - also  see man nfs on your Linux box.

- Use some other file-sharing mechanism, like SMB

Please keep us posted on how it goes.

2887

QueueMetrics installation / Re: Problems going to 1.4.0 from 1.3.4

« on: August 21, 2007, 09:45:16 »

It looks like your queue_log file contains some AgentAttempt-related data that QM does not process correctly and it crashes. In 1.4 the main engine was completely rewritten, so I'd say this is a bug.
Please send the queue_log file over to Loway, so we can debug the problem and patch it for version 1.4.1.

2888

Running QueueMetrics / Re: queue_log problem?

« on: August 20, 2007, 11:58:53 »

We have a number of customers who use a NFS share - QM is read-only on it, so there is no reason why the share does not get updated.

Anyway, if you want to avoid wasting time on it, why don't you try implementing the Qloaderd approach to send data from the Asterisk to the QM database? you can find the latest qloaderd and its docs in QM under WEB-INF/mysql-utils.

2889

Running QueueMetrics / Re: queue_log problem?

« on: August 20, 2007, 08:12:21 »

You mena the file is not written to by the Asterisk process? this sounds really weird... are you sure your calls are hitting the queue() command at all?
If you instead do not see the updated lines on the oether side of the NFS share, there is likely some caching/buffering being made at the mount point; thry and have a look at the various share and mount options.

2890

Running QueueMetrics / Re: queue_log problem?

« on: August 18, 2007, 08:41:49 »

How do you connect the two machines in order to send data over to the QM box? are you using qloaderd?

Anyway,
1. check that the new data gets appended to the queue_log file
2. if you are using qloaderd, check that the new data actually gets written in the queue_log table of the Qm database

If the two tests above pass,
3. check that your queue definition is correct, that is you are running reports for existing queues

2891

Improving QueueMetrics / Re: Show Pause Reason on Realtime page

« on: August 16, 2007, 19:47:45 »

This is already planned for 1.4.2. In fact it's pretty foolish not to show pause codes on the realtime 

2892

General Asterisk configuration / Re: Problem with agent sessions being doubled up in reports

« on: August 16, 2007, 19:45:54 »

It does look like a bug. The queu_log looks correct.
Please contact Loway by email and send over a copy of your queue_log for debugging. Thank you!

2893

QueueMetrics installation / Re: QueueMetrics and CallWeaver

« on: August 10, 2007, 09:11:23 »

That's okay. Just let us go if you get any result.... 

2894

QueueMetrics installation / Re: QueueMetrics and CallWeaver

« on: August 09, 2007, 15:53:42 »

How did your testing go?

2895

General Asterisk configuration / Re: Asterisk log rotating

« on: August 09, 2007, 15:52:32 »

Of course you can rotate all files freely BUT the queue_log, QueueMetrics does not care about any other Asterisk-produced file.

In particular, inthe log rotation file, you use

Code: [Select]

/var/log/asterisk/full {
     ...
}

What it matters is NOT to use the wildcard *log, because that will rotate queue_log as well