[asterisk-bugs] [JIRA] (ASTERISK-19577) Overcoming 64 callgroup / pickupgroup limit by creating "group contexts"

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225156#comment-225156 ] 

Matt Jordan commented on ASTERISK-19577:
----------------------------------------

I know this issue has been open for awhile, and the improvement hasn't been applied. I'm sorry we didn't get to it - since this issue was opened, we've made it easier to get code reviewed/included by letting anyone who has a contributor license agreement push the patch up to review board. While that doesn't help this issue, hopefully any contributions made in the future will get reviewed/included faster.

Unfortunately, a different approach was taken in Asterisk 11 to this patch by allowing the use of named callgroups/pickupgroups, which essentially gives an unlimited number of groups that can be created.

Since an alternative approach ended up being used, I'm going to close this issue out as Won't Fix.



> Overcoming 64 callgroup / pickupgroup limit by creating "group contexts"
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-19577
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19577
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: General
>    Affects Versions: 1.8.10.0
>         Environment: Any
>            Reporter: Alex
>            Assignee: Alex
>            Severity: Minor
>         Attachments: asterisk_caller_group_context_trunk.patch
>
>
> Supplied patch allows to overcome 64 callgroup / pickup group limit by adding "groupcontext" parameter to peers and channels. Each group context (int ID) from the user point of view is a virtual independent set of 64 call/pickup groups. From the developer's perspective, this is just an integer that gets compared along with group mask.
> Result is: call pickup is now determined not only by group mask, but also by the "group context" ID. Pickups between group contexts are impossible. It's suitable for large installations, where each client requires its own pickup group.
> The patch was made to be as inobtrusive as possible, just extending existing functionality.
> The one and only known limitation is with mISDN channels (mISDN is modded in the patch to always use the default group context 0, because group configuration here is integrated with the binary structure I did not want to change). Maybe someone more knowledgeable with the mISDN module can improve that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)