how-to block ads
|
|
Share Topic
 |
 |
|
|
| reply to 11337845
Re: I understand VoIP is actually rather difficult to implement and provide QoS for. There's a lot more involved than hooking up a NID at the side of your house to the phone, and having return back to the l/o. You need to know how many people per node, to allot specific amounts of guaranteed bandwidth so phone conversation quality doesn’t drop, plants need to be built in a more reliable manner. The liability is phenomenal with VoIP. IT would be ideal to replace all the battery operated power supplies with gas-fed power supplies, therefore if the power is out for more than 4 hours, the supply could then switch to a gas generator. That's just 1 example of the process required for VoIP (reliable quality VoIP - not just thrown together of course). Plants typically like to be Node +1 (No more than 1 amplifier per node). Many systems are node +6 even higher. Those will need to be rebuilt, to provide greater uptime (as high as possible). With Cable modems and TV service, "best effort" is ok. With Telephony/VoIP a "better than best effort" is necessary. Then to consider the server end of the process, the call services such as caller ID etc; the billing process, logging usage for federal reports/usage - taping services etc... It becomes very complex and daunting. VoIP is by far the most complicated of any feature to provide via cable. Will be cool when Adelphia gets it though 
--
"When my Linux machine gives me the blue screen of death, I just wiggle my mouse to deactivate the screen saver" | |
11337845Live free or diePremium
join:2002-12-20
Seattle, WA | said by njellis:
VoIP is actually rather difficult to implement and provide QoS for. There's a lot more involved than hooking up a NID at the side of your house to the phone, and having return back to the l/o. You need to know how many people per node, to allot specific amounts of guaranteed bandwidth so phone conversation quality doesn’t drop, plants need to be built in a more reliable manner. The liability is phenomenal with VoIP. IT would be ideal to replace all the battery operated power supplies with gas-fed power supplies, therefore if the power is out for more than 4 hours, the supply could then switch to a gas generator. That's just 1 example of the process required for VoIP (reliable quality VoIP - not just thrown together of course). Plants typically like to be Node +1 (No more than 1 amplifier per node). Many systems are node +6 even higher. Those will need to be rebuilt, to provide greater uptime (as high as possible). With Cable modems and TV service, "best effort" is ok. With Telephony/VoIP a "better than best effort" is necessary. Then to consider the server end of the process, the call services such as caller ID etc; the billing process, logging usage for federal reports/usage - taping services etc... It becomes very complex and daunting. VoIP is by far the most complicated of any feature to provide via cable. Will be cool when Adelphia gets it though
If a startup like Vonage can do it, so can Adelphia.
At least that's how I see it.
When I think of Adelphia and VOIP together, I'm thinking an ATA 186 like Vonage uses, and not a direct plugin to the house phone system, though that is a pretty good idea too.
Is that how other cable providers have chosen to deploy VOIP? | |
| I don't think there is a set standard as to how other companies deploy VoIP. Vonage is an independent company; they do not own the infrastructure. It's sold as a service that works over your broadband. Vonage cannot be held responsible if your phone doesn’t work because X-cable company’s lines went down. And X-cable company cannot be held responsible because they don’t support or endorse VoIP service, so if you do it; it's done at your own risk.
Quite different from getting Adelphia VoIP (or any other Cable company VoIP). Vonage doesn’t roll trucks out to your house to fix the issues w/ your VoIP working etc etc...
It goes back to the "Yah they can make it work; but it'll be a thrown together patch-half@ss system." Not one you want to put your name on especially in our day of lawsuits galore.
The ATA186 is ONE of many ways to do it. Another example: an over builder in our system has voltage (48vts for phone) running though their lines. They have different tags on their lines if voltage runs down their drops... and they have an NID that interfaces w/ the phone NID already in your home. Yet another model is not running voltage down the drop, and instead plugging into the house for your 48vts, one option w/ battery one w/o battery. Again that goes back to a reliability issue. Yet another concept is to have taps @ the pole w/ coax ports and telco ports, where you'd run a telco-style line up to the phone (twisted pair) and hook up. I'm sure there are plenty more ideas than that..
--
"When my Linux machine gives me the blue screen of death, I just wiggle my mouse to deactivate the screen saver" | |
|
