Recent Posts

Pages: 1 ... 8 9 [10]
91
We installed the brand NEW QM 17.06. on our server that is running in Cluster mode.

The QM Cluster Agent page with SIP/XXXX vs Local/XXXX works great in Logging on/off in/out of a queue now.  ;D ;D ;D

In QM main/home web page we went to Explore System Parameters. We changed it to look like this:

DirectAMI
 
The way an agent extension channel is supposed to be: Local/${num}@from-queue/n
Instead of this.
The way an agent extension channel is supposed to be: SIP/${num} ;D ;D ;D ;D

But the pause/unpause is NOT working any longer. We can CLI the agent to pause/unpause like this: asterisk -rx 'queue pause member Local/XXXX@from-queue/n' But the QM Cluster agent web page is still using: asterisk -rx 'queue pause member SIP/XXXX we are guessing.  :(

/rk

 
92
Running QueueMetrics / Re: QueueMetrics Cluster, Agent WEB Page Source file
« Last post by corkuck on June 28, 2017, 17:34:29 »
Thank you again for answering.

We are upgrading to Ver. 17.06

Before this upgrading action. We were looking to see where one could see, learn and possibly change this QM Cluster AMI command file directly, if one desired to?

But don't know where it might be located at.

/rk

93
Running QueueMetrics / Re: QueueMetrics Cluster, Agent WEB Page Source file
« Last post by mirkox on June 28, 2017, 16:16:57 »
Hi, in general when an agent logs in the queues in cluster mode they also have to decide in which server to connect; the AMI commands will be sent directly form QM to that specific server. Not sure I have responded completely tour question though, in case let me know.

Mirko
94
QueueMetrics news / QueueMetrics 17.06 Wallboard Management Tutorial
« Last post by Mausabot on June 27, 2017, 09:59:48 »
With QueueMetrics suite for Asterisk 17.06 you can create custom wallboards dragging and dropping graphical components, changing colors, size and adding custom alarms.
Wallboards are made up of multiple views that rotate periodically and run in kiosk mode.

Learn how to quickly create effective and powerful wallboards for your daily call center management.

Read the tutorial https://www.queuemetrics.com/blog/2017/06/26/Wallboard-Tutorial/?lid=U016
95
Running QueueMetrics / QueueMetrics Cluster, Agent WEB Page Source file
« Last post by corkuck on June 26, 2017, 15:09:23 »
QueueMetrics Cluster, Agent WEB Page Source file

Here is the situation:

We/you have a single dedicated QueueMetrics server in QM Cluster Mode. Itís running nothing but Linux and QueueMetrics (QM) - 16.10.13
Then you have several other remote servers (sites) running Linux, 1.8 Asterisk, FreePBX and QM - 12.5.1 on each of them.

Here is the Question(s):

If you go into the QM Cluster server. Then login to the ďAgentís Web PageĒ and Log an agent into a Queue, where is QM running the AMI command from?
Is the AMI commands to accomplish the Logging on/out/Pause/Unpause coming directly from the QM Cluster?
Or is QM Cluster Server, telling the remote QM Server not running Cluster, to do the AMI commands with the /etc/asterisk/extensions_queuemetrics.conf file?
Iím trying to figure which file the QM Cluster is using to send the AMI Logging on/out/Pause/Unpause from.

Here is the problem:

We are having a problem when using QM Cluster Software logging on Agents as SIP/XXXX into a Queue in the remote server. Instead of logging on agent(s) using Local/XXXX this remote servers Queue. Changing this SIP to Local in the QM Cluster Web Agent page (where ever itís doing the AMI from) should make the Logon/off/Pause/Unpause work. This would make it work when we have a SIP phone not being seen by the system, plugged into the network or registered/attached. Along with the, Follow Me and Dial modification. All of this for call out on the PSTN line(s) for remote queue agents, on a SIP configured extension to work properly.

Here is what we know, think and wish for:

QM recently released and said:
"install of QM using the latest 17.06.1. After this, check for DirectAMI options and change from SIP/${num} to Local/${num}@from-internal/n"

So QM being the great company that they are, is seeing the need and have a fixed for this, as far as we know. We have not installed 17.06.1 yet.

We feel, see and have found that from all indications thus far, that the QM Cluster Server is sending out these AMI commands directly to the remote QM server to Logon/off/pause/unpause agents.

So where is this QM Cluster file? Where does the AMI commands originate from? So one could see, learn and possibly change this file if one desired to?

Thank you QueueMetrics for a great product.

/rk
96
Hi there, actually if you are runnning the latest version of QM you should check out the DirectAMI option (12.5.3: http://manuals.loway.ch/QM_UserManual-chunked/ch12.html#_pbx_actions )
97
We don't know, but are thinking that QM Cluster agent web page, is doing the AMI "add agent" using SIP/XXXX not Local/XXXX directly. Not the remote 1.8 Asterisk, FreePBX, QM box, using the extensions_queuemetrics.conf file to "add agent".

Especially now after being told to try the NEW QM install using ver 17.06.1. It has a SIP vs Local option built in it? Yaaaaaaa.  ;)

But hey what do we know? But we sure love this product, QueueMetrics. We wished it worked with Avaya.

Thought(s), Correction(s), Idea(s) and Direction(s) are always invited.

/rk
98
QueueMetrics may have the solution:

"install of QM using the latest 17.06.1. After this, check for DirectAMI options and change from SIP/${num} to Local/${num}@from-internal/n"

We will try this next week. Thank you QueueMetrics for keeping this product 100%. You have always done a great job for us.  ;)

Thoughts, Corrections, Ideas and Directions are always invited.

/rk


 
99
Thanks again ďmirkoxĒ,

You are correct the ď#include extensions_queuemetrics.confĒ is found I the /etc/asterisk/extensions_custom.conf. Not the /etc/asterisk/extensions_queuemetrics.conf as defined in the file at the top.

So thatís how itís all working.  :) Thank you again for answering back.

Now we need to see how to change this extensions_queuemetrics.conf file using Local not SIP. I will start this now.

When we looked at this before, it looked as if the:

; extension 25: agent addqueuemember (for asterisk v1.4+)
exten => 25,1,Answer
exten => 25,2,NoOp( "QM: AddQueueMember (asterisk v1.4+) Agent/${AGENTCODE} on queue ${QUEUENAME} made by '${QM_LOGIN}' with prioritylabel '${QM_AGENT_PRIOLBL}' and prioritynum '${QM_AGENT_PRIONUM}'" )
exten => 25,3,AddQueueMember(${QUEUENAME},Local/${AGENTCODE}@from-internal)
exten => 25,4,Hangup

Is doing what we would like see. Or a good place to start seeing what the file is doing for some file modification to see what happens as changes are made.

Someone has, had to have done these changes already in the past, we would think.

But the plan is to post it once we get it working for others to use if and when needed.

Thoughts, Corrections, Ideas and Directions are always invited.

Thanks again.

/rk




100
Hi, in freepbx that's normally included from extensions_custom.conf (that file won't be rewritten with freepbx updates).

BTW you can verify that the dialplan is correctly included in Asterisk with:

asterisk -rx "dialplan show queuemetrics"

I'm sure you have it and that it is working because otherwise it's impossible for QM to perform actions on the PBX

Mirko
Pages: 1 ... 8 9 [10]