similar to: Queue device state problem

Hi, I'm wondering - why SIP device state doesn't get updated to anything else, except Not In Use. For queue call (with Local channel) i get: app_queue.c: Device 'SIP/21168' changed to state '1' (Not in use) app_queue.c: Device 'SIP/21168' changed to state '1' (Not in use) app_queue.c: The device state of this queue member, Agent/21168, is still 'Not in

Or, in full: [Sep 20 17:11:26] WARNING[18373]: app_queue.c:2705 try_calling: The device state of this queue member, SIP/612, is still 'Not in Use' when it probably should not be! Please check UPGRADE.txt for correct configuration settings. So, what do I check in UPGRADE.txt? This is with Asterisk 1.4.11

Hi, I'm a little surprised, up until 1.4.22 my agents where using an IAX channel to ZoIPer Softphone, however since after the upgrade to .22 we experienced a problem with hangup failure between zoiper and asterisk (look like bug http://bugs.digium.com/view.php?id=13184) i made them switch to SIP instead. Weird thing is that the 'Not In Use' warning message keep showing

Hello list, asterisk 1.4.30 2 situations in which call-limit should work, but it does not : [Jul 8 09:15:49] WARNING[11132]: app_queue.c:3272 try_calling: The device state of this queue member, test12, is still 'Not in Use' when it probably should not be! Please check UPGRADE.txt for correct configuration settings. In sip.conf I have : limitonpeer = yes In my realtime sip_buddies

Hi all, does anybody know any way that when it run "reload app_queue" in the asterisk cli it don't lose the informations from "show queue (queue name)" ? I'm passing for this trouble, because I need this informations (http://www.voip-info.org/wiki/index.php?page=asterisk+cli+command+show+queue) that asterisk cli command "show queue (queue name)" show me

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

I am experiencing a change in behaviour of my Queues in 1.4.9 vs 1.4.8. I do not pass the 'n' option to any call to Queue() in my dialplan. Yet since I upgraded to 1.4.9, I have occasionally seen this on my console: -- Nobody picked up in 20000 ms -- Exiting on time-out cycle That log message "Exiting on time-out cycle" is exclusive to the logic in app_queue meant to

Hi all, We have an 8 agent support desk setup with 2 call queues running Asterisk 1.4.5. Every so often agents will receive a call from the queue that only rings once not allowing them time to answer. The call doesn't seem to be dropped, just seems to go to voicemail. The agents are also mentioning they do not receive the 30 second wrapuptime I have specified in queues.conf. We're

When working with call queues, if an agent is logged in via AgentCallbackLogin and the extension they are registered at becomes "unavailable" (from a bad connection, or something of the like), calls routed to that extension seemed to be accepted by it, so if the next action for that extension is to go to voicemail, the caller in the queue is sent to the extensions voicemail. Even worse,

Dear all on a debian amd64 i've installed (from source) asterisk 1.4.30 On the system we have in average 50 concurrent calls in queue and 40 sip members. I'm experiencing an apparently random problem: sometimes some users receive 2 calls from asterisk, apparently ignoring the ringinuse=no settings. It appears on users that are members of many queues As you can see from the log, the

Does anyone know what can cause queue members to go into a status of "Unknown"? pbxtel-01*CLI> queue show cs has 2 calls (max unlimited) in 'rrmemory' strategy (24s holdtime), W:0, C:447, A:20, SL:91.7% within 60s Members: SIP/1405 (dynamic) (Unknown) has taken no calls yet SIP/1420 (dynamic) (paused) (Not in use) has taken no calls yet SIP/1442

Asterisk: 1.6.2.15 On the production server I've modify the /etc/asterisk/queues.conf file. Now in CLI I wan't to reload queue configuration gracefully. I did: virtual-pbx*CLI> queue reload members office virtual-pbx*CLI> But `queue show office` tells me that nothing has changed. I tried to reload all -- `queue reload all': virtual-pbx*CLI> queue reload all [Dec 28

Has anyone observed a problem where using Local channels with AddQueueMember results in missing TRANSFER events? Right now I'm using straight SIP channels when I call AddQueueMember(). I'm contemplating moving to Local channels because the non-state-based wrapuptime blows when you have a channel in multiple queues (they can hang up and get a call immediately so long as it's from a

I have a queue defined which I use like this: exten = _X.(reception),n,Ringing exten = _X.,n,Queue(enidan,t,,,20) exten = _X.,n,Voicemail(443,u) exten = _X.,n,Hangup() When I start asterisk, this queue doesn't work - -- Executing [4439000@Business:3] Queue("mISDN/3-u0", "enidan|t|||20") in new stack [May 14 13:53:59] WARNING[17860]: app_queue.c:3541 queue_exec: Unable

[Mar 20 12:45:33] WARNING[4940]: app_queue.c:3136 try_calling: The device state of this queue member, SIP/3617001000, is still 'Not in Use' when it probably should not be! Please check UPGRADE.txt for correct configuration settings. [Cary Fitch] We are running 1.4.22 and this message popped up in console. It could be causing our Queues announcement problem, because if all members

Hello when using Asterisk version 13.12.2 I notice that it takes up to 30 seconds (sometimes even longer) for a call queue to call its members. Example 1 : [Nov 21 08:17:57] pbx.c: Executing [queue at pbx-routing:15] Queue("SIP/incoming-00000246", "myqueue1,,,,300,,,") in new stack [Nov 21 08:17:57] res_musiconhold.c: Started music on hold, class 'default', on

I've noticed that when app_queue.so is reloaded(or just a reload command is used) that all queue members that were paused are automatically unpaused. Is there a workaround for this? (Note, I use statically defined callback agents). --johann

On 21-11-16 15:17, Matthew Jordan wrote: > > On Mon, Nov 21, 2016 at 7:05 AM, Jonas Kellens > <jonas.kellens at telenet.be <mailto:jonas.kellens at telenet.be>> wrote: > > Hello > > when using Asterisk version 13.12.2 I notice that it takes up to > 30 seconds (sometimes even longer) for a call queue to call its > members. > >

Hi all, I'm testing the persistent dynamic queue members functionality on 1.6.0.10. The queue members are agents defined in the agents.conf file. When I issue an asterisk restart and check the queue members again on the CLI, all of them are listed as /invalid/ and there is no way to change this but to unload app_queue.so and load it again. My guess is that the internal AstDB queue

Hi, I'm using queue configuration as follows: - queues from* queues.conf* - queue_members from *external Database thru ODBC*, using* Local channels * as interface - sip extensions from *external Database thru ODBC* When a call is sent from queue to an interface (local channel), it is answered but a message appears at the CLI: *[Nov 4 16:56:04] WARNING[13951]: app_queue.c:3014