Single step conferencing not working with Aspect recording on outbound calls. Calls are being recorded in the connected state rather than the start state
MST and AES logs show the following from the CM end. Tests conducted within the working scenario and working calls show that the call was in a ‘TALK_SUP’ state which is valid and SSC will work.
Within the non working scenario, the
AES logs show the following errors 01/21/2016 13:03:28.390:TSAPI:LinkThread01: cause_value CS0/98
01/21/2016 13:03:28.391:TSAPI:LinkThread01: error(INVALID_OBJECT_STATE)(22)
These are some explanations of that error from TSAPI programmers guide:
INVALID_OBJECT_STATE (22) – The otherCall is not in the alerting, connected, held, or bridged state.
INVALID_OBJECT_STATE (22) The connections specified in the request are not in valid states for the operation to take place. For example, it does not have one call active and one call in the held state as required.
INVALID_OBJECT_STATE (22) (CS0/98) Request (message) is incompatible with the call state.
INVALID_OBJECT_STATE (22) (CS0/98) The request was attempted before the call was answered.Customer requires CM to begin recording in the start state rather the connected stateCall recording takes place utilizing AES dmcc and tspai licensesThis was a configuration issue. Customer was required by the government to record all their calls including the calls that do not get in a connected state and do not get a voice path--which includes ring no answer , 3 tone, calls to vm.
