0

Queue Time-Out

Darren Wright

February 15, 2018 17:50

None

Follow

Hi all.

very new to this and i am wondering if anyone can help. I'm used to asterisk and i know these are built on that in the back end so this feature should be available.

After 50 seconds of ringing a queue (inbound call coming in), I want the call to failover to a second queue which rings an extension which has a ring mobile and rings a mobile number, but i cannot get this to work.

It looks like you cannot set the retry in the queue to 0, just defaults back to 5 seconds.

Is there a way of getting the call to failover after a certain amount of time? 

• Facebook
• Twitter
• LinkedIn

2 comments

• 0
  
  Bradley Bennell February 16, 2018 15:32

  I spent hours fiddling with this last night too... 
  Only reason I tried to configure the incoming call to go to a queue and then eventually to a failover extension was because ring groups doesn't seem to work the way one would expect.
  Instead of a queue, one would think that you could just route an inbound call to a ring group (which consists of an extension group and various other single extensions) set to ring sequentially. The group of extensions in the ring group don't ring together...they either ring sequentially or just the first extension in the group rings and none of the others before moving on to the next single extension.
  I tried to resolve this by creating a queue instead than then failsover but that doesn't seem to be possible either.

• 0
  
  Larry Neblett February 17, 2018 15:58

  To both -

  It might help to know which product is in play and the firmware in use on same.

   

  Bradley - your last paragraph is somewhat confusing as you write about a ring group "set to ring sequentially" and then in the next sentence suggest that there is an issue in that they ring sequentially. If you want the extensions to all ring simultaneously, then select "ring all" in the ring strategy. I tested this on a S20 (30.6.0.20) using a ring group with both using both individual extensions as well as a defined group and all worked as advertised. 

   

  Darren - some systems do not use the user extension settings when the call is "system owned". By this I mean that if you have extensions that have the use cell also setting, they may ignore this as should the call go and then be answered by that person's cellular voice mail (cell off, out of range, call rejected, etc.), then the call control is no longer owned by the system, but by that person's cell. Granted, there may be some who find this acceptable, but not all do.

   

  Now then, there are others that do allow external extensions and cells to some degree and as Yeastar is still a rather new product that is evolving, perhaps this will come about. About the only thing you might try is to use the extension with the cell itself as a fail-over rather than another Q.