Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - revolution

Pages: [1] 2
1
Improving QueueMetrics / Re: Set Alarms on Specific Channels... ?
« on: January 30, 2008, 17:24:55 »
Because you need to configure that in the aggregate queue as well.
The problem, from whaty I can understand, is that there is only one alarm, and that is per queue and not, in case of composite queues, per member of the composite queue.

That is, if you have queues A and B each with their own analrm levels, you can create a queue A|B and set an alarm level for all calls in A or in B, but the alarm levels defined for A or for B will not be shown when seeing A|B.

Is this the problem you're trying to solve? :D

lol... yep!! along with many other problems of the world (including my lack of any real sleep lately... boo insomnia).

2
The problem seems to be with this section

 exten => _9XXX.,1,SetVar(MY_QUE=${EXTEN:1:3})
exten => _9XXX.,2,SetVar(MY_NUM=${EXTEN:4})
exten => _9XXX.,3,SetVar(MY_AGENT=${CALLERIDNUM})
exten => _9XXX.,4,NoOp,Ag: ${MY_AGENT} N: ${MY_NUM} Q: ${MY_QUE}
exten => _9XXX.,5,MixMonitor(Q-${MY_QUE}-${UNIQUEID}.wav|b|)
exten => _9XXX.,6,DeadAGI(queueDial.agi|${MY_NUM}|Zap/g0/${MY_NUM}|q-${MY_QUE}|Agent/${MY_AGENT})
exten => _9XXX.,7,Congestion

Asterisk is not reading at all that section or executing those commands for that matter. I thought it would that the extensions_custom.conf wasn't included, but after checking extensions.conf I can see it included there and also any other commands on that file go through, but just these commands don't.
Any ideas?

I believe the command has been changed to 'SET' as opposed to 'SETVAR' -- so that may be a good place for you to start... :)

3
Improving QueueMetrics / Re: Set Alarms on Specific Channels... ?
« on: January 28, 2008, 15:45:51 »
I did that... it works fine when realtime is only viewing internal calls...

but when you're viewing multiple queues... it doesnt show up :(

4
Improving QueueMetrics / Re: Set Alarms on Specific Channels... ?
« on: January 28, 2008, 06:15:12 »
add alarms by queue...

my example here is one we're using in a real-world application (call-center... primarily inbound with some outbound)

One of the determining factors in an the evaluation of the agents (i.e. to determine if they should be paid more/less, what level of benefits they should receive, etc.) is the amount of 'call-time' per day they average compared to how often they're on the phone -- queuemetrics is useful in tracking this (especially with pause codes, outcomes, etc. -- p.s. i wrote a nifty little php script that pauses an agent and inputs a pause code based on dialed extension if you'd like to see or test it)...

now -- people will *always* try to get over on the system... in this case by making internal calls to simulate call-time (some internal calls are legit... some are bullsh*t)...

What I think would be a good option would be to have the option to have an alarm on a specific queue (in my case -- internal) when you are running real-time with multiple queues -- in your example you use ooAll...) -- this would all the floor supervisor or section supervisor to be aware when an internal call is made so they can discretely listen in on that call to make sure it is a legitimate call... and not one just being used to run-up call time.

Your thoughts?

5
Improving QueueMetrics / Set Alarms on Specific Channels... ?
« on: January 22, 2008, 15:58:15 »
so I really dig the alarm thing (esp. the audible one) in relation to our internal calling (people of course can abuse internal calling in order to skew their numbers) -- but I noticed you can't set an alarm on a specific channel when you've monitoring multiples.

In a call-center type enviroment, this could really be helpful (the ability to set the alarm only on one channel out of 8 for example). I've never done anything with java, so I can't alter it to do this myself. :(

Anyone see the use in this ability?

6
Running QueueMetrics / Re: Queuemetrics stops working every Sunday!
« on: January 15, 2008, 17:35:22 »
What sort of debugging have you done in regards to this problem? Is the mysql daemon still working properly?

I'm curious to know what *exactly* is "not working" -- mysql? the qloader? queuemetrics itself? Asterisk? the box?

more info please :)

