Menu
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
230 Views
Message 1 of 12
Flag for a moderator

Terrible Microsoft Teams

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

0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
229 Views
Message 2 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

253307500001140.4QAM25625
11387500009.339QAM2561
21467500009.339QAM2562
31547500009.638.6QAM2563
41627500009.939QAM2564
51707500009.939QAM2565
617875000010.239QAM2566
718675000010.640.4QAM2567
819475000010.940.4QAM2568
920275000011.140.9QAM2569
1021075000011.140.9QAM25610
1121875000011.140.9QAM25611
122267500001140.9QAM25612
1323475000011.240.9QAM25613
1424275000011.240.4QAM25614
1525075000011.440.4QAM25615
1625875000011.840.9QAM25616
1726675000011.640.4QAM25617
1827475000011.540.9QAM25618
1928275000011.940.9QAM25619
2029075000012.340.9QAM25620
2129875000012.340.9QAM25621
2230675000011.840.4QAM25622
2331475000011.940.9QAM25623
2432275000011.440.4QAM25624
2633875000011.440.9QAM25626
2734675000011.640.4QAM25627
2835475000011.240.4QAM25628
2936275000010.940.4QAM25629
3037075000011.240.9QAM25630
3137875000010.940.4QAM25631



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

25Locked40.36628700
1Locked38.98326100
2Locked38.98326100
3Locked38.60537700
4Locked38.98326100
5Locked38.98326100
6Locked38.98326100
7Locked40.36628700
8Locked40.36628700
9Locked40.94620900
10Locked40.94620900
11Locked40.94620900
12Locked40.94620900
13Locked40.94620900
14Locked40.36628700
15Locked40.36628700
16Locked40.94620900
17Locked40.36628700
18Locked40.94620900
19Locked40.94620900
20Locked40.94620900
21Locked40.94620900
22Locked40.36628700
23Locked40.94620900
24Locked40.36628700
26Locked40.94620900
27Locked40.36628700
28Locked40.36628700
29Locked40.36628700
30Locked40.94620900
31Locked40.36628700



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159944K1840QAM1024424


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked4410.622956093870
0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
228 Views
Message 3 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14620000039.55120 KSym/sec64QAM5
225800000395120 KSym/sec64QAM8
332600000395120 KSym/sec64QAM7
439400000395120 KSym/sec64QAM6



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0040
2US_TYPE_STDMA0010
3US_TYPE_STDMA0030
4US_TYPE_STDMA0040

 

0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
225 Views
Message 4 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
kfoA,.iyewrkldJKDHSUBsgvc



Primary Downstream Service Flow

SFID
3094
Max Traffic Rate
402500089
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
6359
Max Traffic Rate
38500089
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort
0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
224 Views
Message 5 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

Network Log

Time Priority Description

Fri 10/06/2022 10:15:485MIMO 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:024DHCP 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:026DHCP 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:453No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 16/06/2022 03:18:034DHCP 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:036DHCP 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:563No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 19/06/2022 15:18:034DHCP 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:036DHCP 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:034DHCP 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:036DHCP 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:033No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 26/06/2022 15:18:044DHCP 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:046DHCP 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:573No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 03:18:044DHCP 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:046DHCP 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:083No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 03/07/2022 15:18:044DHCP 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:046DHCP 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:043No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 07/07/2022 03:18:044DHCP 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:046DHCP 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:253No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 10/07/2022 15:18:044DHCP 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:046DHCP 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:453No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 14/07/2022 03:18:044DHCP 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:046DHCP 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:044DHCP 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:046DHCP 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:044DHCP 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:046DHCP 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:044DHCP 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:046DHCP 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:044DHCP 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:046DHCP 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:053No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 31/07/2022 15:18:044DHCP 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:046DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
newapollo
  • 12.98K
  • 1.74K
  • 3.96K
Very Insightful Person
Very Insightful Person
201 Views
Message 6 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

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.

att.jpg

 

 

Dave

The Service you do for others is the rent you pay for your room here on Earth - Muhammad Ali


I don't work for Virgin Media.

I'm a Very Insightful Person, I'm here to share knowledge. Learn more

Problem solved? Click to mark as a Helpful Answer, or use Kudos to say thanks

The do's and don'ts. Keep the community welcoming for all. Follow the house rules
0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
178 Views
Message 7 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

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

0 Kudos
Reply
newapollo
  • 12.98K
  • 1.74K
  • 3.96K
Very Insightful Person
Very Insightful Person
173 Views
Message 8 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

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

Dave

The Service you do for others is the rent you pay for your room here on Earth - Muhammad Ali


I don't work for Virgin Media.

I'm a Very Insightful Person, I'm here to share knowledge. Learn more

Problem solved? Click to mark as a Helpful Answer, or use Kudos to say thanks

The do's and don'ts. Keep the community welcoming for all. Follow the house rules
0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
168 Views
Message 9 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

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

0 Kudos
Reply
JamesRoseUK
  • 8
  • 0
  • 0
Tuning in
146 Views
Message 10 of 12
Flag for a moderator

Re: Terrible Microsoft Teams

As I wait for a guru to reply, should I test by putting on one of the left behind attenuators?

0 Kudos
Reply