Brian Parvin Posted December 24, 2018 Report Posted December 24, 2018 We are unable to get the Monitor Recipient API call to work. https://docs.2600hz.com/qubicle/doc/crossbar/qubicle_recipients/#monitor-recipient We are able to make the API call and get a successful response, but it doesn't create the session and connect the user to the call. JSON Response: { "data": { "action": "monitor" }, "timestamp": "2018-12-24T17:30:56Z", "version": "4.3.11", "node": "Ev_F_A7G-rxfdqawJdFRpg", "request_id": "dd450e260b10a8e8969123fcc1f42cb5", "status": "success", "auth_token": "removed on purpose" } None of the 'eavesdrop', 'whisper', or 'barge' options do anything though. There is a mention of "(if the current recipient has the permission enabled)" but we are not sure what permission that is referencing. We have made the user an Admin and also made sure they are in the Call Queue itself. No luck. We have similar API calls working like logging users in and out of the queue and QuickCall which I expect is similar to how the Monitor function would work by calling the recipients phone to connect to the target. Unfortunately nothing seems to happen. We can use some assistance. Thanks!
Brian Parvin Posted January 2, 2019 Author Report Posted January 2, 2019 Just wanted to follow up here and see if anybody has any suggestions or knows whether this feature is supposed to work or not.
2600Hz Employees Mark Magnusson Posted January 2, 2019 2600Hz Employees Report Posted January 2, 2019 Brian, That documentation is a bit out of date, I will update it today to reflect the current status of that functionality. The Eavesdrop / Whisper / Barge functionality is part of the upcoming Callcenter PRO. It is not enabled on the currently deployed Callcenter.
Brian Parvin Posted January 10, 2019 Author Report Posted January 10, 2019 I appreciate the response but the documentation remains the same even though it has been multiple weeks. Also why do the API calls provide a 'success' response if they aren't supposed to exist/work?
2600Hz Employees Mark Magnusson Posted January 11, 2019 2600Hz Employees Report Posted January 11, 2019 Sorry about that, was distracted last week with some other higher priority things. I will get that documentation update pushed today. The API exists because we use it internally for testing.
Recommended Posts