To: pat mudge who wrote (4353 ) 5/4/1998 3:56:00 PM From: fumble Read Replies (1) | Respond to of 18016
On the 'IP Telephony is phoney' thesis: From the Vienna systems whitepaper viennasys.com "IP, as a connectionless protocol, is not a technology that was initially designed for quality of service. However, new standards such as RSVP, 802.1q and MPOA are attempting to address this shortcoming, either in various transport environments or native to IP. In the meantime, voice over IP vendors have engineered their solutions to work around variances in delay, throughput and packet loss to deliver good quality voice solutions even over the Internet. The effects of jitter are minimized through the use of jitter buffers. Voice reconstruction allows many VoIP solutions to tolerate packet losses of 15-20% or more. In a corporate IP network, where the above variables can be more easily controlled, the voice quality is excellent." IP Fax is a bit more reasonable - Fax is not as critical as the human ear. All you need to do is keep the Fax machines from disconnecting before the pages are all sent/received. Again, from the Vienna Systems Fax whitepaper viennasys.com "The destination fax answers and the sending fax is notified which causes it to send the characteristic CNG fax tone. This causes the two gateways (via the CPS) to tear down the voice call and establish an end-to-end, paper-to-paper fax connection between the two fax machines" The immediate situation: there are no end-to-end ATM networks, except for Intranets supplied through Carrier Scale Integration, or built by companies for their own use. IP Telephony is driven by the fact that there IS end-to-end connectivity using IP, however flawed in a timely delivery sense. IP packets leap from network to network, because of common standards which have been implemented. The future situation: IP Telephony will migrate (at some cost) to a MPOA network, where the 'P' will support timely delivery of packets to the earpiece.