QueueMetrics forum
QueueMetrics => Scripting QueueMetrics => Topic started by: emilec on March 30, 2012, 14:39:53
-
I have found that if a call passes through more than one queue you will end up with multiple call recordings with the same Asterisk Call ID. For example:
q84-20120321-083849-1332311914.682792.WAV
q91-20120321-084120-1332311914.682792.WAV
When I then look at the call detail and click on the URL I get the following:
http://172.16.1.1/monitor/2012/03/21/q84-20120321-083849-1332311914.682792.WAV%20/var/www/html/monitor/2012/03/21/q91-20120321-084120-1332311914.682792.WAV
Is there a way to return 2 URLs instead? i.e.
http://172.16.1.1/monitor/2012/03/21/q84-20120321-083849-1332311914.682792.WAV
http://172.16.1.1/monitor/2012/03/21/q91-20120321-084120-1332311914.682792.WAV
-
Does this only happen through the XML-RPC call? or also if you click on the call details pop-up?
-
That's what I see in the call details pop up.
-
Any suggestions yet?
You should be able to reproduce this quite easily by copying an existing call to a new name with the same Call ID in it.
-
It should already return two urls's. I don't understand if this only happens on XMl-RPC or on the GUi as well.
-
Let me put this another way.
We have implemented the XML-RPC skeleton provided by QueueMetrics to return call recording URLs from another server. We have run into a situation where there are multiple recordings for a single unique ID (call has been transfered). I do not see how to return more than one URL in the XML reply.
Is there a way to return more than one URL in an XML-RPC reply?
Tony
-
Hi
Any feedback?
-
The RPC interface for QM.findAudio() already allows multiple file names to be returned in the same data block; I am opening up a bug for this issue.
-
We track this as issue #1623
-
Thanks!
-
Any update on fixing this bug?
-
It is scheduled for the next release
-
This issue was fixed in upcoming version 13.x.
If you'd like to test it please contact us for a beta.
-
An example server was added to the Xml-Rpc browser on GitHub.