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

Sip trunk port cant be same as bind address

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Support
    • Affects Version/s: 15.0.17.11
    • Fix Version/s: None
    • Component/s: Asterisk SIP Settings
    • Labels:
      None
    • Asterisk Version:
      16.13.0
    • Distro Version:
      FreePBX 15.0.17.24
    • Distro:
      FreePBX Distro

      Description

      Sip trunks will no longer connect by either pjsip or chansip if they have the same bind port as the sip trunk.

      For example sipgate.co.uk trunks require port 5060, if I try to set up a trunk using pjsip (on bind port 5060) the provider does not respond to registration requests. If I change the bind port for pjsip to anything other than 5060 it all works fine.  

      The same happens if I use legacy chansip (the bind port cant be the same as the sip trunk port). The wireshark trace does nor see any response from the registration request.

      This was never a problem in the past (version 13.0.197.28) in fact many tutorials say its best to use 5060 at both ends.

      Because sipgate.co.uk required port 5060 for sip trunks moving to the new version of FreePBX would be extremely problematic. Please can you help ?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bakelite bakelite
              • 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.