-
All replies
-
Helpful answers
-
Oct 21, 2014 4:26 PM in response to kernlingby bartfrommidlothian,I have the exact same issue. SMS works fine on my MAC, but keep getting the message that the MAC and iPhone need to be on the same wi-fi network (and mine are as well). So frustrating!
iPhone 6 plus with IOS 8.1 and a 27" iMac
-
Oct 21, 2014 5:00 PM in response to kernlingby b3brett,I am seeing the same error message with my iPhone 5. SMS works, but voice calls do not work.
-
Oct 21, 2014 8:04 PM in response to kernlingby b3brett,I have a question. Are you testing this on your home wi-fi or public wi-fi? I am testing this on a public wi-fi. I'm wondering if this is a factor.
-
-
Oct 22, 2014 6:29 AM in response to kernlingby c7figo,i have same problem on my iPhone 5s and Macbook Air Mid 2012. Is there any solution?
-
Oct 22, 2014 11:44 PM in response to kernlingby Justbepoppin,Hello,
I have encountered the same problem. I've tried everything at home on my router, but here's the kicker when went out to my studio and my phone and mac connected i received a phone call on my mac. Which leaves me to believe its either a router issue or a setting issue in Yosemite that talks to the router. I have a macbook pro Late 2011 and an iphone 5
-
Oct 23, 2014 3:24 AM in response to kernlingby LeZubial,Same issue here, SMS works great (what a pleasure to write SMS through the mac) however looks like this Call continuity either need a router configuration or ... is not fully working . Yosemite tells me iphone and mac must be on the same wifi network ... which is the case.
Any idea ?
-
Oct 23, 2014 3:59 AM in response to LeZubialby kernling,I brought my macbook with me into work today and it works fine here.
It must have something to do with my router at home. I will go trough the router settings this evening and will post if and how i got it fixed.
-
Oct 24, 2014 8:36 AM in response to kernlingby LargeYam,Had this problem for the past week, until now. I had tried all previously mentioned advice, including re-logging into cloud, facetime, etc. Still wasn't working until 10 minutes ago, when, on the third try today...success.
No idea why, but a few days ago on another, similar post, someone else had mentioned that they kept trying multiple times until it worked. Now I can vouch for that stubborn persistence.
-
Oct 24, 2014 9:46 AM in response to kernlingby b3brett,I was traveling on business this week and only testing with public wi-fi hotspots. It was not working. When I got home today it worked fine on my own wi-fi network. It appears that you can not place a call through a public wifi network (Starbucks, etc). I know that doesn't resolve everyone's issue, but it is good to know for the future.
-
Oct 24, 2014 5:59 PM in response to kernlingby squarecircles,I have the same problem. Macbook Pro 2013 Yosemite 10.10 + iOS 8.1. On home network. I tried it before and it worked, now it's not working. Works 1 out of 10 times.
-
Oct 24, 2014 8:07 PM in response to kernlingby HundredthMonkey,If you have multiple bands broadcasting on the same SSID, trying forcing both computer and phone onto the same band
-
Oct 24, 2014 9:09 PM in response to kernlingby Justbepoppin,Alright people!!
Just got mines to work! just made my 1st phone call moments ago. I have an At&t 2wire 3600HGV router. I'll show you with pictures as well.
So,I went to my router settings via (192.168. whatever) and went to
SETTINGS
then to
IP ADDRESS ALLOCATION
I scrolled down until i found my macbook pro (Which is named Just-Mac)
I decided to change the address assignment to the same as my phone (which is Dj's-Talkbox)
Then i selected submit and i tried my phone call and BAM it worked.
SO, putting both devices on the same pool worked out the bugs, i know everybody doesn't have the same router, but i hope this helps.
Btw, i have a Macbook pro (Late 2011) with an iPhone 5. -
Oct 25, 2014 2:30 AM in response to kernlingby pearceshaun,Hi All,
I'm experiencing the same issue on my home network. Interestingly I have 2 MacBooks at home. It works fine one one but not the other so this suggests its an issue with the macbook itself rather than the router.

