Ring Strategy "linear" not working properly

MAA · May 20, 2021, 3:45pm

FreePBX 13.0.197.28
Asterisk Version: 13.29.2
Queues Version 13.0.34.18

Ring Strategy = “linear” not working properly.

For example: I have order 101,102,103
but i get ring 102,101,103

adell4444 · May 20, 2021, 5:09pm

Are they dynamic agents? Linear will ring them in the order that they logged in, not the order they are listed.

MAA · May 21, 2021, 10:07am

Static Agents only

PitzKey · May 21, 2021, 11:55am

If the ring strategy was once different than linear, then you need to restart Asterisk for the changes to go into effect.
https://issues.asterisk.org/jira/browse/ASTERISK-17049

MAA · May 24, 2021, 11:32am

PitzKey
you need to restart Asterisk for the changes to go into effect

Thank you.
I am very surprised that this bug has not been fixed yet.

jcolp · May 24, 2021, 11:42am

It’s up to someone to take it through the review process and get it submitted, which noone has done.

tonyclewis · May 24, 2021, 9:36pm

Or someone with a PBXact support contract can report the issue which will require it to be fixed under the PBXact commercial support and license agreement.

david55 · May 25, 2021, 11:33am

I was under the impression that this was a documented restriction, and therefore any request to change it would be a feature request, rather than a bug report.

PitzKey · May 25, 2021, 1:25pm

Can you please post a link to where it is documented? Thanks

lgaetz · May 25, 2021, 1:27pm

As a result of this thread, I have added a note to the freepbx wiki, but it is only been there since yesterday:
https://wiki.freepbx.org/display/FPG/Queues+Module+User+Guide#QueuesModuleUserGuide-RingStrategy

PitzKey · May 25, 2021, 4:55pm

Thank you, Lorne!

david55 · May 25, 2021, 8:29pm

It’s documented in the Asterisk source code, and in the Asterisk logs of any system that tries to change to the linear strategy, and has warnings enabled:

github.com

asterisk/asterisk/blob/master/apps/app_queue.c#L3315


      
          		} else if (!strcasecmp(option, "unknown")) {
          			*empty |= QUEUE_EMPTY_UNKNOWN;
          		} else if (!strcasecmp(option, "loose")) {
          			*empty = (QUEUE_EMPTY_PENALTY | QUEUE_EMPTY_INVALID);
          		} else if (!strcasecmp(option, "strict")) {
          			*empty = (QUEUE_EMPTY_PENALTY | QUEUE_EMPTY_INVALID | QUEUE_EMPTY_PAUSED | QUEUE_EMPTY_UNAVAILABLE);
          		} else if ((ast_false(option) && joinempty) || (ast_true(option) && !joinempty)) {
          			*empty = (QUEUE_EMPTY_PENALTY | QUEUE_EMPTY_INVALID | QUEUE_EMPTY_PAUSED);
          		} else if ((ast_false(option) && !joinempty) || (ast_true(option) && joinempty)) {
          			*empty = 0;
          		} else {
          			ast_log(LOG_WARNING, "Unknown option %s for '%s'\n", option, joinempty ? "joinempty" : "leavewhenempty");
          		}
          	}
          }
          
          /*! \brief Configure a queue parameter.
           *
           * The failunknown flag is set for config files (and static realtime) to show
           * errors for unknown parameters. It is cleared for dynamic realtime to allow
           *  extra fields in the tables.

The real bug is that this details hasn’t been added to queues.conf.sample, and therefore other documentation.

The reason for it is that Asterisk uses hashing to access the member list, but that means that the hash buckets get read out firstly in order of the hashed value, and only then in order of addition. When you start with the linear strategy, it forces there to be only one hash bucket, loosing the advantages of hashing, but meaning that everything is in the order in which it was added to the list of queue members.

system · June 25, 2021, 8:29pm

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.