Hi all. I'm also on Teksavvy cable (15/1) and having voice quality problems, although I get some breakup/choppiness on incoming voice as well. I set up my SPA2102 using Mango's guide and have tried different RTP settings, to no avail.
To check my cable connection and routing quality I used Ping Plotter to monitor my line quality to various Voip.ms servers over a couple days and my Teksavvy connection (from Toronto) appears to be solid to all the destinations: low pings, low jitter and no ping loss. So I would think that despite the coincidence of endiz and I both having problems, the problem seems more likely to be on the side of Voip.ms. For another test, on the advice from someone I uploaded a continuous test tone WAV file to voip.ms and set up an IVR with an option to listen to the WAV file. When I call, from either a POTS line or other line, and trigger the IVR test tone, I hear periodic blips in the test tone which should not be there. Doesn't this sound lik efurther evidence of a routing or server problem on Voip.ms's end?
I have opened a ticket with a detailed report of my troubleshooting so far but the response so far was just to switch servers. I have since switched from Toronto2 to Chicago servers and encountered voice problems at least as bad.
To check my cable connection and routing quality I used Ping Plotter to monitor my line quality to various Voip.ms servers over a couple days and my Teksavvy connection (from Toronto) appears to be solid to all the destinations: low pings, low jitter and no ping loss. So I would think that despite the coincidence of endiz and I both having problems, the problem seems more likely to be on the side of Voip.ms. For another test, on the advice from someone I uploaded a continuous test tone WAV file to voip.ms and set up an IVR with an option to listen to the WAV file. When I call, from either a POTS line or other line, and trigger the IVR test tone, I hear periodic blips in the test tone which should not be there. Doesn't this sound lik efurther evidence of a routing or server problem on Voip.ms's end?
I have opened a ticket with a detailed report of my troubleshooting so far but the response so far was just to switch servers. I have since switched from Toronto2 to Chicago servers and encountered voice problems at least as bad.