QueueMetrics Call Monitoring Problem

[runderwood]

Hello,

Not sure if someone already posted bout this or not, but I'll like to share this problem, which I solved with a workaround(not nice but works) so it may be solved in the next release of vicidial.
Back in October 2013 I upgraded a Vicibox Cluster from 4 to 5, after several issues we sorted out the cluster started to work very stable, we have a QM integration for reporting and QA, after we upgraded to Vicibox 5 with vicidial VERSION: 2.8-415a BUILD: 131007-1234 our supervisors and QA agents started to complain that they weren't longer enable to listen to the calls from QM, so I started to investigate on it and indeed when on QM in the RealTime Report I clicked on

Monitor now

I got the pop-up window, I typed the extension on which I wanted to listen the call and clicked on Submit and no call was send to my exten but I got this message:

ERROR: Login incorrect, please try again: |361|m1291555140003480184|BAD|

I had to left that unsolved due some other projects, but I started to work on this today and I found the following, when trying to monitor the calls from QM using XML_RPC this script its called QM_live_monitor.php and I found that the API its not being called correctly, this is the url for API generated by the script: http://xx.xx.xx.xx/vicidial/non_agent_api.php?source=queuemetrics&function=blind_monitor&user=361&pass=m1291555140003480184&phone_login=1097&session_id=8600052&server_ip=xx.xx.xx.xx&stage=MONITOR (the IPs are masked for security) and I realized that the "pass" value its not really a password but the call id and that's why we were getting the Login incorrect message due an incorrect call to the API function, so what was my fix well pretty simple I replaced the

user=&pass=

with some hard coded values

user=dummyuser&pass=dummypass

and that user has the enable the API usage but restricted to only that, after that change the Monitoring from QM started to work again, for some reason this used to work on Vicidial 2.7 and below but not on the new versions, maybe someone can look into this and generate patch to fix the issue.

Regards,

[williamconley]

This would be best posted to the Vicidial Issue Tracker as a DIFF against the latest SVN code (ie: show The Vicidial Group exactly how to fix the problem in the Vicidial code ...). Then post a link to that back here for Matt to see. If your solution will resolve the issue and you make it "simple" in this fashion, your next upgrade of Vicidial could include your fix.

[mflorell]

We have clients using QM and the most recent svn/trunk version of Vicidial without issue, so I'm not sure what this issue on your system would be caused by. I'm sure it could be an issue with the code and some specific configuration, but it doesn't appear to be a clear bug that is on all systems in all cases.