Digg

Donkeys and Elephants and Delegates,oh my!
Check out the most popular Elections 2008 content on Digg.

SkypeOut Free US Calls NO GO for IPs 70.x.x.x - 79.x.x.x

share.skype.com — Thread on Skype's release page shows a good number of people who are having trouble getting the free landline/mobile US and Canada calling to work. Seems that SkypeOut doesn't like IPs in the 70.x.x.x-79.x.x.x range.

Bury

dwb75 2 years 144 days ago, made popular 2 years 144 days ago

1001 diggs
digg it

212 Comments
Who Dugg It?
Blog It
Email It

akumukun, on 10/12/2007, -5/+34Thanks again, Rogers! I bet you it has to do with packet shaping...
- Crazy_8, on 10/12/2007, -1/+9I think this could be the doing of the telephone companies in general, not just rogers (keep in mind i'm guessing on this, no solid proof this is whats wrong). I know somone with Verizon DSL in Alrlington VA that has a 70.x.x.x and it's not working. I guess the telephone companies didn't like the idea of people making free calls everywere.
  
  Also, to note my IP. I am a 68.x.x.x on Cox comunnications, works great.
- bennypowers, on 10/12/2007, -2/+5Well it certainly would fit their pattern of customer 'service' to date ;)
- pegisys, on 10/12/2007, -0/+8I have 68.x.x.x number as well, I hope they don't block it later because I have been calling family all day :)
- Hydroxyl, on 10/12/2007, -0/+9I'm using Bellsouth in Miami, Florida and I have a 70.x.x.x IP. :(
- kherrick, on 10/12/2007, -0/+18Bell Canada gives me 70.51.x.x and Skype works fine.
- jo3c, on 10/12/2007, -1/+371.x.x.x here not working.. gotta love verizon
  Not working in Southern Illinois
- kensavage, on 10/12/2007, -11/+3Great!!! I'm 71.x.x.x using Comcast. They banned me so I use their crappy VoIP for $35/month. NOT
  
  -Ken
  http://www.kensavage.com
- Kazanoe, on 10/12/2007, -0/+670.65.*.* and I'm bust.
  
  I was getting excited too, hope its fixed soon
- eppitek, on 10/12/2007, -1/+6Note: 69.x.x.x is not working either from US
  
  (I felt this deserved to be near the top since it is also 69.x.x.x having a problem in addition to the 7x.x.x.x)
- HiddenForce, on 10/12/2007, -0/+6I made a 50 minute call today from a 69.x.x.x (TimeWarner cable) address today without any problems.
- jeff1943, on 10/12/2007, -0/+7I am on 69.107.***.*** and I've made countless calls today with no problem. I'm using AT&T that is
- sahaskatta, on 10/12/2007, -0/+5ive got 71.xxx.xxx.xxx verizon DSL in CA and doesn't work!
- superal1394, on 10/12/2007, -0/+3I have Time Warner Road Runner in upstate new york, IP is 77.x.ect.
- Madh2orat, on 10/12/2007, -0/+3stupid 71.104.xxx.xxx, Verizon is great, but up untill now, i've been happy, now I see what it really is.
- mickoes, on 10/12/2007, -0/+270.xxx.xxx.xxx
  68.xxx.xxx.xxx
  
  Of my Sympatico (BELL) ISP works fine.
- shazbot, on 10/12/2007, -0/+3Actually, my IP is 70.151.14.XXX and I'm just fine.
iotadeltaphi, on 10/12/2007, -4/+25Erm... yeah. I'm on Rogers' net up here in Canada.

Who wants to bet it's got something to do with Rogers and its traffic shaping?
- affanjam, on 10/12/2007, -1/+13Bell Sympatico up here in Canada is good to go.
  
  65.XX.XX.XX
  works great
  
  remember you need to and +1(areacode)-number
