All,
17+ year developer here of multiple languages and former CT/TSAPI/CVLAN and Cisco ICM developer (7 years)
Attempting to consume the Avaya POM API set via C# and I am RANDOMLY getting 9002 errors when calling AGTStateChange.
The 9002 issue happens from time-to-time and I am unable to pinpoint the exact cause or process that triggers it.
9002 = "Agent not registered" per the API docs.
When this happens I can SEE the agent logged into POM via the GUI Agent State interface. (so how can agent NOT be registered when I can see it logged in POM?)
Here are other factors to consider:
1) Agent IS logged into PBX via phone and is auto-in when this occurs.
2) POM API Client has been purposely killed and restarted as part of unit testing.
3) AGTLogon command IS using the FORCE param.
4) Some other POM developers told me to leverage the timeout settings of AGTStateChange - But that param doesn't exist. There is also no timeout setting under AGTLogon as a param.
At the time this issue occurs... I can CLEARLY see that my m_POMAgent object IS valid and I can see my POMSocketInfo defined w/ proper IP address and ports.
Also note that the command AGTStateChange IS received by the API w/ an iResult of 0 (success) - And the 9002 issue I am seeing is coming back as part of the AGTStateChangeRESP event.
Here is a snippet of my dump of data:
{"m_POMHandler":null,"myAgentFactory":null,"myAgent":null,"agentID":null,"extensionID":null,"bResult":false,
"bCanDispose":false,"bAllowFreeForm":false,"iResult":9002,"iGracePeriodMinutes":0,"eEventId":64,"sMethodName":
"AGTStateChangeRESP","sResult":null,"sErrorMsg":null,"sLocalizedErrorMsg":null,"sSessionID":null,"sDueTime":null,
"sZoneName":null,"sRequestingAgentID":null,"sRequestingAgent":null,"sRequestingCampaign":null,"sDefaultExpiryTime":null,
"aZoneList":null,"aAgentNotes":null,"timezones":null,"aPOMCallbackDest":null,"aPOMCallbackType":null,"aPOMCompletionCode":null,
"aPOMDestination":null,"aPOMDestinationType":null,"aPOMAttribute":null,"oPOMWrapupDetails":null,"oPOMNailupStatus":0,
"oPOMAgentState":1,"oPOMContact":null,"oPOMErrorInfo":null,"oPOMCallState":0,"oPOMCapabilities":null,"oPOMDialFailReason":0,
"oPOMAttribute":null,"oPOMCallbackType":0,"oPOMDestinationType":0,"oPOMCustomerDetails":null,"dZoneIPMap":null}] - Caller setAgentStatus,
Questions for the group
A - Is there a way to enable DETAILED debugging and/or trace EACH step of the command AGTStateChange?
B - Is this a common issue with KILLING a API client and attempting to log back in using AGTLogon w/ FORCE enabled?
C - Overall - Consuming this API appears to be a little flaky to me... Anyone else have a similar experience?
D - If you have tribal knowledge of this 9002 issue... PLEASE PLEASE PLEASE share.
