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

Firewall not including AOR Contacts 2+ in iptables chain fpbxregistrations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: 14
    • Fix Version/s: None
    • Component/s: Firewall
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13.38.2
    • Distro Version:
      12.7.8-2104-1.sng7
    • Distro:
      FreePBX Distro

      Description

      When a PJSIP Extension has multiple contacts, Firewall is not adding contacts 2+ to theĀ fpbxregistrations chain. This makes it so that those devices cannot reach provisioning (HTTP, HTTPS, etc) services.

      For example:

      
       Endpoint:  9898922828114/9898922828114                          Not in use    0 of inf
           InAuth:  9898922828114-auth/9898922828114
              Aor:  9898922828114                                      2
            Contact:  9898922828114/sip:9898922828114@1.2.3.4 d3a02653fe Avail        34.621
            Contact:  9898922828114/sip:9898922828114@2.3.4.5 fd8ee3446f Avail       229.097
        Transport:  0.0.0.0-tls               tls      5    184  0.0.0.0:7061
      
      

      In this example, 1.2.3.4 will get added to fpbxregistrations, but 2.3.4.5 will not.

      
      -A fpbxregistrations -s 1.2.3.4/32 -j fpbxknownreg
      

      Hoping this can be fixed quickly so that these endpoints can reach the provisioning services to pick up their new configs as they have invalid subscriptions filling up the logs and asterisk console.

      Thanks,

      Dave

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                david.sovereen@mercury.net David Sovereen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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