Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
wont let me activate wifi calling on my iPhone 6S Plus when contact AT&T they claim "AT&T doesn't support the following bring your own device models: A1688 and A1700 (6s) and A1687 and A1699 (6s Plus)" and mine they say is a A1687 I pre-ordered on Apple.com choose AT&T Model 128GB Space Grey and a 128GB Rose Gold doing PAY IN FULL so would be unlocked. Well guess in their eyes I didn't get a AT&T Model....

They suggest returning and getting right one... well problem is now its over the 14 day return period 2 they probably have none in stock as still on back order. So would be without a phone..

So warning if you have a UNLOCKED Phone don't expect to us AT&T WiFi Calling

View attachment 591104
Well that sure SUCKS!
Looks like AT&T is getting back at Apple for starting their own plan.
YIKES!
 
  • Like
Reactions: iOSFangirl6001
So much confusion here about what this is and what it does...

1. This feature only works when your call via Cell network fails. It's seamless, and you can't force it or even notice it when it occurs. (unless you notice that you have zero cell bars, and are still talking....)
2. This does NOT bypass the AT&T network (or Sprint or T-Mobile or... or... or any other network you might use for Wi-Fi calling) The call origination is the only part that changes. Your call is still routed to your carrier's network, and still uses their equipment to complete the call. SO, yes, you still use minutes on your plan, and you still get charged for long distance as you should be charged for using their network, because you ARE using their network.

OMG...SO MUCH MISINFORMATION!!!!

1. The status bar will CLEARLY show AT&T Wi-Fi when it's enabled, and only show AT&T when it's not. Somewhere between 1 and 2 dots of signal is the threshold where it enables automatically.
2. AT&T documentation CLEARLY shows that calls placed over WiFi DO NOT count towards liminted minutes.

Seriously...don't post here if you have no idea what you are talking about.
 
  • Like
Reactions: iOSFangirl6001



AT&T has flipped the switch on Wi-Fi calling, making it available to customers with eligible plans that are running iOS 9. MacRumors has received tips from customers who were able to activate Wi-Fi calling and we were able to activate the feature on our own iPhones. A number of readers in our forums are also having success activating Wi-Fi calling.

Wi-Fi calling is a feature that lets calls be placed over a wireless connection when cellular connectivity is poor, functioning much like an AT&T M-Cell does now. It's similar to Apple's own FaceTime Audio feature, which also routes calls over a Wi-Fi connection.

AT&T customers can turn on Wi-Fi calling by going to the Phone section of the Settings app and toggling on the Wi-Fi calling feature. From there, there are a set of steps to walk through, including entering an emergency 911 address. Wi-Fi calling is available on the iPhone 6, 6s, 6 Plus, and 6s Plus running iOS 9.

att_wifi_calling_setup_1-800x704.jpg

Customers who want to use Wi-Fi calling need to have AT&T HD voice features enabled, along with an Internet connection. Wi-Fi calling can be used for voice calls within the United States, Puerto Rico, and United States Virgin Islands at no charge. Long distance global voice calls will be charged standard long distance rates.

Once the setup process is complete, customers are receiving notifications letting them know the Wi-Fi calling feature will be available after a short activation period.

att_wifi_calling_setup_2-800x354.jpg

AT&T promised to launch Wi-Fi calling alongside iOS 9, but last week announced the feature was delayed due to its inability to get an FCC waiver that would temporarily allow the carrier to forgo offering support options for deaf and hard-of-hearing customers. On Tuesday of this week, AT&T finally received the waiver that it needed to move forward with Wi-Fi calling.

Article Link: Wi-Fi Calling Now Available for AT&T Users


Does not work. Keep getting error: Oops! That wasn't supposed to happed. Give us a minute and we'll get it fixed so you can try again.

But can resolve it.
 
  • Like
Reactions: chriscrowley
The reason is simple and not stupid. Only the 6 and newer have the proper combo of hardware and software to fully support it properly

That's actually not true. This is an AT&T decision. I have a 5S working just peachy with Wifi calling on T-Mobile. The 5s is more than capable of this and support it just fine.
 
  • Like
Reactions: solodogg
That's actually not true. This is an AT&T decision. I have a 5S working just peachy with Wifi calling on T-Mobile. The 5s is more than capable of this and support it just fine.
And it doesn't hand off from WiFi to HSPA, right? It drops the call, unlike if you had VoLTE support
 
You cannot in any realistic way expect any cellular company to provide you with flawless perfect service coast to coast in all weather/atmospheric conditions no matter what type/size/age of structure you are currently in. This is asinine. This is a juvenile and idiotic demand.

