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

Confirm Call on Ring-group fails when Ringing Extension with Follow Me

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 14
    • Fix Version/s: None
    • Component/s: Follow Me, Ring Groups
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      16.3.0
    • Distro Version:
      14.0.11
    • Distro:
      FreePBX Distro

      Description

      When I send a call through a ring group with confirm call enabled to an extension with follow me enabled I get the “I’m sorry, the incoming call is no longer available or has been answered elsewhere,” message. 

      I’m running asterisk 16.3.0, my followme and ringgroups modules are both updated.

      Confirm call does seem to work when putting the external number in the ring group, or by dialing the extension with follow me. The problems happens when you put an extension with an external number in follow me in the ring group.

      I was able to reproduce this on another server with up-to-date modules and running asterisk 16.3.0. But when testing on a server with only the ringgroups and followme modules updates, I didn’t encounter this problem. Maybe it’s due to a combination of those three things?

       

      Asterisk Output:

      Executing [s@macro-confirm:1] Set("Local/200@from-internal-00000009;1", "LOOPCOUNT=0") in new stack
      – Executing [s@macro-confirm:2] Set("Local/200@from-internal-00000009;1", "__MACRO_RESULT=ABORT") in new stack
      – Executing [s@macro-confirm:3] NoOp("Local/200@from-internal-00000009;1", " and arv= ") in new stack
      – Executing [s@macro-confirm:4] ExecIf("Local/200@from-internal-00000009;1", "0?Set(ARG1=)") in new stack
      – Executing [s@macro-confirm:5] ExecIf("Local/200@from-internal-00000009;1", "0?Set(ALT_CONFIRM_MSG=)") in new stack
      – Executing [s@macro-confirm:6] Set("Local/200@from-internal-00000009;1", "MSG1=incoming-call-1-accept-2-decline") in new stack
      – Executing [s@macro-confirm:7] BackGround("Local/200@from-internal-00000009;1", "incoming-call-1-accept-2-decline,m,en,macro-confirm") in new stack
      – <Local/200@from-internal-00000009;1> Playing 'incoming-call-1-accept-2-decline.slin' (language 'en')
      – Channel Local/8638000311@from-internal-0000000a;1 joined 'simple_bridge' basic-bridge <1f83ae38-9b44-429c-9bf4-fb49ba05af9c>
      – Channel Local/200@from-internal-00000009;2 joined 'simple_bridge' basic-bridge <1f83ae38-9b44-429c-9bf4-fb49ba05af9c>
      – Channel PJSIP/Voipms-0000000b joined 'simple_bridge' basic-bridge <c5eeca15-d631-4339-a701-784d9ebdc318>
      > 0x7fea403805f0 – Strict RTP switching to RTP target address 162.254.144.173:14832 as source
      – Channel Local/8638000311@from-internal-0000000a;2 joined 'simple_bridge' basic-bridge <c5eeca15-d631-4339-a701-784d9ebdc318>
      – Executing [1@macro-confirm:1] GotoIf("Local/200@from-internal-00000009;1", "1?toolate,1") in new stack
      – Goto (macro-confirm,toolate,1)
      – Executing [toolate@macro-confirm:1] Set("Local/200@from-internal-00000009;1", "MSG2="incoming-call-no-longer-avail"") in new stack
      – Executing [toolate@macro-confirm:2] Playback("Local/200@from-internal-00000009;1", ""incoming-call-no-longer-avail"") in new stack
      – <Local/200@from-internal-00000009;1> Playing 'incoming-call-no-longer-avail.slin' (language 'en')

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  matthewljensen Matthew Jensen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

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