on 27-11-2022 14:02
Hi, after a month or so of intermittent broadband connection that has finally broken altogether, a technician visit (following a couple of appointments cancelled because VM said the problem was a network issue that was resolved when it was not), I have been told I need a drop cable replacement and given a date of 20 December for installation. Having read other comments on the forum I am concerned that even if I keep patient and wait for that there is a fair chance that no one will show on the 20th, or the repair will not be complete, and we will then be into the Christmas period with no internet.
Does any one have any suggestions as to how to convince VM to treat my issue with a bit more urgency? Their call centres either say they are detecting no issues and suggest cancellation of the visit, or welcome me as a new customer awaiting first installation (I have been with them for 15+ years) and say that only movement of a visit to a later date is possible. Reading the other comments on here I appreciate that they are probably dealing with an outside contractor but even so, I would assume there is some VM team that interacts with them that could shake things up, any suggestions as to how to get hold of them?
Thanks!
on 27-11-2022 14:50
27-11-2022 14:50 - edited 27-11-2022 14:53
@StephenH2 wrote:Hi, after a month or so of intermittent broadband connection that has finally broken altogether, a technician visit (following a couple of appointments cancelled because VM said the problem was a network issue that was resolved when it was not), I have been told I need a drop cable replacement and given a date of 20 December for installation. <snip> Their call centres either say they are detecting no issues and suggest cancellation of the visit, or welcome me as a new customer awaiting first installation <snip>
Thanks!
Don't have any helpful answers for you, unfortunately, but for clarity, are you totally without any VM services right now?
on 27-11-2022 17:03
Thanks:
here are the network logs:
TimePriorityDescription27/11/2022 16:50:40criticalREG RSP not received;CM-MACb;CMTS-MACCM-QOS=1.1;CM-VER=3.0;27/11/2022 16:50:40ErrorT6 Timeout and retries exceeded;CM-MAC;CMTS-MACCM-QOS=1.1;CM-VER=3.0;27/11/2022 16:50:40criticalRegistration RSP rejected unspecified reason;CM-MACCMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:50:40criticalRegistration RSP rejected message syntax error;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:50:22criticalNo Ranging Response received - T3 time-out;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:49:56criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:49:41criticalREG RSP not received;CM-MAC; CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:49:41ErrorT6 Timeout and retries exceeded;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:49:41criticalRegistration RSP rejected unspecified reason;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:49:41criticalRegistration RSP rejected message syntax error;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:49:21criticalNo Ranging Response received - T3 time-out;CM-MAC;CMTS-MAC59;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:48:54criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:48:43criticalREG RSP not received;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:48:43ErrorT6 Timeout and retries exceeded;CM-MAC;CMTS-MAC59;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:48:43criticalRegistration RSP rejected unspecified reason;CM-MAC;CMTS-MACCM-QOS=1.1;CM-VER=3.0;27/11/2022 16:48:43criticalRegistration RSP rejected message syntax error;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:48:19criticalNo Ranging Response received - T3 time-out;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:47:51criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:47:37criticalREG RSP not received;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;27/11/2022 16:47:37ErrorT6 Timeout and retries exceeded;CM-MAC;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;
on 27-11-2022 17:10
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | 46200000 | 57 | 5120 | 64 qam | 1 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
on 27-11-2022 17:13
Second post to you is the other info, sorry for the messy submissions, doing it all on my phone and having to go next on and off the router as it obviously has no internet connection. Hope this is the correct stuff and many thanks in advance for anything that you can suggest!
on 27-11-2022 18:52
on 27-11-2022 20:03
Thanks, here we go..
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 234750000 0.4 38 256 qam 13
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 0 0
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46200000 57 5120 64 qam 1
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 1 0
Network Log
Time Priority Description
27/11/2022 19:55:16 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:54:50 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:54:35 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:54:35 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:54:35 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:54:35 critical Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:54:16 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:53:45 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:53:35 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:53:35 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:53:35 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:53:35 critical Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:53:11 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:52:45 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:52:30 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:52:30 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:52:30 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:52:30 critical Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:52:13 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2022 19:51:34 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
on 27-11-2022 21:11
on 27-11-2022 22:03
Hi, thanks for taking a look! The fault was intermittent at first and still was when the technician first came. He said it may be a network fault and only to worry if it came back. At that point he reckoned that replacement cable may be need as that is 20yrs old. A couple of days later it did reappear and then a day later stopped altogether. No one has suggested a replacement hub! Let’s see what the VM person say if they take a look at this.