[Future-Nine] sip2 is alive again!

Author	All Replies
nitzan join:2008-02-27 ·Comcast ·ViaTalk	[Future-Nine] sip2 is alive again! After replacing pretty much anything that can be replaced... this little server that could is finally alive again! Anybody feels like testing it? Just change your proxy to sip2.future-nine.com. In theory everything should be working properly on it - including incoming calls. Theory aside, I'd like to put it to action a bit before we turn it up in production. Please let me know how it works for you! Thanks!! -- Nitzan Kon, CEO Future Nine Corporation
	to forum · permalink · · 2008-07-24 12:18:12 ·
baj475 join:2004-11-02 Chico, CA	Changed proxy to sip2.future-nine.com. Will let you know if I experience any problems.
	to forum · permalink · · 2008-07-24 14:37:46 ·
JohnnyBeGood join:2008-04-18 Seattle, WA	reply to nitzan Have you set it up so that its not pingable? I would like to see if it will improve my latency. C:\Documents and Settings\Johnny>tracert sip2.future-nine.com Tracing route to sip2.future-nine.com [65.111.186.2] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1] 2 * * * Request timed out. 3 8 ms 9 ms 11 ms GE-1-1-ur01.federalway.wa.seattle.comcast.net [6 8.86.98.201] 4 12 ms 24 ms 13 ms te-8-4-ar02.burien.wa.seattle.comcast.net [68.86 .96.181] 5 12 ms 87 ms 88 ms 68.86.90.222 6 14 ms 14 ms 15 ms 68.86.90.221 7 17 ms 13 ms 15 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.10 6] 8 13 ms 14 ms 13 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105] 9 25 ms 13 ms 17 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62] 10 50 ms 58 ms 49 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54] 11 114 ms 140 ms 54 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 12 76 ms 71 ms 72 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106] 13 73 ms 67 ms 71 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.136.146] 14 65 ms 72 ms 72 ms ae-83-83.ebr3.Dallas1.Level3.net [4.69.136.161] 15 100 ms 89 ms 89 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22] 16 94 ms 86 ms 117 ms ae-11-51.car1.Atlanta1.Level3.net [4.68.103.2] 17 86 ms 88 ms 85 ms 4.68.110.74 18 93 ms 92 ms 95 ms jcvlflnj2m6-so-3-0-0.ip.epik.net [216.22.67.253] 19 98 ms 110 ms 100 ms miamfllr1m6-so-3-0-0.ip.epik.net [216.22.67.229] 20 98 ms 98 ms 100 ms miamfllr2m6-so-6-0-0.ip.epik.net [216.22.67.226] 21 96 ms 96 ms 95 ms miamfllrh07-custbr-opensystems.ip.epik.net [216. 22.64.94] 22 97 ms 99 ms 96 ms 64.251.7.99 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. C:\Documents and Settings\Johnny>
	to forum · permalink · · 2008-07-24 14:59:06 ·
nitzan join:2008-02-27	Try to ping it now. I don't think it'll make much of a difference to latency since it's the same data center. BUT- our next server is planned on the west coast - either Seattle or LA.
	to forum · permalink · · 2008-07-24 15:04:38 ·
yahoo2003 join:2007-11-02 Mclean, VA	reply to nitzan said by nitzan : After replacing pretty much anything that can be replaced... this little server that could is finally alive again! I will put one of my peers (PAP2) to "sip" and the other (IP8100) to "sip2" so my VOIP will be so reliable .
	to forum · permalink · · 2008-07-24 15:26:07 ·
ropeguru Premium join:2001-01-25 Hollywood, FL clubs: edit: July 24th, @03:39PM	reply to JohnnyBeGood Looks good from my FreePBX box. :D traceroute to sip2.future-nine.com (65.111.186.2), 30 hops max, 40 byte packets 1 1-120-60-69.serverpronto.com (69.60.120.1) 0.811 ms 1.101 ms 2.385 ms 2 ge2-edge.mia.infolink.com (64.251.0.65) 0.110 ms 0.102 ms 0.100 ms 3 64.251.7.99 (64.251.7.99) 0.263 ms 0.378 ms 0.506 ms 4 2-181-111-65.serverpronto.com (65.111.186.2) 0.263 ms !X 0.253 ms !X 0.25
	to forum · permalink · · 2008-07-24 15:38:52 ·
