I have the same symptoms but much more info at this point.
System is: CentOS 5.3, Asterisk 1.6.1.0, FreePBX 2.5.1. the problem has existed from the beginning (about 2 weeks ago).
From a fresh boot, all active SIP phones register properly as below:
Name/username Host Dyn Nat ACL Port Status
6001/6001 10.1.6.71 D N A 5060 OK (8 ms)
6002/6002 10.1.6.72 D N A 5060 OK (7 ms)
6003/6003 10.1.6.73 D N A 5060 OK (10 ms)
6004/6004 10.1.6.74 D N A 5060 OK (10 ms)
6005/6005 10.1.6.75 D N A 5060 OK (9 ms)
6006/6006 10.1.6.76 D N A 5060 OK (9 ms)
6007/6007 10.1.6.77 D N A 5060 OK (10 ms)
6008/6008 10.1.6.78 D N A 5060 OK (9 ms)
6009/6009 10.1.6.79 D N A 5060 OK (11 ms)
6010/6010 10.1.6.80 D N A 5060 OK (10 ms)
These devices are associated with users (operating in users-and-devices mode)and are static members in the queues (there are several, they all behave the same).
The queues will show all members as (invalid) initially, any calls sit in the queue, and go nowhere. I don’t know WHY/HOW we get to this state.
asterisk*CLI> queue show
100 has 0 calls (max unlimited) in ‘ringall’ strategy (2s holdtime), W:0, C:0, A:0, SL:0.0% within 0s
Members:
Local/6204@from-internal/n (Invalid) has taken no calls yet
Local/6103@from-internal/n (Invalid) has taken no calls yet
Local/6201@from-internal/n (Invalid) has taken no calls yet
Local/6205@from-internal/n (Invalid) has taken no calls yet
Local/6602@from-internal/n (Invalid) has taken no calls yet
Local/6104@from-internal/n (Invalid) has taken no calls yet
Local/6222@from-internal/n (Invalid) has taken no calls yet
Local/6202@from-internal/n (Invalid) has taken no calls yet
Local/6101@from-internal/n (Invalid) has taken no calls yet
No Callers
If I simply reload the queues, all is well.
asterisk*CLI> module reload app_queue.so
– Reloading module ‘app_queue.so’ (True Call Queueing)
== Parsing ‘/etc/asterisk/queues.conf’: == Found
== Parsing ‘/etc/asterisk/queues_general_additional.conf’: == Found
== Parsing ‘/etc/asterisk/queues_custom_general.conf’: == Found
== Parsing ‘/etc/asterisk/queues_custom.conf’: == Found
== Parsing ‘/etc/asterisk/queues_additional.conf’: == Found
== Parsing ‘/etc/asterisk/queues_post_custom.conf’: == Found
asterisk*CLI> queue show
100 has 0 calls (max unlimited) in ‘ringall’ strategy (2s holdtime), W:5, C:1, A:0, SL:0.0% within 0s
Members:
Local/6204@from-internal/n (Not in use) has taken no calls yet
Local/6103@from-internal/n (Not in use) has taken no calls yet
Local/6201@from-internal/n (Not in use) has taken no calls yet
Local/6205@from-internal/n (Not in use) has taken no calls yet
Local/6602@from-internal/n (Not in use) has taken no calls yet
Local/6104@from-internal/n (Not in use) has taken no calls yet
Local/6222@from-internal/n (Not in use) has taken no calls yet
Local/6202@from-internal/n (Not in use) has taken no calls yet
Local/6101@from-internal/n (Not in use) has taken 1 calls (last was 3 secs ago)
If I reboot the system, or if asterisk segfaults (as it does about 6 times a day, but that’s another post) then the queues come back up non-operational. I tend to think the queues are getting initialized before the SIP channel is initialized, or before the phones are registered.
Your thoughts on this would be greatly appreciated as it is business impacting. At the moment, I just keep a console up to the server on my desk and reload the queues when there’s an issue.
Tim