Re: [Asterisk-java-users] AsteriskQueue Interface

[Carlos G M. <tr...@ac...>]

Hi,
I'm also looking into this...

A start could be defining the AsteriskAgent model data ?
-ID
-Associated extension (as reported by Loginchan)
-Associated channel (as in SIP/XXX used for login)
-Mode (call back/dedicated)
-Status (inbound/outbound/free/<queueName>)
(I'm a litle confused though because of the capacity of an agent to
have more than one call at one time..., invalidating this approach,
but I'm trying to have some way of mapping agent to logical extension)

-Since (i.e. time at which entered current state)

and an association from AsteriskQueue to AsteriskAgent,
which needs also some data:
-Membership
-CallsTaken
-Penalty
-LastCall
-Paused

AsteriskQueue could be extended to have some running averages like
avgHold, avgConnTime.

Thoughts ?
I hope my abrupt chime in is ok :)
-Carlos

Chris Howard @ 27/09/2006 10:24 -0300 dixit:
> Stefan Reuter wrote:
>> Hey Chris,
>>
>>   
>>> 1. Number of queue members logged into the queue.
>>> 2. Number of queue members available to take calls
>>> 3. Number of channels currently waiting in the queue (looks like 
>>> AsteriskQueue will do this one)
>>> 4. Average wait time.
>>>     
>> Yes these sound like a good fit for AsteriskQueue.
>>
>>   
>>> It looks like the AsteriskQueue interface is a good start for this but 
>>> I'm not sure if it's even possible to get the other information without 
>>> parsing through a big list of queuemember responses.
>>>     
>> There already is an empty method in live.internal.QueueManager called
>> handleQueueMemberEvent() that is called on initialization, where we
>> could put some meat in.
>> A new live object QueueMember (or AsteriskAgent) will be needed to
>> represent agents.
>> The interesting part starts after initialization, i.e. tracking agent
>> events and updating the model. The relevant ones seem to be
>> - AgentLoginEvent
>> - AgentLogoffEvent
>> - AgentCallbackLoginEvent
>> - AgentCallbackLogoffEvent
>> To associate agents with the callers they are serving (and to see
>> whether they are busy or not) looking for AgentCalledEvents will be
>> needed as well as observing the associated channel for hangup or
>> redirection so we know when the agent is available again.
>>
>> Once that has been done some new methods could be added to AsteriskQueue
>> and AsteriskAgent like support for easy login/logout, etc.
>>   
> We are doing something similar in our queue management application 
> (external from Asterisk-Java).  Getting the initial state is fun as you 
> probably already have callers in the queue and agents on the phone.  I'm 
> willing to invest some resources in this as it would make my life much 
> easier to keep this info in Aasterisk-Java and make my presentation 
> piece more light weight.  Where do we start?
> 
>>   
>>> I'm thinking about 
>>> adding an action to asterisk QueueStatSummaryRequest that will take as 
>>> an argument the queue name and return the above info as a response (I 
>>> really hate the way asterisk tries to send events as a response).  Any 
>>> thoughts?
>>>     
>> I hope that this is not needed because the idea of the live package is
>> to observe asterisk events and update an in memory model of asterisks
>> state so you dont have to talk to asterisk each time you query the state.
>>   
> For our immediate needs we created a QueueSummary action that returns 
> the info needed.  This patch has already been accepted in trunk.
> http://bugs.digium.com/view.php?id=8035
> 

-- 
Carlos G Mendioroz  <tr...@ac...>