Fraud at worst, misleading at best.<br><br>Voice can tolerate latency, but what it doesn't tolerate is jitter. At the network level, jitter is controlled by a strict priority queue, ie if a voice packet is seen on the ingress port it is the next packet to leave the router no matter what (well, assuming you haven't bursted beyond what you're allowed). Anything else and you're not helping voice quality.
<br><br>I guess this might explain why nobody at Shaw can explain how packets are classified -- they simply aren't. <br><br>This almost sounds like something for Consumer Affairs: <a href="http://consumer.ic.gc.ca/epic/internet/inoca-bc.nsf/en/ca01506e.html">
http://consumer.ic.gc.ca/epic/internet/inoca-bc.nsf/en/ca01506e.html</a><br><br>Sean<br><br><div><span class="gmail_quote">On 9/7/06, <b class="gmail_sendername"><a href="http://LES.NET">LES.NET</a> (1996) INC.</b> <<a href="mailto:voip@les.net">
voip@les.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">When I queried shaw about what QoS was they explained that it is method of
<br>remotely monitoring the signal levels on the modem over time. (Versus<br>just checking when a problem happens). This way they could see changes in<br>signal levels in the past and come to some conclusion when customers
<br>complain about quality. It was not described as a packet priority scheme.<br><br>Shaw defines the QoS $10 feature as:<br>"Shaw is now able to offer its High Speed Internet customers the<br>opportunity to improve the quality of Internet telephony services offered
<br>by third party providers. For an additional $10 per month Shaw will<br>provide a quality of service (QoS) feature that will enhance these<br>services when used over the Shaw High Speed Internet network. Without this<br>
service customers may encounter quality of service issues with their voice<br>over Internet service"<br><br>If they are simply monitoring signal levels (which has been explained to<br>myself and others), then this is simply a passive method, and could not
<br>possible enhance the connection. In which case, this is fundamentally<br>consumer Fraud with a capital F, and should be exposed as such.<br><br><br>Les<br><br>> On Wed, 2006-09-06 at 16:15 -0500, Kevin D Scott wrote:
<br>><br>>> Well I was cut off, as expected, so I haven't tried the QOS enhancement<br>>> yet.<br>>><br>>> Has anybody else here tried it? Any results? My biggest concern is<br>>> that it
<br>>> doesn't help all VoIP traffic, just some to the bigger services, Vonage,<br>>> Primus, ect.<br>><br>> My personal belief is that it does nothing. If you press Shaw hard (as I<br>> did) to describe what kind of QOS they are using you ultimately will
<br>> discover that it does not exist in the telephony sense.<br>><br>> The final answer I got was that it actually stands for "Quality of<br>> Signal" monitoring. This is some kind of real-time reporting system they
<br>> use to monitor your modem's performance.<br>><br>> Looking up QOS on Wikipedia finds that it has more than one meaning:<br>><br>> <a href="http://en.wikipedia.org/wiki/Quality_of_service">http://en.wikipedia.org/wiki/Quality_of_service
</a><br>><br>> "Quality of Service (QoS) refers to the probability of the<br>> telecommunication network meeting a given traffic contract"<br>><br>> According to the tech I spoke with at Shaw, that is the meaning of the
<br>> term they are using even though their web site clearly indicates that<br>> QOS is packet prioritization.<br>><br>> Of course there are many different ways to do QOS, the one that would<br>> make the most sense for Shaw to implement would be DiffServ.
<br>><br>> "The second and currently accepted approach is "DiffServ" or<br>> differentiated services. In the DiffServ model, packets are marked<br>> according to the type of service they need."
<br>><br>> But of course, if they were doing DiffServ, they would need to tell you<br>> how to mark the packets so they get priority and that is what I was<br>> calling them to find out.<br>><br>> The other option would be to put your entire modem on a IEEE
802.1q VLAN<br>> and give it higher priority for _all_ traffic coming from your modem.<br>><br>> Actually, the current problems with Shaw gives me a unique opportunity<br>> to test their QOS service so I think I will order it and see if it makes
<br>> any difference.<br>><br>> John<br>><br>><br>> _______________________________________________<br>> Asterisk mailing list<br>> <a href="mailto:Asterisk@muug.mb.ca">Asterisk@muug.mb.ca</a><br>>
<a href="http://www.muug.mb.ca/mailman/listinfo/asterisk">http://www.muug.mb.ca/mailman/listinfo/asterisk</a><br>><br><br><br>_______________________________________________<br>Asterisk mailing list<br><a href="mailto:Asterisk@muug.mb.ca">
Asterisk@muug.mb.ca</a><br><a href="http://www.muug.mb.ca/mailman/listinfo/asterisk">http://www.muug.mb.ca/mailman/listinfo/asterisk</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com">
sean@ertw.com</a>> <a href="http://ertw.com/">http://ertw.com/</a>