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

Outgoing CID dial pattern includes objects that causes trunk to reject call due to incorrect number

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Out of Date
    • Affects Version/s: 14
    • Fix Version/s: None
    • Component/s: Other
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      15.4.0
    • Distro Version:
      14.0.5.2
    • Distro:
      FreePBX Distro

      Description

      FreePBX version 14.0.5.2

      Outgoing calls being rejected by trunk due to invalid number format. 

      Free PBX is outputting additional characters into the dial output string which is causing this error. It has been verified that the trunk is receiving these characters.

      Example output (extraneous characters in red) : 

       
       

      Executing [s@macro-dialout-trunk:32] Dial("SIP/100-00000049", "SIP/digium-siptrunk/*dialed number*@TLC_*outgoing CID*,300,Tb(func-apply-sipheaders^s^1)") in new stack

       
       

       

      Upon checking all CID fields, no fields contain "TLC_" and are set to the correct CID.

      All previous lines in CLI (running in level 5) show correct CID setting being applied.

       

       

      It is possible that this erroneous value was entered and applied to an earlier configuration, but it is no longer present in the GUI and multiple configurations and settings have been tried/reapplied since.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ChrisN ChrisN
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Feedback Requested:

                  NextupJiraPlusStatus

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