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

sent to invalid extension but no invalid handler: context,exten,priority=restrictedroute-0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.11
    • Fix Version/s: None
    • Environment:
    • ToDo:
    • Distro:
      FreePBX Distro

      Description

      This issue was covered in 2.11.0.5 for Extension Routing, apparently fixed in 2.11.0.6. However, we may have a revisit in 2.11.0.9.

      When this module is enabled, and it is licensed, this is the error.

      sent to invalid extension but no invalid handler: context,exten,priority=restrictedroute-0

      When dialing a 10-digit #, as soon as you hit the 10th digit, you get a fast busy signal. The call never hits the outbound route. Calling extensions works, in and out. My extension is remote and I can call any extension and vice versa.

      Disabling Extension Routes allows you to make outbound calls, once again.

      Debug Info:
      – Executing [8325338604@from-internal:3] GotoIf("SIP/900-00000011", "1?restrictedroute-0,xxxxxxxxxx,2:outbound-allroutes,xxxxxxxxxx,2") in new stack
      – Goto (restrictedroute-0,xxxxxxxxxx,2)
      [2014-06-26 06:20:47] WARNING[4892][C-00000011]: pbx.c:6643 __ast_pbx_run: Channel 'SIP/900-00000011' sent to invalid extension but no invalid handler: context,exten,priority=restrictedroute-0,xxxxxxxxxx,2

      This is the document I found that led me to it.
      http://community.freepbx.org/t/issue-with-extensions-routes-2-11-0-5/21023

      Why are we still having this issue?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                tm1000 Andrew Nagy
                Reporter:
                rhall Roland Hall
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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