 
homebrewer5
join:2001-01-23
Lowell, MA |  Very Interesting
But will this be enough to save Qwest?
--
Bavarian Berthold | |
| |  | 
dvd536
as Mr. Pink as they come
Premium
join:2001-04-27
Phoenix, AZ | Re: Copycatting SprintION at last! Where is 8m mentioned? the best i see is 256/256 and 1024/1024 offered. | |
| 
RAZ Black
join:2001-10-04
Mansfield, TX |  Let's sell old technology like new!
I've used VoIP, and it basically sucks... they've been trying to get that crap to work for years now and a strong move 'slowly' doesn't mean anything. They're searching for sucker opportunist investors.. good luck. | |
| 
Brendan
Warr Guitar is here
join:2000-07-14
Littleton, CO | Just Maybe... Maybe, just maybe, this will be a 'call' (no pun intended) to upgrade areas stuck with "POTS and nothing else". Ergo, areas without broadband technologies (like mine). I sure do hope so!! | |
| | 
sporkme
drop the crantini and move it, sister
Premium,MVM
join:2000-07-01
Morristown, NJ
 ·Optimum Online
| Re: Just Maybe... Two things I remember of Qwest before the US West merger:
-they were doing VOIP for LD
-they were doing it over a private IP network that they had full control over.
-it worked (I've had Qwest LD for years)
The article is shamefully vague about where this fits. I doubt it's in the last mile, but more likely between CO's.
VoIP is not sucky, bad implementations of it are. Two shining examples I know of are my own LD service and the Cisco call center, which besides sounding great routes you to whatever international location has techs awake and answering the phones. During a crunch it can spread the load of support calls all over the world. Needless to say, you can't hear the difference.
For telcos, if they can pull it off in bulk, it's a big money saver. As it stands, a T1 carries 24 voice channels, a T3 28 T1's, or 672 calls over T3. By putting all CO services over a few fat pipes, they waste less capacity. A T3 of VoIP calls could have at least double the amount of calls at the same quality, maybe more. It gets better when you're looking at replacing say a few OC-3's to a CO that carry seperate services (voice, data, frame, ATM, etc.) with a few OC-12s that have all that stuff aggregated together.
Packet networks are more economical. | |
| | | 
highjinx
join:2000-10-12
Alturas, CA
| Re: Just Maybe...quote:
..., a T3 28 T1's, or 672 calls over T3. By putting all CO services over a few fat pipes, they waste less capacity. A T3 of VoIP calls could have at least double the amount of calls at the same quality, maybe more...
The default Codec (G.711) for the Cisco call manager is 64kbps and supports codecs that go as low as 5.3kbps. That's a lot of call's over a T3! An example would be one of the local wireless carriers using 8kbps codecs. When you do the math it comes out to 11.2kbps of bandwidth used per call. So taking the circuit switching out of the local infastructure and going IP is a no brainer.
It will be interesting to see if Qwest will really make a IP local loop available. I've heard of Centrex IP and a few other "planned service", but what it'll probably be is an integrated service (voice and data over T1, T3, DSL, etc.). This is why the big race to get everyone onto their ATM networks.
Too bad the article wasn't clear on if Qwest was talking about inter-office or local loop facilities.
-jinx
[text was edited by author 2001-10-17 01:44:50] | |
| 
headshot12
join:2001-04-02
Plano, TX
| Finally a tier one with guts ?! Deploying VoIP in a carrier network through to the lat mile is not your basic SOHO LAN. Qwest has an ATM backbone that could maybe support the QOS and traffic shaping that differentiated services require. That said, there are a few obstacles that Qwest needs to overcome to gain acceptance:
1. Improve the reliability of the current Qwest ATM network (in 1999 it sucked - it may be better now).
2. Do NOT neglect bandwidth management of the last mile (i.e. provide a residential broadband router that supports MPLS or other diffserv QOS.) The technology is here, carriers and subscribers just have to use it (read $$$).
3. Do NOT support any VoIP products that ride on Microsoft TCP/IP stack. Otherwise you will get RAZzed 
Spork may be right about carrier trunking only - Qwest has been doing it for years. This news could just be spin to jack up the shareholder value. | |
| | | |
|
|
