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 ... 143 144 [145] 146 147 ... 202
2161
Scripting QueueMetrics / Re: Wallboard Example script
« on: January 14, 2009, 15:28:42 »
Have you enabled the "robots" user?
Are you sure you are pointing to the correct QM instance?

2162
I came across this JavaScript library: http://code.google.com/p/json-xml-rpc/

I was able to port the sample script to it, it's pretty easy.

Code: [Select]
<html>
<head>
<title>javascript_client.html</title>
<script src="rpc.js"></script>
</head>
<body>

<h1>QueueMetrics JavaScript XML-RPC example </h1>
<hr>

<script>
var server = "/DAILY/xmlrpc.do";

function run() {

        try {
             var service = new rpc.ServiceProxy( server, {
                        asynchronous:false,
                        protocol: "XML-RPC",
                        methods: ["QM.stats"]
  } );

res = service.QM.stats( "q1", "robot", "robot","", "",
"2005-10-10.10:23:12", "2009-10-10.10:23:10","",
[ "KoDO.DiscCauses", "CallDistrDO.AnsDistrPerDay" ]
);

                document.getElementById("RESULT").innerHTML = plotBlocks(res);

        } catch(e) {
                alert("Error raised: " + e);
        }

}


function plotBlocks( hmBlocks ) {

        s = "";

        for (var i in hmBlocks) {
                s += "<h2>Block: " + i + "</h2>";
                s += plotBlock( hmBlocks[i] );
        }

        return s;
}

function plotBlock( arBlock ) {
        s = "";
        for ( r =0; r < arBlock.length; r++ ) {
                s += "<tr>";
                for ( c = 0; c < arBlock[r].length; c++ ) {
                        s += "<td>" + arBlock[r][c] + "</td>";
                }
                s += "</tr>";
        }
        return "<table border=1>"  + s + "</table>";
}


</script>

<input type="button" value="Click me!" onclick="run();" >

<div id="RESULT"></div>

</body>
</html>



This example requires the file rpc.js that comes from the client side
of the JSON-XML-RPC JavaScript library (see here: http://code.google.com/p/json-xml-rpc/ ).

Please note that the following file should be served on the same webserver as the QueueMetrics app it's going to access, or it will be denied access by the browser.

Please edit the file to set up access preferences.

We are going to include this example in QM as well.

2163
Scripting QueueMetrics / Re: Question on RealtimeDO.RTRiassunto
« on: January 14, 2009, 11:48:07 »
You should be doing a separate query for each queue. It's not 100% sure that all reports are simply additive, meaning that it's not always true that f(A+B) = f(A) + f(B).

2164
Running QueueMetrics / Re: Generate reports and send them by email
« on: January 14, 2009, 11:42:28 »
You should really enclose the URl within quotes "http://..." otherwise the shell with split at the & signs.....

2165
As in next, non beta. If not 1.5.1, surely 1.5.2.

2166
Improving QueueMetrics / Re: Option to "show" days with 0 calls
« on: January 13, 2009, 16:30:43 »
I am glad to tell you that issue #84 has been fixed and added to the upcoming release 1.5.1.

Thanks for making QM better! ;D

2167
The NFS mount was used when qloaderd was not present yet, but now it's outdated.

2168
In theory, Local/xxx@yyy/n should be passthrough.... but if this didi fix your problems, it's very nice you poisted it so other users can benefit. Thanks!



2169
This is so because on many CCs a call that lasts one hour is impossibly long, so QM thinks it's a mistake.
This can of course be set. see http://queuemetrics.com/faq.jsp#faq-030-disappear

2170
QueueMetrics installation / Re: Pause Status not changing in reports
« on: January 12, 2009, 10:04:25 »
I think this might be a bug - what usually happens is that the LAST code is set (so you can change it e.g. if you select a wrong one).
 
We are tracking this as #603.

2171
General Asterisk configuration / Device state "Not in use"
« on: January 12, 2009, 10:01:17 »
See this thread: http://lists.digium.com/pipermail/asterisk-users/2009-January/224452.html

About the "dreaded" message "Not in use":
WARNING[1863]: app_queue.c:3136 try_calling: The device state of this
queue member, Agent/136, is still 'Not in Use' when it probably should
not be! Please check UPGRADE.txt for correct configuration settings.)



2172
This is a known issue and we are working ion it for the next major release. Our internal tracking code is #498.

2173
The problem her is that in order to have agents appearing, you should really use agents with a logon/logoff. This is better because:
- you get a complete trail of who was working when
- you get pause information
- the system will not try to dial an unmanned extension

About showing names, this can be done: just enter e.g. SIP/1234 as the "Agent code" and John Doe as the description.


2174
You should really see the clustering guide: http://queuemetrics.com/download/QM_mysql_cluster_100.pdf

Basically you use a daemon that's called qloaderd that will upolad data to QM, where each box has its own partition.

In order to run reports on it, you will need a clustering licence - please contact support to be sent a clustering demo key (unless you alread have one).


2175
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: January 09, 2009, 09:58:09 »
That's good.  ;)

Pages: 1 ... 143 144 [145] 146 147 ... 202