Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-11017

Use namedpickupgroup instead of pickupgroup



    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 13
    • Component/s: Asterisk SIP Settings
    • Labels:
    • Distro:
      FreePBX Distro


      Currently the number of "numeric callgroups" is limited to 64. If 'namedcallgroup' and 'namedpickupgroup' settings are used in sip configs, then number of call groups are unlimited and also can be alpha/numeric.

      For example-I want to use directed call pickup on handset but this allows me to pick up any BLF that's ringing on the handset. This is not good from a security standpoint. I have to use group call pickup so I can create an "access control list for call pickup permissions". Now I am limited to 64 groups unless I want to add the config manually in the custom_post config files.

      While using named call/pickup groups, we could set the call group the same as the extension number. Then you don't have to remember or note group names or members. I can just assign permissions by typing in the extension number(s) in the pickup group list on the web GUI.

      I was able to modify the /function.inc.php in freepbx version 12 to get this to work on my test box. I changed the variables from 'pickupgroup' and 'callgroup' to 'namedpickupgroup' and 'namedcallgroup'.

      Can we get this working in FreePBX Distro 13?

        Gliffy Diagrams


          1. Dahdi.class.php
            5 kB
            Dustin Howard
          2. PJSIP_Settings_001.png
            39 kB
            Tom Ray
          3. Sip.class.php
            22 kB
            Dustin Howard

            Issue Links



                • Assignee:
                  jfinstrom James Finstrom
                  dhoward Dustin Howard
                • Votes:
                  0 Vote for this issue
                  8 Start watching this issue


                  • Created:


                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.