Yes, I'm definitely waiting for the call to clear. I'm using snapshotservice.snapshotDevice to get a list of all connections for my deviceId, the previously existing consultationCall isn't even in this list, just the original call that I'm expecting. With the appropriate HOLD and CONNECTED states as expected.
Do you guys have any ideas for troubleshooting the state of this call? I logged into AES and found some entries in the logs to verify my ResourceBusyException, but it's not enough information.
<135>Jan 9 21:00:17 clt-a7-aes-01 DmccMain[7398] -05:00 2018 923 1 com.avaya.aes | :CstaUnMarshalerNode-4: com.avaya.api.cmapi FINE - invokeID= 26 Routing request=session[session 5F97E82643FBB0642B84860CB6553FE3-150] ch.ecma.csta.binding.SnapshotDevice@40ffdb
<135>Jan 9 21:00:17 clt-a7-aes-01 DmccMain[7398] -05:00 2018 947 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 26 Sent response session[session 5F97E82643FBB0642B84860CB6553FE3-150] ch.ecma.csta.binding.SnapshotDeviceResponse@8b5004
<135>Jan 9 21:00:17 clt-a7-aes-01 DmccMain[7398] -05:00 2018 955 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.cmapi FINE - invokeID= 27 Routing request=session[session 5F97E82643FBB0642B84860CB6553FE3-150] ch.ecma.csta.binding.RetrieveCall@16e7783
<132>Jan 9 21:00:18 clt-a7-aes-01 DmccMain[7398] -05:00 2018 047 1 com.avaya.aes | :DistributeCSTAEvent: com.avaya.async.impl.AsyncCallbackImpl WARNING - A service method threw an Exception when invoked!#012ServiceMethod: com.avaya.platform.broker.impl.AsyncServiceMethodImpl@b07ac6[com.avaya.cmapi.extsvc.CallControlServicesImpl@1213671, public void com.avaya.cmapi.extsvc.CallControlServicesImpl.retrieveCall(ch.ecma.csta.binding.RetrieveCall,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.CstaException]#012Exception: ch.ecma.csta.errors.ResourceBusyException: Device was not available for this operation: error code 33#012Request: session[session 5F97E82643FBB0642B84860CB6553FE3-150] ch.ecma.csta.binding.RetrieveCall@16e7783
<135>Jan 9 21:00:18 clt-a7-aes-01 DmccMain[7398] -05:00 2018 048 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 27 Sent response ch.ecma.csta.errors.ResourceBusyException: Device was not available for this operation: error code 33
