Message |
[+]
DMCC APIs
» Selective Listening Hold, 29/06/2020 17:48:24
» Go to message
|
|
We are trying to use Selective Listening Hold using TSAPI. We acquired the advanced license as well.
When we call the API, we are getting OUTSTANDING_REQUEST_LIMIT_EXCEEDED.
The call is initially dialed and conferenced using CVLAN (due to limitation of existing application), and then we are using Selective Listening Hold using TSAPI.
Before we acquired the advanced license, we tested with ClearConnection and it worked when the call was initially dialed and conferenced using CVLAN and clear connection using TSAPI.
Is there any reason why ClearConnection is working while Selective Listening Hold is not? Also is there a way to fix OUTSTANDING_REQUEST_LIMIT_EXCEEDED error?
|
|
[+]
DMCC APIs
» OUTSTANDING_REQUEST_LIMIT_EXCEEDED Error 44 when calling ClearConnection TSAPI, 29/06/2020 15:52:58
» Go to message
|
|
We got the TSAPI advanced license, and now we are testing SLH, and we are getting OUTSTANDING_REQUEST_LIMIT_EXCEEDED.
The call is initiated from CVLAN, and we are trying to do SLH on the station.
ClearConnection worked when used on the station even when the call is initiated by CVLAN, so we were hoping SLH would work, but apparently not.
We are guessing it is because CVLAN is taking control of the call, but just want to confirm if that is correct, because we were able to use ClearConnection.
|
|
[+]
DMCC APIs
» OUTSTANDING_REQUEST_LIMIT_EXCEEDED Error 44 when calling ClearConnection TSAPI, 05/06/2020 10:39:32
» Go to message
|
|
Thanks a lot Martin and John for the insights. I will look into points you provided.
But there is one thing I forgot to mention. We are actually able to clear the connection of the station (the agent), which has devIDType STATIC_ID and initiator of the conference call, even when the conference call was created by the CTI application we have. And we are failing to clear the connection for other devices that have devIDType DYNAMIC_ID. So it seems like the connection of the station can be cleared whether there is a lock on a call or not.
I tried clearing the connection on the device with devIDType DYNAMIC_ID repeately as John suggested, and was rejected constantly.
Also, actually our final goal is to put SLH on one of the calls, not clearing the connection. We were testing the flow with Clear Connection while we wait for TSAPI advanced license. I am now wondering if SLH have the same behavior, if it will work on the station only just like Clear Connection.
Thanks a lot,
|
|
[+]
DMCC APIs
» OUTSTANDING_REQUEST_LIMIT_EXCEEDED Error 44 when calling ClearConnection TSAPI, 05/06/2020 09:41:38
» Go to message
|
|
We have one CTI application which connects to AES and creates a conference call (I think it is using CVLAN but not completely sure), and separately we are using TSAPI, and calling ClearConnection to disconnect one of the calls in the conference call.
We were successful to do it when the conference call was created by TSAPI, but getting OUTSTANDING_REQUEST_LIMIT_EXCEEDED error when the conference call was created by the CTI application.
Just wondering if this is an existing behavior and if there is a way to work around this.
Thanks,
|
|