Messages

31

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 05, 2010, 19:14:39 »

You're right. But in the supplied extensions_queuemetrics.conf the original extension 20 is this one:

Code: [Select]

; extension 20: agent callback login
;               For this to work, there must be no password on the agent.
exten => 20,1,Answer
exten => 20,2,NoOp( "QM: Logging on Agent/${AGENTCODE} to extension ${AGENT_EXT}@from-internal made by '${QM_LOGIN}'" )
exten => 20,3,AgentCallBackLogin(${AGENTCODE},,${AGENT_EXT}@from-internal)
exten => 20,4,Hangup

And it uses AgentCallBackLogin, which is no longer available on Asterisk 1.6.1.   So you're using outbound with Asterisk 1.6 but not logging the agents via their page on QM, is that right?

Yeah that's correct, I am not using the QM agents page presently. It is something I will be adding at some stage. However, I have done my own thing to implement AgentCallBackLogin style functionality using realtime members, and only having the AGENTCODE and AGENT_EXT would suffice.

Can you post your dialplan which agents use to log in? I am sure there is a way to make it work.

EDIT: Forgot to add this. So, considering that Asterisk 1.6 has no longer the app AgentCallBackLogin and it appears that QM doesn't set the required variables in order to add dynamically the channel to the queue... all indicates that 1.6 isn't the best choice in this case. As this is my first QM implementation, I hope I'm dead wrong about this. 

It can be done. I admit the changes in 1.6 caused a lot of headaches to a lot of people. In my case, however, the pain turned out to be worth it because my system now is totally realtime and very efficient.

I intend to document it and make it available, but finding the time is a challenge!

-Barry

32

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 05, 2010, 15:33:27 »

I used the dialplan provided by Loway. Here's the extension 20 on the context queuemetrics:

Code: [Select]

; extension 20: agent addqueuemember (for asterisk v1.4+)
exten => 20,1,Answer
exten => 20,n,NoOp( "QM: AddQueueMember (asterisk v1.4+) Agent/${AGENTCODE} on queue ${QUEUENAME} made by '${QM_LOGIN}'" )
exten => 20,n,AddQueueMember(${QUEUENAME},Local/${AGENTCODE}@interno)
exten => 20,n,Hangup
Looks like the variable QUEUENAME is not being set. Also, I have specified the agent's extension as 201, and I can't see where that info is used.

Guess I'm doing something very wrong here. Any suggestions?

Hi,

Extension 20 is for agent login (at least in the example extensions_queuemetrics.conf supplied) , whereas you appear to be calling the AddMember extension. For agent login $QUEUENAME would not be required, only the following are needed: AGENTCODE and AGENT_EXT and they both get set in my test.

-Barry

33

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 05, 2010, 11:41:22 »

Do we have to list you as "Non-continnetal support team"? 

But then I would have to answer the hard questions as well ;-)

Wannabe Hero?

-Barry

34

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 04, 2010, 16:24:28 »

Yeah, but I'm still listed as a newbie 

35

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 03, 2010, 17:50:52 »

the real problem is that when the agent logs off, he still is listed as logged in on the wallboard. Here's a few entries on my queue_log:

1267634130|1267634122.11|NONE|Local/101@xagents|AGENTCALLBACKLOGIN|201
1267634130|1267634122.11|q-001|Local/101@xagents|ADDMEMBER|
1267634228|1267634228.12|q-001|Agent/101|ENTERQUEUE|-|21047051|
1267634234|1267634228.12|q-001|Agent/101|CONNECT|6||
1267634247|1267634228.12|q-001|Agent/101|COMPLETECALLER|6|13|
1267634266|1267634260.16|q-001|Local/101@xagents|REMOVEMEMBER|
1267634266|1267634260.16|NONE|Local/101@xagents|AGENTCALLBACKLOGOFF|

Even after that, the agent is still listed as logged in. Any ideas on solving this?

Hi,

The problem is that you are alternating between referring to your aghents as Agent/101 and as Local/101
Queuemetrics by default expects to see Agent/ - that's why it is seeing the agent once they are on a call, but not the login/logoff part.

If you edit configuration.properties and change:
# Rewrites Local/XXX@ext channels in the format Agent/XXX
default.rewriteLocalChannels=false

to
# Rewrites Local/XXX@ext channels in the format Agent/XXX
default.rewriteLocalChannels=true

...you should be good.

Hope this helps.

-Barry

36

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 03, 2010, 16:49:28 »

Thanks for the help. How are you registering the agent's logoff?

In my dialplan which handles this, I include the following:

exten => s,n,Set(GLOBAL(AGENTBYCALLERID_${CALLERID(num)})="")
exten => s,n,QueueLog(NONE,NONE,Agent/${AGENTID},AGENTCALLBACKLOGOFF,${CALLERID(num)}@from-internal,,CommandLogoff)

This basically does the reverse - clears the AGENTBYCALLERID_${CALLERID(num)} variable and writes a suitable queue_log entry.

37

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: March 03, 2010, 15:45:26 »

Hi,

I use outbound queues fine with Asterisk 1.6. If add something like the following to the part of your dial plan where agents actually log in, it should work:

