on 03-08-2022 10:36
Hi,
I'm a new VM customer and my connection in Microsoft Teams is awful. every other second cuts out on the audio front. This happens on multiple devices and I've already had a good read through the various posts that have already been made around this.
I have a Hub 4 and a M350 connection.
I've started a Broadband Quality Monitor on thinkbroadband already (based on previous posts) and have also run the "network diagnostic tool" in the Hub 4's configuration pages. It comes back with errors on telephone line and wifi, however it does not go in to detail and simply displays a exclamation mark.
I also have these logs:
Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
Ok... so what is next? Currently the service is unusable for work meetings, which is probably going to be it's main use day to day. eeeek.
Thanks so much to whoever replies!
James
on 03-08-2022 10:37
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 11 | 40.4 | QAM256 | 25 |
1 | 138750000 | 9.3 | 39 | QAM256 | 1 |
2 | 146750000 | 9.3 | 39 | QAM256 | 2 |
3 | 154750000 | 9.6 | 38.6 | QAM256 | 3 |
4 | 162750000 | 9.9 | 39 | QAM256 | 4 |
5 | 170750000 | 9.9 | 39 | QAM256 | 5 |
6 | 178750000 | 10.2 | 39 | QAM256 | 6 |
7 | 186750000 | 10.6 | 40.4 | QAM256 | 7 |
8 | 194750000 | 10.9 | 40.4 | QAM256 | 8 |
9 | 202750000 | 11.1 | 40.9 | QAM256 | 9 |
10 | 210750000 | 11.1 | 40.9 | QAM256 | 10 |
11 | 218750000 | 11.1 | 40.9 | QAM256 | 11 |
12 | 226750000 | 11 | 40.9 | QAM256 | 12 |
13 | 234750000 | 11.2 | 40.9 | QAM256 | 13 |
14 | 242750000 | 11.2 | 40.4 | QAM256 | 14 |
15 | 250750000 | 11.4 | 40.4 | QAM256 | 15 |
16 | 258750000 | 11.8 | 40.9 | QAM256 | 16 |
17 | 266750000 | 11.6 | 40.4 | QAM256 | 17 |
18 | 274750000 | 11.5 | 40.9 | QAM256 | 18 |
19 | 282750000 | 11.9 | 40.9 | QAM256 | 19 |
20 | 290750000 | 12.3 | 40.9 | QAM256 | 20 |
21 | 298750000 | 12.3 | 40.9 | QAM256 | 21 |
22 | 306750000 | 11.8 | 40.4 | QAM256 | 22 |
23 | 314750000 | 11.9 | 40.9 | QAM256 | 23 |
24 | 322750000 | 11.4 | 40.4 | QAM256 | 24 |
26 | 338750000 | 11.4 | 40.9 | QAM256 | 26 |
27 | 346750000 | 11.6 | 40.4 | QAM256 | 27 |
28 | 354750000 | 11.2 | 40.4 | QAM256 | 28 |
29 | 362750000 | 10.9 | 40.4 | QAM256 | 29 |
30 | 370750000 | 11.2 | 40.9 | QAM256 | 30 |
31 | 378750000 | 10.9 | 40.4 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 40.366287 | 0 | 0 |
1 | Locked | 38.983261 | 0 | 0 |
2 | Locked | 38.983261 | 0 | 0 |
3 | Locked | 38.605377 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.983261 | 0 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.366287 | 0 | 0 |
9 | Locked | 40.946209 | 0 | 0 |
10 | Locked | 40.946209 | 0 | 0 |
11 | Locked | 40.946209 | 0 | 0 |
12 | Locked | 40.946209 | 0 | 0 |
13 | Locked | 40.946209 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.946209 | 0 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 40.946209 | 0 | 0 |
19 | Locked | 40.946209 | 0 | 0 |
20 | Locked | 40.946209 | 0 | 0 |
21 | Locked | 40.946209 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.946209 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.946209 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 40.366287 | 0 | 0 |
29 | Locked | 40.366287 | 0 | 0 |
30 | Locked | 40.946209 | 0 | 0 |
31 | Locked | 40.366287 | 0 | 0 |
159 | 94 | 4K | 1840 | QAM1024 | 424 |
159 | Locked | 44 | 10.6 | 2295609387 | 0 |
on 03-08-2022 10:37
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 39.5 | 5120 KSym/sec | 64QAM | 5 |
2 | 25800000 | 39 | 5120 KSym/sec | 64QAM | 8 |
3 | 32600000 | 39 | 5120 KSym/sec | 64QAM | 7 |
4 | 39400000 | 39 | 5120 KSym/sec | 64QAM | 6 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 4 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 3 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 4 | 0 |
on 03-08-2022 10:38
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | kfoA,.iyewrkldJKDHSUBsgvc |
SFID | 3094 |
Max Traffic Rate | 402500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 6359 |
Max Traffic Rate | 38500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
on 03-08-2022 10:40
Time Priority Description
Fri 10/06/2022 10:15:48 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 12/06/2022 15:18:02 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 12/06/2022 15:18:02 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/06/2022 16:22:45 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 16/06/2022 03:18:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 16/06/2022 03:18:03 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 18/06/2022 08:09:56 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/06/2022 15:18:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/06/2022 15:18:03 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/06/2022 03:18:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/06/2022 03:18:03 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 26/06/2022 08:54:03 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 26/06/2022 15:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 26/06/2022 15:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 28/06/2022 20:52:57 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 30/06/2022 03:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 30/06/2022 03:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 01/07/2022 12:40:08 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 03/07/2022 15:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 03/07/2022 15:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 04/07/2022 10:41:04 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 07/07/2022 03:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 07/07/2022 03:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 10/07/2022 08:28:25 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 10/07/2022 15:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 10/07/2022 15:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 12/07/2022 02:04:45 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 14/07/2022 03:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 14/07/2022 03:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 17/07/2022 15:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 17/07/2022 15:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 21/07/2022 03:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 21/07/2022 03:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 24/07/2022 15:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 24/07/2022 15:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/07/2022 03:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/07/2022 03:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 30/07/2022 09:44:05 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 31/07/2022 15:18:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 31/07/2022 15:18:04 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 03-08-2022 11:07
Hi @JamesRoseUK
Your downstream power levels are too high.
Was this a tech install or self installation?
Do you have an attenuator connected? If so it will look something like the image below.
on 03-08-2022 11:59
Hi Dave,
Was a self install. I don't have one of those devices connected, however the previous owners left some cables which looks to me like the had broadband and tv as the contain a splitter and two of those devices on each cable.
Do I need to use it?
Thanks
03-08-2022 12:13 - edited 03-08-2022 12:16
Hi again James,
Will wait for one of the more knowledgable broadband gurus' to pick this up.
To be honest I would use ethernet where possible, especially for work.
Also suggest checking all of your cabling, internal and external is finger tight, especially the white coaxial, and make sure there are no kinks in the cables.
The splitter may be the problem. Ooh since previous people also used VM I would check that there's no staples in the cabling as lot fasten them with staples and clip the wires.
EDIT - Don't forget to post your BQM, but make sure you erase yuor ip address if it's showing on the BQM
on 03-08-2022 12:25
Thanks Dave,
Should note that the splitter cabling is not being used and I'm just going from the wall box to the Hub with the provided push on cable.
James
on 03-08-2022 17:41
As I wait for a guru to reply, should I test by putting on one of the left behind attenuators?