similar to: Parial Hang with cvs-HEAD and queues/agentcallbacklogin

Hello, http://dev.rubyonrails.org/ticket/9742 If anyone is annoyed by that, please find a moment to review the patch. It''s rather tiny and tested enough. It still applies cleanly (r8962) as I write this. Thanks, Jacek Becela --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core"

dummy0 Link encap:Ethernet HWaddr C6:C8:2A:04:FD:23 BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX

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 =>

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:

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

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

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:

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, 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

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

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

Hi, We?re looking at options for logging agents into the system programmatically via Perl/PHP and I was wondering if anyone else is doing this and if so, how. We're using AgentCallbackLogin now but would like to set up a web interface instead. I've been looking at Asterisk::Manager and didn't see anything relevant and wanted to ask the group before we dove into the Asterisk source.

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

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

Good afternoon, I have a server still using Asterisk 1.4.44, it has not been done migrating to a more updated. My problem is in AgentCallBackLogin. When many people (more than 100) try to run it at the same time, the application simply hangs or is extremely slow. It takes anywhere from four minutes just to ask for the password of the agent. I thought I might be missing hardware, but both the CPU

I'm using ver. 1.0.7 here are a couple of lines from my extensions.conf file: exten => x,1,AgentCallbackLogin(${CALLERIDNUM}|${CALLERIDNUM}@sip) exten => x,2,Hangup I'm looking for a way to capture the Agent ID after login, to keep track which agent is associated in a certain call.

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

Hi all, I would like to know if there is any application replacement for the AgentCallBackLogin() from asterisk 1.4 on asterisk 1.6. I know, from what I've read that the call back login agent can be done using a smart dialplan as showed on the docs. But I cannot thinks a flexible dialplan for a dinamic reassignation of agents to different queues every day. Thanks in advance. Mariano