I am having trouble with the AgenCallBackLogin app. I can't seem to
define a context for the queue.
Here is the relevant configs:
queues.conf:
[general]
[default]
[q_lo_1]
music = default
strategy = ringall
context = c_in_1
timeout = 15
retry = 2
maxlen = 0
member => Agent/@3
agents.conf:
[agents]
autologoff=10
wrapuptime=15000
group=1
agent => 1001,1234,Agent1
agent => 1002,1234,Agent2
agent => 1010,1234,Agent3
group=2
agent => 1020,1234,Agent4
group=3
agent => 1021,1234,Agent5
agent => 1022,1234,Agent6
agent => 1023,1234,Agent7
agent => 1024,1234,Agent8
agent => 1025,1234,Agent9
extensions.conf:
[c_in_1]; internal lines (up to 48 agents and admins)
exten => 400,1,AgentCallbackLogin(|c_in_1)
exten => 100,1,Queue(q_ld_1)
exten => 101,1,Queue(q_ld_2)
exten => 102,1,Queue(q_ld_3)
exten => 103,1,Queue(q_lo_1)
exten => t,1,Playback(invalid)
exten => t,2,Hangup
ignorepat => 8
exten => _8NXXXXXX,1,Dial(Zap/97/${EXTEN:1})
exten => _8NXXXXXX,2,Congestion
ignorepat => 8
exten => _9NXXXXXX,1,Dial(Zap/97/${EXTEN:1})
exten => _9NXXXXXX,2,Congestion
exten => 201,1,Dial(Zap/73)
exten => 202,1,Dial(Zap/74)
exten => 203,1,Dial(Zap/75)
exten => 204,1,Dial(Zap/76)
exten => 205,1,Dial(Zap/77)
exten => 206,1,Dial(Zap/78)
exten => 207,1,Dial(Zap/79)
exten => 208,1,Dial(Zap/80)
exten => 209,1,Dial(Zap/81)
exten => 210,1,Dial(Zap/82)
exten => 211,1,Dial(Zap/83)
exten => 212,1,Dial(Zap/84)
exten => 213,1,Dial(Zap/85)
exten => 214,1,Dial(Zap/86)
exten => 215,1,Dial(Zap/87)
exten => 216,1,Dial(Zap/88)
exten => 217,1,Dial(Zap/89)
exten => 218,1,Dial(Zap/90)
exten => 219,1,Dial(Zap/91)
exten => 220,1,Dial(Zap/92)
exten => 221,1,Dial(Zap/93)
exten => 222,1,Dial(Zap/94)
exten => 223,1,Dial(Zap/95)
exten => 224,1,Dial(Zap/96)
When I dial 400 I can log an agent on extension 201 in but when I dial
103 to enter the q_lo_1 queue the CLI interface says:
-- Executing Queue("Zap/74-1", "q_lo_1") in new stack
queue: q_lo_1, options: (null), url: (null), announce: (null)
-- Started music on hold, class 'default', on Zap/74-1
NOTICE[540691]: File chan_local.c, Line 310 (local_alloc): No such
extension/context default@201 creating local channel
NOTICE[540691]: File app_queue.c, Line 468 (wait_for_answer): No one is
answered queue q_lo_1
I don't understand where the default context comes from in the message
'No such extension/context default@201'. Where do I tell the queue app
the proper context? Any ideas?
Jim Friedeck
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) > > exten => 400,1,AgentCallbackLogin(|c_in_1)[...]> I don't understand where the default context comes from in the message > 'No such extension/context default@201'. Where do I tell the queue app > the proper context? Any ideas?Try adding an "@" in front of the context in the argument to "AgentCallbackLogin", like so: exten => 400,1,AgentCallbackLogin(|@c_in_1) Also make sure you're running the latest CVS-version, as the functionality has just been added yesterday or so. Grtz, Oliver
Jim I added a patch that mark got into cvs last night use ackcall=no in agent.conf -----Original Message----- From: Jim Friedeck <asterisk@carhil.com> To: asterisk-users@lists.digium.com <asterisk-users@lists.digium.com> Date: August 6, 2003 1:46 PM 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 ago. Thanks again. > >Jim Friedeck > >--------------------------------- > >The Traveller wrote: > >>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) >>> >>>exten => 400,1,AgentCallbackLogin(|c_in_1) >>> >>> >> >>[...] >> >> >> >>>I don't understand where the default context comes from in the message >>>'No such extension/context default@201'. Where do I tell the queue app >>>the proper context? Any ideas? >>> >>> >> >>Try adding an "@" in front of the context in the argument to >>"AgentCallbackLogin", like so: >> >>exten => 400,1,AgentCallbackLogin(|@c_in_1) >> >>Also make sure you're running the latest CVS-version, as the functionality >>has just been added yesterday or so. >> >> >> >> Grtz, >> >> Oliver >>_______________________________________________ >>Asterisk-Users mailing list >>Asterisk-Users@lists.digium.com >>http://lists.digium.com/mailman/listinfo/asterisk-users >> >> >> >> > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users
> 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 define MYSQL_LOGUNIQUEID in the top of cdr/cdr_mysql.c and recompile, it will start logging the unique id you want. wkr, -- Envida http://www.envida.net/ Armand A. Verstappen Graadt van Roggenweg 328 armand@nl.envida.net 3531 AH Utrecht tel: +31 (0)30 298 2255 Postbus 19127 fax: +31 (0)30 298 2111 3501 DC Utrecht -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20030807/7d140b79/attachment.pgp
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 staff forgetting to log into the support queue and never receiving support calls. Thanks Shawn Dillon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041112/9e38af03/attachment.htm
> 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 staff forgetting to log into the support queue and > never receiving support calls.As far as I know, it's enought to add those extensions as a members in queue.conf. -- Graf0 Ok, I will share more details with my particular installation. 1) In my extensions.conf I have the following; exten => 997,1,AgentCallBackLogin(999|999@default) 2) In my agents.conf I have the following group=1 agent => 999,1234,Test Agent 3) In my queues.conf I have he following member => Agent/999 When an agent dials extension 997 and enters their password they will then be included in the support queue for calls. If they do not call extension 997 and enter their password when a call is placed into the support queue a message appears on the console stating that "no one is answering the support queue". Is there a way to get a certain extension to automatically log into a support queue? Or do I need to have every technician , at the start of every shift, log into the support queue manually? As an aside , this community has been very helpful in getting my Asterisk box up and running. Thanks to all. Shawn Dillon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041115/dc5cf75c/attachment.htm
Hi, Does anybody know if it is possible to DO NOT let AgentCallbackLogin hangup at the end of "Agent logged in, Goodbay", but to go on with the next exten in the dialplan? Gr. Steven
Hi again,
Can it be a problem with AgentCallbackLogin?
-- Executing AgentCallbackLogin("Zap/4-1",
"1010|XXXXXXXXXX@agents")
in new stack
-- Setting global variable 'AGENTBYCALLERID_XXXXXXXXXX' to
'1010'
-- Playing 'agent-loginok' (language 'en')
-- Callback Agent '1010' logged in on XXXXXXXXXX@agents
-- Playing 'vm-goodbye' (language 'en')
== Spawn extension (agent-io, 1, 5) exited non-zero on 'Zap/4-1'
-- Hungup 'Zap/4-1'
Gr. Steven
-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Steven Lam
Sent: zaterdag 4 juni 2005 17:12
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] AgentCallbackLogin
Hi,
Does anybody know if it is possible to DO NOT let AgentCallbackLogin
hangup at the end of "Agent logged in, Goodbay", but to go on with the
next exten in the dialplan?
Gr. Steven
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
> Can it be a problem with AgentCallbackLogin? > > -- Executing AgentCallbackLogin("Zap/4-1", "1010|XXXXXXXXXX@agents") > in new stack > -- Setting global variable 'AGENTBYCALLERID_XXXXXXXXXX' to '1010' > -- Playing 'agent-loginok' (language 'en') > -- Callback Agent '1010' logged in on XXXXXXXXXX@agents > -- Playing 'vm-goodbye' (language 'en') > == Spawn extension (agent-io, 1, 5) exited non-zero on 'Zap/4-1' > -- Hungup 'Zap/4-1'That's how it is supposted to work. It calls you back when the agent gets a call from the queue.> Does anybody know if it is possible to DO NOT let AgentCallbackLogin > hangup at the end of "Agent logged in, Goodbay", but to go on with the > next exten in the dialplan?If it doesn't continue in the dialplan, it would require modification of the source to change the return code. You want to do additional processing before it hangs up the line? If you don't want it to hang up at all, then you need to use AgentLogin. Kevin
Hi Kevin, After the agent logs in i would like to present him a voice menu to let him chose the queue's he want to be a member of. Using AddQueueMember. So the next step in the dial plan and n+101 (via a option) would be a great solution. Do you think this is possible? Gr. Steven -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] 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 AgentCallbackLogin? > > -- Executing AgentCallbackLogin("Zap/4-1", > "1010|XXXXXXXXXX@agents") in new stack > -- Setting global variable 'AGENTBYCALLERID_XXXXXXXXXX' to '1010' > -- Playing 'agent-loginok' (language 'en') > -- Callback Agent '1010' logged in on XXXXXXXXXX@agents > -- Playing 'vm-goodbye' (language 'en') > == Spawn extension (agent-io, 1, 5) exited non-zero on 'Zap/4-1' > -- Hungup 'Zap/4-1'That's how it is supposted to work. It calls you back when the agent gets a call from the queue.> Does anybody know if it is possible to DO NOT let AgentCallbackLogin > hangup at the end of "Agent logged in, Goodbay", but to go on with the> next exten in the dialplan?If it doesn't continue in the dialplan, it would require modification of the source to change the return code. You want to do additional processing before it hangs up the line? If you don't want it to hang up at all, then you need to use AgentLogin. Kevin _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
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, and the other one that was on behalf of the agent that made the mistake. Shouldn't Asterisk block the second agent in case he tries to login using an extension that is already in use by other agent? Thank you Dov -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20051222/5b7092e4/attachment.htm