[Asterisk-Dev] Agents, members - who's taking the call in the queue?

[Alexander Lopez]

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com 
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of 
> Olle E Johansson
> Sent: Thursday, January 05, 2006 1:43 PM
> To: Asterisk Developers Mailing List
> Subject: [Asterisk-Dev] Agents, members - who's taking the 
> call in the queue?
> 
> Corydon and I have been discussing terminology in the bug tracker.
> 
> Up until recently, we've been teaching this in the trainings:
> 
> * A queue (started by app queue() ) consists of MEMBERS
> * A member can be either a device (tech/name) or an agent
> 
> Normally, when people talk about a sales queue, it's "agents" 
> answering. 
> A queue consists of agents.
> 
> There's a new function that breaks the terminology and use 
> the word "agent" as "all members of a queue". This is no 
> good, for documentation or for teaching. We need to be strict.
> 
> I can agree that "agents" are a better word for "everyone 
> that answers a queue" but how do we then separate agents from 
> "someone with an account that logs in to the agent channel"?
> 
> Either way, we need to clean up. Either rename the function 
> and stick with the old style or rename chan_agent and 
> agents.conf and update the docs and teaching material.
> 
>

I have remember seeing your notes in Mantis (5451) I Understand the
question now.

If we were to rename members  - > queueagents.

It would be MUCH simpler than changing the name of the Agent channel. 

I do not think that the Agent channel should be changed in any way, It
is what it is an Agent! I am sure it can be used for other items but it
is 'almost' always used by a PERSON to answer a CALL.



> What do you think?
> 
> /O
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>