exten => s,n(loggedin),Set(GLOBAL(AGENTBYCALLERID_${CALLERID(num)})=${AGENTID})
exten => s,n,QueueLog(NONE,NONE,Agent/${AGENTID},AGENTCALLBACKLOGIN,${CALLERID(num)}@from-internal)

..in the above, I set the global variable AGENTBYCALLERID_${CALLERID(num)} so that it is then available for the queuedial-loggedon context to check if the agent is logged on.

The Queuelog line will write out to the queue_log that the agent has logged on, which should sort out your agents being displayed on the wallboard.

Hope this helps.

-Barry

38

Running QueueMetrics / Re: Agents dissapear out of the Realtime monitor

« on: March 03, 2010, 14:29:19 »

Hi,

You need to edit your configuration.properties file and change the default.maxOngoingTalkTime setting to be:

default.maxOngoingTalkTime=0

...otherwise QM considers calls of over 2000 seconds (33 min) to perhaps be zombie and clears it.

Hope this helps.

-Barry Flanagan

39

Improving QueueMetrics / Slight bug? q_frontpage and reports

« on: March 03, 2010, 14:25:46 »

Hi,

Using QM 1.5.5

If you set a particular queue to not show on the frontpage, when running reports, the reports do not show the queue Alias, but rather the queue composition.

We use a log of subqueues, so the queues are 511.14373599, 511.1800929007 etc based on the DDI used to call the queue. We dont really want to show these on the QM home page, so set "show on front page" to No. However, this results in the 511.XXXXXXX being shown in reports as the queue name, rather than our descriptive name ,which describes the campaign that the DDI relates to.

This makes reporting far less informative / or clutters up the front page.


-Barry

40

Running QueueMetrics / Re: Question on Subqueues and agent membership

« on: February 15, 2010, 13:31:43 »

I think the only way - for the moment - is doing that manually.

OK, can you consider this a feature request then? :-)

-Barry

41

Running QueueMetrics / Re: Question on Subqueues and agent membership

« on: February 12, 2010, 16:28:56 »

Thanks for the response, but I dont think you understand the question.

My agents are logged in and QM sees them as such. However, the question is about how I can make agents appear as members of all the subqueues without manually from within QM adding them to each of the subqueues?

In Asterisk I am a member of queue 511, which on QM splits into 10 subqueues 511.1, 511.2, 511.3, etc.

In QM you will not see me as a member of any of the subqueues UNLESS I go in and manually enter myself into each subqueue definition - i.e. that in the QM database table "code_possibili" I am entered under agenti_membri for each subqueue

-Barry

42

Running QueueMetrics / Question on Subqueues and agent membership

« on: February 11, 2010, 14:18:47 »

Hi,

Just started using subqueues today, and I think it will greatly simplify my life.

I am currently using subqueues on one of my asterisk queues - 511. I have about 20 subqueues corresponding to each inbound number which goes into this queue - i.e.

511.18000101010
511.18901010101
511.14948383
....etc.

In Queuemetrics I also have a composite queue for viewing these queues set up as 511.*

I found that if I made the agents members of the 511.* queue, they did not show up as being logged in, so I place all the agents into a special queue called 511.1

In the realtime wallboard, QM correctly shows the agents as being logged in, however, the subqueues all show zero agents as being logged in, and does nopt show their pause status, etc.

How can I make it so that QM knows that this group of agents are members of all the subqueues without manually putting each agent into each subqueue? We use realtime agents, and have an interface for dynamically moving agents in and out of queues as load dictates. I do not want to have to add each agent to each subqueue just to see them as being a member of all the subqueues.

Thanks.

-Barry

43

General Asterisk configuration / Re: "Configuring URLs to be launched by the agent real-time page" with FreePBX

« on: February 10, 2010, 15:01:06 »

Hi,

Just to let you know, I have created a patch against FreePBX 2.6 which allows the setting of the URL parameter to queues form within FreePBX. I have submitted this to the FreePBX trac as a patch today (Ticket #4035 http://www.freepbx.org/trac/ticket/4035). No idea whether they will include it, but if anyone else here would like to see it then perhaps drop them a note to that effect.

With this patch you can use QM subqueues seemlessly with FreePBX. I set the optionalurl to ${FROM_DID} which creates subqueues for each incoming number pointwed at the queue.

-Barry

44

General Asterisk configuration / Subqueues - Setting URL on a Queue() in FreePBX - Patch

« on: February 10, 2010, 15:00:46 »

Hi,

Just to let you know, I have created a patch against FreePBX 2.6 which allows the setting of the URL parameter to queues form within FreePBX. I have submitted this to the FreePBX trac as a patch today (Ticket #4035 http://www.freepbx.org/trac/ticket/4035). No idea whether they will include it, but if anyone else here would like to see it then perhaps drop them a note to that effect.

With this patch you can use QM subqueues seemlessly with FreePBX. I set the optionalurl to ${FROM_DID} which creates subqueues for each incoming number pointwed at the queue.

-Barry

45

MySQL storage and Qloaderd/Uniloader / Recommended MySQL connector version?

« on: November 13, 2009, 14:01:33 »

Hi,

In the manuals it states what "It is important that you use the file named mysql-connector-java-3.0.10-stable-bin.jar"

However, in the FAQ for installing on Debian type systems is says to get version 5.0.5

What is the recommended version?

Thanks.

-Barry