Intermittent problem - only affecting VoIP
Hi,
I have just started new contract, VM insisted on sending new hub; moved from the old voom500 to voom600 - there was nothing wrong with the old router and everything worked fine.
Switch over to new hitron CM seemed fine, I left the 3db in-line attenuator on the cable as i figured it was needed before so will probably be needed now.
Speed tests appear fine (300 down, 60up), ping tests mainly appear to be fast and lossless. However there are sporadic inconsistencies and 2 VoIP phones that are attached to a PoE+ switch regularly are losing connection and not happy when they regain connection (This is new behaviour, not seen with exactly the same equipment bar the new CM).
Already raised ticket, but they said that there was nothing wrong with the connection and they reset the docsis event log (i had already screenshotted all the previous errors and notices). Have spoken with the VoIP provider and they said no known issues on their network; after discussion with them I disabled ALG in the VM CM and asked for static IP (now done) incase CGNAT from dynamic IP pool was causing issues.
Problem has had varying levels of disruption, today has been especially bad. Will post up current docsis event log, let me know if other reports can be of use.
DOCSIS Logs
No. Time Type Priority Event
1 03/07/2025 14:06:52 67061601 Notice US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
2 03/07/2025 14:07:12 74010100 Notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
3 03/07/2025 14:11:55 67061601 Notice US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
4 03/07/2025 14:35:45 74010100 Notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
5 03/08/2025 10:34:26 82000200 Critical No Ranging Response received - T3 time-out;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
6 03/08/2025 11:19:37 74010100 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
7 03/09/2025 06:34:24 68010300 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
8 03/09/2025 07:04:48 74010100 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
9 03/09/2025 16:51:13 82000400 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
10 03/10/2025 05:21:16 82000200 Critical No Ranging Response received - T3 time-out;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
11 03/10/2025 06:01:29 74010100 Notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
12 03/11/2025 09:17:56 67061601 Notice US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
13 03/11/2025 09:17:57 84000500 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
14 03/11/2025 09:18:12 74010100 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
15 03/11/2025 10:03:15 67061601 Notice US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
16 03/11/2025 10:03:45 74010100 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
17 03/11/2025 10:08:18 67061601 Notice US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
18 03/11/2025 10:11:23 74010100 Notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
19 03/11/2025 10:16:08 67061601 Notice US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=fc:77:7b:68:db:a0;CMTS-MAC=00:01:5c:84:2e:d9;CM-QOS=1.1;CM-VER=3.1;
I also captured several other warnings and errors before they got expunged :
Critical - config file rejected due to invalid or unexpected TLV
Notice - TLV-11 unrecognised OID
Critical - no ranging response received - T3 time-out
critical - unicast ranging received abort response - initialising MAC
Warning - RNG-RSP CCAP commanded power in excess of 6dB below the value corresponding to the top of the DRW
Now in my non-expert opinion, I was assuming that this could be a power level issue and probably need a different strength attenuator. I ran the codes through chatgpt, which sort of confirmed my line of thinking.
Any thoughts ?
