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

dialparties.agi ends up with wrong dialstring after call hits multiple ring groups then all-busy condition

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 14
    • Fix Version/s: None
    • Component/s: Ring Groups
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      Asterisk 16.11.1 built by mockbuild @ jenkins7 on a x86_64 running Linux on 2020-07-20 19:57:13 UTC
    • Distro Version:
      SNG7
    • Distro:
      FreePBX Distro

      Description

      Call rings in and is routed through time conditions to Ring-Group 00:

      [2020-08-27 11:24:37] VERBOSE[30180][C-00001523] pbx_builtins.c: Goto (ext-group,00,1)

      Since x314 was engaged and CallWaiting disabled, dialstring became 300-304 and executed:

      [2020-08-27 11:24:37] VERBOSE[30180][C-00001523] pbx.c: Executing [s@macro-dial:21] ExecIf("PJSIP/nexVortex_MASSACHUSETTS-00003a3f", "0?Set(ds=SIP/99300&PJSIP/300/sip:300@151.181.87.210:23555;x-ast-orig-host=192.168.3.33:13410&SIP/99304&PJSIP/304/sip:304@151.181.87.210:15310;x-ast-orig-host=192.168.3.84:5210,11,HhtrQ(NO_ANSWER)M(auto-blkvm)g)") in new stack

      x300 answers and transfers to Ring Group 373:

      [2020-08-27 11:24:43] VERBOSE[30180][C-00001523] app_dial.c: PJSIP/300-00003a40 answered PJSIP/nexVortex_MASSACHUSETTS-00003a3f
      [2020-08-27 11:24:52] VERBOSE[30180][C-00001523] res_musiconhold.c: Started music on hold, class 'abmahaitian', on channel 'PJSIP/nexVortex_MASSACHUSETTS-00003a3f'
      ⋮
      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx_builtins.c: Goto (from-internal,373,8)
      ⋮
      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx.c: Executing [373@from-internal:21] Macro("PJSIP/300-00003a43", "dial,11,m(abmahaitian)HhTt,314") in new stack
      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx.c: Executing [s@macro-dial:1] NoOp("PJSIP/300-00003a43", "Blind Transfer: , Attended Transfer: , User: 300, Alert Info: ") in new stack

      Since everyone was busy:

      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx.c: Executing [s@macro-dial:7] NoOp("PJSIP/300-00003a43", "Returned from dialparties with no extensions to call and DIALSTATUS: BUSY") in new stack

      per Ring Group 373 settings the destination is now 374, the "overflow" Ring Group:

      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx.c: Executing [373@from-internal:30] Goto("PJSIP/300-00003a43", "ext-group,374,1") in new stack
      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx_builtins.c: Goto (ext-group,374,1)

      the "dial" macro is then executed with the correct parameters, 306-310-315-314 belong to this Ring Group 374:

      [2020-08-27 11:24:53] VERBOSE[30186][C-00001525] pbx.c: Executing [374@ext-group:21] Macro("PJSIP/300-00003a43", "dial,20,m(abmahaitian)HhTt,306-310-315-314") in new stack

      HOWEVER, SOMETHING STRANGE HAPPENS HERE AND WE END UP with 304 (who, incidentally, is in the first ring group that answered this incoming call, directly off the inbound route from the time conditions to ring group "00") RINGING THE MEMBERS OF THE "00" RING GROUP THAT THE CALL FIRST HIT AFTER TIME CONDITIONS:

      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Added extension 300 to extension map
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Added extension 304 to extension map
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Added extension 314 to extension map
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 300 cf is disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 304 cf is disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 314 cf is disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 300 do not disturb is disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 304 do not disturb is disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 314 do not disturb is disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: EXTENSION_STATE: 1 (INUSE_ORIGINATOR)
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 300 has ExtensionState: 1
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Checking CW and CFB status for extension 300
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 300 is not available to be called
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 300 has call waiting disabled
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: EXTENSION_STATE: 0 (NOT_INUSE)
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Extension 304 has ExtensionState: 0
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Checking CW and CFB status for extension 304
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Discovered PJSIP Endpoint PJSIP/304
      [2020-08-27 11:24:54] VERBOSE[30186][C-00001525] res_agi.c: dialparties.agi: Ended up with real PJSIP Dial string PJSIP/304/sip:304@151.181.87.210:15310;x-ast-orig-host=192.168.3.84:521

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  asiplas Andrew Siplas
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    NextupJiraPlusStatus

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