Hi Team,

I'm trying to build a softphone using Avaya DMCC SDK for .net. When i try to set the agent state using OnSetAgentState. I get the below error.

<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><operation>invalidAgentState</operation></CSTAErrorCode>

Below is my code.

ThirdPartyCallController.SetAgentStateParameters objSetAgentStateParameters = new ThirdPartyCallController.SetAgentStateParameters();
objSetAgentStateParameters.AgentId = "1031002";
objSetAgentStateParameters.Device = "61801:swlink1:0.0.0.0:0";
objSetAgentStateParameters.EnablePending = false;
objSetAgentStateParameters.Group = "";
objSetAgentStateParameters.Password = "123456";
objSetAgentStateParameters.ReasonCode = 4;
objSetAgentStateParameters.RequestedAgentState = ThirdPartyCallController.RequestedAgentState.AM_LOG_IN;

Is there something i'm missing?

Regards,

1) the CSTA error codes by themselves are not very helpful other than to say what you asked for did not work. A DMCC trace usually provides more helpful information although not always.
2) square one is always to try what you are trying through CTI via the phone UI. Can you login the agent using feature access codes or buttons from the phone's UI to the agent ID you are trying to login with?
3) I suspect but have not checked that AgentID is defined as a deviceID, and thus needs to be in the format of a third party deviceID. e.g. "1031002:swlink1:0.0.0.0:0"
4) I don't think reason code is a necessary value for login, but it shouldn't hurt either.

o Make sure that agent "1031002" is not already logged in. You can see what agents are logged in using the SAT command "list agent".

o Make sure that the station 61801 is logged in (if using a DMCC station, make sure you have performed a Register Terminal request)

o Make sure that no other agent is logged in at 61801.

Martin

Thanks for your reply, really appreciate it.

I have checked agent id was not logged into any other extension and no other agent was logged into same extension.

Is there any other was i can expedite this issue?

Regards,

DevConnect provides consulting services for fee. The forums are best effort and notintended to be a vehicle for troubleshooting issues. If you would like to consider a Support enabled membership Please review the materials here:
https://www.devconnectprogram.com/site/global/program_benefits/membership_overview/index.gsp#tabs-1


Using the DMCC Dashboard and my lab setup I captured the following exchange between a DMCC application and AE Services.
Please enable DMCC FINEST Tracing through the AES Web OA&M interface, run your test, and check the XML message AES receives against what I captured from what the DMCC Dashboard sent.

---------------------
Outgoing XML 60
<?xml version="1.0" encoding="utf-8"?>
<SetAgentState xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<device typeOfNumber="other" mediaClass="notKnown">32100:S8300:135.9.231.41:0</device>
<requestedAgentState>loggedOn</requestedAgentState>
<agentID>50001</agentID>
<password>3530303031</password>
<extensions>
<privateData>
<private>
<SetAgentStatePrivateData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<workMode>autoIn</workMode>
</SetAgentStatePrivateData>
</private>
</privateData>
</extensions>
</SetAgentState>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<DisplayUpdatedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>9</monitorCrossRefID>
<device>
<deviceIdentifier typeOfNumber="other" mediaClass="voice" bitRate="constant">32100:S8300:135.9.231.41:0</deviceIdentifier>
</device>
<logicalRows>1</logicalRows>
<logicalColumns>48</logicalColumns>
<contentsOfDisplay>2 2000* </contentsOfDisplay>
</DisplayUpdatedEvent>
-----------------------
Incoming XML 60
<?xml version="1.0" encoding="UTF-8"?>
<SetAgentStateResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<extensions>
<privateData>
<private>
<SetAgentStateResponsePrivateData xmlns:ns1="http://www.avaya.com/csta" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="SetAgentStateResponsePrivateData">
<isPending>false</isPending>
</SetAgentStateResponsePrivateData>
</private>
</privateData>
</extensions>
</SetAgentStateResponse>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<DisplayUpdatedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>9</monitorCrossRefID>
<device>
<deviceIdentifier typeOfNumber="other" mediaClass="voice" bitRate="constant">32100:S8300:135.9.231.41:0</deviceIdentifier>
</device>
<logicalRows>1</logicalRows>
<logicalColumns>48</logicalColumns>
<contentsOfDisplay>
</contentsOfDisplay>
</DisplayUpdatedEvent>

It may be that the existing agent password is not what you think it is. I suggest that you edit the agent's configuration on Communication Manager to set the password to "123456" so as to be sure.

Martin