Hi,
We have the big troubles at the last days.
Ourself Agent Application don't receive the AgentLoggenOnEvent.

Earlier we had next sequence of XML requests, responses and events:
MonitorStart,
MonitorStartResponse,
SnapshotDevice,
SnapshotDeviceResponse,
GetAgentState,
GetAgentStateResponse,
SetAgentState,
SetAgentStateResponse
and AgentLoggedOnEvent!

And now (nothing has changed):
MonitorStart,
MonitorStartResponse,
SnapshotDevice,
SnapshotDeviceResponse,
GetAgentState,
GetAgentStateResponse,
SetAgentState,
CSTAErrorCode. Why???
That's all.
And AgentLoggedOnEvent is absent.

Our 300++ operators in the call center can not work well.

Can you halp me?
Where should I look on the AES Server to find the cause?

Thanks

You really help me, Martin.
Thank you.

Is <ConsultationCall> the initiating of the new call?
Can you write full list of initiating requests?

Hi,
Our Win32 Application uses the sockets for direct connect to the AES Server.
When Application receives the new Call, It tries writing the UUI to this Call.

For example (CallID is 5555 and UUI is 1234567890) when we send the request:
<?xml version="1.0" encoding="utf-8"?>
<SendUserInformation xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<existingCall>
<callID>5555</callID>
<deviceID typeOfNumber="other">123123</deviceID>
</existingCall>
<userData>1234567890</userData>
</SendUserInformation>

We receive answer from the server:
<?xml version="1.0"?>
<AXMLSErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<axmlsOperation>UnSupported</axmlsOperation>
</AXMLSErrorCode>

and UUI not saved in the Call.

How we can write our UUI to the Call?