Jump to content
Where is that coyote - I'll git 'im!
Jon, I understand. All I am saying is that CL should be able to complete certain calls even with a fiber cut way south of town. During the outage none of my calls went through. My calls were on my CL landline so they "hit the PSTN" when I got dial tone. Two of those calls I know to be CL landlines also. Those calls should have gone through.
And I do know how cell phones work. I did say I was not talking about them (different animal). Nor am I talking about internet voice (different animal).
As far as the power failure went this morning, it affected several condo complexes on the mountain at least, including mine. My phone was the only thing working - no TV, no Internet, no coffee. I completed a call to a land line in Stagecoach. When I called a business down the street, I got dead air because their IP PBX was out. I don't know about the medical group, but CL's switch was up and working for me. Maybe some of their local loop carrier systems lost power, but mine didn't.
Jon, let me be a bit more specific. I am referring to 879/870 calls to other 879/870 phones. There is no reason that any of those calls should be switched outside of the Steamboat CO. Those calls were disrupted during both outages and in a strange way that leads me to believe that access to a database was involved, not actual talk paths.
And VOIP is nothing more than digitizing your voice and throwing the packets into the internet, hoping they make it to the other end.
Cell phones are a whole different animal.
Jon, my comments have been aimed at the traditional telephone networks. VOIP is not telephone service, just another Internet app with no promise of any reliability. But the telephone network was designed from the ground up to provide universal and reliable service. CL doesn't seem to be upholding that philosophy.
Yes, but my point is that this call should involve my phone, the CL switch downtown, the database mapping my phone to a street address and the 911 call center out in the courthouse, all of which are (should be) right here in Steamboat. What possible effect could a fiber cut in Kremmling have on that call. Everything necessary could be and should be here.
Eric, I never worked on 911 systems so I don't understand the subtleties or the Routt County topology for connecting calls. Maybe you can enlighten me? I did add 911 service features to PBXs back in the days when 911 was new. Connection of a 911 call from a phone in Steamboat to the Routt 911 center would seem to be a simple default route to a specific trunk group with Caller ID on steroids on an aux data link. So again, I am mystified that CL can't complete 911 calls with a fiber cut up Rabbit Ears or down in Kremmling. Thus my theory that our switch is totally dependent on database queries to Denver.
Yes - no - maybe?
Most modern fiber bundles are equipped with copper wire. Or a copper wire is pulled alongside the cable bundle.
Your are wasting your effort trying to give me digital transmission 101 lessons. The technology you describe is called multiplexing, in particular SONET. I have designed SONET multiplexers. I was a member of the T1X1 Committee that set the standards for how it works.
This has nothing to do with the responsibility of a carrier to provide redundant circuits and systems to maintain service. And it doesn't require care, it requires a minimally trained Telco engineer doing his job. And if he goofed back a few months ago, that outage certainly would have wakened up the CL folks to the error.
No, like my last post said, this is a failure strictly within CL. They have not provided redundant paths to query their own database. Or that redundancy failed to work (again). Nothing was cut in Steamboat. The CO switch down there on 7th and Oak was perfectly capable of completing our calls in town. It just couldn't look up phone numbers from the database in Denver to know where to switch the calls.
Charlie, you are absolutely right about this. Those that are saying it's a contractor problem are missing the point. Cable cuts are going to happen. Whose is at fault is just so much noise. It is incumbent on CL to keep services up when this happens. Telephone equipment has batteries in the case of power failure, generators in the case of battery failure, shock mounted floors in the case of earthquakes, and they should know how keep equipment and comm lines up all the time.
AHA!!! I have been trying to debug these outages since the first one happened. None of the reported symptoms or CL explanations made sense to me. It's been a long time since I designed telephone switches and networks, so there are parts of my brain harboring rust and cobwebs. I could not fathom how CL could possibly be switching a phone call between me and my next door neighbor through a pasture south of Kremmling or on Muddy Pass. The answer, of course, is they aren't.
This is a database lookup problem. CL must have their telephone number database centralized in, say, Denver. It appears that even local calls are looked up through this data line that keeps being cut. This would explain the weird symptoms - "number not in service", ATBs (all trunks busy - what people commonly call "fast busy"), inability to route 911 calls. And it appears there is no redundant path to another database and no local backup of numbers where our local Class 5 offices could be completing local calls. CL should easily be able to back this link up. It doesn't even have to carry telephone traffic, just simple database queries (= low bandwidth).
Comments appreciated from anyone having knowledge here. I am just winging it. Any CL employees want to jump in? Is this root issue?
Last login: yesterday
Contents of this site are © Copyright 2015 Steamboat Pilot & Today. All rights reserved.