Messages

2776

Running QueueMetrics / Re: Popup in Queue Details not working

« on: November 07, 2007, 13:33:53 »

You should send over a sample of your logs - see http://astrecipes.net/index.php?n=251 .
Very likely this is a system crash that gets somehow hidden.

2777

Running QueueMetrics / Re: Agent goes available after 30 minutes

« on: November 07, 2007, 13:29:45 »

Yes: this is because on most CCs such a long talk time would be considered a system error, as call turnaround is much much faster. You can edit configuration.properties and change the following two paramenters:

Code: [Select]

#If an ongoing call has a wait time that exceeds this value, drop it. 0: ignore
default.maxOngoingWaitTime=1000

#If an ongoing call has a talk time that exceeds this value, drop it. 0: ignore
default.maxOngoingTalkTime=2000

Try setting them to 3600 (1hr) or 7200 (2hrs).

2778

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

« on: November 07, 2007, 13:27:35 »

I suggest you track the h extension and write a fake entry, though the actual talk time will be mistracked.

2779

Outbound and QueueMetrics / Re: Problem in outbound queue

« on: November 05, 2007, 14:45:07 »

I thoiught the variable would be set uatomatically buy AgentCallBackLigin in any case; if it's not the case, just set the AstDB variable yourself after the first AgentCallBackLogin.

2780

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

« on: November 04, 2007, 13:27:25 »

If anybody is using * 1.4, try the following:

A locally executed AGI script will receive SIGHUP on hangup from the channel except when using DeadAGI. This can be disabled by setting the AGISIGHUP channel variable to "no" before executing the AGI application.

And see if the application behaves correctly. If you're running 1.2, this cannot be done. I believe the cause of this problem is the script receiving HANGUPs.

2781

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

« on: November 04, 2007, 10:36:56 »

Does thei happens whenever the agent hangs up, or only when the agent hangs up while not in conversation or while the agents hangs up while in conversation?
I am trying to replicate this behaviour on both * 1.2 and 1.4 we have here in the lab and I am not having success...

2782

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

« on: November 04, 2007, 10:19:00 »

We are investigating on this issue - bug #229.

2783

Outbound and QueueMetrics / Re: Problem in outbound queue

« on: November 04, 2007, 10:13:51 »

I would do the following:
- Start a call from one agent and leave it open
- Find the Asterisk channel name through the CLI

Code: [Select]

aleph*CLI> show channels
Channel              Location             State   Application(Data)
H323/ip$10.10.3.6:22 s@coda-dps:9         Up      Queue(queue-dps|t|http://www.p

- Show the details of the channel, like:

Code: [Select]

aleph*CLI> show channel H323/ip$10.10.3.6:2256/14
 -- General --
           Name: H323/ip$10.10.3.6:2256/14
           Type: H323
       UniqueID: 1194167463.819
      Caller ID: 21
 Caller ID Name: test
.....
 --   PBX   --
        Context: coda-dps
      Extension: s
       Priority: 9
.....

      Variables:
MACRO_DEPTH=0
SYSTEMSTATUS=SUCCESS
TRANSFER_CONTEXT=queuetransfer
CallRefNum=1194167463.819
QueueName=queue-dps
MONITOR_FILENAME=DPS-1194167463.819

So you can spot what is correct for you to read.

2784

Running QueueMetrics / Re: An Agent can change the state of other different Agent.

« on: October 31, 2007, 20:03:21 »

Not at the moment, I fear.
But this is planned for the future.

2785

Running QueueMetrics / Re: I can Log on an Agent to an Extension that not exist.

« on: October 31, 2007, 19:58:57 »

Because QueueMetrics is not Asterisk, and it usually prefers not to block what people ask it to do because it thinks that humans know better. Of course this is not always the case 

2786

Outbound and QueueMetrics / Re: Problem in outbound queue

« on: October 31, 2007, 19:57:28 »

Not sure if it's a typo, but

Code: [Select]

Set(MY_AGENT=${AGENTBYCALLERID_${CALLERIDNUM})
Is lacking at least one }!

2787

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

« on: October 31, 2007, 19:55:38 »

Maybe here is the answer: http://www.asteriskguru.com/board/ringinuse-setting-in-queueconf-vt2306.html

2788

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

« on: October 31, 2007, 19:54:35 »

It looks correct - as you can see, it is generated exactly where Asterisk would generate its own event.
Looks like an Asterisk bug to me - maybe the exact version you're using ignores

Code: [Select]

ringinuse = no

2789

Running QueueMetrics / Re: An Agent can change the state of other different Agent.

« on: October 30, 2007, 14:07:36 »

Because he might do it in order to help a colleague.

2790

Improving QueueMetrics / Re: More flexible reporting

« on: October 30, 2007, 12:24:09 »

This is already available if you run with multi-stint mode enabled.