ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    PJSIP trunk- endpoint not found

    IT Discussion
    pjsip trunk vitalpbx
    4
    5
    1.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • RomoR
      Romo
      last edited by

      Getting a strange issue, with my PJSIP trunks all of a sudden. They are SKyetel pjsip trunkgs and they have been working perfectly fine for the last weeks but all of sudden I get the following in the logs:

      [2020-03-04 14:33:47] WARNING[16477] res_pjsip_endpoint_identifier_ip.c: Identify 'bf' points to endpoint 'bf' but endpoint could not be found
      

      If I do a pjsip show endpoints in the cli the trunk is not there. As if no trunk was configured, nothing I seem to do makes me be able to recover the ability of the trunk to properly create a pjsip endpoint and the trunk is basically completely down.

      Anyone seen something like this before

      1 Reply Last reply Reply Quote 1
      • JaredBuschJ
        JaredBusch
        last edited by

        Since I assume that you are not using raw asterisk, the obvious answer is to check your PBX distro settings.

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @JaredBusch
          last edited by

          @JaredBusch said in PJSIP trunk- endpoint not found:

          Since I assume that you are not using raw asterisk, the obvious answer is to check your PBX distro settings.

          VitalPBX. Been through every setting. First, they were working yesterday, no config changes made. Second, they match Skyetel's documented configs. Third, they match other VitalPBX on Skyetel that are still working. All identical patch levels.

          So while easily we've missed something, we've compared against a lot to see what is configured wrong and can't find anything.

          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender
            last edited by

            any firewall differences/changes?

            1 Reply Last reply Reply Quote 0
            • RomoR
              Romo
              last edited by

              Found the issue and fixed it.

              There were some extra entries in the default pjsip profile which were the culprit. The entries were there since quite a few versions back and hadn't caused any sort of issue with the trunks until we updated yesterday. Even after reverting to the previous working version, the trunks wouldn't get properly created until I found the extra entries and removed them. After that, the endpoints are created and the trunks are up once again.

              1 Reply Last reply Reply Quote 1
              • 1 / 1
              • First post
                Last post