Galera, alguém daqui usa JTAPI, não estou conseguindo implementar os eventos ready e notReady
Segundo a documentação:
Interface javax.telephony.callcenter.Agent
public interface Agent
Introduction
An Agent represents an individual capable of handling telephone calls for a particular Address. For example, an agent may be a customer service
representative in a call center environment. An Agent is associated with a particular AgentTerminal, which represents the particular Terminal
endpoint associated with the Agent. Each Agent is also logged into a particular ACDAddress. The act of logging into an address announces the
availability of the Agent to handle Calls which come into that ACDAddress. Distinct Agents are used to represent the same individual who is logged
into multiple ACDAddresses from the same AgentTerminal
Adding and Removing Agents
Agents are created and added to a particular ACDAddress via the AgentTerminal.addAgent() method. This method creates a new Agent
associated with the AgentTerminal and the ACDAddress given as an argument.
Agents are removed from an AgentTerminal via the AgentTerminal.removeAgent() method. This method also removes the Agent from its
ACDAddress. The Agent is no longer available to receive telephone calls coming into its ACDAddress.
The Agent's State
The state of the Agent describes whether it is currently logged into an ACDAddress or its current ability to handle telephone calls. Applications obtain
the state of the Agent via the Agent.getState() method. Applications may also directly change the state of the Agent via the
Agent.setState() method. Each state is an integer constant defined in this interface and summarized below.
Agent.LOG_IN This state indicates the Agent is logged into an ACDAddress.
Agent.LOG_OUT This state indicates the Agent has logged out of an ACDAddress.
Agent.NOT_READY
This state indicates the Agent is not available to handle Calls because it is busy with other non-call servicing related
tasks.
Agent.READY This state indicates the Agent is available to service Calls.
Agent.WORK_NOT_READY This state indicates the Agent is not available to service Calls because it is busy with other call-servicing related tasks.
Agent.WORK_READY This state indicates the Agent is available to service Calls and is also performing other call-servicing related tasks.
Agent.BUSY This state indicates the Agent is not available to service Calls because it is busy with another Call.
Agent.UNKNOWN This state indicates the state of the Agent is currently not known.
The following diagram illustrates the valid state transitions for the Agent. The implementation must guarantee the Agent state adheres to these state
transitions. If an applications requests an Agent state change which violates the transitions, the setState() method on this interface will throw
InvalidStateException. The state of this object can be altered by invoking the the setState method.
NOT_READY
The Agent.NOT_READY state indicates the Agent is not available to handle Calls because it is busy with other non-call servicing related
tasks.
READY
The Agent.READY state indicates the Agent is available to service Calls.
NOT_READY
public static final int NOT_READY
The Agent.NOT_READY state indicates the Agent is not available to handle Calls because it is busy with other non-call servicing related
tasks.
READY
public static final int READY
The Agent.READY state indicates the Agent is available to service Calls.
Alguma sugestão?