#Updating coda 2 lost sites install#
#Updating coda 2 lost sites update#

The Hitron modem is also ridiculously large and ugly. Rogers' 1Gbps service is just marketing, and you're better off with the 150/20 service and a different modem. Don't trust Rogers (not that I did previous to this). Problems are (apparently) evident mostly with static IP setups and bridge-mode with your own router. So this old 'new' modem is now on order, as 150/20 will be fine for this client, especially if the issues go away. The onsite tech called me (a contractor, who actually knew what he was talking about), and told me the issues would only be resolved by DOWNGRADING to the old model modem and dropping their plan to 150/20 (because the Hitron is what's needed to support 1G/50 service). So they did that 2 days ago, and then called me to say the signals to the client's building were not great, and were sending an onsite tech to check it out the next day (yesterday).

#Updating coda 2 lost sites update#

32 version of the firmware, and would update the firmware. The signal strength is still well under 10 db, but the SNR is now in the 31-39 dB range depending on channel, with most in the 32-36 range. When I first got my modem installed the signal strength and signal-to-noise ratio seemed OK, but now Im getting 'Lost MDD Timeout'. So in troubleshooting another client with the same Hitron who has been unable to attend Zoom meetings (they are extremely flakey), Rogers support advised me there were known issues with the. Rogers technical phone support says its a signal issue. And the problems continued (plus the first Hitron was getting ridiculously hot). The onsite tech replaced the modem, and then just left without saying anything (I was furious, as was the client). Rogers came out and replaced the modem (this before the vDSL line was in place), and took the clients main office down for 4 hours.

#Updating coda 2 lost sites install#

The main thing that prompted us to install a secondary ISP was not because of the QoS issues (because we were assuming the source of this was NOT the Rogers service), but because our remote connections between our NOC and the client were extremely flaky, and after doing packet traces at both ends, we found huge packet loss between the locations, which meant the packets were getting lost in the Rogers network. somewhere in here should be either a coda sign or an al coda instruction so that we miss out the bits we shouldnt repeat so jump from the coda sign to the coda so just to make sure (by repetitions) D.S. At one client we installed a Bell vDSL line as a 'backup' about 4 months ago, and have since switched all primary traffic to it, as we can't trust the Rogers service. On re-reading the thread I was struck by the lack of symbols like segno: which is the start of a repeat controlled by the instruction to return to the segno.

I have 2 clients with this modem on a 1Gbps plan (not for much longer), and until this week for the past number of months, we have had huge issues with VPN and VoIP.