Anthony Francis wrote:
> Anthony Francis wrote:
>
>> oumar ndiaye wrote:
>>
>>
>>> Thanks all for your responses.
>>> I am not sure I know every thing AgentCallBackLogin is capable. I
>>> don't know either if I have to have all the functions offered by
>>> AgentCallBackLogin. All I n
Anthony Francis wrote:
> oumar ndiaye wrote:
>
>> Thanks all for your responses.
>> I am not sure I know every thing AgentCallBackLogin is capable. I
>> don't know either if I have to have all the functions offered by
>> AgentCallBackLogin. All I need is a way to allow call takers to login
oumar ndiaye wrote:
> Thanks all for your responses.
> I am not sure I know every thing AgentCallBackLogin is capable. I
> don't know either if I have to have all the functions offered by
> AgentCallBackLogin. All I need is a way to allow call takers to login
> and before they can take calls.
You guys... grr...
I'm still on 1.4 svn ... not ready to even think about 1.6 OR 1.8(when
it's released) for production right now. :-)
--
Regards,
Robert Broyles
Rob Hillis wrote:
> ...except that Macros are now deprecated and will most likely be removed
> in 1.8.
>
> Robert Broyles wrote:
>>
Thanks all for your responses.
I am not sure I know every thing AgentCallBackLogin is capable. I don't know
either if I have to have all the functions offered by AgentCallBackLogin.
All I need is a way to allow call takers to login and before they can take
calls. How is this done today in 1.6.
Than
Rob Hillis schrieb:
> ...except that Macros are now deprecated and will most likely be removed
> in 1.8.
>
> Robert Broyles wrote:
>> Looks like using a Macro and the 'M' Dial() option is the way to go for
>> now if you need the answer confirmation.
Use U() and Gosubs then!
Philipp Kempgen
...except that Macros are now deprecated and will most likely be removed
in 1.8.
Robert Broyles wrote:
> Hmm, this is all very interesting.
>
> Looks like using a Macro and the 'M' Dial() option is the way to go for
> now if you need the answer confirmation.
>
> http://www.voip-info.org/wiki-Aste
Hmm, this is all very interesting.
Looks like using a Macro and the 'M' Dial() option is the way to go for
now if you need the answer confirmation.
http://www.voip-info.org/wiki-Asterisk+cmd+Dial
Look at example #2, and adapt it for your needs.
--
Regards,
Robert Broyles
Philipp Kempgen wrote
Philipp Kempgen schrieb:
> Anthony Francis schrieb:
>> Robert Broyles wrote:
Check out this alternative:
http://hostseries.com/agentcallbacklogin-alternative/
>
> ---cut---
> [agents]
> exten => 1050,1,Set(AGENT_SIP=${DB(agent_sip/1050)})
> exten => 1050,n,Dial(SIP/${AGENT_SIP})
> ---cut
Anthony Francis schrieb:
> Robert Broyles wrote:
>>> Check out this alternative:
>>> http://hostseries.com/agentcallbacklogin-alternative/
---cut---
[agents]
exten => 1050,1,Set(AGENT_SIP=${DB(agent_sip/1050)})
exten => 1050,n,Dial(SIP/${AGENT_SIP})
---cut---
> I like what he came up ,with howeve
Why don't you use followme if you want to do that?
In fact, you can have followme, plus the local agents as mentioned in
the previous alternative that I mentioned.
--
Regards,
Robert Broyles
Anthony Francis wrote:
> Robert Broyles wrote:
>>> Check out this alternative:
>>> http://hostseries.co
Robert Broyles wrote:
>> Check out this alternative:
>> http://hostseries.com/agentcallbacklogin-alternative/
>>
>> Regards,
>> Robert Broyles
>>
>>
>
I like what he came up ,with however it doesn't replace the agent
callback login systems use of being able to make an agent press a key to
ac
Danny Nicholas schrieb:
> http://www.voip-info.org/tiki-index.php?page=Asterisk%20cmd%20AgentCallbackL
> ogin
http://www.voip-info.org/wiki/view/Asterisk+cmd+AgentCallbackLogin
Philipp Kempgen
--
AMOOCON 2009, May 4-5, Rostock / Germany -> http://www.amoocon.de
Asterisk: http://the-aster
3:16 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] AgentCallBackLogin no longer works after
installing asterisk 1.6
The deprecation of Agent Callback login was announced in 1.4.
Robert Broyles wrote:
> Check out this alternative:
>
The deprecation of Agent Callback login was announced in 1.4.
Robert Broyles wrote:
> Check out this alternative:
> http://hostseries.com/agentcallbacklogin-alternative/
>
> Regards,
> Robert Broyles
>
> oumar ndiaye wrote:
>
>> Hi,
>>
>> My queue used to work fine until I upgraded to 1.6. I
Check out this alternative:
http://hostseries.com/agentcallbacklogin-alternative/
Regards,
Robert Broyles
oumar ndiaye wrote:
> Hi,
>
> My queue used to work fine until I upgraded to 1.6. I am getting the
> message:
> No application 'AgentCallBackLogin' for extension (default, 31001, 1)
> Aft
On Wed, Sep 3, 2008 at 11:09 AM, Lee, John (Sydney)
<[EMAIL PROTECTED]> wrote:
>> > Just out of curiosity, where do you get this AddQueueMember syntax
> from?
>>
>> Here:
>>
> http://www.digium.com/elqNow/elqRedir.htm?ref=http://downloads.oreilly.c
> om
>> /books/9780596510480.pdf
>> page: 367
>
>
> > Just out of curiosity, where do you get this AddQueueMember syntax
from?
>
> Here:
>
http://www.digium.com/elqNow/elqRedir.htm?ref=http://downloads.oreilly.c
om
> /books/9780596510480.pdf
> page: 367
Oh so the VOIP Wiki is out of date!
Now, where should we go to for reliable Asterisk info the
> Just out of curiosity, where do you get this AddQueueMember syntax from?
Here:
http://www.digium.com/elqNow/elqRedir.htm?ref=http://downloads.oreilly.com/books/9780596510480.pdf
page: 367
___
-- Bandwidth and Colocation Provided by http://www.ap
> I need login Agent(Member) in asterisk.
> use this option:
> for example:
> AddQueueMember(queuetest,SIP/ekiga,10,,Agent/13)
Just out of curiosity, where do you get this AddQueueMember syntax from?
http://www.voip-info.org/wiki/view/Asterisk+cmd+AddQueueMember
Description:
AddQueueMember(que
On Tue, Sep 2, 2008 at 6:07 PM, Krzysztof Zimnicki <[EMAIL PROTECTED]> wrote:
> Hi
>
> i have problem with AddQueueMember logic.
>
> I need login Agent(Member) in asterisk.
> use this option:
> for example:
> AddQueueMember(queuetest,SIP/ekiga,10,,Agent/13)
>
> and now i want to call to this Agent:
>
> Martin
>
>
>
> - Original Message -----
> From: "Kevin P. Fleming" <[EMAIL PROTECTED]>
> To: "Alan Ferrency" <[EMAIL PROTECTED]>
> Cc: "Asterisk Users Mailing List - Non-Commercial Discussion"
>
> Sent: Wednesday, April 11, 2
- Original Message -
From: "Kevin 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
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
Maybe if we make enough noise it can be replaced with something better,
rather than just thrown away.
Agentcallabacklogin is great - easy to setup, and provides some useful
functionality.
PaulH
On Wed, 2006-12-20 at 19:09 -0800, Carla Schroder wrote:
> Ick. Don't WANT to do all that. no. A
Ick. Don't WANT to do all that. no. Anyway, according to this it should
still work in 1.4:
http://www.mail-archive.com/asterisk-users%40lists.digium.com/msg166873.html
"Yes, AgentCallbackLogin is deprecated, but it will not be removed until after
1.4. "
On Wednesday 20 December 2006 3:25 pm,
You can use Local channels, plus some custom queue_log logging, unless you
want fancy agent/extension association; in that case you'll have to have
your fun with the dialplan :)
l.
On Wed, 20 Dec 2006 23:51:31 +0100, Carla Schroder <[EMAIL PROTECTED]>
wrote:
Sooo what replaces it? Con
Sooo what replaces it? Convoluted dialplans? AEL stuff? Agentcallbacklogin was
simple and easy. Hardly anything in Asterisk is simple or easy. Maybe that's
why it was removed. :)
On Wednesday 20 December 2006 2:21 pm, Lenz wrote:
> I would not say that * has been "taken out of the realm of reaso
I would not say that * has been "taken out of the realm of reasonable CC
solutions", luckily there are still a lot of ways to configure * to meet
the most diverse needs, but it's surely a fact that a very convenient and
used approach being deprecated will be an annoyance for CC designers an
I have been speaking privately to a number of CC integrators and resellers
about the AgentCallbackLogin() deprecation issue, and I'd dare say nobody
is enthusiastic about it. With all its problems, AgentCallBackLogin is the
workhorse of most of today's Asterisk CCs, and my impression is tha
> -Original Message-
> From: Gavin Hamill [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 20, 2006 7:10 AM
> To: asterisk-users@lists.digium.com
> Subject: Re: [asterisk-users] AgentCallbackLogin() deprecated in 1.4
>
>
> On Wed, 20 Dec 2006 14:39:42 +0100
Yes, we have issues with this application being removed as well. In my opinion,
it's a loss of functionality.
> -Original Message-
> From: "Markus Bönke" [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 20, 2006 6:40 AM
> To: asterisk-users@lists.digium.com
> Cc: [EMAIL PROTECTED]
>
On Wed, 20 Dec 2006 14:39:42 +0100
"Markus Bönke" <[EMAIL PROTECTED]> wrote:
> Hello all,
> The other thing is, that "show agents"
> doesn't show me which agents are logged in and if I use "show queue"
> I can see local channels attached to a queue but no agents. For my
> point of view there is s
On Tue, 28 Nov 2006 17:57:04 -0600
"Octavio Ruiz (Ta^3)" <[EMAIL PROTECTED]> wrote:
> Why? Seems that reinventing the well was the agentcallbacklogin
> implementation, when it could be happend in dialplan logic.
Hm, now that I have examined this in more depth, I still seem to be
missing one vital
On Tue, 28 Nov 2006 17:57:04 -0600
"Octavio Ruiz (Ta^3)" <[EMAIL PROTECTED]> wrote:
> > Is there an isolated example somewhere of how to use existing
> > dialplan logic and dynamic queue membership to simulate the current
> > behaviour?
>
> http://svn.digium.com/view/asterisk/trunk/doc/queues-wit
> > Yes, AgentCallbackLogin is deprecated, but it will not be removed
> > until after 1.4.
>
> Is there an isolated example somewhere of how to use existing dialplan
> logic and dynamic queue membership to simulate the current behaviour?
http://svn.digium.com/view/asterisk/trunk/doc/queues-with-
On Tue, 28 Nov 2006 10:27:27 -0600 (CST)
Jason Parker <[EMAIL PROTECTED]> wrote:
> Yes, AgentCallbackLogin is deprecated, but it will not be removed
> until after 1.4.
Is there an isolated example somewhere of how to use existing dialplan
logic and dynamic queue membership to simulate the curren
Yes, AgentCallbackLogin is deprecated, but it will not be removed until after
1.4.
- Original Message -
From: Miguel Paolino <[EMAIL PROTECTED]>
To: asterisk-users@lists.digium.com
Sent: Monday, November 27, 2006 7:19:44 AM GMT-0600 US/Central
Subject: [asterisk-users] AgentCallbackL
this asks only for a password
exten => 123,1,AgentCallbackLogin(${CALLERIDNUM},${EXTEN})
hope it helps...
Guido
> -Ursprüngliche Nachricht-
> Von: Gleidson Antonio Henriques [mailto:[EMAIL PROTECTED]
> Gesendet: Samstag, 8. April 2006 18:38
> An: Asterisk-Digium
> Betreff: [asterisk-u
Yes, there is a patch for this (search mantis), it's static in that it's
a single announcement that doesn't currently relate to the queue.
Steve
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 03 January 2006 10:00
To: asterisk-us
On 12/22/05, Dov Bigio <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On of my agents made a mistake while logging in to the Queue system, and
> entered another agent's extension.
> Asterisk allowed that, and the first agent was then able to receive two
> calls from the queue, on that was actually for him, a
BJ Weschke wrote:
For your outbound calling problem, if you're operating with CVS-HEAD
you can PauseQueueMember and then UnpauseQueueMember as part of the
dial-plan for your outbound calls for those agents.
Thanks, I think this will do the trick. For short breaks, I can wrap
this around an e
For your outbound calling problem, if you're operating with CVS-HEAD you can PauseQueueMember and then UnpauseQueueMember as part of the dial-plan for your outbound calls for those agents.
On 9/17/05, Rajkumar S <[EMAIL PROTECTED]> wrote:
Hi,I have a small callcenter with 3 agents who login usingA
>
> Hi,
>
> I have a small callcenter with 3 agents who login using
> AgentCallbackLogin. They normally receive calls, but needs to call
> outside also. When they call outside, though they are busy the "show
> agents" shows them as available, and calls gets routed to them. How
can
> I make them
There is a variable that is set, but it has issues and a complete fix
was put in CVS HEAD. See http://bugs.digium.com/view.php?id=4616
If you don't kick people for not answering you should be fine by using
the variable
KRTorio wrote: ${AGENTBYCALLERID_${CALLERID}} . Keep in mind that if
they
ling List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] AgentCallbackLogin
Can it be a problem with AgentCallbackLogin?
-- Executing AgentCallbackLogin("Zap/4-1",
"1010|[EMAIL PROTECTED]") in new stack
-- Setting global variable 'AGENTBYCALLERID_XX
ginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Bockman
Sent: zaterdag 4 juni 2005 18:55
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] AgentCallbackLogin
> Can it be a problem with AgentCallb
> Can it be a problem with AgentCallbackLogin?
>
> -- Executing AgentCallbackLogin("Zap/4-1", "1010|[EMAIL PROTECTED]")
> in new stack
> -- Setting global variable 'AGENTBYCALLERID_XX' to '1010'
> -- Playing 'agent-loginok' (language 'en')
> -- Callback Agent '1010' logged
Hi again,
Can it be a problem with AgentCallbackLogin?
-- Executing AgentCallbackLogin("Zap/4-1", "1010|[EMAIL PROTECTED]")
in new stack
-- Setting global variable 'AGENTBYCALLERID_XX' to '1010'
-- Playing 'agent-loginok' (language 'en')
-- Callback Agent '1010' logged in
In queues.conf, try:
member => Local/@
So, for instance, something like:
member => Local/[EMAIL PROTECTED]
Cheers,
Chad
On Nov 15, 2004, at 7:59 AM, Shawn Dillon wrote:
> I have the AgentCallBackLogin working well when the support
technician
> logs into the queue manually. If there a way to get ce
W liście z pią, 12-11-2004, godz. 23:55, Shawn Dillon pisze:
> I have the AgentCallBackLogin working well when the support technician
> logs into the queue manually. If there a way to get certain extensions
> to automatically log into the queue? That way I do not have to worry
> about help desk st
[EMAIL PROTECTED] wrote:
> As I understand it, you'd enter the extension at which you wish to be
> called
> back at, your 9665 has nothing to do with it.
>
> Instead of dialling 28 you could dial 9665 and that would add that
> SIP phone
> as an agent to the cytelcs queue.
>
> Steve
>
>
>
As I understand it, you'd enter the extension at which you wish to be called
back at, your 9665 has nothing to do with it.
Instead of dialling 28 you could dial 9665 and that would add that SIP phone
as an agent to the cytelcs queue.
Steve
-Original Message-
From: Harold Workman [mailto
It looks like the AgentCallBackLogin app is not working in the latest
CVS Asterisk CVS-03/15/04. Can someone please verify this. I had
this exact setup running on a different CVS load prior to running the
updates.
Thanks,
-gcc
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMA
Hi!
> I'm using the AgentCallbackLogin function to log my agents onto multiple
> call queues.
>
> exten => 3001,1, AgenCallbackLogin(1001,@sip). This works very well.
>
> I can not work out how to log them back out? On of the forum members was
> kind enough to point me into the directions of '
Thanks! I'm trying that now.
Jim Friedeck
Armand A. Verstappen wrote:
out. Is there some way to distunguish them in CDR? I also noticed the
management interface maintains a Unique ID for each call and lets that
call be traced throughout its life in
Thanks! I don't know why that works. Where is that behaviour documented?
Also is there any way to turn off the '#' to confirm so the agent can
just pick up the phone to answer the call? I'm running CVS as of about
an hour ago. Thanks again.
Jim Friedeck
-
The T
The unique id is generated when a channel is requested, so the uniqueid
will be unique for any call or channel. You should never see the same
uniqueid more than once. The uniqueid is available as a channel var
${UNIQUEID}, as an agi environment var (agi_uniqueid), as an entry in
(hopefully) every
Subject: Re: [Asterisk-Users] AgentCallbackLogin
Thanks! I don't know why that works. Where is that behaviour documented?
Also is there any way to turn off the '#' to confirm so the agent can
just pick up the phone to answer the call? I'm running CVS as of about
an hour
Jim
I added a patch that mark got into cvs last night
use
ackcall=no
in agent.conf
-Original Message-
From: Jim Friedeck <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: August 6, 2003 1:46 PM
Subject: Re: [Asterisk-Users] AgentCallbackLogin
>Thanks! I
I am trying to record all logins and logouts for posterity. The act of
logging in with AgentCallbackLogin produces the same CDR data as logging
out. Is there some way to distunguish them in CDR? I also noticed the
management interface maintains a Unique ID for each call and lets that
call be tr
> out. Is there some way to distunguish them in CDR? I also noticed the
> management interface maintains a Unique ID for each call and lets that
> call be traced throughout its life in the PBX. Can that data be added to
> CDR as well to allow for easier call tracking?
It looks like if you defi
I don't think that's the same unique id. It changes for each record in
the CDR. I believe the management interface unique id is maintained as
specific to each incoming or 'original' call. Any ideas?
Jim Friedeck
---
Jim Friedeck wrote:
Thanks! I'm trying that now.
Jim
Hey Jim,
On Wed, Aug 06, 2003 at 15:12:50 -0500, Jim Friedeck wrote:
> I am having trouble with the AgenCallBackLogin app. I can't seem to
> define a context for the queue.
>
> Here is the relevant configs:
[...]
> extensions.conf:
>
> [c_in_1];internal lines (up to 48 agents and admins)
74 matches
Mail list logo
