Voip teleophony - Anyone know Packet-8 or others?

[gaf at blu.org (Jerry Feldman)]

On Wednesday 14 December 2005 9:29 am, Laura Conrad wrote:
> In Verizon's case, this is complicated by the fact that they don't
> have a problem with needing to maintain equipment that neither they
> nor their customer has access to.
This is true for a number of cases. 
In the case of 3rd party DSL, you've got Verizon delivering the transport to 
the customer. You've got another vendor's router at the customer site. 
You've then got some additional issues with equipment at the Verizon CO as 
well as the DSL vendors' server. 
In the case of a single vendor providing the service (such as Comcast 
providing both the transport and the servers) they own the problem. It's 
not a new problem. I've seen cases in major DP installations where there is 
some 3rd party hardware connected to a mainframe. When something doesn't 
work the mainframe vendor blames the 3rd party and the 3rd party blames the 
mainframe. The customer is in the middle. Verizon loves to do this. One 
time when I complained of static on my phone they tried to blame my house 
wiring. However, at the time, I had disconnected the house wiring and was 
talking to them from a phone patched into the cable at the outside 
junction. They never did fix the static, they just made it less 
unacceptable until I switched to Comcast for phone service. 
-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9