evin P. Fleming" <[EMAIL PROTECTED]>
To: "Alan Ferrency" <[EMAIL PROTECTED]>
Cc: "Asterisk Users Mailing List - Non-Commercial Discussion"
Sent: Wednesday, April 11, 2007 11:45 PM
Subject: Re: [asterisk-users] AgentCallBackLogin vs AddQueueMember
Alan Ferren
On Wed, 11 Apr 2007, Kevin P. Fleming wrote:
> Alan Ferrency wrote:
>
> > This means that all queue activity is associated with a SIP channel
> > in the logs, which is not acceptable.
>
> This is why we added the 'membername' argument to the
> AddQueueMember application, so that queue logs can ref
Alan Ferrency wrote:
> However, this is not what we need. This adds a phone channel to the
> queue, and does not track which person is using that phone. This means
> that all queue activity is associated with a SIP channel in the logs,
> which is not acceptable.
Right. This is why we added the 'm
I apologize for not responding sooner, I obviously don't read this
mailing list regularly.
> Alan Ferrency wrote:
> > In our investigation of the "AddQueueMember" vs.
> > "AgentCallbackLogin" situation, the major loss with using the
> > published "AddQueueMember" replacement is that it assumes ea
Alan Ferrency wrote:
> In our investigation of the "AddQueueMember" vs.
> "AgentCallbackLogin" situation, the major loss with using the
> published "AddQueueMember" replacement is that it assumes each agent
> is always using the same phone.
This is not true; it is certainly possible to call AddQue
Hello,
In our investigation of the "AddQueueMember" vs.
"AgentCallbackLogin" situation, the major loss with using the
published "AddQueueMember" replacement is that it assumes each agent
is always using the same phone.
We were not implementing agents this way at all. In fact the _only_
thing we r
On 2/14/07, gc <[EMAIL PROTECTED]> wrote:
So you have to hard code each queue name in the dialplan for an agent to
login. What about hundreds of agents login 30-40 different queues? If this
is the only way to do it, I will not use AddQueueMember at all. I do not
know the reason for deprecatin
So you have to hard code the each queue name in the dialplan for an agent to
login. What about hundreds of agents login 30-40 different queues? If this is
the only way to do it, I will not use AddQueueMember at all. I do not know
the reason for deprecating AgentCallBackLogin. But I do think r
- Original Message -
From: James FitzGibbon
To: Asterisk Users Mailing List - Non-Commercial Discussion
Sent: Wednesday, February 14, 2007 10:34 AM
Subject: Re: [asterisk-users] AgentCallBackLogin vs AddQueueMember
On 2/13/07, gc <[EMAIL PROTECTED]> wrote:
So you have to hard code each queue name in the dialplan for an agent to login.
What about hundreds of agents login 30-40 different queues? If this is the
only way to do it, I will not use AddQueueMember at all. I do not know the
reason for deprecating AgentCallBackLogin. But I do think remov
On 2/13/07, gc <[EMAIL PROTECTED]> wrote:
I am developing an ACD front end using Asterisk 1.2.14. I heard that
AgentCallBackLogin will be deprecated in future version of *.
Is this true? If it is, how can I use AddQueueMember to replace
AgentCallBackLogin? I mean to login an agent in multiple qu
I am developing an ACD front end using Asterisk 1.2.14. I heard that
AgentCallBackLogin will be deprecated in future version of *.
Is this true? If it is, how can I use AddQueueMember to replace
AgentCallBackLogin? I mean to login an agent in multiple queues at once. I have
multiple queues and a
12 matches
Mail list logo
