If you have your PBX hosted at some distance from your office and phones, how much does that affect the call quality? Seems those providing hosting are based in Auckland whereas I'm in Wgton. And what about setting up a cloud based pbx on EC2?
gchiu: If you have your PBX hosted at some distance from your office and phones, how much does that affect the call quality? Seems those providing hosting are based in Auckland whereas I'm in Wgton. And what about setting up a cloud based pbx on EC2?
latency from wellington to auckland is about 10 msec. it'd be faster/smoother than hosting on your own dsl connection in wellington if coming from another dsl connection.
also, just because you may have a hosted pbx in wellington doesn't mean that their phone ports don't route via auckland. i considered this for a bit, when i was thinking about how no voip providers seem to host in christchurch (where the latency is slightly higher). but it's probably the case that no voip providers are operating directly in wellington too.
that said considering you have multiple phones in one office - if you have poor bandwidth then everyone will be effected.
could pbx on ec2 would be pretty atricious. ec2 performance from nz tends to be terrible. you'd probably be fine with a cloud based pbx in sydney... but i'd stay from asia/us cloud providers.
I was thinking of using rentpbx.com for a home pbx system .. save me the power on running my own box. I would continue to use Open VFX as the SIP provider.
gchiu: I was thinking of using rentpbx.com for a home pbx system .. save me the power on running my own box. I would continue to use Open VFX as the SIP provider.
it looks like their closest node is in los angeles.. using a voip provider in the US would be a lot more effective than a NZ one.. otherwise you're doubling the latency (plus a bit probably, xnet's routing is a bit lousy.. goes through sydney)
trace from los angeles, another host in los angeles was pretty much the same. vocus are peering in san jose for any2ix, which is one of the major internet exchanges in california, which means traffic has about 8 msec to san jose.. then 125'ish to new zealand, unless you go via sydney...
# traceroute pan.wxnz.net traceroute to pan.wxnz.net (58.28.20.150), 64 hops max, 40 byte packets 1 174.136.111.233 (174.136.111.233) 57.25 ms 3.344 ms 228.476 ms 2 vocus.com.au.any2ix.coresite.com (206.223.143.136) 8.239 ms 8.269 ms 8.285 ms 3 pos-0-0-1.cor02.syd03.nsw.VOCUS.net.au (114.31.199.47) 160.507 ms 160.626 ms 160.432 ms 4 pos-0-0-3.bdr02.akl01.akl.vocusconnect.co.nz (114.31.202.77) 159.798 ms 159.750 ms 159.798 ms 5 ip-89.202.31.114.VOCUS.net.au (114.31.202.89) 160.595 ms 160.565 ms 160.468 ms 6 ten-0-1-0.bdr01.akl02.akl.VOCUS.net.au (114.31.202.42) 160.787 ms 160.855 ms 160.785 ms 7 as17435.cust.bdr01.akl02.akl.VOCUS.net.au (114.31.203.90) 160.406 ms 160.520 ms 160.540 ms 8 ip-58-28-21-1.wxnz.net (58.28.21.1) 160.893 ms 161.46 ms 161.80 ms 9 *^C
pretty much with voip latency you have to add the latency of each connection.
so if you have a cellphone call that has some latency, if you have an international call that has some latency etc.
so if you're in wellington on dsl with no interleaving, with a provider that has good routes to los angeles, best case latency is likely to be about 140 to 145 msec. then from there to xnet is around 160 msec latency. so you're already sitting at 300 msec latency.. then say you do a call to sydney.. then you may add another 30 msec latency.. then they're on a cellphone and you add another 80 msec latency.. then you're sitting around 410 msec latency and you're both talking at the same time, and it's hard to communicate.
but then if you had pabx in auckland.. and you connect to sip provider in auckland.. then it's like 20 msec to auckland.. 1 from auckland to auckland.. then you do a cellphone call to christchurch and it's 20 msec to christchurch.. 80 msec to cellphone .. and you're at like 121 msec latency.. and it's still not too bad..
Rent a local VPS or VM. I run a number of clients' PBX's on an ESXi server in Auckland including some from Wellington and call quality is always excellent.
Actually it wasn't so terrible. I signed up to rentpbx.com for a PIAF purple and configured an extension. Then called my home phone which is a POTS line. Voice quality was acceptable to me. I called another number and they said I sounded distant.
Maybe I have a 150 msec ping to them but I wonder if WXC have a much lower ping time to them?
The cost is $US14.99 a month, and I can cancel in 7 days for full refund which I will probably do. But I get a 1.2ghz processor, with 200Gb of traffic for this.
gchiu: Actually it wasn't so terrible. I signed up to rentpbx.com for a PIAF purple and configured an extension. Then called my home phone which is a POTS line. Voice quality was acceptable to me. I called another number and they said I sounded distant.
Maybe I have a 150 msec ping to them but I wonder if WXC have a much lower ping time to them?
The cost is $US14.99 a month, and I can cancel in 7 days for full refund which I will probably do. But I get a 1.2ghz processor, with 200Gb of traffic for this.
wxc probably have a higher ping to them based upon my traceroutes going via sydney. can you get a shell and do a traceroute?
I just realised I was using 2talk. But here are both.
traceroute to pan.wxnz.net (58.28.20.150), 30 hops max, 60 byte packets 1 unifiedweb.net (204.14.52.33) 0.315 ms 0.295 ms 0.517 ms 2 66-109-98-53.SW1.layer42.net (66.109.98.53) 0.811 ms 0.797 ms 0.781 ms 3 xe5-1.core1.mpt.layer42.net (69.36.239.241) 12.448 ms 12.836 ms 12.828 ms 4 vocus.com.au.any2ix.coresite.com (206.223.143.136) 25.688 ms 25.674 ms 25 .399 ms 5 ten-0-2-0.bdr01.sjc01.ca.VOCUS.net.au (114.31.199.116) 169.179 ms 169.152 ms 169.118 ms 6 pos-0-0-1.cor01.syd03.nsw.VOCUS.net.au (114.31.199.45) 168.627 ms 168.972 ms 168.951 ms 7 pos-0-0-3.bdr01.akl01.akl.vocusconnect.co.nz (114.31.202.75) 176.031 ms 17 6.021 ms 176.007 ms 8 ten-0-1-0.bdr01.akl02.akl.VOCUS.net.au (114.31.202.42) 176.532 ms 176.184 ms 174.982 ms 9 as17435.cust.bdr01.akl02.akl.VOCUS.net.au (114.31.203.90) 166.885 ms 166.8 86 ms 166.863 ms 10 ip-58-28-21-1.wxnz.net (58.28.21.1) 178.362 ms * *
and 2talk
traceroute to 2talk.co.nz (202.180.76.163), 30 hops max, 60 byte packets 1 unifiedweb.net (204.14.52.33) 0.311 ms 0.298 ms 0.557 ms 2 66-109-98-53.SW1.layer42.net (66.109.98.53) 0.545 ms 0.534 ms 0.733 ms 3 xe2-4.core1.pao.layer42.net (69.36.239.149) 4.876 ms 4.872 ms 4.858 ms 4 f0-0.pabr1.netgate.net.nz (198.32.176.97) 1.162 ms 1.155 ms 1.142 ms 5 ae0.sjbr2.global-gateway.net.nz (203.96.120.73) 1.917 ms 1.906 ms 1.891 m s 6 xe7-0-0.tkbr9.global-gateway.net.nz (202.50.232.17) 130.202 ms 126.129 ms 130.544 ms 7 xe0-0-0.akbr5.global-gateway.net.nz (202.50.232.73) 160.233 ms 160.220 ms 150.485 ms 8 callplus-int.akbr5.global-gateway.net.nz (202.50.234.62) 218.996 ms 218.99 4 ms 218.980 ms 9 vlan7-cpcak3-e1.tranzpeer.net (202.180.81.62) 131.128 ms 131.403 ms 131.3 96 ms 10 2talk.peer.tranzpeer.net (119.224.138.17) 130.702 ms 131.344 ms 131.566 m s
gchiu: I just realised I was using 2talk. But here are both.
traceroute to pan.wxnz.net (58.28.20.150), 30 hops max, 60 byte packets 1 unifiedweb.net (204.14.52.33) 0.315 ms 0.295 ms 0.517 ms 2 66-109-98-53.SW1.layer42.net (66.109.98.53) 0.811 ms 0.797 ms 0.781 ms 3 xe5-1.core1.mpt.layer42.net (69.36.239.241) 12.448 ms 12.836 ms 12.828 ms 4 vocus.com.au.any2ix.coresite.com (206.223.143.136) 25.688 ms 25.674 ms 25 .399 ms 5 ten-0-2-0.bdr01.sjc01.ca.VOCUS.net.au (114.31.199.116) 169.179 ms 169.152 ms 169.118 ms 6 pos-0-0-1.cor01.syd03.nsw.VOCUS.net.au (114.31.199.45) 168.627 ms 168.972 ms 168.951 ms
hmm you have the same problem of routing through australia. as well as that, it appears to be giving high pings to san jose.. like from two different los angeles hosts there is around 8.4 msec ping to hop 4...
traceroute to 2talk.co.nz (202.180.76.163), 30 hops max, 60 byte packets 1 unifiedweb.net (204.14.52.33) 0.311 ms 0.298 ms 0.557 ms 2 66-109-98-53.SW1.layer42.net (66.109.98.53) 0.545 ms 0.534 ms 0.733 ms 3 xe2-4.core1.pao.layer42.net (69.36.239.149) 4.876 ms 4.872 ms 4.858 ms 4 f0-0.pabr1.netgate.net.nz (198.32.176.97) 1.162 ms 1.155 ms 1.142 ms 5 ae0.sjbr2.global-gateway.net.nz (203.96.120.73) 1.917 ms 1.906 ms 1.891 m s 6 xe7-0-0.tkbr9.global-gateway.net.nz (202.50.232.17) 130.202 ms 126.129 ms 130.544 ms 7 xe0-0-0.akbr5.global-gateway.net.nz (202.50.232.73) 160.233 ms 160.220 ms 150.485 ms 8 callplus-int.akbr5.global-gateway.net.nz (202.50.234.62) 218.996 ms 218.99 4 ms 218.980 ms 9 vlan7-cpcak3-e1.tranzpeer.net (202.180.81.62) 131.128 ms 131.403 ms 131.3 96 ms 10 2talk.peer.tranzpeer.net (119.224.138.17) 130.702 ms 131.344 ms 131.566 m s
2talk is much better for routing than xnet in this instance.. about 40 msec difference..
also 2talk.. is kind of confirming that this provider is nearer to san jose than los angeles.. which isn't a bad thing.. and should be aiding vocus as that's nearer where they interconnect.. but there's screwed up routes first (and the whole sydney thing)
anyway, it's kind of moot.. routing to the US and back again for NZ phone calls is silly! even for initiation it's not a wonderful thing. what if there's a war? what if there's a cable cut? what if US decides to monitor all phone calls?
i wouldn't be againt zeon's suggestion of getting a nz vps. but i'm under the impression that you don't want to manage such a thing? and in that instance maybe xnet can recommend someone? i'd stay away from 2talk myself if reliability is important. that said - 2talk's interface is world's ahead..
anyway, it's kind of moot.. routing to the US and back again for NZ phone calls is silly! even for initiation it's not a wonderful thing. what if there's a war? what if there's a cable cut? what if US decides to monitor all phone calls?
I guess they'll find out what I am having for dinner that night!
I might hook up a googlevoice account to this and see how it works for talking to US based relatives.
anyway, it's kind of moot.. routing to the US and back again for NZ phone calls is silly! even for initiation it's not a wonderful thing. what if there's a war? what if there's a cable cut? what if US decides to monitor all phone calls?
I guess they'll find out what I am having for dinner that night!
I might hook up a googlevoice account to this and see how it works for talking to US based relatives.
oh i thought this was for office not home use.
i don't like this disturbing trend of relying on overseas services for more and more things. when people can host in NZ they should!
google voice.. and NZ to US shouldn't be nearly as bad as NZ to US to NZ.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
Biddle Corp
