similar to: AgentCallBackLogin - stopping

Hello! I wonder what the default context that the Queue application uses to call extensions. If there is a possibility to change this into a context created by me possible? Would you like to get this load value to variables before calling the extension. tks, Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL:

Good morning?... I'm?using?Asterisk?1.4.40?AgentCallbackLogin?in?a?Call Center.?What?is?happening?isthat?when the?Call?Center?has more?than 15?simultaneous calls?the?login application?isextremely?slow to?fall into?the?low?priority,?ie, the?agent?can?log in,?but?takes about 1minute to?drop?in?priority?below.?.. I've tried?to recompile?the?asterisk, I

Hello, working in a call center where we set up a structure in asterisk. When my voip reaches 150 calls are with bad quality. We do not transcode codec. What I realized using the top command server (CentOS) processing is too high for the asterisk. But the general processor server is down. Would any limitation of Asterisk to use more hardware resources? tks Eduardo -------------- next part

Can someone tell me why this is not valid... [start] exten => 1000,1,Answer exten => 1000,2,Wait,1 exten => 1000,3,AgentcallbackLogin(1000||2000@Local) exten => 2000,1,Macro(DialProxy,115551212) exten => 3000,1,Queue(testq||||45) while this is: [start] exten => 1000,1,Answer exten => 1000,2,Wait,1 exten => 1000,3,AgentcallbackLogin(1000||2000@start) exten =>

people I have a running Asterisk 1.8.28 in great Dell server with two xeon processors and 16gb of ram and HD SAS 15k (Raid 1). This server is recording all calls (placed to record the audio in a ram disk), the entire CDR goes straight to MySQL by cdr_mysql.so. Each call runs some validation and AGI's have an auto dialer system that generates calls over the manager. Calls originate and

Hello all. I'm setting up a new call center PBX using * v1.4, and figure it's better to go with AddQueueMember over AgentCallbackLogin. The functionality of AgentCallbackLogin still works, but without a firm idea of how long it will be in the codebase, I'm wary of building a system on top of it. The basic mechanics work, but I'm having some trouble on logging. With

Which kind of transfer do you use? Try using the # transfer. Hope that helps.. Guido Hecken -----Urspr?ngliche Nachricht----- Von: Diego Magalh?es [mailto:diego@redetaho.com.br] Gesendet: Mittwoch, 2. Februar 2005 17:21 An: asterisk-users@lists.digium.com Betreff: [Asterisk-Users] AgentLogin / AgentCallbackLogin transfer problem Hello guys, I?m running Asterisk CVS-HEAD-02/01/05-12:22:46 and

Hmm i found the problem... I?m using a Grandstream BT100. The transfer just works in a queue if I first acknowledged the call using the # key, and then press the TRANSFER key in the Grandstream. In the asterisk console I receive a: -- SIP/4002-4563 acknowledged Then I can transfer the call... Weird because i?m using ackcall=NO in agents.conf ... Diego Magalh?es diego@redetaho.com.br +55 24

Hello guys, I?m running Asterisk CVS-HEAD-02/01/05-12:22:46 and having a problem with call transfers using the cmds AgentCallBackLogin and AgentLogin First Case (using cmd AgentCallbacklogin): When the incoming call comes and enters the queue, the agent logged in answer the call. But when I try to transfer this call to another agent, the incoming call is dropped. I don?t receive any error

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) After some rearch I learnt that AgentCallBackLogin is removed in 1.6. Any one has a configuration that works in place of AgentCallBackLogin in 1.6. -- ond -------------- next part -------------- An HTML attachment was scrubbed... URL:

Guys, I have a problem. I have a queue on asterisk 1.8 that members are added dynamically via the AMI QueueAdd. When you run the CLI a "reload app_queue.so" all members who were in the queue disappear. This is a bug or some parameter that I do not know? Would have another way to do the reload queue without any risk to members who are already in it? tks Ed -------------- next part

Hi All, I'm having trouble setting up a queue: I'm using AgentCallBackLogin to login in the queue, but: 1 - When an agent answer the call and another call arrive his phone rings again. 2 - When no there are no one answer the queue the system goes to voicemail of agent 1234 I'm using asterisk-1.2.0-beta1. My configuration is below, Any ideas? Many thanks, Joao Antunes

Hi Trying to get logout by dialling an extension sorted out. Thought the it worked was agent logs in and logs off on an extension clears any previous agents currently on that extension like: 1. agent 1 login to extension1 2. agent 2 login to extension1 3. agent 2 logout agent 1 and 2 logged out Is this how it should work? I am using current cvs. Thanks Jack agent => 0,,nullagent agent

I agree with these fella's, this is a piss poor way of fixing it. I only know of one call center that used static agents, mostly because they were sold a peice of crap and they had no idea how to use it the other way. I think you will find the majority of call centers are callback centers. This decision has taken Asterisk out of the realm of providing reasonable call center solutions. VIVA

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 lot of agents defined in queues.conf and agents.conf. Each agent may login more than one queue. It

I would like to know if AgentCallbackLogin will be discontinued anytime shortly in Asterisk 1.4.x . I've read a page in voip-info that said so [1], but it was not an official announcement. I have to be sure, because I'm in the process of setting up a medium-to-big callcenter with Asterisk and calling the agents when a call is placed in a queue is a requisite (I've also read it can be

Hi, I'm currently migrating to 1.4 and have problems changing deprecated AgentCallbackLogin to AddQueueMember. I have dynamic queues and dynamic agents (MySQL Realtime), and pseudo-dynamic agents.conf (with huge amount of possible agent numbers). Agent login is done trough manager API: * AgentCallbackLogin * QueueAdd In 1.4 seems AddQueueMember can do all the same, but there is no such

Hi List, Ive got a few * boxes connecting together, one box is doing AgentCallBackLogin() and then the 2nd box is holding some phones at a remote site. I have users login to the main box and * shows the user is logged into a extension that resides on the other box, problem is, when I go to make a call to a agent, I get "May 16 05:59:08 NOTICE[13897]: chan_sip.c:9750 handle_response_invite:

When I use AgentCallbackLogin() function to login an agent, I got following warning message saying the agent is not valid for auto login while my other extensions work fine for this function. Does anybody know why? This extension has the same settings as the other ones like agents.conf and queues.conf. Here is the message from asterisk: -- Executing

With the 1.4 series I see that AgentCallbackLogin is deprecated and that to get the functionality it is suggested that it be implemented via dialplan. I've read through and followed the examples near as I can tell. Agent login/logout works fine with the agents being added to their respective queues and offered calls from the queues to which they've been added. The catch however is with