asterisk users - Jul 2015 - Queues don't follow dialplan if no members are registered

----- Original Message -----
> From: "John Kiniston" <johnkiniston at gmail.com>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
<asterisk-users at lists.digium.com>
> Sent: Tuesday, July 28, 2015 12:12:05 PM
> Subject: Re: [asterisk-users] Queues don't follow dialplan if no
members are	registered
> 
> In your queues.conf do you have a leavewhenempty and joinempty set?
> 
> in queues.conf
> [myqueue]
> leavewhenempty = strict
> joinempty = strict
> strategy = ringall
> ringinuse = no
> 
> 
John,

Thanks for the fast reply! I had "joinempty=yes" in queues.conf,
which explains why I was seeing this behavior. It looks like the
"strict" setting is partially-deprecated, so instead I'm using
the following combination:

[myqueue]
musiconhold=default
music=default
strategy=ringall
joinempty=unavailable,invalid,unknown
leavewhenempty=unavailable,invalid,unknown
timeout=18

member => SIP/100
member => SIP/101

Is there any reason that using any of these options would be a
problem, in particular "unknown"? It is not very well defined
what an "unknown" state is exactly.

Thanks,

Andrew

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 at xes-inc.com>
wrote:
> ----- Original Message -----
> > From: "John Kiniston" <johnkiniston at gmail.com>
> > To: "Asterisk Users Mailing List - Non-Commercial
Discussion" <
> asterisk-users at lists.digium.com>
> > Sent: Tuesday, July 28, 2015 12:12:05 PM
> > Subject: Re: [asterisk-users] Queues don't follow dialplan if no
members
> are  registered
> >
> > In your queues.conf do you have a leavewhenempty and joinempty set?
> >
> > in queues.conf
> > [myqueue]
> > leavewhenempty = strict
> > joinempty = strict
> > strategy = ringall
> > ringinuse = no
> >
> >
>
> John,
>
> Thanks for the fast reply! I had "joinempty=yes" in queues.conf,
> which explains why I was seeing this behavior. It looks like the
> "strict" setting is partially-deprecated, so instead I'm
using
> the following combination:
>
> [myqueue]
> musiconhold=default
> music=default
> strategy=ringall
> joinempty=unavailable,invalid,unknown
> leavewhenempty=unavailable,invalid,unknown
> timeout=18
>
> member => SIP/100
> member => SIP/101
>
> Is there any reason that using any of these options would be a
> problem, in particular "unknown"? It is not very well defined
> what an "unknown" state is exactly.
>
> 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
>


-- 
A human being should be able to change a diaper, plan an invasion, butcher
a hog, conn a ship, design a building, write a sonnet, balance accounts,
build a wall, set a bone, comfort the dying, take orders, give orders,
cooperate, act alone, solve equations, analyze a new problem, pitch manure,
program a computer, cook a tasty meal, fight efficiently, die gallantly.
Specialization is for insects.
---Heinlein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20150729/660a4c41/attachment-0001.html>

----- Original Message -----
> From: "John Kiniston" <johnkiniston at gmail.com>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
<asterisk-users at lists.digium.com>
> Sent: Wednesday, July 29, 2015 11:53:13 AM
> Subject: Re: [asterisk-users] Queues don't follow dialplan if no
members are	registered
> 
> 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.
> 
John,

Thanks for the clarification and your help resolving this issue!

Andrew