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

Follow Me blocked by permission from class of service



    • ToDo:
    • Asterisk Version:
    • Distro Version:
    • Distro:
      FreePBX Distro


      I use comm. module "class of service" to restrict extension avoiding outbound to external extension. Restricted extensions are routed to a dummy trunk with an annoucement.

      In combination with "Follow Me" the wrong permission is used. Follow me is blocked if the caller isn't allowed to use the outbound route to external trunk even if the "follow me" extension has the right to call out.


      Ext. 100 is routed to dummy trunk

      Ext. 200 is routed to outbound trunk; follow me active to an external number with hash like 004179XXXX#.

      ext 100 calls ext. 200 --> follow me to external number  ==> blocked hangs-up

      Example with external inbound:

      external number (from-pstn) --> call 200 --> follow me to ext. number ==> blocked hangs-up

      As soon as I assign the allowed outbound route to ext. 100 in class of service following is working. (not possible for external numbers)

      My finding in log:

      Follow me starts correctly. Reported caller-id in "dialparties.agi" is ext. 100 or DID of ext. caller. "ROUTEUSER" is ext. 100 resp. ext DID. As consequence class of service asssigns the blocked route or can't find caller id. 

      Correct behavior from my point of view should be:

      • for routing permission the extension with follow me should be used (in my example ext. 200).
      • For display purpose the original caller id (eg. ext. 100 or external DID) should be used (as is now).

      Thank you for correcting it.


        Gliffy Diagrams




              • Assignee:
                jphilip Philip Joseph
                enrica_r Enrica Ruedin
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created:


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