on 29-07-2021 14:28
Hi - I have been experiencing high jitter - e.g. 58, 120 and 91ms. This is seriously affecting testability and functionality of MS teams that I rely on for work. Is this something virgin media can investigate / fix?
Cheers
29-07-2021 21:53 - edited 29-07-2021 21:53
As a first step, go to the Hub on 192.168.0.1 Click on Router Status. Copy and paste into a message here (as text, not screenshot) the Downstream, Upstream and Network Log. This will give a clue as to what is happening.
Are you using a WiFi or ethernet connection?
on 30-07-2021 08:56
Downstream
1 | 139000000 | 3 | 40 | 256 qam | 1 |
2 | 147000000 | 3 | 40 | 256 qam | 2 |
3 | 155000000 | 3 | 40 | 256 qam | 3 |
4 | 163000000 | 2.7 | 40 | 256 qam | 4 |
5 | 171000000 | 2.7 | 40 | 256 qam | 5 |
6 | 179000000 | 2.7 | 40 | 256 qam | 6 |
7 | 187000000 | 2.9 | 40 | 256 qam | 7 |
8 | 195000000 | 2.7 | 40 | 256 qam | 8 |
9 | 203000000 | 2.5 | 40 | 256 qam | 9 |
10 | 211000000 | 2.4 | 40 | 256 qam | 10 |
11 | 219000000 | 2.2 | 40 | 256 qam | 11 |
12 | 227000000 | 2.2 | 40 | 256 qam | 12 |
13 | 235000000 | 2 | 40 | 256 qam | 13 |
14 | 243000000 | 1.5 | 40 | 256 qam | 14 |
15 | 251000000 | 1.4 | 40 | 256 qam | 15 |
16 | 259000000 | 1.5 | 40 | 256 qam | 16 |
17 | 267000000 | 1.7 | 40 | 256 qam | 17 |
18 | 275000000 | 1.7 | 40 | 256 qam | 18 |
19 | 283000000 | 2 | 40 | 256 qam | 19 |
20 | 291000000 | 2.2 | 40 | 256 qam | 20 |
21 | 299000000 | 2.5 | 40 | 256 qam | 21 |
22 | 307000000 | 2.2 | 40 | 256 qam | 22 |
23 | 315000000 | 2.2 | 40 | 256 qam | 23 |
24 | 323000000 | 2.2 | 40 | 256 qam | 24 |
1 | Locked | 40.9 | 21 | 0 |
2 | Locked | 40.9 | 55 | 0 |
3 | Locked | 40.9 | 41 | 0 |
4 | Locked | 40.9 | 45 | 0 |
5 | Locked | 40.9 | 49 | 0 |
6 | Locked | 40.9 | 73 | 0 |
7 | Locked | 40.9 | 74 | 0 |
8 | Locked | 40.9 | 84 | 0 |
9 | Locked | 40.9 | 74 | 0 |
10 | Locked | 40.9 | 81 | 0 |
11 | Locked | 40.9 | 72 | 0 |
12 | Locked | 40.9 | 61 | 0 |
13 | Locked | 40.3 | 33 | 0 |
14 | Locked | 40.9 | 43 | 0 |
15 | Locked | 40.9 | 56 | 0 |
16 | Locked | 40.9 | 49 | 0 |
17 | Locked | 40.9 | 26 | 0 |
18 | Locked | 40.9 | 38 | 0 |
19 | Locked | 40.3 | 35 | 0 |
20 | Locked | 40.9 | 25 | 0 |
21 | Locked | 40.3 | 26 | 0 |
22 | Locked | 40.9 | 34 | 0 |
23 | Locked | 40.9 | 62 | 0 |
24 | Locked | 40.9 | 45 | 0 |
upstream
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID1 | 39400000 | 47.5 | 5120 | 64 qam | 4 |
2 | 46200000 | 47.5 | 5120 | 64 qam | 3 |
3 | 53700000 | 47.5 | 5120 | 64 qam | 2 |
4 | 60300000 | 49 | 5120 | 64 qam | 1 |
on 30-07-2021 08:56
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 4 | 0 |
3 | ATDMA | 0 | 0 | 2 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
log
Time Priority Description
30/07/2021 07:45:35 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/07/2021 23:34:36 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/07/2021 23:34:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/07/2021 17:11:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/07/2021 11:34:36 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/07/2021 11:34:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/07/2021 22:55:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 16:40:12 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 16:40:12 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 16:14:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 17:29:20 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 17:29:20 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 01:05:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 05:29:18 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 05:29:18 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/07/2021 03:51:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/07/2021 17:29:19 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/07/2021 17:29:19 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 15:40:36 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 05:29:19 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Using wifi connection.
Cheers!
on 30-07-2021 09:37
The connection data doesn't show any serious problems.
Wi-Fi will always show some jitter. The degree depends on a number of local factors. An ethernet connection will always be better than Wi-Fi. Can you try that?
on 30-07-2021 09:40
Thanks - will start using ethernet connection and see how it goes.
Cheers!
on 31-07-2021 15:29
Thanks for your post and updates, C_L_62,
Sorry to hear that you have been having connection issues. How has things been since your post? I have run a remote diagnostic and have not been able to identify any issues with your connection.
We can also provide online broadband help here: https://www.virginmedia.com/help/services-support/broadband
Let us know how it goes with a wired connection.
Cheers,
Corey C