Tim
What about the confirmation tone (Thank You) for the * codes working on 'sip7' and getting a "busy" confirmation tone on 'sip' ?
Printable View
Tim
What about the confirmation tone (Thank You) for the * codes working on 'sip7' and getting a "busy" confirmation tone on 'sip' ?
Open a ticket on it with info on how to reproduce and devs will look into it. Could be a bug.Quote:
Originally Posted by chevyman
Tim
Sip7.voipwelcome.com is unstable, sometimes i'll make a calls and the call don't go through, then it looses registration and I have to switch back to sip.voipwelcome.com.
When i do a trace to sip7.voipwelcome.com its not very good to liquidweb.com from here in the Seattle area, its a lot better to softlayer.com on sip.voipwelcome.com.
Is there any chance Voipo going to have a sip in the Northwest?
Quote:
Originally Posted by chevyman
I too get better traceroute results to Texas but find sip7 works very well from Bremerton. Who is your ISP chevyman?
74ms but my jitter is relatively low.
Code:C:\>tracert sip7.voipwelcome.com
Tracing route to sip7.voipwelcome.com [72.52.231.45]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [172.31.125.1]
2 9 ms 10 ms 11 ms 10.28.0.1
3 13 ms 11 ms 11 ms static-24-113-126-254.wavecable.com [24.113.126.254]
4 13 ms 11 ms 10 ms wave-gw.ae0.sea-bdr0.noanet.net [64.146.252.249]
5 12 ms 13 ms 13 ms xe-0-0-0.3006.oly-cor1.noanet.net [64.184.178.22]
6 17 ms 17 ms 17 ms xe-0-3-1.3026.ptl-bdr0.noanet.net [64.184.178.89]
7 16 ms 17 ms 17 ms te3-3.ccr01.pdx01.atlas.cogentco.com [38.104.104.181]
8 17 ms 18 ms 16 ms te0-0-2-2.rcr11.pdx02.atlas.cogentco.com [154.54.0.86]
9 20 ms 21 ms 21 ms te0-3-0-2.ccr21.sea01.atlas.cogentco.com [154.54.40.118]
10 21 ms 20 ms 22 ms be2083.ccr21.sea02.atlas.cogentco.com [154.54.0.250]
11 48 ms 42 ms 41 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
12 52 ms 51 ms 52 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
13 64 ms 63 ms 64 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
14 77 ms 76 ms 76 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
15 82 ms 76 ms 76 ms be2005.ccr21.ord03.atlas.cogentco.com [66.28.4.74]
16 77 ms 77 ms 77 ms be2409.rcr11.b002281-5.ord03.atlas.cogentco.com[154.54.29.66]
17 101 ms 101 ms 94 ms cogent-chi.liquidweb.com [38.104.103.166]
18 72 ms 71 ms 71 ms lw-dc3-core2-te8-16.rtr.liquidweb.com [209.59.157.229]
19 74 ms 74 ms 73 ms lw-dc3-dist16-po6.rtr.liquidweb.com [69.167.128.95]
20 74 ms 73 ms 73 ms 72.52.231.45
Trace complete.
Same here. SIP7 doesn't look as good "on paper", but seems to work better in practice.Quote:
Originally Posted by chpalmer
But now that the TCP flooding has been cleaned up, SIP in Texas seems to work pretty well too.
Yes, we're planning to add a west coast POP soon.Quote:
Originally Posted by chevyman
We still feel Dallas is the best for 99% of customers and the connectivity there is very robust especially since Softlayer is now owned by IBM, but we understand that there are a handful of people that may have a better connection to a different DC so that's where sip7 comes in and we're going to add a west coast option soon.
I'm using Centurylink (old Qwest), i think they are getting cheap. A while back i was having problems and found they had started to use Comcast for a while and now it seems they are using some (zip.zayo.com) whoever they are. here is a trace back on 9-2013.
http://forums.voipo.com/showthread.p...8805#post58805
It was 71 ms to texas now i'm getting 125 ms
when i do a voip quality test with megapath's test, i get good results with San Francisco, so that would be a good west coast option, other than Seattle :)Quote:
Originally Posted by VOIPoTim
For those of you wanting a west coast node, how is your connection to this IP? 198.55.111.5Quote:
Originally Posted by chevyman
It's is a facility we're considering.
I'm not west coast, but here's some data. I'm using Comcast in Texas.
west coast server
198.55.111.5
53ms avg
14 hops
here's sip7
72.52.231.45
58ms avg
14 hops
and dallas
67.228.182.2
18ms avg
10 hops