Forum Discussion

faze82's avatar
faze82
Tuning in
12 months ago

Packet Loss - Teams Audio Dropping

Hi, I am experiencing intermittent packet loss which is causing connectivity issues and the audio on my Teams calls to drop. This is affecting my ability to work from home. This is happening on multiple devices and only on my Virgin Media connection.

Is there anything I can do or does this need to be resolved by Virgin Media?

I've tried the usual... reboot router, use wired connection, test using mobile phone connection (no issues)

BQM Graph: 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fcc67bab99a27431ac6c0b8208ba34b0449408d8-22-05-2024

Thanks 

10 Replies

  • jbrennand's avatar
    jbrennand
    Very Insightful Person

    BQM looks poor.  What devices do you have connected to your Hub on ethernet cables ?

    Can you do this....

    Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax and ethernet cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing. When its light, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. Then switch the Hub back on and leave ~5 minutes

    When all done, Post up your Hub/network connection details and someone will check to see if there is a problem there.  In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.
    Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts

  • Hi John,

    Thanks for your detailed response. I checked and re-seated all the connections and all look good. I'm still getting the issue and still seeing latency spikes and dropped packets on the BQM. I still have a Super Hub 2. I do have devices connected to the hub via ethernet cables (mesh wifi, tv, etc.) 

     

    Downstream  DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

    Frequency (Hz)258750000266750000274750000282750000290750000298750000306750000314750000
    Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
    Channel ID1617181920212223
    Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
    Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
    Interleave DepthI=12
    J=17
    I=12
    J=17
    I=12
    J=17
    I=12
    J=17
    I=12
    J=17
    I=12
    J=17
    I=12
    J=17
    I=12
    J=17
    Power Level (dBmV)2.503.844.214.084.054.184.384.68
    RxMER (dB)34.6335.4235.4234.3534.0835.4235.6035.78
    Pre RS Errors53280813758273411825241796420804649387362623963988093
    Post RS Errors992761522917239576147182399576985816545088
  • Upstream  US-1 US-2 US-3 US-4

    Channel Type2.02.02.02.0
    Channel ID4219
    Frequency (Hz)30100000431000004960000023600000
    Ranging StatusSuccessSuccessSuccessSuccess
    Modulation64QAM64QAM64QAM16QAM
    Symbol Rate (Sym/sec)5120000512000051200005120000
    Mini-Slot Size2222
    Power Level (dBmV)45.7545.5045.7546.00
    T1 Timeouts0000
    T2 Timeouts0000
    T3 Timeouts6002
    T4 Timeouts0000
  • Network Log

    First TimeLast TimePriorityError NumberDescription
    23/05/2024 09:26:17 GMT23/05/2024 09:26:17 GMTWarning (5)66050310Auth Success - Web login successful.
    23/05/2024 09:26:07 GMT23/05/2024 09:26:07 GMTWarning (5)66050310Auth Success - Web login successful.
    22/05/2024 18:40:16 GMT22/05/2024 18:40:16 GMTCritical (3)82000200No Ranging Response received - T3 time-out
    22/05/2024 18:18:08 GMT22/05/2024 18:18:08 GMTWarning (5)84020200Lost MDD Timeout
    22/05/2024 18:18:02 GMT22/05/2024 18:18:02 GMTWarning (5)84020200Lost MDD Timeout
    22/05/2024 18:17:56 GMT22/05/2024 18:17:56 GMTWarning (5)84020200Lost MDD Timeout
    22/05/2024 15:05:34 GMT22/05/2024 15:05:34 GMTError (4)68010300DHCP RENEW WARNING - Field invalid in response v4 option
    22/05/2024 07:10:24 GMT22/05/2024 07:10:24 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
    22/05/2024 04:17:24 GMT22/05/2024 04:17:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
    22/05/2024 01:35:50 GMT22/05/2024 01:35:50 GMTCritical (3)82000200No Ranging Response received - T3 time-out
    21/05/2024 15:06:42 GMT21/05/2024 15:06:42 GMTWarning (5)66050310Auth Success - Web login successful.
    21/05/2024 15:06:30 GMT21/05/2024 15:06:30 GMTWarning (5)66050310Auth Success - Web login successful.
    21/05/2024 15:06:20 GMT21/05/2024 15:06:20 GMTWarning (5)66050300Auth Fail - Web login failed.
    21/05/2024 14:49:31 GMT21/05/2024 14:49:31 GMTWarning (5)66050310Auth Success - Web login successful.
    21/05/2024 14:49:21 GMT21/05/2024 14:49:21 GMTWarning (5)66050310Auth Success - Web login successful.
    21/05/2024 14:33:05 GMT21/05/2024 14:33:05 GMTWarning (5)66050310Auth Success - Web login successful.
    21/05/2024 14:32:55 GMT21/05/2024 14:32:55 GMTWarning (5)66050300Auth Fail - Web login failed.
    21/05/2024 13:13:12 GMT21/05/2024 13:13:12 GMTCritical (3)82000200No Ranging Response received - T3 time-out
    21/05/2024 11:00:37 GMT21/05/2024 11:00:37 GMTWarning (5)66050310Auth Success - Web login successful.
    21/05/2024 11:00:26 GMT21/05/2024 11:00:26 GMTWarning (5)66050310Auth Success - Web login successful.
  • The SH2 is really outdated in itself - I’m surprised you haven’t been contacted about this already.

     

    I’m not familiar with the stats from the SH2 (they are a little different to the newer hubs) 

    However:

    There’s a lot of PostRS errors (which support the fact that you are experiencing packet loss)  - when was the router last restarted? If if’s been a while, might be worth restarting to confirm that they are still rising. Either way, repost in a few hours to confirm they are rising.

    One of the other issues I’ve identified is that one of the upstream channels has a modulation of 16QAM (should be 64) 

  • Thanks RT123

    I restarted the Hub on the 21st:

    Session Time   2day 16h:57m:44s

    They are still rising:

    Post RS Errors1022931565517773578402183937584335868545837
  • Thanks all for your responses. While I'm waiting for an engineer - I will try disconnecting the ethernet connections from the hub.