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

Enable inbound routes based on source ip

    XMLWordPrintable

    Details

    • Asterisk Version:
      1.2.18

      Description

      Hello,

      When you receive an incoming call from an inbound route that you have created in, it shows the following information for that call:

      {noformat}
      – Executing NoOp("SIP/5060-b782af20", "Received incoming SIP connection from unknown peer to 514xxxxxxx") in new stack
      – Executing Set("SIP/5060-b782af20", "DID=51490xxxxx") in new stack
      – Executing Goto("SIP/5060-b782af20", "s|1") in new stack
      – Goto (from-sip-external,s,1)
      – Executing Ringing("SIP/5060-b782af20", "") in new stack
      – Executing GotoIf("SIP/5060-b782af20", "1?from-trunk|51490xxxxx|1") in new stack
      – Goto (from-trunk,51490xxxxx,1)
      – Executing Set("SIP/5060-b782af20", "FROM_DID=51490xxxxx") in new stack
      – Executing Gosub("SIP/5060-b782af20", "app-blacklist-check|s|1") in new stack
      – Executing LookupBlacklist("SIP/5060-b782af20", "") in new stack
      – Executing GotoIf("SIP/5060-b782af20", "0?blacklisted") in new stack
      – Executing Return("SIP/5060-b782af20", "") in new stack
      – Executing Goto("SIP/5060-b782af20", "ivr-2|s|1") in new stack{noformat}

      Now, it shows that "Received incoming SIP connection from unknown peer to 514xxxxxxx" instead of matching the SIP IP address to one of the inbound trunks that we have.
      Could this be fixed so that we can properly use the trunk with the inbound parameters?
      Or is this just a cosmetical thing?

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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