JohnnyBeGood join:2008-04-18 Seattle, WA edit: July 24th, @03:41PM	reply to nitzan Much better. C:\Documents and Settings\Johnny>tracert sip2.future-nine.com Tracing route to sip2.future-nine.com [65.111.186.2] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1] 2 * * * Request timed out. 3 9 ms 13 ms 16 ms GE-1-1-ur01.federalway.wa.seattle.comcast.net [6 8.86.98.201] 4 13 ms 14 ms 9 ms te-8-4-ar02.burien.wa.seattle.comcast.net [68.86 .96.181] 5 10 ms 16 ms 9 ms 68.86.90.222 6 23 ms 13 ms 24 ms 68.86.90.221 7 16 ms 22 ms 18 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.10 6] 8 17 ms 18 ms 17 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105] 9 32 ms 15 ms 33 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62] 10 47 ms 46 ms 53 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54] 11 54 ms 43 ms 49 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 12 75 ms 82 ms 77 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106] 13 64 ms 73 ms 68 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.136.146] 14 65 ms 67 ms 75 ms ae-83-83.ebr3.Dallas1.Level3.net [4.69.136.161] 15 103 ms 103 ms 110 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22] 16 86 ms 180 ms 233 ms ae-11-51.car1.Atlanta1.Level3.net [4.68.103.2] 17 88 ms 86 ms 99 ms 4.68.110.74 18 107 ms 91 ms 103 ms jcvlflnj2m6-so-3-0-0.ip.epik.net [216.22.67.253] 19 104 ms 105 ms 102 ms miamfllr1m6-so-3-0-0.ip.epik.net [216.22.67.229] 20 99 ms 101 ms 99 ms miamfllr2m6-so-6-0-0.ip.epik.net [216.22.67.226] 21 101 ms 119 ms 99 ms miamfllrh07-custbr-opensystems.ip.epik.net [216. 22.64.94] 22 101 ms 96 ms 95 ms 64.251.7.99 23 95 ms 98 ms 104 ms 2-181-111-65.serverpronto.com [65.111.186.2] Trace complete. C:\Documents and Settings\Johnny> said by nitzan : Try to ping it now. I don't think it'll make much of a difference to latency since it's the same data center. BUT- our next server is planned on the west coast - either Seattle or LA. Seattle Please :)
	to forum · permalink · · 2008-07-24 15:40:09 ·
nitzan join:2008-02-27 ·Comcast ·ViaTalk	reply to yahoo2003 said by yahoo2003 : said by nitzan : After replacing pretty much anything that can be replaced... this little server that could is finally alive again! I will put one of my peers (PAP2) to "sip" and the other (IP8100) to "sip2" so my VOIP will be so reliable . Eventually we're just going to load balance them so it shouldn't matter - but if you wanted to hardcode one or another you can use: 64.251.23.244 for sip 65.111.186.2 for sip2 85.17.148.32 for europa
	to forum · permalink · · 2008-07-24 22:05:30 ·
DSLHeadaches join:2001-01-03 Woodland Hills, CA ·VoiceStick ·RoadRunner Cable	reply to nitzan LA Please that is for the new server... its great to hear there could be one on the West Coast, that would certainly make my decision a simple one in a few days when I chose the new provider; ping time was one of my concerns about going with FN.
	to forum · permalink · · 2008-07-24 22:37:44 ·
nitzan join:2008-02-27	Out of curiosity - what is your traceroute looking like from LA to 4.71.156.18?
	to forum · permalink · · 2008-07-24 23:09:22 ·
Javaguy216 join:2005-03-18 Cleveland, OH	reply to nitzan nitzan, I will test it and let you know the results.
	to forum · permalink · · 2008-07-25 13:54:23 ·
