Summary: | ASTERISK-09787: Unable to join queue bevor reload | ||
Reporter: | Daniel Gerstner (jacky0815) | Labels: | |
Date Opened: | 2007-07-02 04:03:58 | Date Closed: | 2011-06-07 14:07:51 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_queue |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | I have a test-computer with asterisk 1.4.5 and 1.4.6 to upgrade my system from asterisk 1.2 I have copied the queue.conf from the old version. On startup no queue works (show message in additional information). But when I type "module reload" everything works fine only after (re)-start the asterisk-daemon the queues don't work. On startup no error-message from the queue is printed (verbose 3). So I don't know who is the error. ****** ADDITIONAL INFORMATION ****** Errormessage after dial the queue after startup: app_queue.c:3549 queue_exec: Unable to join queue 'vermittlung' queue.conf: [vermittlung] ; musiconhold = default strategy = ringall servicelevel = 0 maxlen = 3 announce-frequency = 90 periodic-announce-frequency=50 queue-youarenext = queue-youarenext queue-thereare = queue-thereare queue-callswaiting = queue-callswaiting queue-holdtime = queue-holdtime queue-minutes = queue-minutes queue-seconds = queue-seconds queue-thankyou = queue-thankyou queue-lessthan = queue-less-than queue-reporthold = queue-reporthold timeout = 20 reportholdtime = no memberdelay = 0 member => SIP/910 member => Zap/g7 extensions.conf: exten => s-free,n,Queue(vermittlung||||90) | ||
Comments: | By: Joshua C. Colp (jcolp) 2007-07-02 10:46:34 Can you do a Noop(${QUEUESTATUS}) afterwards to see the reason why it was unable to join? Thanks. By: Daniel Gerstner (jacky0815) 2007-07-03 01:22:02 WARNING[6526]: app_queue.c:3549 queue_exec: Unable to join queue 'vermittlung' -- Executing [s-free@macro-vermittlung2:8] NoOp("SIP/100-081fac58", "JOINEMPTY") in new stack By: Joshua C. Colp (jcolp) 2007-07-05 09:43:32 The queue is being considered empty, can you do a queue show <queue name> to see what the member's statuses are? By: Daniel Gerstner (jacky0815) 2007-07-09 10:46:04 after start asterisk: *CLI> queue show vermittlung vermittlung has 0 calls (max 3) in 'ringall' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s Members: Zap/g7 (Invalid) has taken no calls yet SIP/910 (Invalid) has taken no calls yet No Callers after make a "reload": *CLI> queue show vermittlung vermittlung has 0 calls (max 3) in 'ringall' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s Members: Zap/g7 (Unknown) has taken no calls yet SIP/910 (Not in use) has taken no calls yet No Callers By: Joshua C. Colp (jcolp) 2007-07-09 12:44:09 The issue here is module load order. When app_queue is loaded chan_zap and chan_sip aren't so it considers them invalid until reload. What does your modules.conf look like? Can you make it explicitly load chan_zap, chan_sip, and then app_queue? By: Daniel Gerstner (jacky0815) 2007-07-09 14:32:45 my modules.conf: [modules] autoload=yes noload => pbx_gtkconsole.so noload => pbx_kdeconsole.so noload => app_intercom.so noload => chan_modem.so noload => chan_modem_aopen.so noload => chan_modem_bestdata.so noload => chan_modem_i4l.so load => res_musiconhold.so noload => chan_alsa.so [global] When I make an "modules reload app_queue" after new boot it works good. But I can't see any error in the modules.conf By: Joshua C. Colp (jcolp) 2007-07-10 08:34:22 Can you add the following in: load => chan_zap.so load => chan_sip.so load => app_queue.so And see if it fixes the issue? By: Daniel Gerstner (jacky0815) 2007-07-10 08:49:48 It works. Thanks By: Joshua C. Colp (jcolp) 2007-07-18 10:29:24 Module load order issue. |