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

BYE message in TLS trunk generating errors and are not sent

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core - Trunks/Routing
    • Labels:
    • Bug Tracker:
      Customer Issue
    • Kayako Ticket IDs:
    • ToDo:
    • Asterisk Version:
      18.14.0
    • Distro Version:
      16.0.21.18
    • Distro:
      FreePBX Distro

      Description

      When sending a BYE in an inbound call in a TLS trunk, PJSIP throws the following error:
       
      ERROR[6320]: res_pjsip/pjsip_transport_events.c:160 verify_log_result: Transport 'x.x.x.x-tls' to remote '1.2.3.4' - The server identity does not match to any identities specified in the certificate

      See attached screenshot of a SIP ladder presenting the problem. The BYE from FreePBX is marked, and this does not seem to arrive to the far end, which is why they send their own BYE after a while (to which FreePBX responds with a 481).

      The expected correct behavior would be the BYE from FreePBX actually getting sent out (to the correct TCP port), and the error message would not be displayed.

      Additional information: the TLS trunk is set up using the FQDN of the far end system, not as an IP address.

      Found this issue in PJSIP/pjporject:

      https://github.com/pjsip/pjproject/issues/2706

      Upon further testing the above PJPROJECT issue appears to have been nailing the problem: in case PJSIP (and so Asterisk/FreePBX) handles an inbound call on a TLS trunk, and needs to end the call, it fails.

      The issue does not happen with outbound calls in the TLS trunk.

       

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                pekkaar pekkaar
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:

                  NextupJiraPlusStatus

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