Hi,

We have an implementation where it was reported a specific situation when trying to login agents. It happens just in a few cases. The most of them complete successfully.

My question is:
What could be the causes which prevent to addAgent?
I think one would be that the agent had a call (active line) but is the only that I know.

Thanks in advance.

Felix Ayala

Here is my code to login:

lucentAgent = (LucentAgent) agentTerminal.addAgent(agentAddress, acdAddress, Agent.LOG_IN,
agente.getId(), agente.getPwd());

And this is my log file:

2012-08-29 19:12:35,423 [http-8080-3] ERROR AgentAdmin - setAgentState failure
com.avaya.jtapi.tsapi.TsapiPlatformException: setAgentState failure
   at com.avaya.jtapi.tsapi.impl.core.TSDevice.setTSAgent(TSDevice.java:1525)
   at com.avaya.jtapi.tsapi.impl.core.TSDevice.addTSAgent(TSDevice.java:1648)
   at com.avaya.jtapi.tsapi.impl.TsapiTerminal.addAgent(TsapiTerminal.java:812)
   at mx.com.siditel.cti.AgentAdmin.agentLogin(AgentAdmin.java:1012)
   at mx.com.siditel.cti.CtiManager.agentLogin(CtiManager.java:881)
   at com.mx.siditel.web.ws.AdminServices.asociaAgente(AdminServices.java:383)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
   at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
   at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
   at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
   at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
   at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
   at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
   at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)

Hi Felix,

Here ae some reasons, whipped from the Agent View sample application:

1. Agent is already Logged In
2. Call is already in progress at the station
3. Station is out of Service
4. Agent Password is incorrect
5. Agent ID entered is incorrect

You should be able to get better information from the TSAPI traces on the AE Services. Have a look at the FAQ 'What is the procedure for enabling and accessing the AE Services logs for TSAPI (trace, tracing, g3trace, csta_trace)?'. The g3 traces will show what the Communication Manager is saying.

Martin