The cellular company cannot in any realistic way expect my bill to be paid flawlessly in all financial conditions. This is a juvenile and idiotic demand.

Funny how they're really good at extracting money from the customers, no glitches or issue there, huh?

So, you're saying, hey, let's cut AT&T a break here, and give them an easy "out" of providing quality service. Because, you know, physics and weather and what-not.

These are the exact conditions that are ripe for a Google or an Apple to jump in and be a service provider and smack AT&T. You know, like Apple did with cell phones, Tesla with electric cars, Google with maps, email, ...

In the mean time, you can continue shilling for cellular providers and enjoying your crappy service.
 
It is impossible for HSPA+ to transition to WiFi calling (and the phone isn't even supposed to attempt it), but it is possible to transition from WiFi to LTE or HSPA+. I have been able to replicate this issue on 4 different phones, with different iOS 9 beta, 9.0 GM, 9.0.1 and 9.0.2 final versions, and every one would mute the call until disconnected when going from strong signal to a low enough signal where WiFi would normally activate.

The only difference here is that you are initiating the call on HSPA+ while your phone is not in rage of WiFi signal. Each time I have had this issue appear, my phone was connected to WiFi, but the WiFi calling signal threshold had not been met. Once I moved to an area where signal dropped enough for WiFi calling to activate (while still connected to the same WiFi network), the call mutes until disconnected. As soon as I terminate the call, the status bar immediately changes from just AT&T to AT&T Wi-Fi.


*EDIT* just enabled WiFi calling, not in a VoLTE area, and while talking on the phone, I unplugged the router. The "call failed" screen appeared as the phone attempted to switch to VoLTE, but it's not available in this market. There is no way for the handoff from WiFi to HSPA+ to complete on AT&T.

I can only tell you my personal experience. I have been on calls started in my home on wifi calling left, driven miles down the road obviously outside of wifi range and the call never failed. There is no VoLTE in my area according to ATT. So the call did definitely have to hand off. I use an Apple Airport Extreme router and the range is awesome but it's not a over a mile down the road. So I have to argue that you are incorrect in your statements about it handing off.

Unplugging a router and moving out of range are to very different situations. One is sudden with zero time for the phone/network to adapt the other is more gradual. Perhaps as the phone sees the wifi getting weaker as you move away it transitions the call so that it's not dropped. Where as with a sudden interruption there is no chance to transfer so the call simply failed?

Again I can only speak for my own experiences I live in Starke, Florida you can look at the ATT coverage maps for yourself and see there is no VoLTE anywhere near me. The closest is South Florida or up around Atlanta.

*EDIT* I just checked the coverage maps myself out of curiosity to see if they had changed from when I checked them a couple of weeks ago. To my utter astonishment they now so HDVoice in my area. In fact it's gone from being just a small area of south Florida to nearly the entire state. So perhaps you were right after all. Maybe the VoLTE, which is what HDVoice requires, was already here but not showing on the map because it was only in that trial/beta phase. We shall probably never really know.

I'm only glad that my calls do hand off cleanly and flawlessly and that I can now enjoy HDVoice. I've been using FaceTime audio calls to call other friends and family with iPhones because of the massive difference in call quality already.
 
Last edited:
  • Like
Reactions: iOSFangirl6001
I went home and tried this and it worked well. At work, it odes not work. I guess they have this blocked, which kind of defeats the feature a bit. Has anyone tried it at a starbucks or other free access point to see if they get blocked or not?
Doesn't work at my place of business either. Corporate IT departments are real paranoid and stuffy about opening up ports, and will complain that calls will degrade their network performance and compromise security.

Basically, if there's technology to make things run more smoothly and conveniently for employees, IT is guaranteed to shut it down.
 
  • Like
Reactions: iOSFangirl6001
The cellular company cannot in any realistic way expect my bill to be paid flawlessly in all financial conditions. This is a juvenile and idiotic demand.

Funny how they're really good at extracting money from the customers, no glitches or issue there, huh?

So, you're saying, hey, let's cut AT&T a break here, and give them an easy "out" of providing quality service. Because, you know, physics and weather and what-not.

These are the exact conditions that are ripe for a Google or an Apple to jump in and be a service provider and smack AT&T. You know, like Apple did with cell phones, Tesla with electric cars, Google with maps, email, ...

In the mean time, you can continue shilling for cellular providers and enjoying your crappy service.

And again you prove your lack of intellectual ability. The number of ways the two situations are different are almost beyond number. One has to do with the physical ability to build towers, obtain limited spectrum, and the laws of physics regarding penetration of structures by said spectrum. The other is about money.

In the area where I live there is a main highway that has a dead spot. It's a dead spot for every carrier out there. It's not a dead spot because none of these carriers care. It's not a dead spot because they think no one notices. It's a dead spot because they can't build a tower anywhere near it. literally all of the land around that particular area is unavailable or unsuitable for a tower. Either for environmental or economic reasons.

So in your mind it's blame ATT Verizon and all the other carriers for this and damn them all for a dead spot? Or maybe we look on this change in technology and the ability to have a new way around such inconveniences as a good thing and the fact that they don't have to offer this. They don't have to support this. So they are in fact working to improve our service. They may not do it in the way you would approve of, but then given your afore mentioned lack of intellectual ability I don't think it matters all that much that you don't like it. You don't understand it.

And as for them expecting your bill to be paid in any financial conditions. Yes they do. But you also have the flexibility of chasing another carrier if your financial situation changes, or indeed not having any carrier at all. So again, options.
 
Getting the "Oops, Can't turn on WiFi for this account" message. This is the chat I had with the rep. Can anyone else confirm (or deny) this?

Att.jpg
 
"functioning much like an AT&T M-Cell does now."

Wi-Fi calling is nothing like AT&T M-Cell. Wi-Fi calling uses the Wi-Fi signal. M-Cell uses a small, local cellular signal from the microcell device.
 
Yes as long as the "AT&T Wifi" banner is up and you're connected to a decent enough fully compatible WiFi source then yes both incoming and outgoing calls can be relieved over WiFi as an added bonus benefit not mentioned much you'll also be able to send/receive texts , picture or multimedia messages too





You do know you can enable/force WiFi on whilst in airplane mode do you not?





There could be a number of reasons why you both had issues non the least if it was early on in the Beta period the expectations shouldn't of been set too high.

That being said possibilities can include:

Not a fully compatible WiFi connection

Poss issues with the WiFi Connection and or ISP used

Were you in a targeted Beta market?
( Upon discussing issues with ATT in the Beta period was informed ONLY Chicago, Manhattan and 2 or 3 other markets were ever intended to be allowed in the Beta yet people found ways to trick/forcibly join )

Persons you both called may not of had compatible coverage/devices on their end


WiFi Calling has improved over the testing period and I would urge you both to give it at least 1 more chance and not completely discredit/discount it if there is potential it could at some point be useful to you





Pretty good not much noticeable issue or difference



If you get a paper bill in the mail you'll see a section labeled "WiFi Minutes used" split into night/weekend , Daytime, and Mobile 2 Mobile if applicable


If you get a detailed bill which lists/breakdowns ALL Your usage
WiFi Calling will have a feature code differing from regular calls


If you view your call/usage logs in your online account or the MyATT APP calls will also have a special feature code.


So far on the paper bill I see them listed/coded as WIFI in the online coding it labels em PVWIFI


If by billion you meant costs sorry for the long winded reply. The answer is no
WiFi Calling or WiFi Call Blocking are both 100% FREE Features however looks like all accounts will/must have 1 or the other I'd assume by default accounts whom activated like myself will have "ATT WiFi Calling Feature $0.00" on their account by default while others who've not activated or AT&T records show as ineligible based on plan, region, device etc. will by default have the "ATT WiFi Call Blocking Feature $0.00" added onto their features list
Thanks for explanation.
 
  • Like
Reactions: iOSFangirl6001
Can this work on Cricket?

Wish it did ... Can't beat the three lines for $75 we'd get today if it were available! Unfortunately we're stuck with ATT due to my wife's 5s and two year contract. We'd ETF it but not without WiFi calling.
 
It says it requires AT&T HD Voice which requires both the caller and receiver to have AT&T HD Voice. This means, you cannot use this feature to call outside of AT&T.

I enabled this feature this morning (Austin TX) on my iPhone 6 and gave it a try. I encountered no such requirement that both parties needed to have AT&T HD Voice. I turned on airplane mode and then enabled Wi-Fi, then placed a call to a friend's phone who is NOT even on AT&T at all, but instead Verizon. Worked just fine.
 
Just use FaceTime Audio or Skype. There are so many ways to communicate over wifi these days. Tons of options.
Except not everyone uses Skype for calls. And others don't have iPhones. ;)

You don't need to have a iPhone to run Skype; it also works on Android and Windows Phone so on 99% of all mobile devices.
Yes, I know that. I was replying to the suggestion to use FaceTime Audio. :D
 
  • Like
Reactions: iOSFangirl6001
If this is indeed the case (which I have no reason to doubt your statement), than this is exactly as I suspected from Ralph and company. They found a way to F'k everyone anyway. I don't have HD voice in my area (testing T-mobile currently btw), so I will have to keep my microcell anyway w/ATT if I choose to keep them.

ATT just loves to push the envelope on you can "IF"...

That is not the case. I successfully test called someone today over Wi-Fi who is not even an AT&T subscriber, but instead with a competitor (Verizon).
 
  • Like
Reactions: iOSFangirl6001
Was able to successfully turn it on yesterday but cannot make a call with it. Trying to initiate a call and it starts to ring then decides to switch over to wifi and I get dead air. Also it likes to turn off the speakerphone for some reason.
 
My home router (ASUS-RT-N66U) has both a 2.4 and 5GHz SSIDs. VoWiFi works on the 2.4 SSID (with limited cell coverage and airplane+wifi) but the 5GHz SSID will not initiate it. Same AP, same internal/external IP, just a different SSID. The signal is strong on the 5GHz, and I can successfully do anything data related on it with 4x data transmission speed. I have a wireless poewerline repeater in the back of the house with a different 2.4GHz SSID and it works there too. The firewall settings are the same across the board (QoS is off). Has anyone else tried VoWiFi on a 5GHz SSID?
works fine over my 5ghz via comcast
 
*EDIT* I just checked the coverage maps myself out of curiosity to see if they had changed from when I checked them a couple of weeks ago. To my utter astonishment they now so HDVoice in my area. In fact it's gone from being just a small area of south Florida to nearly the entire state. So perhaps you were right after all. Maybe the VoLTE, which is what HDVoice requires, was already here but not showing on the map because it was only in that trial/beta phase. We shall probably never really know.

I'm only glad that my calls do hand off cleanly and flawlessly and that I can now enjoy HDVoice. I've been using FaceTime audio calls to call other friends and family with iPhones because of the massive difference in call quality already.

Glad to see you are one of the lucky ones in a VoLTE area now. You should also notice while you are on the phone, the status bar will continue to display LTE instead of 4G now, and yes, with VoLTE working, handoff should be seamless. AFIAK, VoLTE to WiFi handoff was not supposed to be a supported feature, only WiFi to VoLTE...but it does appear AT&T has it set to attempt both (thus causing my audio to drop when passing the threshold for WiFi calling to enable).

My wife was in Orlando at the beginning of the week, and said VoLTE worked flawlessly in that market. Previously when we were down, we experienced quite a few dropped calls around the I Drive area, and just to the north, but I was able to hold a conversation with her all over the south end of town this time.
 
Glad to see you are one of the lucky ones in a VoLTE area now. You should also notice while you are on the phone, the status bar will continue to display LTE instead of 4G now, and yes, with VoLTE working, handoff should be seamless. AFIAK, VoLTE to WiFi handoff was not supposed to be a supported feature, only WiFi to VoLTE...but it does appear AT&T has it set to attempt both (thus causing my audio to drop when passing the threshold for WiFi calling to enable).

My wife was in Orlando at the beginning of the week, and said VoLTE worked flawlessly in that market. Previously when we were down, we experienced quite a few dropped calls around the I Drive area, and just to the north, but I was able to hold a conversation with her all over the south end of town this time.

Yes I am very glad. I'm very surprised by how much of the state is suddenly showing the coverage. Literally only a couple of weeks ago I checked and the only HDVoice coverage in the state was down around Miami and Ft. Lauderdale with a little around palm beach. No surprise the largest markets would get it first. Then look today and boom nearly the entire state. And the areas that are not covered are very rural very isolated where there has been no coverage at all or very limited coverage.

Looks like att are really working to push this out. I know moving as much voice traffic as possible over from the older 3G and 4G networks will help free up spectrum so there is incentive. Now if the major carriers can work together to make it HDVoice between them all it will be even more beneficial to their customers.
 
  • Like
Reactions: iOSFangirl6001
Was able to successfully turn it on yesterday but cannot make a call with it. Trying to initiate a call and it starts to ring then decides to switch over to wifi and I get dead air. Also it likes to turn off the speakerphone for some reason.

It's certainly plausible as AT&T rolls this out some bugs or unexpected resource constraints could surface. I'd keep trying it for a few days and if it continues to fail then call in the troops ;-).

Weird about the speakerphone though...
 
  • Like
Reactions: iOSFangirl6001
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.