CISCO JTAPI EXCEPTION

[kbreboot]

[b]extracted is the logs from the URS.. earlier as shown we had an EventError - Destination invalid and the call is deleted by the strategy.. [/b]

12:37:03.394_T_E_ [14:0c] EventError is received for tserver T-Server_OSR_CCM[OSR_CCM] - destination invalid
12:37:03.394_A_E_006f01a7ae7f2713 [14:32] <-----------ERROR
    _T_W_006f01a7ae7f2713 [0E:0f] [b]emergency: delete call due to this error[/b]
    _I_I_006f01a7ae7f2713 [01:08] call deleting truly
CALL (006f01a7ae7f2713) HISTORY ( Error Default ):
[b]
Is there a way when the event in the log below occurs that the same emergency can be used to delete the call for some reason the guys that put in the strategy tries to route the call as per normal when it does not exist. The call is now a ghost call and banks up the queue it is on[/b]
12:42:21.066_T_E_ [14:0c] EventError is received for tserver T-Server_OSR_CCM[OSR_CCM] - [b]CISCO JTAPI EXCEPTION(UNSPECIFIED) in 'redirect'[/b]. Type=InvalidStateException, Object = [1312/(P1-GenesysJTAPI) GCID=(2,1379118)->ACTIVE]->FAILED(CONNECTION_OBJECT), State = 53. Did not meet pre-conditions.
12:42:21.066_A_E_006f01a7ae7f26ec [14:32] <-----------ERROR
12:42:21.066_M_I_006f01a7ae7f26ec [17:11] VQ(00e8c9a0) first available call: 006f01a7ae7f26ec, reason=strategy
12:42:21.066_M_I_006f01a7ae7f26ec [17:11] VQ(00ea59c0) first available call: 006f01a7ae7f26ec, reason=strategy
12:42:21.066_M_I_006f01a7ae7f26ec [17:11] VQ(00eca220) first available call: 006f01a7ae7f26ec, reason=strategy
    _T_W_006f01a7ae7f26ec [0E:0f] [b]emergency: continue strategy on this error[/b]

[Fra]

?
'Emergency' message is a URS internal logging, it's not a strategy function.
I'd try to understand the cause of the issue you are facing instead of trying to "delete" the ghost calls.

Fra

[kbreboot]

we have just figured out the cause of our problems. It is correct emergency is only a URS log - we have found that a default settings that handles this situation is to delete the call but for some reason they changed it to Strategy_OK

We've since changed it, but i tell you it has caused as a lot of grief with the customers.