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

    Solved FreePBX showing trunks available but Skyetel showing down ...

    IT Discussion
    freepbx skyetel
    1
    3
    354
    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.
    • B
      BraswellJay
      last edited by

      We are in the process of changing our WAN access and I activated the new WAN port this afternoon. I had thought that I could create a new IP group in the Skyetel portal and copy the trunk defintions from the old WAN IP address to create new trunks in FreePBX. I did this and FreePBX is showing the trunks as online :

      9c7986f9-cedb-40b5-8329-791ed78cc015-image.png

      7bdafbae-f301-43c6-9c56-8c91adf3e3af-image.png

      However the Skyetel portal is showing the status as offline:

      1b28f87e-0d71-4b53-8785-6db9987f3811-image.png

      I figure this must be a firewall rule issue on the new WAN port but I can't see it. The rules are the same on both ports. How does Skyetel determine the health of a link?

      B 2 Replies Last reply Reply Quote 0
      • B
        BraswellJay @BraswellJay
        last edited by

        @BraswellJay

        Turned out to be a SIP port issue. I remember when I set this particular site up I ended up using port 5160 instead of 5060 but when I configured the new IP group in the skyetel portal I didn't change to the correct port. Once I made that change the portal now shows the new interface as healthy.

        1 Reply Last reply Reply Quote 2
        • B
          BraswellJay @BraswellJay
          last edited by

          @BraswellJay

          According to this link https://support.skyetel.com/hc/en-us/articles/360041178573-IP-Health it is a just a ping to determine if the interface is up. I'm able to ping the new WAN interface from other devices.

          1 Reply Last reply Reply Quote 0
          • B
            BraswellJay @BraswellJay
            last edited by

            @BraswellJay

            Turned out to be a SIP port issue. I remember when I set this particular site up I ended up using port 5160 instead of 5060 but when I configured the new IP group in the skyetel portal I didn't change to the correct port. Once I made that change the portal now shows the new interface as healthy.

            1 Reply Last reply Reply Quote 2
            • B BraswellJay has marked this topic as solved on
            • 1 / 1
            • First post
              Last post