Messages

2056

Outbound and QueueMetrics / Re: outboun calls

« on: March 17, 2009, 08:47:52 »

If in QM you see the agent as Agent/111, you should change it to:

Code: [Select]

exten => 14,6,ChanSpy(sip/${QM_AGENT_CODE:6})

The agent code being chanspied on is passed in the ${QM_AGENT_CODE} variable by QM.

2057

Outbound and QueueMetrics / Re: outboun calls

« on: March 16, 2009, 09:20:18 »

That's likely because the channel name in the ChanSpy is wrong.

Try this:
- when the call is ongoing, enter a show channels; so you know how the channel is called.
- edit the ChanSpy line so that it matches said channel

2058

Outbound and QueueMetrics / Re: outboun calls

« on: March 15, 2009, 12:04:39 »

For outbound use any piece of code that works - for LISTENING TO OUTBOUND instead add the piece of code I told you about.

2059

Outbound and QueueMetrics / Re: outboun calls

« on: March 14, 2009, 10:54:54 »

You have to add this to extensions_queuemetrics.conf

Code: [Select]

; extension 14 makes remote monitoring possible for OUTBOUND CALLS
exten => 14,1,Answer
exten => 14,2,NoOp( "QM_AGENT_CODE: ${QM_AGENT_CODE}" )
exten => 14,3,NoOp( "QM_EXT_MONITOR: ${QM_EXT_MONITOR}" )
exten => 14,4,NoOp( "QM_AGENT_EXT: ${QM_AGENT_EXT}" )
exten => 14,5,NoOp( "QM_LOGIN: ${QM_LOGIN}" )
exten => 14,6,ChanSpy(Local/${QM_AGENT_CODE:6}@from-internal)
exten => 14,7,Hangup

Make sure that the format of the ChansPy() command matches your outbound channels.


See also: http://queuemetrics.com/manuals/QM_Trixbox-chunked/ar01s03.html

2060

QueueMetrics news / New TrixBox integration giude

« on: March 12, 2009, 19:05:56 »

If you use TrixBox, we are pleased to announce that we have written a new TrixBox integration guide for QueueMetrics 1.5.1 that covers:

- Dynamic agents (no more Agent/XXX channels) with managed login to their correct queues
- Using the new agent's page
- Inbound queues with audio recordings
- Live listening of inbound calls
- Outbound queues with presence and audio recordings
- Live listening of outbound calls

...all this in about 30 pages

Even if you do not use TrixBox, it is well worth a look because we give a concrete example of using fully dynamic agents, thus avoiding the deprecated AgentCallBackLogin problems (but QM will continue to support it if you use it, so don't worry  - no need to change existing configs).

The tutorial can be downloaded from: http://queuemetrics.com/download/QM_Trixbox_300.pdf

Or it can be read online at: http://queuemetrics.com/manuals/QM_Trixbox-chunked

As always, we value your comments, corrections and ideas.

2061

Outbound and QueueMetrics / Re: outboun calls

« on: March 12, 2009, 16:54:29 »

Is the call you want to listen to inbound or outbound?

2062

Running QueueMetrics / Re: Historical Report

« on: March 12, 2009, 16:53:46 »

Yes; run a report for all queues for the given period, go to the agent's page and click on an agent's name.

Or click on the "Agent session detail" button on the bottom of the page (depends if you want to see them one-by-one or all together).

2063

QueueMetrics installation / Re: Upgrade to 1.5.1 from 1.4.3

« on: March 12, 2009, 16:50:05 »

1. make sure that yuour agents have somethingin the LOCATION field or they will never appear for monitoring.

2. Try using Local/XXX@ctxt chhannels and enable agent rewrite, and then log oin agents as agent/XXX

2064

Outbound and QueueMetrics / Re: outboun calls

« on: March 11, 2009, 12:20:21 »

Does the audio file exist at all? was the call recorded?

2065

QueueMetrics installation / Re: Upgrade to 1.5.1 from 1.4.3

« on: March 11, 2009, 12:19:36 »

About live call audio monitoring, try and run it and see what you get on the CLI.

Are you using Agent channels on the 1.6 or Local/XXX channels? do you have rewrite enabled?

2066

Outbound and QueueMetrics / Re: Queuemetrics 1.5.1 outbound by Agent problems

« on: March 10, 2009, 16:03:46 »

What do you see on the Asterisk CLI?

I think that you'll have to use queueDial.agi for Asterisk 1.2; the dialplan is for version 1.4+

See  http://queuemetrics.com/faq.jsp#faq-013-queueDial
 
If it does not work, try this: http://queuemetrics.com/faq.jsp#faq-014-agi

Please let us know how it goes.

2067

Outbound and QueueMetrics / Re: Problem in outbound queue

« on: March 10, 2009, 16:01:28 »

 

2068

MySQL storage and Qloaderd/Uniloader / Re: QM on Windows 2003

« on: March 06, 2009, 19:19:49 »

1. about negative time, the clock must be exactly aligned on the Asterisk, MySQL and QM server. If it's not, real-time will be off.

2. QM does not poll the AMI continuously; it does atr most every few seconds. If you see constant activity, it's not from QM.

2069

Outbound and QueueMetrics / Re: Queuemetrics 1.5.1 outbound by Agent problems

« on: March 06, 2009, 19:17:34 »

We realize there is a bug with the version of extensions_queuemetrics.conf that ships with QM 1.5.1; you have to add this part:

; extension 28: agent custom dial
exten => 28,1,Answer
exten => 28,2,NoOp( "QM: Agent Custom Dial. Dialing ${EXTTODIAL} on queue ${OUTQUEUE}  made by '${QM_LOGIN}'" )
exten => 28,3,Set(QDIALER_QUEUE=${OUTQUEUE})
exten => 28,4,Set(QDIALER_NUMBER=${EXTTODIAL})
exten => 28,5,Set(QDIALER_AGENT=Agent/${AGENTCODE})
exten => 28,6,Set(QDIALER_CHANNEL=SIP/${QDIALER_NUMBER})
exten => 28,7,Set(QueueName=${QDIALER_QUEUE})
exten => 28,8,MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV|b|)
exten => 28,9,Goto(qm-queuedial,s,1)
exten => 28,10,Hangup

Of course, set QDIALER_CHANNEL so that it makes sense with your system.
We are preparing a new tutorial for Trixbox that will use only dynamic agents and we will release it in a few days.

2070

Running QueueMetrics / Re: asking for licences but I'm alone in the system

« on: March 06, 2009, 19:14:01 »

QM licencing is linked to the numbe rof "cative agents" in the systems, not on those who use it.