rizzo2dial
Premium
join:2004-08-05
edit:
May 4th, @12:59PM
| reply to akant
Re: [Other] axvoice - performance problems
I've got Axvoice service on both their RNK reseller network (sip.axvoice.com a.k.a. sip.rnkcomm.com) as well as their (former beta) Magnum network (magnum.axvoice.com).
Call quality on the RNK network is for the most part OK, but I have noticed a considerable increase in quality issues on it this year. Calls don't always go through, sometimes when they connect they're poor quality (where hanging up and re-establishing the call typically does the trick), have been hearing noticeable echo on some (but not all) incoming calls, etc.
As for the Magnum network, it worked great while it was in BETA but has since become completely useless. I signed up for their $0/mo OUTBOUND ONLY plan (@ 1.5¢/min usage) and pre-paid $10. I've used less than 50¢ worth of service because OUTBOUND call quality has been completely unintelligible. In fact, I'm at the point where I'd rather get refunded than continue to try and use this service.
I've tested the Magnum service at several locations, and in all cases, the RNK network worked fine at each location, but the Magnum network for outbound traffic, was completely unusable. When talking over that network, my transmitted speech came out incomplete/fragmented on the calling end. (Since I only have outbound service now on the Magnum network, I'm unable to test whether the same issue occurs w/ incoming calls). I emailed Axvoice about this and a voicemail issue a few weeks ago, but they only responded to the voicemail issue. Thus, I haven't been using the Magnum network since.
Clarification: Incoming voice (i.e. what I hear) on the Magnum network sounds crystal clear. Outbound Voice (i.e. what my callers hear) suffers from the the incomplete/fragmented problem described above.
I have also since discovered that calls from the Magnum Network to the RNK network are downright horrible. I did the test a few weeks ago so am not 100% fresh on the results, but I believe that call quality was awful bi-directional. I suspect it's an internal routing configuration within Axvoice's network causing issues between the RNK side and the Magnum side.
Rizzo |
|
axvoice
join:2007-08-20
NY | Anyone having issues with the outbound call quality please PM your username. We'll work with you to resolve it. |
|
deliberate
Premium
join:2002-10-25
| reply to rizzo2dial
said by rizzo2dial  :I've got Axvoice service on both their RNK reseller network (sip.axvoice.com a.k.a. sip.rnkcomm.com) as well as their (former beta) Magnum network (magnum.axvoice.com). I've got both as well but haven't even had time to check out the beta/magnum service yet tho I did start paying for it earlier. I've used the old RNK-based service as a backup VOIP service for quite some time now but I only use it occasionally so don't have a good basis to really judge.
Nonetheless, finding this thread caused me to check my connectivity to both servers and I find that coming from Cox in Henderson/LasVegas I get 100ms either way. The path from here to Magnum wanders around in Cox for awhile then up thru Seattle, Vancouver, across to Toronto and finally NYC.
Guess I'll be dropping one or the other, or perhaps even both, soon ... when I get time to look more closely at it.
BTW: I've started with BroadVoice for 2 years and then a couple years with SunRocket before moving on to ViaTalk (mid-way thru my paid 2yr signup). Why can't VOIP be easier?
Thanks to all previous posters,
- Don |
|
akant
join:2008-05-03
| reply to rizzo2dial
What rizzo2dial is describing is what I am experiencing. I will setup a call with a friend in town and they experience choppy / lost voice signal from me. I always hear them fine, but outgoing media packets or something from me seem to just disappear. This has happened less on magnum since I moved from sip.axvoice.com but still occurs. It seems that it happens during the day time more often.
I am also starting to get SIP 503 errors when attempting to establish outbound calls. I will dial the same number 5 times outbound and only get 2 of the calls to go through. I have just emailed support on this.
Kenny |
|
