VoIP that travels through the Internet could very likely be indistinguishable from regular traffic, however, the quality will be quite low (ie. high compression) and the stream will be subject to dropouts, jitter and other anomalies. More advanced VoIP programs will use RTP, RSVP, DiffServ, etc to try and reseve the required bandwidth and for this they will need the help of various routers along the way. One thing ISPs could do would be to charge you for respecting the IP ToS field or charge you for RSVP reservations.
Standards compliant VoIP will use RTP/RTCP for the audio payload and control streams, respectively, and probably H.323 and related standards for the signalling (call setup/tear-down, interaction with analogue phone network) -- these are all pretty easy to detect at the router level. In fact if the router *doesn't* detect them and route the stream accordingly, the voice quality will probably deteriorate really quickly.
BTW, anyone know anybody who is rolling out VoIP networks that travel thru the Internet yet? AFAIK all the bug routor vendors are still doing the 100mbit switched ethernet thing...
> Besides, your employer should consider the
> legal implications of making sites proprietry.
> In the UK there's the Disability Discrimination
> Act, the US has something similar. By making
> sites use proprietry extensions you are
> limiting access to those who cannot use
> mainstream browsers for whatever reason.
here in australia a blind guy took the AOC to the anti-discrimination tribunal for not providing alt tags on the image maps for www.olympics.com(.au?) and won.. IBM then quoted them ~2 years and $10m to fix the site:)
Slashdot Mirror
My friend implemented this game recently. It's call The Odd Couplet. Lots of fun for those days when you don't feel like working :)
VoIP that travels through the Internet could very likely be indistinguishable from regular traffic, however, the quality will be quite low (ie. high compression) and the stream will be subject to dropouts, jitter and other anomalies. More advanced VoIP programs will use RTP, RSVP, DiffServ, etc to try and reseve the required bandwidth and for this they will need the help of various routers along the way. One thing ISPs could do would be to charge you for respecting the IP ToS field or charge you for RSVP reservations.
...
Standards compliant VoIP will use RTP/RTCP for the audio payload and control streams, respectively, and probably H.323 and related standards for the signalling (call setup/tear-down, interaction with analogue phone network) -- these are all pretty easy to detect at the router level. In fact if the router *doesn't* detect them and route the stream accordingly, the voice quality will probably deteriorate really quickly.
BTW, anyone know anybody who is rolling out VoIP networks that travel thru the Internet yet? AFAIK all the bug routor vendors are still doing the 100mbit switched ethernet thing
yeh, Foster's started showing up on tap at various pubs that never used to touch it :) .. it's kinda died down again now
Coopers is still the best Australian beer (IMNSHO)
> Besides, your employer should consider the
.. IBM then quoted them ~2 years and $10m to fix the site :)
> legal implications of making sites proprietry.
> In the UK there's the Disability Discrimination
> Act, the US has something similar. By making
> sites use proprietry extensions you are
> limiting access to those who cannot use
> mainstream browsers for whatever reason.
here in australia a blind guy took the AOC to the anti-discrimination tribunal for not providing alt tags on the image maps for www.olympics.com(.au?) and won
> not based on magnetism, but on "tiny bubbles of ectoplasmic phlogiston"
no, they're actually based on midichloreans
and remember that 1 USD buys almost 2 AUD these days