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

    Ping time for VoIP

    Scheduled Pinned Locked Moved IT Discussion
    voipnetwork connectioncomcast
    19 Posts 8 Posters 2.3k Views
    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.
    • EddieJenningsE
      EddieJennings @JaredBusch
      last edited by

      @jaredbusch said in Ping time for VoIP:

      @scottalanmiller said in Ping time for VoIP:

      @eddiejennings said in Ping time for VoIP:

      I think the Networking Gods are screwing with me. I ran traceroute to try to get an idea of the number of hops between FreePBX and I. Everything timed out, except for the last hop (#10), which was the FreePBX host itself, which was a 30ms ping.

      Now, pinging my FreePBX again shows 24ms average with 19/20 echo requests received.

      LOL, there you go. You just had a bad route or something.

      But this is something you need to continually check prior to deploying a system. Because you need to know how stable your ISP is to your host.

      I will be. Unfortunately, I have no choice in ISP. 😞

      DustinB3403D 1 Reply Last reply Reply Quote 0
      • DustinB3403D
        DustinB3403 @EddieJennings
        last edited by

        @eddiejennings said in Ping time for VoIP:

        @jaredbusch said in Ping time for VoIP:

        @scottalanmiller said in Ping time for VoIP:

        @eddiejennings said in Ping time for VoIP:

        I think the Networking Gods are screwing with me. I ran traceroute to try to get an idea of the number of hops between FreePBX and I. Everything timed out, except for the last hop (#10), which was the FreePBX host itself, which was a 30ms ping.

        Now, pinging my FreePBX again shows 24ms average with 19/20 echo requests received.

        LOL, there you go. You just had a bad route or something.

        But this is something you need to continually check prior to deploying a system. Because you need to know how stable your ISP is to your host.

        I will be. Unfortunately, I have no choice in ISP. 😞

        Everyone has a choice, just pay way more money for the choice. .

        EddieJenningsE 1 Reply Last reply Reply Quote 0
        • EddieJenningsE
          EddieJennings @DustinB3403
          last edited by

          @dustinb3403 said in Ping time for VoIP:

          @eddiejennings said in Ping time for VoIP:

          @jaredbusch said in Ping time for VoIP:

          @scottalanmiller said in Ping time for VoIP:

          @eddiejennings said in Ping time for VoIP:

          I think the Networking Gods are screwing with me. I ran traceroute to try to get an idea of the number of hops between FreePBX and I. Everything timed out, except for the last hop (#10), which was the FreePBX host itself, which was a 30ms ping.

          Now, pinging my FreePBX again shows 24ms average with 19/20 echo requests received.

          LOL, there you go. You just had a bad route or something.

          But this is something you need to continually check prior to deploying a system. Because you need to know how stable your ISP is to your host.

          I will be. Unfortunately, I have no choice in ISP. 😞

          Everyone has a choice, just pay way more money for the choice. .

          Correction. There are no choices that will pass the laugh test with the owners.

          DustinB3403D 1 Reply Last reply Reply Quote 3
          • DustinB3403D
            DustinB3403 @EddieJennings
            last edited by

            @eddiejennings said in Ping time for VoIP:

            @dustinb3403 said in Ping time for VoIP:

            @eddiejennings said in Ping time for VoIP:

            @jaredbusch said in Ping time for VoIP:

            @scottalanmiller said in Ping time for VoIP:

            @eddiejennings said in Ping time for VoIP:

            I think the Networking Gods are screwing with me. I ran traceroute to try to get an idea of the number of hops between FreePBX and I. Everything timed out, except for the last hop (#10), which was the FreePBX host itself, which was a 30ms ping.

            Now, pinging my FreePBX again shows 24ms average with 19/20 echo requests received.

            LOL, there you go. You just had a bad route or something.

            But this is something you need to continually check prior to deploying a system. Because you need to know how stable your ISP is to your host.

            I will be. Unfortunately, I have no choice in ISP. 😞

            Everyone has a choice, just pay way more money for the choice. .

            Correction. There are no choices that will pass the laugh test with the owners.

            You mean if they don't die from laughter then it's a no go. . .

            EddieJenningsE 1 Reply Last reply Reply Quote 0
            • EddieJenningsE
              EddieJennings @DustinB3403
              last edited by

              @dustinb3403 Ha!

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

                @jaredbusch said in Ping time for VoIP:

                @scottalanmiller said in Ping time for VoIP:

                @eddiejennings said in Ping time for VoIP:

                I think the Networking Gods are screwing with me. I ran traceroute to try to get an idea of the number of hops between FreePBX and I. Everything timed out, except for the last hop (#10), which was the FreePBX host itself, which was a 30ms ping.

                Now, pinging my FreePBX again shows 24ms average with 19/20 echo requests received.

                LOL, there you go. You just had a bad route or something.

                But this is something you need to continually check prior to deploying a system. Because you need to know how stable your ISP is to your host.

                Very true.

                1 Reply Last reply Reply Quote 1
                • Reid CooperR
                  Reid Cooper
                  last edited by

                  I'd suggest a script that just does a ping say every ten minutes or something slightly more random like every 9.2 minutes so that you don't hit the same times over and over again to avoid any problems from being on even intervals. Then just log the ping times over a few days or weeks. That will give you a really good idea of how much it varies and if time of day is a factor.

                  EddieJenningsE 1 Reply Last reply Reply Quote 1
                  • EddieJenningsE
                    EddieJennings @Reid Cooper
                    last edited by

                    @reid-cooper said in Ping time for VoIP:

                    I'd suggest a script that just does a ping say every ten minutes or something slightly more random like every 9.2 minutes so that you don't hit the same times over and over again to avoid any problems from being on even intervals. Then just log the ping times over a few days or weeks. That will give you a really good idea of how much it varies and if time of day is a factor.

                    Made something like that before I left work. Great minds think alike 🙂

                    1 Reply Last reply Reply Quote 1
                    • bigbearB
                      bigbear @EddieJennings
                      last edited by

                      @eddiejennings said in Ping time for VoIP:

                      I cannot win today.

                      Ping time from FreePBX on Vultr (Atlanta) to Twilio's New Jersey POP averages 13ms.

                      Twilio New Jersey POP? Or do you mean Virginia?

                      1 Reply Last reply Reply Quote 0
                      • bigbearB
                        bigbear
                        last edited by

                        Also have you tested your ping to to NJ/NY data center for VULTR? Might surprise you.

                        I was surprised and ended up moving some things from Chicago to NJ/NY despite it being twice the distance from me as Chicago VULTR instances were (500 miles to Chicago, 1200 miles to NJ/NY). Latency went from 80/90ms to 30ms or less on average when I moved to NJ/NY Vultr instance.

                        .

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