Environment: Avaya CM 3.1, AES 3.1.2 and TSAPI application.
Using cstaQueryAgentState on a extension at the end of a call returns agentState AG_READY and private param talkState as TS_ON_CALL even when the extension is actually on Auto-in and in Idle mode. Strange enough a cstaQueryAgentState for the same extension from another application (TSAPI exerciser) returns agentState AG_READY and talkState as TS_IDLE. My application re-queries the agent state for up to 10 seconds and the talkState is still TS_ON_CALL. Reopening the TSAPI stream seems to clear the agent state. Also, it only happens sporadically during the day, but when it happens it happens for most of the extensions in the call centre. Any idea what could cause this?
Thank you.
Using cstaQueryAgentState on a extension at the end of a call returns agentState AG_READY and private param talkState as TS_ON_CALL even when the extension is actually on Auto-in and in Idle mode. Strange enough a cstaQueryAgentState for the same extension from another application (TSAPI exerciser) returns agentState AG_READY and talkState as TS_IDLE. My application re-queries the agent state for up to 10 seconds and the talkState is still TS_ON_CALL. Reopening the TSAPI stream seems to clear the agent state. Also, it only happens sporadically during the day, but when it happens it happens for most of the extensions in the call centre. Any idea what could cause this?
Thank you.
