Hardware

end result is your voip phone traffic has no priority while on the public internet. if the mitel pbx is not voip then it is not the problem. if voip at far end, they can set voice traffic to be given priority while on your company's net.

in the end, the POTS is faster and more reliable even tho it is using tcp/ip over large chunks. sure, increased bandwidth might help on public net, but like freeways, instead of toll roads, as fast as they thro bandwidth at the internet, it will be used up by non-phone traffic with video on demand, flash ads, etc.

So I'm not sure there is a solution. Much as voip vendors would like to hype this technology, it is not as good quality as regular phone lines much of the time, as you described

Can you take this system over to a friends house with DSL and try this? It could be the TW cable "shared" pipe is being overutilized and this is causing the breakups. If it works well with DSL, cancel your cable and put in an order!

Other considerations....

I work as support for a VoIP Provider. When a user calls in with call quality issues we look (at Level 1) at 2 things first....

i. You didn't really specify network settings. Is the VoIP ATA both behind your Modem AND a Router ?? You may need to open ports or stick the ATA in a DMZ for it to get to the Sip servers correctly.

ii. We usually run pings and traceroutes. As you stated you have a 5 Mb pipe, so it should be good, but you never know. The VoIP service lives on your Internet connection and if that is flaky, VoIP will be flaky.

Good Luck.

Data traffic on the web does not suffer from packet delays.

Worst case the computer request a resend.

Delay a voip packet and you know the result. Broken and choppy audio.

Nothing you can do about it.

Not ready for prime time. Ya Think?

Lee

This question was closed by the author