VoIP Mailing List Archives

[amartin at xes-inc.com]

Hello,

I am running Asterisk 11 on CentOS 6.x. I have configured several queues as
follows in extensions.conf:
exten => s,1,Queue(myqueue,rtnC,1
same => n,Background(user_unavail)
same => n,WaitExten(10)
exten => 1,1,Voicemail(1111@my-vm,s)

This rings the phones in the queue for 18 seconds. If no queue members answer,
the caller is then prompted to press 1 and leave a voicemail. This works well
when at least 1 member is registered in the queue, however if no members are
registered in the queue, the Queue() call never seems to return, and thus the
remaining steps in the dialplan never execute. How can I correct this behavior
so that even if the queue has no registered members, the dialplan is still
followed?

Thanks,

Andrew

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[johnkiniston at gmail.com]

In your queues.conf do you have a leavewhenempty and joinempty set?

in queues.conf
[myqueue]

leavewhenempty = strict
joinempty = strict
strategy = ringall
ringinuse = no






On Tue, Jul 28, 2015 at 9:58 AM, Andrew Martin <amartin@xes-inc.com (amartin@xes-inc.com)> wrote:

[johnkiniston at gmail.com]

Wow, Looks like they have really increased the options since I last looked.


I just pulled down the Asterisk 13 queues.conf.sample and it's got this in it:

; paused: a member is not considered available if he is paused
; penalty: a member is not considered available if his penalty is less than QUEUE_MAX_PENALTY
; inuse: a member is not considered available if he is currently on a call
; ringing: a member is not considered available if his phone is currently ringing
; unavailable: This applies mainly to Agent channels. If the agent is a member of the queue
;              but has not logged in, then do not consider the member to be available
; invalid: Do not consider a member to be available if he has an "invalid" device state.
;          This generally is caused by an error condition in the member's channel driver.
; unknown: Do not consider a member to be available if we are unable to determine the member's
;          current device state.
; wrapup: A member is not considered available if he is currently in his wrapuptime after
;         taking a call.


An unknown state would be a device that has a valid configuration but isn't registered.


On Tue, Jul 28, 2015 at 8:51 PM, Andrew Martin <amartin@xes-inc.com (amartin@xes-inc.com)> wrote: