Messages

2401

Running QueueMetrics / Re: Call Details Issues

« on: July 22, 2008, 09:21:53 »

It's a memory problem in any case

2402

Running QueueMetrics / Re: Total calls processed

« on: July 22, 2008, 09:20:47 »

Yes - by using the Attempts page. This will work on a specially patched * 1.2. or on 1.4s.

2403

Running QueueMetrics / MOVED: Generating customised reports using XML RPC

« on: July 22, 2008, 09:19:54 »

This topic has been moved to Scripting QueueMetrics.

http://forum.queuemetrics.com/index.php?topic=309.0

2404

Running QueueMetrics / Re: calls not being dropped

« on: July 22, 2008, 09:19:04 »

It sometimes happens - with the next release we are adding a "ghost call killer" mode for QM. 

2405

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

« on: July 22, 2008, 09:18:23 »

I think you could automate that by calling to a fixed number, and then having the dialplan there use the CALLERID{num} or the extension ID and log that on and off. I have no experience with SNOM 360s, but I think it should be straightforward.
 

2406

Running QueueMetrics / Re: Agents not shown in some reports

« on: July 22, 2008, 09:16:15 »

As a general rule, to see agent activity, you should run a report that encompasses the agent sessions. If not, agents with no calls in the specified time frame are not shown. This can be changed by seeting a config switch.

2407

Running QueueMetrics / Re: Queuemetrics keeps Dieing

« on: July 22, 2008, 09:14:40 »

Did you use a different VM? it's strange that it was going SO bad as to die every 10 minutes. 

2408

General Asterisk configuration / Re: Incoming calls generate single-ring calls randomly

« on: July 22, 2008, 09:13:09 »

Do you have a log of what happened with that call? It would be interesting to see what went wrong. Maybe it's just a known bug in * (QM has no control of the call dispatch logic, just shows what is going on).
 

2409

General Asterisk configuration / Re: Enabling Agent's page action

« on: July 22, 2008, 09:10:24 »

Maybe is callfile.dir=tcp:admin: **********@127.0.0.1?

Yes that's it.
You should be seeing connection attempts on the Asterisk CLI anyway.

I suggest that when trying to configure you remove the deny/permit lines, see if it works and add them afterwards.

2410

General Asterisk configuration / Re: Dynamic Agents and Asterisk ARA

« on: July 22, 2008, 09:07:39 »

The problem with this is that QM actually uses the interface name as it's logged for the agent name. One siomple thjing that comes to my mind is: you could try using Local/1234@agents for agents, where 1234 is the agent code, and the [agents] context takes an agent id, does a DB lookup and calls the required SIP terminal. Do you think this would be OK?
 

2411

QueueMetrics installation / Re: Using fully dynamic members with QM 1.4 and Asterisk 1.4

« on: July 22, 2008, 09:03:10 »

Looks good

2412

QueueMetrics installation / Re: QueueMetric Vicidial Integration

« on: July 22, 2008, 09:02:08 »

In QM, set the "filename" as e.g.  sql:P001, where P001 is the name of the partition that your ViciDial instance writes to (easy to see that by using the MySQL storage entry under the config menu).
Then you should configure the queues (i.e. campaigns) you are running on the ViciDial in QM.
This should be it.

2413

Outbound and QueueMetrics / Re: Problem in outbound queue

« on: July 03, 2008, 22:25:28 »

While the conversation is ongoing (and incorrectly logged...) run a show channel command on the Asterisk CLI for the leg of the call that goes from the agent to Asterisk.

2414

Outbound and QueueMetrics / Re: Problem in outbound queue

« on: July 03, 2008, 08:59:47 »

Try this:
when the channel is open, try a "show variables"
one of the channel variables will surely holr the agent id/extension.
use that.

2415

General Asterisk configuration / Re: Enabling Agent's page action

« on: July 03, 2008, 08:56:59 »

This is meant only for true Agent/xxxx channels. Of course you can change the dialplan to suit your needs.