ap3lovr, on 10/12/2007, -2/+20Almost Guaranteed it;s Rogers being stoopid.... Oh well, just another reason they will get hosed in the long run.
- jonnyeh, on 10/12/2007, -16/+2I'm on Rogers, and I have an IP address with 69.x.x.x, but I haven't tested skype out yet.
- zatrix, on 10/12/2007, -0/+5works fine here, im a 69.*
Mike.ohara, on 10/12/2007, -5/+22Friggen Rogers.. its official there are NO good ISPs in Canada.
- vh1`, on 10/12/2007, -4/+10I'm pretty happy with Aliant
- TehSuper, on 10/12/2007, -4/+7I'm happy with MTS.
- LegendarySock, on 10/12/2007, -2/+9yay quebec
  videotron baby
- netwerx, on 10/12/2007, -4/+3I'm on cogeco, works dandy.
- nuclearsnake, on 10/12/2007, -2/+1@LegendarySock "yay quebec videotron baby"
  Do you have a 7*.x.x.x IP.
  Because its not working for me with my 70.81.x.x
  
  I dont think its Videotron or Rogers or Verizon etc doing it otherwise we would see many others complaining it doesnt work
- mrops, on 10/12/2007, -0/+23web all good in canada. called my buddies all over US and Canada, 66.x.x.x
- Zippo, on 10/12/2007, -0/+3On Aliant as well. Just called a friend in Cali and it works great.
- seitanguy, on 10/12/2007, -0/+4Shaw is pretty good here in Vancouver
- JoVoCop, on 10/12/2007, -1/+1Telus isn't too bad on the West Coast
- Pseudorious, on 10/12/2007, -0/+0Skype Out on Rogers is working fine for me, but I'm sure they'll be shaping the traffic in hours. Just like with bittorrent.
acey049, on 10/12/2007, -0/+18Our IP here in the panhandle of FL is 70.183.x.x through Cox Communications and the free SkypeOut is working perfectly fine.
- mshade, on 10/12/2007, -1/+4I'm on Cox in Virginia 74.x.x.x range -- works fine here. Is everyone sure they're using 1 then the number?
  If i dial it with 17035554321 it works great. If i leave off that sign, no go. Everyone double check your dialing.
- phillip3225, on 10/12/2007, -0/+5Also using cox cable with a 70.179.x.x and it working great with skype.
- LCmidas, on 10/12/2007, -0/+3Likewise. Using Cox in Louisiana. Apparently throttling VOIP isn't one of this co's flaws.
16x9, on 10/12/2007, -1/+18It seems that some Rogers fan modded down some of the above comments. Weird, but it takes all kinds I guess. Because I am so very much against packet shaping, I modded everyone back up.

Take that "Pro Packet Shaping and Tiered Internet Agenda!" :)
Mike.ohara, on 10/12/2007, -2/+9Friggen Rogers.. its official there are NO good ISPs in Canada. but on that note, it doesnt seem to be limted to just Rogers... any ISP that uses 7.x.x.x ips seems to be blocked, could it be an issue with the software, or something?
djnull, on 10/12/2007, -0/+8its not working for me with 71.blah.blah.blah in CT either
Moremoe, on 10/12/2007, -0/+572.xxx.xxx.xxx not working. After a 1/2 call I found out that it isn't working. Not that it really matters it was like $.30.
Skeksis, on 10/12/2007, -0/+6Awesome, this is what i get living in CT! 70.xxx.x.x
DarkEnder, on 10/12/2007, -0/+870.xxx.xx.xx, and it works fine for me.
jgee, on 10/12/2007, -0/+871.xxx.xxx.xxx is working just fine In PA
seanroth, on 10/12/2007, -0/+1271.xxx.xxx.xxx no workie in southern CA. (verizon)
- ssanders, on 10/12/2007, -1/+2Sadly, same here. I was actually just coming here to vent on the other skype thread that it wasn't working for me... then I saw this. I'm going to try to get a different IP assigned... I use to have an IP in the 100 range I believe.
t0ny, on 10/12/2007, -0/+772.24.118.* and its not working for me and I live in Nampa, Idaho.
http://forum.skype.com/viewtopic.php?p=250342#250342
- bristevens, on 10/12/2007, -0/+1Are you on cable one? I am in Southern CA right now, but will be trying it when I get back next week. I live in Boise.
- addisonj, on 10/12/2007, -0/+1yeah... cable one blows, live in nampa also and am so frustrated with them... but better than DSL or wireless, a month ago i was getting drops all the time and dips in speed, has gotten better but still not happy with them :(
Billistic, on 10/12/2007, -2/+7Man this sucks, I'm a 72.xxx.xxx.xxx and it's not working for me either :(
cvp1, on 10/12/2007, -1/+2Gotta love Road Runner... freakin 72.xxx.xxx.xxx...
- TehFRAG, on 10/12/2007, -0/+1ditto here
dkoolaid, on 10/12/2007, -1/+2 71.227.xxx.xxx
comcast cable modem blocked
retral, on 10/12/2007, -0/+4I'm 70.104.x.x and it's working fine for me.
spooky760, on 10/12/2007, -1/+8Not sure if this has anything to do with it, but I had to reinstall skype to get the freebies. Just my $0.02.
- kruykaze, on 10/12/2007, -8/+2LOL!
- spooky760, on 10/12/2007, -0/+270.191.*.* - Cox cable in Bakersfield. Works good. FYI
fizzalex, on 10/12/2007, -1/+370.143.xx.xxx

Works fine here.
I have a friend with 70.251.xxx.xx who has problems calling, so I don't know
Persol, on 10/12/2007, -3/+43I'm in the 192.0.x.x range, and it doesn't work either!
- abandonow, on 10/12/2007, -9/+24Yeah, and I'm on 127.0.0.xxx and it isnt working for me either.
- ACalcutt, on 10/12/2007, -11/+4lol
- YoHowdy, on 10/12/2007, -6/+29192...You must be in my house!
- GerbilSoft, on 10/12/2007, -22/+12And everyone falls for it.
  
  192.0.x.x isn't an internal IP range. Only the 192.168.0.0/16 range is internal IP. 192.0.0.0/16 is assigned to IANA (the Internet Assigned Numbers Authority).
- Persol, on 10/12/2007, -1/+15Just HAD to ruin my fun, eh Gerbil?
- cazbar, on 10/12/2007, -1/+13As stated above, most of 192.x.x.x isn't private. I found out the hard way that some of the root dns servers are in the 192.x.x.x range when I incorrectly entered a subnet mask for a network interface on a dns caching server.
- leighhalliday, on 10/12/2007, -1/+10What how is it possible that you and I have the same IP address?!?!?! 127.0.0.xxx Have you hacked my computer??
- FlyboyP, on 10/12/2007, -0/+15You must be from Tuttle, Oklahoma.
- Urusai, on 10/12/2007, -0/+4My 10.x.x.x address doesn't work...curse you intarweb!
martinjester, on 10/12/2007, -1/+4I'm on 70.56.208.*** with Qwest DSL in NM and it isn't working for me.
analdisco, on 10/12/2007, -6/+7My internet access might not work for half the things I'd like to use it for, and it might drop every hour, but at least I know it's up to 10 times faster than DSL!

It's Comcastic!
- Daychilde, on 10/12/2007, -0/+1It really sucks that you're having whatever problems you're having -- I've used Comcast back in Dallas and now in Panama City -- I've never ever had any trouble (well, okay, after some storms the other day, it was down for about 18 hours... that sucked... and there have been one or two other times in the past FIVE YEARS I've lost access for an hour or two -- other than that, it's always been faster than they advertise for pretty much anything I want to do.... And the two times I've had cable installed (back in Dallas and now here), I've been up and running within two days from my initial "I'd like to schedule installation, please" -- which is NOT something I can say for me two DSL experiences in Dallas (both with Southwestern Bell / SBC / now at&t because the bastards can't find the SHIFT key anymore ;-) )
  
  So I'm sure there are many bad experiences with Comcast -- but I sure haven't had them.
  
  (Well, off-topic: the video-on-demand service that started had a lot of teething problems - but after a few months, it seems to work pretty well now -- but it was free, so hey... heh.)
Mudcrutch, on 10/12/2007, -1/+271.74.xx.xxx not working in Columbus, OH
crl620, on 10/12/2007, -0/+7Was that part of the old BOGON range? Might still be filtered if so...

http://www.completewhois.com/bogons/
- mikeazorin, on 10/12/2007, -10/+3These are the 7* bogus IPs. I don't think this is the problem.
  
  70.15.0.0 - 70.15.255.255
  70.42.64.0 - 70.42.255.255
  70.43.128.0 - 70.43.255.255
  70.44.192.0 - 70.44.255.255
  70.45.128.0 - 70.45.255.255
  70.46.128.0 - 70.46.255.255
  70.62.112.0 - 70.63.255.255
  71.6.32.0 - 71.6.127.255
  71.6.160.0 - 71.6.255.255
  71.7.64.0 - 71.7.127.255
  71.7.192.0 - 71.7.255.255
  71.17.64.0 - 71.17.255.255
  71.18.64.0 - 71.18.255.255
  71.19.64.0 - 71.19.127.255
  71.41.224.0 - 71.43.255.255
  71.47.48.0 - 71.47.255.255
  71.57.192.0 - 71.63.255.255
  71.94.0.0 - 71.95.255.255
  71.163.0.0 - 71.191.255.255
  71.237.0.0 - 71.239.255.255
  72.0.48.0 - 72.0.63.255
  72.0.80.0 - 72.0.95.255
  72.0.144.0 - 72.0.159.255
  72.0.208.0 - 72.0.223.255
  72.0.240.0 - 72.0.255.255
  72.1.48.0 - 72.1.63.255
  72.1.112.0 - 72.1.127.255
  72.1.240.0 - 72.1.255.255
  72.2.112.0 - 72.2.127.255
  72.2.176.0 - 72.2.191.255
  72.2.240.0 - 72.2.255.255
  72.4.96.0 - 72.4.127.255
  72.4.176.0 - 72.4.255.255
  72.8.64.0 - 72.8.255.255
  72.9.112.0 - 72.9.127.255
  72.9.144.0 - 72.9.159.255
  72.10.176.0 - 72.10.191.255
  72.10.208.0 - 72.10.223.255
  72.11.48.0 - 72.11.63.255
  72.11.176.0 - 72.11.191.255
  72.11.240.0 - 72.11.255.255
  72.12.112.0 - 72.12.127.255
  72.12.240.0 - 72.12.255.255
  72.13.16.0 - 72.13.31.255
  72.13.80.0 - 72.13.95.255
  72.13.112.0 - 72.13.127.255
  72.13.144.0 - 72.13.159.255
  72.13.208.0 - 72.13.223.255
  72.14.176.0 - 72.14.191.255
  72.15.48.0 - 72.15.63.255
  72.15.224.0 - 72.15.255.255
  72.18.48.0 - 72.18.63.255
  72.18.112.0 - 72.18.127.255
  72.18.144.0 - 72.18.159.255
  72.18.208.0 - 72.18.223.255
  72.19.48.0 - 72.19.63.255
  72.19.176.0 - 72.19.191.255
  72.20.112.0 - 72.20.127.255
  72.20.176.0 - 72.20.191.255
  72.21.80.0 - 72.21.95.255
  72.21.144.0 - 72.21.159.255
  72.21.176.0 - 72.21.191.255
  72.22.16.0 - 72.22.31.255
  72.22.112.0 - 72.22.127.255
  72.22.176.0 - 72.22.191.255
  72.22.208.0 - 72.22.223.255
  72.22.240.0 - 72.22.255.255
  72.26.48.0 - 72.26.63.255
  72.26.112.0 - 72.26.127.255
  72.26.176.0 - 72.26.191.255
  72.26.240.0 - 72.26.255.255
  72.27.160.0 - 72.27.255.255
  72.28.64.0 - 72.28.255.255
  72.29.144.0 - 72.29.159.255
  72.29.176.0 - 72.29.191.255
  72.32.96.0 - 72.32.255.255
  72.34.16.0 - 72.34.31.255
  72.34.48.0 - 72.34.63.255
  72.34.80.0 - 72.34.95.255
  72.34.112.0 - 72.34.127.255
  72.34.176.0 - 72.34.191.255
  72.34.240.0 - 72.34.255.255
  72.35.16.0 - 72.35.31.255
  72.35.80.0 - 72.35.95.255
  72.35.112.0 - 72.35.127.255
  72.35.176.0 - 72.35.191.255
  72.35.208.0 - 72.35.223.255
  72.35.240.0 - 72.35.255.255
  72.36.64.0 - 72.36.127.255
  72.39.0.0 - 72.39.255.255
  72.42.64.0 - 72.42.255.255
  72.44.16.0 - 72.44.255.255
  72.45.64.0 - 72.45.255.255
  72.46.128.0 - 72.46.255.255
  72.47.192.0 - 72.47.255.255
  72.48.128.0 - 72.48.255.255
  72.50.128.0 - 72.50.255.255
  72.51.64.0 - 72.51.255.255
  72.52.64.0 - 72.52.255.255
  72.53.160.0 - 72.53.255.255
  72.54.128.0 - 72.54.255.255
  72.55.128.0 - 72.55.255.255
  72.135.96.0 - 72.135.255.255
  72.162.0.0 - 72.163.255.255
  72.166.0.0 - 72.167.255.255
  72.170.0.0 - 72.171.255.255
  72.172.64.0 - 72.172.255.255
  72.173.64.0 - 72.173.255.255
  72.175.0.0 - 72.175.255.255
  72.186.96.0 - 72.191.255.255
  72.216.0.0 - 72.223.255.255
  72.233.0.0 - 72.233.255.255
  72.241.64.0 - 72.241.255.255
  72.243.0.0 - 72.243.255.255
  72.247.64.0 - 72.247.255.255
  72.249.0.0 - 72.249.255.255
  72.250.128.0 - 72.251.255.255
  72.253.0.0 - 72.253.255.255
  73.192.0.0 - 73.255.255.255
  74.2.0.0 - 74.3.255.255
  74.4.16.0 - 74.5.255.255
  74.7.0.0 - 74.7.255.255
  74.9.0.0 - 74.11.255.255
  74.23.0.0 - 74.31.255.255
  74.42.0.0 - 74.47.255.255
  74.49.0.0 - 74.51.255.255
  74.53.0.0 - 74.55.255.255
  74.57.0.0 - 74.59.255.255
  74.60.128.0 - 74.61.255.255
  74.62.80.0 - 74.62.255.255
  74.63.16.0 - 74.63.255.255
  74.68.64.0 - 74.79.255.255
  74.84.0.0 - 74.87.255.255
  74.89.128.0 - 74.95.255.255
  74.122.160.0 - 74.127.255.255
  74.138.0.0 - 74.223.255.255
  75.48.0.0 - 75.125.255.255
  75.126.32.0 - 75.126.255.255
  75.127.16.0 - 75.191.255.255
  75.216.0.0 - 75.255.255.255
  76.8.0.0 - 76.190.255.255
  76.191.16.0 - 76.255.255.255
  77.0.0.0 - 79.255.255.255
- dkoolaid, on 10/12/2007, -1/+6i'm not in that range, but i am being blocked
  71.227.222.xxx
  bellingham, WA
  comcast cable
  
  my neighbor has qwest dsl, and also has a 71.xxx.xxx.xxx and is being blocked too
abandonow, on 10/12/2007, -9/+1- removed -
mjaleo, on 10/12/2007, -1/+371.xxx.xxx.xxx Verizon FIOS. Didn't work with the free one, but I ditched Tomatovine VOIP for the Skype and after paying $10 for the phone line and some credit, I'm not getting charged for my calls. I don't think it's on the ISP's end...
bobmcsmith, on 10/12/2007, -0/+470.71.xx.xx on Shaw Cable in Canada working fine
h4lofourt33n, on 10/12/2007, -1/+2I'm in Toledo, OH and it isn't working either. @ 72.240.xxx.xx. Sort of odd how it is messing up in just that range though, oh well, I'm sure a fix is already being worked on.
nyrol, on 10/12/2007, -1/+2wow mine is 70.51.xx.xxx and it works fine. i use bell sympatico highspeed ultra
BETA7, on 10/12/2007, -1/+3umm my ip is 78.x.x.x so im skrewed
psycobrat, on 10/12/2007, -1/+2209.62.x.x with iptables firewall doing shaping and nat. worked fine.
BETA7, on 10/12/2007, -1/+5also did i metnion that i have rogers? so that might be the problem god dam bastards trying to stop voip simply because its better and cheaper
mieses, on 10/12/2007, -4/+1My Covad DSL IP starts with 72.xxx, clearly a US IP address, and Skype is still charging Skype-Out credits for local calls.

I can make SkypeOut calls to US numbers. There is no network interference from the ISP. It's completely up to Skype to charge or not to charge. Why are they charging when they said they would not?

Skype needs to explain this offer. Is this a marketing ploy with yet-to-be released fine print?

If this offer excludes IP's starting with 7, then it is useless to a very large percentage of users.
tifoco, on 10/12/2007, -1/+171.x.x.x in Charlotte NC.
No kidding.
grrrrrrrr.
coheedcollapse, on 10/12/2007, -0/+3Yup, my Verizon line (71.115.x.x) doesn't work and hasn't worked. I hope they fix this problem because I'm really excited to try it out if I can.
1800yolk, on 10/12/2007, -1/+3I have an IP address in that range, and it tells me that I can't make calls to land line phones, but I still can. I just ignore it, and I don't have any problems. Peace, Brian
Macattack15, on 10/12/2007, -0/+3Verizon FiOS 71.XXX.XXX.XXX

No Go - sigh... i still love FiOS anyway
FiZi, on 10/12/2007, -0/+370.68.x.x on Shaw Cable in B.C, Canada. No problem here, called a buddy in $Texas
- Protoss, on 10/12/2007, -0/+4"And you put, Texas with a dollar sign (Texa$)" Sorry, but that just reminded me of Celebrity Jeopardy from SNL.
AlexPi, on 10/12/2007, -2/+1I have Verizon FiOS in that IP range and it sure is not working at all!
kkapoor, on 10/12/2007, -4/+1I'm on Rogers in Canada and everything is working fine.
kruykaze, on 10/12/2007, -6/+1did anybody try proxies?
tifoco, on 10/12/2007, -2/+1So is this Skype's problem?
will they fix it?
- icurnvs, on 10/12/2007, -0/+10It's not an issue with Skype. Your ISP is more than likely deliberately blocking you from being able to use Skype. The only thing that could possibly keep it from happening is to have the traffic encrypted from your PC to the Skype servers. Dunno if that'll ever happen though.
- DefensiveCore, on 10/12/2007, -0/+1It's not an ISP problem where they are blocking Skype. You can still use SkypeOut if you pay. Skype just can't verify you are in the U.S. or Canada to not charge you. With a decent chunk of the 70.x.x.x-79.x.x.x having the problem across multiple ISPs (and getting an IP out of the affected range from the same ISPs have fixed it for some people), I would have to say it is in Skype's part of the court.
TheQwe, on 10/12/2007, -1/+4doesn't work, and I'm on Qwest DSL, 71.xxx.xxx.xxx. It's not the client, either; I was able to use skypeout from my college's internet connection.
FresnonserF, on 10/12/2007, -2/+271.xxx.xxx.xxx is not working. SBC Yahoo
jzimmerman, on 10/12/2007, -1/+2If you are on Comcast, clone the mac address on your router from you computer.

Then powercycle your modem and router.

This will possibly give you a 24.x.x.x ip address which will probably work fine.
- t0ny, on 10/12/2007, -0/+3Worked for me I just turned my cloning off and rebooted my router got a 67.*... ip! :)
  I have cable one.
- jzimmerman, on 10/12/2007, -0/+1CableOne is somehow affiliated with Comcast I think.
  
  If you try to locate comcast service in an area like Boise, ID it directs you to CableOne. Pricing and services are similar as well.
JackT, on 10/12/2007, -0/+370.49.*.* and it works fine.
rbaibich, on 10/12/2007, -2/+1Sympatico here, 70.53.xxx.xxx and it didn't work for me.
netwerx, on 10/12/2007, -3/+224.141.*.* just called to US from Canada, works dandy. On Cogeco Cable.
klownkiller, on 10/12/2007, -1/+2 70.135.*.* thru AT&T Yahoo! DSL

& workin fine for me!
Show 51 - 100 of 141 discussions
Login or register to add a comment

Create a new account or login to join in the conversation on Digg. You'll also be able to Digg stories to help promote things you like.

SkypeOut Free US Calls NO GO for IPs 70.x.x.x - 79.x.x.x

Login or register to add a comment