ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Incoming Call Issue

    Scheduled Pinned Locked Moved IT Discussion
    asteriskfreepbxfreepbx 14voippbxtelephony
    4 Posts 2 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      VoIP_n00b
      last edited by scottalanmiller

      Running FreePBX v14... No resent changes made, except to change the name on an extension.

      When some calls in, and let's say they dial 555 then end up getting 511, 511 can then forward the call to 555 no issue, but I have no idea what is causing this.

      JaredBuschJ 1 Reply Last reply Reply Quote 2
      • JaredBuschJ
        JaredBusch @VoIP_n00b
        last edited by

        @VoIP_n00b said in Incoming Call Issue:

        Running FreePBX v14... No resent changes made, except to change the name on an extension.

        When some calls in, and let's say they dial 555 then end up getting 511, 511 can then forward the call to 555 no issue, but I have no idea what is causing this.

        Because they released a horrible fucking update to IVR.

        Edit your IVR and set strict dial time out to No - legacy

        V 1 Reply Last reply Reply Quote 3
        • JaredBuschJ
          JaredBusch
          last edited by

          https://community.freepbx.org/t/ivr-trouble/62100/3

          1 Reply Last reply Reply Quote 0
          • V
            VoIP_n00b @JaredBusch
            last edited by

            @JaredBusch said in Incoming Call Issue:

            @VoIP_n00b said in Incoming Call Issue:

            Running FreePBX v14... No resent changes made, except to change the name on an extension.

            When some calls in, and let's say they dial 555 then end up getting 511, 511 can then forward the call to 555 no issue, but I have no idea what is causing this.

            Because they released a horrible fucking update to IVR.

            Edit your IVR and set strict dial time out to No - legacy

            That fixed it! Thank you so much!!!

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post