meister_sd Premium join:2006-01-29 La Mesa, CA	reply to nitzan said by nitzan : Out of curiosity - what is your traceroute looking like from LA to 4.71.156.18? From San Diego: H:\>tracert 4.71.156.18 Tracing route to er2-sea-B-g2.bb.spectrumnet.us [4.71.156.18] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 74.7.228.21 2 10 ms 9 ms 7 ms 172.31.20.138 3 6 ms 7 ms 8 ms car00-3-0-2.sndgca02.cbeyond.net [192.168.59.2] 4 8 ms 8 ms 9 ms ccr00-401.sndgca02.cbeyond.net [192.168.58.60] 5 10 ms 222 ms 224 ms ge-6-23.car2.SanDiego1.Level3.net [4.79.34.25] 6 8 ms 16 ms 8 ms ae-11-11.car1.SanDiego1.Level3.net [4.69.133.209] 7 22 ms 25 ms 14 ms ae-5-5.ebr1.LosAngeles1.Level3.net [4.69.133.206] 8 19 ms 17 ms 24 ms ae-71-71.csw2.LosAngeles1.Level3.net [4.69.137.6] 9 12 ms 17 ms 16 ms ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.37] 10 36 ms 32 ms 25 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9] 11 30 ms 24 ms 32 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234] 12 29 ms 24 ms 33 ms ae-81-81.ebr1.SanJose1.Level3.net [4.69.134.201] 13 47 ms 40 ms 49 ms ae-3.ebr1.Seattle1.Level3.net [4.69.132.50] 14 38 ms 36 ms 36 ms ae-14-55.car4.Seattle1.Level3.net [4.68.105.133] 15 39 ms 40 ms 42 ms er2-sea--g2.bb.spectrumnet.us [4.71.156.18] Trace complete. H:\> Not bad at all.
	to forum · permalink · · 2008-07-25 22:27:00 ·
nitzan join:2008-02-27	Cool. I wonder which one of the two (LA or Seattle) has a better connection to Japan...
	to forum · permalink · · 2008-07-26 03:26:30 ·
Test99 Premium join:2003-04-24 San Jose, CA ·DSL EXTREME ·InPhonex edit: July 26th, @05:00AM	There's a list of cables here: »en.wikipedia.org/wiki/List_of_in···s_cables. Here are some cables linking the US and Japan: C2C Hillsboro, Oregon, Redondo Beach and Los Angeles, California - 320 gigabits/sec, expandable to 7,560? CUCN Bandon, Oregon and San Luis Obispo, California - 80 gigabits/sec Japan-US Manchester and San Luis Obispo, California - 80 gigabits/sec, expandable to 640 NPC Pacific City, Oregon - 1.3 gigabits/sec -- 50775@fwd.pulver.com
	to forum · permalink · · 2008-07-26 04:20:48 ·
nitzan join:2008-02-27	Yep.. I found that earlier too. Overall looks about the same for both... I think.
	to forum · permalink · · 2008-07-26 05:26:49 ·
Test99 Premium join:2003-04-24 San Jose, CA	I don't see any cables out of Seattle. -- 50775@fwd.pulver.com
	to forum · permalink · · 2008-07-26 05:31:31 ·
nitzan join:2008-02-27	Seattle is probably something like 3 ms to Hillsboro, OR. I guess overall anything on the west coast would be fine as long as it has a good connection to any of the cables.
	to forum · permalink · · 2008-07-26 05:37:11 ·
fareedf join:2008-01-25 Portland, OR	Why not in Hillsboro, Oregon. Hillsboro is Silicon Valley of OR. This is the state with no sales tax.
	to forum · permalink · · 2008-07-26 12:57:40 ·
baysoor join:2002-03-12 San Jose, CA ·AT&T Yahoo edit: July 27th, @04:17PM	reply to nitzan 4.71.156.18 looks good from NorCal. When can you add this west coast server? 3 64.164.107.1 (64.164.107.1) 20.000 ms 21.688 ms * 4 * * * 5 * * * 6 * * * 7 * * * 8 * ae-71-71.ebr1.SanJose1.Level3.net (4.69.134.197) 20.039 ms 20.419 ms 9 ae-3.ebr1.Seattle1.Level3.net (4.69.132.50) 41.223 ms 41.758 ms 42.065 ms 10 ae-14-55.car4.Seattle1.Level3.net (4.68.105.133) 206.030 ms 206.734 ms 207.611 ms 11 er2-sea-B-g2.bb.spectrumnet.us (4.71.156.18) 47.534 ms 49.876 ms 52.578 ms BTW SIP2 seems to take a different route (compared to sip.future-nine.com) and does not involve cogent for some reason. Are they in same data center?
	to forum · permalink · · 2008-07-27 16:01:44 ·
nitzan join:2008-02-27 ·Comcast ·ViaTalk	said by baysoor : BTW SIP2 seems to take a different route (from sip.future-nine.com) and does not involve cogent for some reason. Are they in same data center? Yep- same data center.. but I believe it's a different switch so it may be going through a different route for capacity reasons? not sure.
	to forum · permalink · · 2008-07-27 16:07:31 ·


Monday, 01-Dec 10:40:42	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 9 years online! © 1999-2008 dslreports.com. page compression OFF