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

    VoIP One-way Audio and Voice drops

    IT Discussion
    voip freepbx meraki sip
    9
    215
    119.7k
    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.
    • S
      scottalanmiller
      last edited by

      Wow, so now to track down the packet loss. If the desktops don't see it.... where is it coming from?

      What is the packet loss when trying to hit your firewall? What about hitting the router on the other end of the WAN?

      C 1 Reply Last reply Reply Quote 0
      • ?
        A Former User
        last edited by

        Is the PBX still running in Hyper-V?

        C 1 Reply Last reply Reply Quote 0
        • C
          coliver @scottalanmiller
          last edited by

          @scottalanmiller said:

          Wow, so now to track down the packet loss. If the desktops don't see it.... where is it coming from?

          What is the packet loss when trying to hit your firewall? What about hitting the router on the other end of the WAN?

          PBX
          2015-06-03 09_21_29-root@pbx_~.png

          Desktop
          2015-06-03 09_21_38-Windows PowerShell.png

          1 Reply Last reply Reply Quote 0
          • C
            coliver @A Former User
            last edited by

            @thecreativeone91 said:

            Is the PBX still running in Hyper-V?

            It is, I don't have another option right now.

            1 Reply Last reply Reply Quote 0
            • S
              scottalanmiller
              last edited by

              So no issues hitting the local firewall. Now the other wise of the WAN but still "local"?

              C 1 Reply Last reply Reply Quote 0
              • A
                art_of_shred Banned
                last edited by

                You don't have a Broadcom NIC, by chance?

                C 1 Reply Last reply Reply Quote 0
                • C
                  coliver @art_of_shred
                  last edited by

                  @art_of_shred said:

                  You don't have a Broadcom NIC, by chance?

                  All Intel.

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User
                    last edited by

                    I really think it's related to the Hyper-V Nic Driver & Linux. Make sure the Hyper-V host has all windows updates installed. You could also Disable VMQ and Disable Large Send Offload Version 2

                    C 1 Reply Last reply Reply Quote 2
                    • C
                      coliver @A Former User
                      last edited by

                      @thecreativeone91 said:

                      I really think it's related to the Hyper-V Nic Driver & Linux. Make sure the Hyper-V host has all windows updates installed. You could also Disable VMQ and Disable Large Send Offload Version 2

                      I moved to a different host last night. I disabled VMQ, not Large Send Offload though, I will look into that.

                      1 Reply Last reply Reply Quote 0
                      • C
                        coliver @scottalanmiller
                        last edited by

                        @scottalanmiller said:

                        So no issues hitting the local firewall. Now the other wise of the WAN but still "local"?

                        This is the WAN access IP address.

                        PBX
                        2015-06-03 09_29_40-root@pbx_~.png

                        Desktop
                        2015-06-03 09_29_49-Select Windows PowerShell.png

                        1 Reply Last reply Reply Quote 0
                        • S
                          StrongBad
                          last edited by

                          Tested that ping and did not see any errors.

                          1 Reply Last reply Reply Quote 0
                          • S
                            scottalanmiller
                            last edited by

                            Yup, testing from here and not seeing packet loss. Looks good at the WAN side, as far as the pure WAN link.

                            1 Reply Last reply Reply Quote 0
                            • C
                              coliver
                              last edited by

                              I've tested it from my house as well and it works fine. So that tells me it is something internal.

                              Have people had issues running a PBX on Hyper-V? I've heard about the linux driver issues that 2008 had, but I was fairly certain that those had been resolved.

                              ? 1 Reply Last reply Reply Quote 0
                              • J
                                JaredBusch
                                last edited by

                                I run PBX in a Flash and Free PBX on Hyper-V no issues.

                                I have ran Elastix 2.4 as a demo on Hyper-V.

                                1 Reply Last reply Reply Quote 1
                                • ?
                                  A Former User @coliver
                                  last edited by

                                  @coliver said:

                                  I've tested it from my house as well and it works fine. So that tells me it is something internal.

                                  Have people had issues running a PBX on Hyper-V? I've heard about the linux driver issues that 2008 had, but I was fairly certain that those had been resolved.

                                  Are you running it as a Generation 1 or Generation 2 VM?

                                  C 1 Reply Last reply Reply Quote 0
                                  • C
                                    coliver @A Former User
                                    last edited by

                                    @thecreativeone91 said:

                                    @coliver said:

                                    I've tested it from my house as well and it works fine. So that tells me it is something internal.

                                    Have people had issues running a PBX on Hyper-V? I've heard about the linux driver issues that 2008 had, but I was fairly certain that those had been resolved.

                                    Are you running it as a Generation 1 or Generation 2 VM?

                                    Generation 1

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      coliver
                                      last edited by coliver

                                      More ping data all started at about the same time for about the same length.

                                      VM Host 1 - Windows and Linux Server
                                      Windows Server
                                      2015-06-03 09_54_06-ssi-mail - Remote Desktop Connection.png
                                      Linux Server
                                      2015-06-03 09_54_17-coliver@localhost_~.png

                                      VM Host 2 - PBX
                                      PBX
                                      2015-06-03 09_54_25-root@pbx_~.png

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        scottalanmiller
                                        last edited by

                                        That really makes it seem like a driver or similar issue. Very weird.

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          coliver
                                          last edited by

                                          I'm really concerned as to why it would pop up 5 months after the original deployment. Even if it were a driver issue. Could a Linux update have caused this?

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            scottalanmiller
                                            last edited by

                                            A Linux update could have, of course. But were both of these systems patches recently? It is far more likely to be a HyperV issue. But either is certainly possible.

                                            C 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 5
                                            • 6
                                            • 7
                                            • 8
                                            • 9
                                            • 10
                                            • 11
                                            • 7 / 11
                                            • First post
                                              Last post