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 - QueueMetrics

Pages: 1 ... 20 21 [22] 23 24 ... 202
316
OK. There may be two things that go wrong:
- the agent selects the wrong server. The agent's page only runs on one single Asterisk instance, not all of the cluster
- the log in does not match the agent code in Asterisk

BTW, when running a real-time report on the cluster, do you see those calls? and what do you see when they are answered?

317
QM is independent from Asterisk and uses it only by generating calls to perform actions. When monitoring, QM is not even aware Asterisk is running or not (but for the data).

318
This looks like an issue of QM not findingthe agent code in the records for that server. You sure they match?

319
Not sure I understand the question. Can you post a screenshot?

321
If the agent gets a call, does it display on the agent's page after you reload?

322
FYI this is bug #1850

323
Here is what I can do:  I can add this to the queue as a potential improvement. Priority won't be too high though, unless other people are interested as well.

324
It something we have to do ourselves - if you want contact the Support Line to get a customization quote.

325
Added the QM.findAudio() method and an example XML-RPC audio server (under "/servers")

326
This is because if you use e.g.  hotdesking you would not know what the agent extension is. Doing it in a limited way - like pre-loading from the agent code - it would be  trivial to do.
 

327
Thank you, Do you have a bug tracker page? So I can track the progress in this case. This feature is extremely important for us, and my demo license is about to expire.

Please ask for a renewal to our support line. We want you to be happy with the product.


328

Hi Luiz,
we don't verify your issue.
With the following settings:
   
   
Code: [Select]
# This is the default queue log file.
default.queue_log_file=cluster:*


#callFile spool dir, set to blank for no call files at all or use TCP AMI connection
callfile.dir=tcp:admin:amp111@127.0.0.1


# Cluster to poll for RT data
# list of pipe-separated members of the cluster
# if callfilesdir = "", the commands will be sent through the manager API
cluster.servers=aleph|trix

cluster.aleph.manager=tcp:admin:amp111@127.0.0.1
cluster.aleph.queuelog=sql:P001
cluster.aleph.monitored_calls=
cluster.aleph.callfilesdir=
cluster.aleph.audioRpcServer=
cluster.aleph.agentSecurityKey=

cluster.trix.manager=tcp:admin:amp111@127.0.0.1
cluster.trix.queuelog=sql:P002
cluster.trix.monitored_calls=z:/qm_streamcall/server_trix
cluster.trix.callfilesdir=
cluster.trix.audioRpcServer=
cluster.trix.agentSecurityKey=

I get the drop-down server selection. What matters here is the "cluster:*" that tells the agent page to ask for a selector.

We are marking bug #1839 as "not verified" for now, pending further input.

329
FYI bug #1776 was fixed for the next public release. Thanks for making QM better!

330
An example server was added to the Xml-Rpc browser on GitHub.

Pages: 1 ... 20 21 [22] 23 24 ... 202