Comment Research the product (Score 3, Interesting) 160
I think we need to examine Shaw vs Vonage telephony for a minute. ***Disclaimer: After comparing the two services side-by-side, I'm a Shaw Phone customer.
Vonage is VoIP running over standard ethernet on the Internet. It's voice traffic competes with every other data packet on the Internet, no matter if it's on Shaw's network, or Telus' network, or the Internet in general. Vonage is portable and available on any high speed network.
Shaw Phone may technically be VoIP, but it runs on seperate hardware (an independant modem with no active data connections), on a seperate channel allocation than Internet (a managed voice network) and doesn't have to compete with Internet traffic. It's routed to the PSTN without touching the Internet so the voice packets don't require QoS. Shaw's telephony is NOT portable, its for home use only.
This is like comparing apples to oranges. I've tried Vonage and although it worked okay, at times the packet loss was unbearable. I don't care what the excuse is (overloaded nodes, Internet traffic spikes, etc), when I use the phone I just want it to work. Period. I also think that 911 is pretty much a required service and there are some significant differences between Shaw and Vonage in that respect, but thats a different debate. Shaw Phone isn't perfect, but its certainly better than Vonage in my experience.
The QoS service definitely isn't a tax because its not mandatory and Vonage works as advertised without it. Besides all that, Shaw can only offer QoS on their own network. Once the traffic leaves their network QoS is meaningless. Would I subscribe to QoS? Probably not, but then again I'm not using Vonage.
And to the earlier poster who suggested that Shaw should reduce the number of customer spambots on their networks to reduce traffic overhead - I couldn't agree more. Turn that bandwidth shaping towards the spam relays and cut their service until they correct their problems. They'd probably gain a significant amount of usable bandwidth for the effort.
Vonage is VoIP running over standard ethernet on the Internet. It's voice traffic competes with every other data packet on the Internet, no matter if it's on Shaw's network, or Telus' network, or the Internet in general. Vonage is portable and available on any high speed network.
Shaw Phone may technically be VoIP, but it runs on seperate hardware (an independant modem with no active data connections), on a seperate channel allocation than Internet (a managed voice network) and doesn't have to compete with Internet traffic. It's routed to the PSTN without touching the Internet so the voice packets don't require QoS. Shaw's telephony is NOT portable, its for home use only.
This is like comparing apples to oranges. I've tried Vonage and although it worked okay, at times the packet loss was unbearable. I don't care what the excuse is (overloaded nodes, Internet traffic spikes, etc), when I use the phone I just want it to work. Period. I also think that 911 is pretty much a required service and there are some significant differences between Shaw and Vonage in that respect, but thats a different debate. Shaw Phone isn't perfect, but its certainly better than Vonage in my experience.
The QoS service definitely isn't a tax because its not mandatory and Vonage works as advertised without it. Besides all that, Shaw can only offer QoS on their own network. Once the traffic leaves their network QoS is meaningless. Would I subscribe to QoS? Probably not, but then again I'm not using Vonage.
And to the earlier poster who suggested that Shaw should reduce the number of customer spambots on their networks to reduce traffic overhead - I couldn't agree more. Turn that bandwidth shaping towards the spam relays and cut their service until they correct their problems. They'd probably gain a significant amount of usable bandwidth for the effort.
