how-to block ads
|
MartinM
join:2008-07-21
Montreal, QC
| Information
I would like to add that we're not "Just proxying" otherwise we would have servers all over the place. Each location is has been selected thoroughly in regard to the Tier-1 routes from one data center to another. For example, if you have a DID in UK1 and use the US3 Server, the DID is connected to our provider's pop in Los Angeles and then connected to the US3 Server for delivery to customer. Our uplinks with our carriers/providers is much stable than what can be achieved from a DSL or Cable Connection. That is the advantage of using a server close to your location.
The myth that the Direct Peering with the Carrier of the RTP will improve your quality is not true. While it could, in theory, reduce your latency if the carrier is closer to your location, in most cases it is not. The other reason the majority of VoIP providers will not re-invite their RTP Stream to you, is that it causes a lot of issues with users behind routers/nat. Nowadays, most users are behind nat.
I'm very sorry to hear that you have had issues with out service. I verified our ticket for today, I'm not sure if you are the users in question but our sys admin modified the route to USA for your account in hope perhaps this would resolve your issues. If it doesn't, there's probably some kind of issue in regard to compatibility with our equipment and yours. Let us know via our support system if this fixed your issue.
best regards,
Martin Mercier
VoIP.ms | |
espaeth
Digital Plumber
Premium,MVM
join:2001-04-21
Minneapolis, MN
 ·voip.ms
·Vitelity VOIP
·Callcentric
·VoiceStick
·ViaTalk
 ·Comcast
 ·Embarq
| said by MartinM  :The myth that the Direct Peering with the Carrier of the RTP will improve your quality is not true. I have a pile of anecdotal evidence to suggest otherwise, both on my side and remote parties of the calls I participate in.
said by MartinM :While it could, in theory, reduce your latency if the carrier is closer to your location, in most cases it is not. The real payoff isn't in the latency reduction, it's in getting more crap out of the middle of the voice transport path. Working with companies that broker connections directly to media gateways eliminates a lot of the risk of having servers running multiple processes mangling the call quality. Servers proxying the media stream have the potential to become overwhelmed and have momentary hits on managing the packet-to-packet bridging of individual RTP streams, while a properly designed carrier network will have gateways that cannot be overrun as the SBCs will run out of slots to assign calls before network capacity is saturated. The media gateways being network "appliance" hardware also has the added benefit of not allowing a botched cron job impact call quality; the purpose of the platform is focused and protected.
said by MartinM :The other reason the majority of VoIP providers will not re-invite their RTP Stream to you, is that it causes a lot of issues with users behind routers/nat. Nowadays, most users are behind nat. For providers catering specifically to residential end users, I completely agree this is a necessary evil based on the realities of end-user connectivity through NAT. That said, I asked before signing up if direct RTP would be supported: »Re: [Other] VOIP.MS Then it turned out when I opened a ticket to ask for that to be setup on my account it was not available as an option. Fair enough.
My biggest gripe was that call quality was too inconsistent. The value route started out being absolutely perfect, then it was plagued with DTMF issues so I switched to the premium US route, but eventually call quality became too variable there to be trusted as well. Maybe if I had spent more time bouncing between servers I could have worked out better quality, but since I already had other carriers in my dialplan delivering rock solid consistent calls for (at the time) slightly higher pricing, it just made sense to use them instead. Now that those providers are offering 1c flat-rate the choice for me is even more straight forward.
said by MartinM : I'm not sure if you are the users in question but our sys admin modified the route to USA for your account in hope perhaps this would resolve your issues. That wasn't me. I'm using other providers for US term. I did open a ticket a few days back about not being able to hit UK NTS prefixes (+44 08*), and got a response back that you've disabled them due to fraud. Fair enough, I've lined up other providers to meet those needs.
At this point I've got my PAYG DID with Voip.ms, and I've been happy with the quality on that. | |
MartinM
join:2008-07-21
Montreal, QC
| I can ensure you we do not run "proxies" with 'butched up cron jobs'. Seems that your issues were probably due to some sort of incompatibility with your equipment or you had network issues between you and the server you were connecting. Thank you for your feedback. | |
-
| Forums » comments on review of voip.ms | | |
|
