I have an ongoing issue that I can't seem to wrap my head around. I do not have audio during real time communication when taking calls at work. The only time audio works is in Teams, however audio seems to struggle in a group teams session too.
I've had my ISP come out many times. They tell me everything looks fine, lost count of how many times they have swapped out my modem and router. I have a standard modem and a router pod. I can not get them to check the cables/wiring as their equipment is not throwing any errors. ISP is saying it could be my work's VPN that is causing the disconnect.
My work IT department has tried many different things to troubleshoot and nothing has worked. They feel it is my ISP as out of all the users who take calls, there are only 2 (which includes myself) that have the most issues and we both have the same ISP.
I am at a loss and need some guidance or recommendations. I have shown my ISP the event log from the modem. After doing research myself on the event logs and showing my IT department, it appears there is a connection loss or power loss somewhere in the cables. My ISP said that the event logs have nothing to do with the internet, it serves more like a support for the modem. Can someone please explain this? Is there truth to this or is there more that my ISP is not telling me? I have screenshots of the event logs from my modem. I can't make any changes on the modem myself either.
The screenshots don't seem to be loading...here is what I'm getting only event log.
I've had my ISP come out many times. They tell me everything looks fine, lost count of how many times they have swapped out my modem and router. I have a standard modem and a router pod. I can not get them to check the cables/wiring as their equipment is not throwing any errors. ISP is saying it could be my work's VPN that is causing the disconnect.
My work IT department has tried many different things to troubleshoot and nothing has worked. They feel it is my ISP as out of all the users who take calls, there are only 2 (which includes myself) that have the most issues and we both have the same ISP.
I am at a loss and need some guidance or recommendations. I have shown my ISP the event log from the modem. After doing research myself on the event logs and showing my IT department, it appears there is a connection loss or power loss somewhere in the cables. My ISP said that the event logs have nothing to do with the internet, it serves more like a support for the modem. Can someone please explain this? Is there truth to this or is there more that my ISP is not telling me? I have screenshots of the event logs from my modem. I can't make any changes on the modem myself either.
The screenshots don't seem to be loading...here is what I'm getting only event log.
06/05/2023 03:11 | 68010600 | 6 | "DHCP Renew - lease parameters UTC Time Offset modified;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/05/2023 03:11 | 68010300 | 4 | "DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 2436694061 | 5 | "Dynamic Range Window violation" |
06/02/2023 15:11 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 2436694061 | 5 | "Dynamic Range Window violation" |
06/02/2023 15:11 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 73040100 | 6 | "TLV-11 - unrecognized OID;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 66010100 | 4 | "Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 66010100 | 4 | "Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
06/02/2023 15:11 | 68000300 | 5 | "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:00 | 2436694066 | 6 | "Honoring MDD; IP provisioning mode = IPv4" |
01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
05/24/2023 07:48 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
05/17/2023 10:04 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
05/11/2023 15:00 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:ca:b1;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:02 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:01 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:01 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 08:26 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:01:5c:b3:30:4b;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 08:26 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 08:26 | 84000200 | 3 | "SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 08:26 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:25 | 68000100 | 3 | "DHCP FAILED - Discover sent, no offer received;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:01:5c:b3:30:4b;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:25 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:01:5c:b3:30:4b;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:25 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:20 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:20 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:19 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:19 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:19 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:19 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:19 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:19 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:18 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/25/2023 09:18 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |
03/15/2023 10:16 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:72:84:49;CMTS-MAC=00:5f:86:92:b0:ed;CM-QOS=1.1;CM-VER=3.1;" |