View Full Version : Los Angeles
VOIPoTim
03-04-2010, 12:04 AM
We are looking for a few people to test new potential Los Angeles servers.
You can ping and traceroute sip-west01.voipwelcome.com to check out your connection.
If you have a good connection to it and would like to help test, please contact support@voipo.com and asked to be moved to it.
When we are finished testing, we will automatically move you back to Dallas.
usa2k
03-04-2010, 05:44 AM
I am currently on the Chicago server, but if LA is more useful now ...
Round-Trip: 94.252 min, 100.387 avg, 118.639 max (ms)
Packets: 5 transmitted, 5 received, 0% lostUnless you don't like these numbers?
Ticket ID: JEB-641927 submitted Support did not like my ping times.
My Chicago pings are much better!
Pinging sip-chicago.voipwelcome.com
Round-Trip: 24.794 min, 26.394 avg, 28.470 max (ms)
Packets: 5 transmitted, 5 received, 0% lost
tylerscell1
03-04-2010, 10:38 AM
Sent in a email to support.
tylerscell1
03-04-2010, 11:11 AM
Have you guys ever thought of any Atlanta servers?
We are looking for a few people to test new potential Los Angeles servers.
You can ping and traceroute sip-west01.voipwelcome.com to check out your connection.
If you have a good connection to it and would like to help test, please contact support@voipo.com and asked to be moved to it.
When we are finished testing, we will automatically move you back to Dallas.
I'll chime in since i'm getting 19ms ping times from sip-west01.
I hope i'm able to use a 2nd SIP phone so i can maintain a connection w/ my primary SIP phone to the TX gw?
Support ID: EZN-285677
VOIPoTim
03-04-2010, 02:59 PM
Unfortunately our BYOD SIP credentials are completely isolated from main VOIPo network servers, so the BYOD credentials won't work on any other servers but Dallas.
The other networks are only for provisioned users at this time.
burris
03-04-2010, 03:01 PM
This is what I get from Miami...not too promising..
Tracing route to sip-west01.voipwelcome.com [72.51.46.124]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms burris [192.168.1.1]
2 8 ms 8 ms 7 ms adsl-64-82-1.mia.bellsouth.net [98.64.82.1]
3 17 ms 16 ms 17 ms 70.159.200.229
4 9 ms 8 ms 8 ms 70.159.200.241
5 15 ms 16 ms 14 ms 12.83.4.196
6 15 ms 15 ms 14 ms 12.83.4.61
7 15 ms 14 ms 14 ms 12.83.9.93
8 14 ms 14 ms 13 ms 12.83.9.77
9 14 ms 15 ms 14 ms 74.175.192.130
10 74 ms 74 ms 74 ms cr1.ormfl.ip.att.net [12.122.143.10]
11 74 ms 74 ms 74 ms cr2.hs1tx.ip.att.net [12.122.1.5]
12 * 75 ms 75 ms cr1.dlstx.ip.att.net [12.122.28.157]
13 74 ms 74 ms 75 ms cr2.dlstx.ip.att.net [12.122.1.210]
14 74 ms 73 ms 74 ms cr2.la2ca.ip.att.net [12.122.28.178]
15 73 ms 73 ms 73 ms gar2.lsrca.ip.att.net [12.122.129.49]
16 74 ms 73 ms 73 ms 12.118.130.42
17 73 ms 73 ms 74 ms 216.187.88.58
18 75 ms 74 ms 74 ms sip-west.voipwelcome.com [72.51.46.124]
Trace complete.
Pinging sip-west01.voipwelcome.com [72.51.46.124] with 32 bytes of data:
Request timed out.
Reply from 72.51.46.124: bytes=32 time=74ms TTL=47
Reply from 72.51.46.124: bytes=32 time=74ms TTL=47
Reply from 72.51.46.124: bytes=32 time=75ms TTL=47
Ping statistics for 72.51.46.124:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 75ms, Average = 74ms
usa2k
03-04-2010, 03:29 PM
After mine reached Washington, thats when it went bad.
Tracing route to sip-west01.voipwelcome.com [72.51.46.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 10 ms 21 ms te-8-2-ur02.canton.mi.michigan.comcast.net [68.85.85.89]
4 13 ms 11 ms 9 ms te-9-2-ur02.vanburen.mi.michigan.comcast.net [68.87.190.118]
5 11 ms 9 ms 11 ms te-0-6-0-4-ar01.taylor.mi.michigan.comcast.net [68.87.190.41]
6 24 ms 23 ms 29 ms pos-2-8-0-0-cr01.mclean.va.ibone.comcast.net [68.86.90.105]
7 23 ms 23 ms 83 ms xe-8-3-0.edge1.Washington1.Level3.net [63.210.62.49]
8 35 ms 22 ms 30 ms vlan79.csw2.Washington1.Level3.net [4.68.17.126]
9 33 ms 35 ms 35 ms ae-74-74.ebr4.Washington1.Level3.net [4.69.134.181]
10 110 ms 104 ms 101 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]
11 278 ms 227 ms 220 ms ae-14-60.car4.LosAngeles1.Level3.net [4.69.144.6]
12 * * * Request timed out.
13 * * * Request timed out.
14 93 ms 95 ms 94 ms sip-west.voipwelcome.com [72.51.46.124]
Trace complete.
Unfortunately our BYOD SIP credentials are completely isolated from main VOIPo network servers, so the BYOD credentials won't work on any other servers but Dallas.
The other networks are only for provisioned users at this time.
Ah!
Oh well. Would have been great to get a 19ms connection on BYOD.
caseydoug
03-05-2010, 04:36 PM
Is there a quick way to tell what server I'm on now so I can compare? I think they removed the "preferences" option that listed the current server. My "devices" tab says VOIPo Central, but I don't recall the address.
lost_
03-08-2010, 07:48 PM
sip-central01.voipwelcome.com
sip-eastXX.voipwelcome.com (01, 02)
sip-westXXX.voipwelcome.com (01, 02, ... 100, 101, 102; though 02 and up are the same IP right now)
not sure what Chicago is
patoka
03-09-2010, 03:06 PM
from san diego
1 1 ms 1 ms <1 ms 192.168.100.1
2 12 ms 11 ms 12 ms netblock-68-183-146-1.dslextreme.com [68.183.146.1]
3 12 ms 12 ms 14 ms LAX1.CR1.Gig9-0-3.dslextreme.com [66.51.203.33]
4 136 ms 12 ms 12 ms ge-6-18-115.car1.LosAngeles1.Level3.net [63.209.70.133]
5 12 ms 12 ms 12 ms ae-24-70.car4.LosAngeles1.Level3.net [4.69.144.70]
6 13 ms 12 ms 13 ms 216.187.89.45
7 14 ms 13 ms 15 ms 216.187.88.38
8 14 ms 13 ms 14 ms sip-west.voipwelcome.com [72.51.46.124]
usa2k
03-09-2010, 03:22 PM
from san diego
1 1 ms 1 ms <1 ms 192.168.100.1
...
Show-off! :D
walletless
03-14-2010, 12:43 AM
I'm in seattle, and I signed up for this beta server. So far, things have been very good.
chpalmer
03-14-2010, 07:48 PM
I'm in seattle, and I signed up for this beta server. So far, things have been very good.
Cool another Washington resident here besides me. Bremerton Area...
stevech
03-14-2010, 11:22 PM
from san diego, 10PM hour on a Sunday (zzzz)
1 1 ms 1 ms <1 ms 192.168.100.1
2 12 ms 11 ms 12 ms netblock-68-183-146-1.dslextreme.com [68.183.146.1]
3 12 ms 12 ms 14 ms LAX1.CR1.Gig9-0-3.dslextreme.com [66.51.203.33]
4 136 ms 12 ms 12 ms ge-6-18-115.car1.LosAngeles1.Level3.net [63.209.70.133]
5 12 ms 12 ms 12 ms ae-24-70.car4.LosAngeles1.Level3.net [4.69.144.70]
6 13 ms 12 ms 13 ms 216.187.89.45
7 14 ms 13 ms 15 ms 216.187.88.38
8 14 ms 13 ms 14 ms sip-west.voipwelcome.com [72.51.46.124]
From San Diego North County (858)
Tracing route to sip-west.voipwelcome.com [72.51.46.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 7 ms cpe-72-130-128-1.san.res.rr.com [72.130.128.1]
3 9 ms 7 ms 7 ms wcsdca1-gsr3-ge14-0-4.san.rr.com [24.25.197.89]
4 11 ms 11 ms 8 ms so-0-0-0.gar1.SanDiego1.Level3.net [209.0.8.1]
5 11 ms 28 ms 9 ms ae-14-14.car1.SanDiego1.Level3.net [4.69.142.74]
6 27 ms 17 ms 17 ms ae-5-5.ebr1.LosAngeles1.Level3.net [4.69.133.206
]
7 11 ms 11 ms 12 ms ae-44-90.car4.LosAngeles1.Level3.net [4.69.144.1
98]
8 * * * Request timed out.
9 * * * Request timed out.
10 12 ms 12 ms 15 ms sip-west.voipwelcome.com [72.51.46.124]
Trace complete.
Pinging 72.51.46.125 with 32 bytes of data:
Reply from 72.51.46.125: bytes=32 time=17ms TTL=116
Reply from 72.51.46.125: bytes=32 time=15ms TTL=116
Reply from 72.51.46.125: bytes=32 time=16ms TTL=116
Reply from 72.51.46.125: bytes=32 time=14ms TTL=116
Reply from 72.51.46.125: bytes=32 time=15ms TTL=116
Reply from 72.51.46.125: bytes=32 time=14ms TTL=116
Reply from 72.51.46.125: bytes=32 time=17ms TTL=116
Reply from 72.51.46.125: bytes=32 time=14ms TTL=116
Reply from 72.51.46.125: bytes=32 time=15ms TTL=116
Reply from 72.51.46.125: bytes=32 time=13ms TTL=116
Reply from 72.51.46.125: bytes=32 time=12ms TTL=116
Ping statistics for 72.51.46.125:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 17ms, Average = 14ms
caseydoug
03-15-2010, 12:05 PM
Cool another Washington resident here besides me. Bremerton Area...Seattle, Capitol Hill here.