Messages

2191

Running QueueMetrics / Re: Call routing on Queues

« on: December 20, 2008, 22:06:34 »

The fact that you get the same number of calls on the first and second lines does not signal a problem per se; it might just be that the queue is very saturated - how many calls are you losing?

Instead, I suggest routing  a call when one of the agents in layer 1 is free and see if it gets connected correctly.

By the way, I think there is a mistake in your queue config, because it's rrmemory and not rrememory. 

2192

AGAW / Re: agaw-runner SQL problem?

« on: December 19, 2008, 09:23:40 »

Looks like it's a known bug, as of here: http://forum.queuemetrics.com/index.php?topic=402.0 - easy to fix though

2193

Outbound and QueueMetrics / Re: outbound calls not working if logged in via QM

« on: December 19, 2008, 09:22:06 »

I really see no difference, but if in a case it does not work, there must be some. 
Can you point a trace of an outbound call when you are logged in manually versus logged in via QM, so we can see what the difference is?

2194

Outbound and QueueMetrics / Re: EXPERIMENTAL: replace the queueDial.agi with a pure-scripting solution

« on: December 17, 2008, 14:44:57 »

Well there is no reason to be concerned - I'm not sure what the macro does, but surely is not needed by the underlying Asterisk architecture, as long as the trunk name makes sense. 

2195

General Asterisk configuration / Re: File permissions in /var/spool/asterisk/outgoing/

« on: December 17, 2008, 14:43:45 »

I think the easiest way is to skip call files at all and use a Manager connection by setting:

Code: [Select]

callfile.dir=tcp:dial:bingo@10.10.3.100
This will connect to the Manager port of an Asterisk on 10.10.3.100 with user "dial" password "bingo". You of course have to set the relevant manager.conf settings right.

2196

QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem

« on: December 17, 2008, 14:39:41 »

Thanks.

2197

Outbound and QueueMetrics / Re: EXPERIMENTAL: replace the queueDial.agi with a pure-scripting solution

« on: December 17, 2008, 09:15:14 »

I'd say that you do something like:

Code: [Select]

exten =>_XXXXXXXXXX,1,Set(QDIALER_QUEUE=q-999)
exten => _XXXXXXXXXX,n,Set(QDIALER_NUMBER=1${EXTEN})
exten => _XXXXXXXXXX.,n,Set(QDIALER_AGENT=Agent/${CALLERID(num)})
exten => _XXXXXXXXXX,n,Set(QDIALER_CHANNEL=SIP/trunk-name/${QDIALER_NUMBER})
exten => _XXXXXXXXXX,n,Set(QueueName=${QDIALER_QUEUE})
exten => _XXXXXXXXXX,n,MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV|b|)
exten => _XXXXXXXXXX,n,Goto(qm-queuedial,s,1)
Basically you take the Agent code from the caller-id, the number is 1+number, and you dial on SIP/trunk-name/number.
This has NOT been tested, so take this as an example.

2198

Outbound and QueueMetrics / Re: outbound calls not working if logged in via QM

« on: December 16, 2008, 10:15:56 »

From what you say, the agent IS logged on correctly....

Code: [Select]

  == Callback Agent '1002' logged in on 1002@from-internal

2199

QueueMetrics installation / Re: 3 node cluster each with a different timezone

« on: December 16, 2008, 10:14:54 »

At the moment, the clustering feature is expectiong all data to be in the same time-zone, or it will not understand things. What you can do is to use the offset parameter of qloaderd to make al lthe calls have the same timestamp.

Code: [Select]

my $timezone_offset  = 0 * 3600;  # in seconds
The timezone offset is ADDED to the current timestamp when sending data over to QM.

2200

AGAW / Re: agaw-runner.sh problem

« on: December 15, 2008, 10:04:46 »

Good - do you like the new AGAW module?

2201

Outbound and QueueMetrics / Re: outbound calls not working if logged in via QM

« on: December 15, 2008, 10:02:44 »

OK what do you get in the CLI when you try calling the logon code from QM?

2202

QueueMetrics installation / Re: Live Monitoring Problems

« on: December 15, 2008, 09:57:38 »

Hello Gavin,
you should modify the configuration file so that it can call back to your telephone - for example, if your extension is 200@from-internal, it needs to be set in the configuration.èproperties file like:

callfile.monitoring.enabled=true
callfile.monitoring.channel=Local/$EM@from-internal/n
callfile.monitoring.extension=11
callfile.monitoring.context=queuemetrics
 
This is because it will first try ringing the number you enter as Local/num@context/n and your local extension should ring.

After that, it will bridge the call to the chanspy session as defined in 11@queuemetrics, that is like:

; extension 11 makes remote monitoring possible
exten => 11,1,Answer
exten => 11,2,NoOp( "QM_AGENT_CODE: ${QM_AGENT_CODE}" )
exten => 11,3,NoOp( "QM_EXT_MONITOR: ${QM_EXT_MONITOR}" )
exten => 11,4,NoOp( "QM_AGENT_EXT: ${QM_AGENT_EXT}" )
exten => 11,5,ChanSpy(${QM_AGENT_CODE})
exten => 11,6,Hangup


If you encounter problem with this second part, you should make sure that what you end up passing to the Chanspy() application is what yuou expect it to be - usually it's the Agent code (like Agent/1234) but if you use a different setting you may set it differently.

 

2203

Outbound and QueueMetrics / Re: outbound calls not working if logged in via QM

« on: December 12, 2008, 09:12:19 »

To place an outbound call, it's not technically necessary that the agent be logged on - though it's nice for uniformity, etc. and you can logon any way you like, as long as it's a valid logon - so using or not using the QM dialplan, it's the same.
The QM dialplan was made to be called from the agent interface, so variables are set correctly.

2204

QueueMetrics installation / Re: Missing dirs on install?

« on: December 11, 2008, 15:08:03 »

That's okay. Sometimes people have a few problems with youm, I cannot really understand why, because it happens to very few people.

2205

QueueMetrics news / Re: New FAQ entries

« on: December 10, 2008, 12:17:21 »

A new FAQ was added today: Using multi-stint mode in QM