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.9k
    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.
    • ?
      A Former User @coliver
      last edited by

      @coliver said:

      I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

      But from what I've read this shouldn't cause any issues with actual connectivity.

      Likely means it's suffering performance hit as the NIC might not be fully virtualized.

      coliverC DashrenderD 2 Replies Last reply Reply Quote 0
      • coliverC
        coliver @A Former User
        last edited by

        @thecreativeone91 said:

        @coliver said:

        I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

        But from what I've read this shouldn't cause any issues with actual connectivity.

        Likely means it's suffering performance hit as the NIC might not be fully virtualized.

        Ok, I will see if there is an update available for that version of Linux.

        1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender @A Former User
          last edited by

          @thecreativeone91 said:

          @coliver said:

          I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

          But from what I've read this shouldn't cause any issues with actual connectivity.

          Likely means it's suffering performance hit as the NIC might not be fully virtualized.

          yeah, I would say this could be your whole problem (only the fact that SIP directly to a phone still had the same problem tells us it's not this error that's likely the problem).

          JaredBuschJ 1 Reply Last reply Reply Quote 1
          • dafyreD
            dafyre @coliver
            last edited by dafyre

            @coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.

            It may be worth a shot, but there will be a brief blip if you use the powershell command to disable VMQ.

            get-help VMQ

            will list the commands.

            get-netadaptervmq|where {$_.Name -eq 'NIC1'}|disable-netadaptervmq

            Just replace NIC1 with whichever NIC is currently running your PBX VM.

            JaredBuschJ 1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @dafyre
              last edited by

              @dafyre said:

              @coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.

              This was the issue I had. Poor performance. and it was a Dell server with Braodcom chipset.

              coliverC 1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch @Dashrender
                last edited by

                @Dashrender said:

                yeah, I would say this could be your whole problem (only the fact that SIP directly to a phone still had the same problem tells us it's not this error that's likely the problem).

                His VM is not the problem because a PHONE with the credentials directly entered has the same problem.

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

                  lol maybe the brackets around the second part of my statement made it invisible? lol

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

                    It is obviously a load issue. After ~3-4 pm I no longer see any issues. During the weekend I also saw no issues.

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

                      @JaredBusch said:

                      @dafyre said:

                      @coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.

                      This was the issue I had. Poor performance. and it was a Dell server with Braodcom chipset.

                      IBM server with Intel NICs.

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

                        Just in case I've updated the integration services for Linux.

                        1 Reply Last reply Reply Quote 1
                        • coliverC
                          coliver
                          last edited by

                          Moving the VM to my lab server, trying to see if maybe that will resolve it. Currently nothing is running on the lab server. Wishful thinking I know but worth a shot.

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

                            Try your phone again directly to the SIP trunk.

                            coliverC 1 Reply Last reply Reply Quote 0
                            • coliverC
                              coliver @Dashrender
                              last edited by

                              @Dashrender said:

                              Try your phone again directly to the SIP trunk.

                              I will tomorrow when the issues start up again. Right now everything is working as expected.

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

                                @coliver said:

                                It is obviously a load issue. After ~3-4 pm I no longer see any issues. During the weekend I also saw no issues.

                                A network load issue. Maybe on the ISP's end? It could be, while unlikely, that RTP traffic is being completely dropped under saturation, kind of like inverted QoS.

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

                                  @coliver said:

                                  @Dashrender said:

                                  Try your phone again directly to the SIP trunk.

                                  I will tomorrow when the issues start up again. Right now everything is working as expected.

                                  I thought that I read that that was tested already?

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

                                    @scottalanmiller said:

                                    @coliver said:

                                    @Dashrender said:

                                    Try your phone again directly to the SIP trunk.

                                    I will tomorrow when the issues start up again. Right now everything is working as expected.

                                    I thought that I read that that was tested already?

                                    I tested a third party SIP Trunk. Haven't done that with the ISP trunk yet.

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

                                      Ah, okay. Thanks.

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

                                        @scottalanmiller said:

                                        @coliver said:

                                        It is obviously a load issue. After ~3-4 pm I no longer see any issues. During the weekend I also saw no issues.

                                        A network load issue. Maybe on the ISP's end? It could be, while unlikely, that RTP traffic is being completely dropped under saturation, kind of like inverted QoS.

                                        Came in this morning to the same issues. I'm in early before most people. The only difference between now and last night is that the manufacturing facility is here and working. Generally they shutdown ~3:30-4:30pm.

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

                                          Do you have good traffic monitoring to get a history on the network saturation and compare it to phone issues?

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

                                            @scottalanmiller said:

                                            Do you have good traffic monitoring to get a history on the network saturation and compare it to phone issues?

                                            No.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 10
                                            • 11
                                            • 5 / 11
                                            • First post
                                              Last post