7
Running QueueMetrics / Re: Callers Stuck In Queue
« on: January 08, 2008, 15:57:24 »
you can always use "queue show <queue_name>" in the CLI :)

8
Ok well I figured out that 555 is the command for chain spy...oops, but I have one more question for you. What is the proper syntax to disable auto log off?

look in agents.conf

9
Running QueueMetrics / Re: Callers Stuck In Queue
« on: January 07, 2008, 22:34:36 »
personally I'd require a little more responsibility out of your agents -- why have autologoff turned on at all? Are you running a call-center?

regardless -- 15 (the default) is waaaaaay too low imho... at least double that if not more...

10
Running QueueMetrics / Re: Callers Stuck In Queue
« on: January 07, 2008, 20:09:07 »

That's what I was thinking about as well.


I know... I was co-signing and agreeing with your idea. ;)

11
Running QueueMetrics / Re: Callers Stuck In Queue
« on: January 07, 2008, 15:20:41 »
i second that motion -- maybe check autologoff=?????? in agents.conf :)

12
Running QueueMetrics / Re: Callers Stuck In Queue
« on: January 03, 2008, 16:49:15 »
This is more of an Asterisk question than a QM question -- but if you can provide me with a little more information, I'll be glad to try to help.

What version of Asterisk are you using? How are your Queues setup? What do debug/trace logs show?

13
Outbound and QueueMetrics / Re: monitoring transfer in QM
« on: December 17, 2007, 16:21:23 »
not a problem. just happy to be able to contribute in some way... I just want someone else to test it out and let me know if it's working the same for them.

14
Outbound and QueueMetrics / Re: monitoring transfer in QM
« on: December 12, 2007, 19:04:03 »
test it out and see if it works for you... maybe I just did something weird on the system ;x but its worked fine on the last 4 i've built.

15
Outbound and QueueMetrics / monitoring transfer in QM
« on: December 10, 2007, 23:36:23 »
Using the standard vm-macro... this monitors whether the call is internal (of course we want to keep an eye on our agents and make sure they aren't avoiding calls by staying on the phone with one another)... inbound (i.e. when someone calls in and enters an agents direct extension)... or a transfer from another extension. Just a matter of setting up the appropriate queues in QM (much like you'd setup an outbound queue), calling the macro in your extensions and adding a few lines to your vmail macro and changing queueDial.agi slightly.

example :

extensions ---

exten => 2000,1,Macro(voicemail|SIP/2000|2000|{vmail_group_name}|inbound or internal --depending on where the call originates)

exten => s,1,NoOp
exten => s,n,Set(context="${ARG4}")

exten => s,n,GotoIf($["${context}" = "internal"]?5:4) <--- does the context argument = internal? yes? move forward determine if it is a transfer and then reset the arg4... no? move to the next.

exten => s,n,GotoIf($["${context}" = "inbound"]?7:8)<--- does the context argument = inbound? yes? move forward and reset the arg4... no? move to the hangup.

exten => s,n,GoToIf($[${LEN(${CALLERID(num)})} > 5]?6:7) <--- in my case  the internal extensions are 4 digits long...so I look to see if the callerID is longer than that -- if it is not proceed to set the context as transfer...

exten => s,n,Set(context="transfer")
exten => s,n,Set(ARG4="")
exten => s,n,Set(agent="${CALLERID(num)}")
exten => s,n,DeadAgi(dial.agi|${ARG1}|${ARG1}|${context}|${agent})
exten => s,n,GoTo(s-${DIALSTATUS},1)
exten => s,n,HangUp()


make sure your altered queueDial.agi (saved as dial.agi) looks like this starting at line 34.

# Entering the program
logit(0,  "QueueDial ---- " . $ARGV[0] . "- " . $ARGV[1] ."----" . (scalar localtime) );

my $NUMBER  = $ARGV[3];
my $CHANNEL = $ARGV[3];
my $QUEUE   = $ARGV[2];
my $AGENT   = $ARGV[0];



maybe a bit sloppy... but it works.

Pages: [1] 2