AT&T Allows VoIP On iPhone Subscribers' Broadband Channels

Abrupt reversal precedes FCC announcement of network neutrality proposals

Here is one of those little coincidences that make Washington such an interesting place to work.

Regular readers know about the friction among Apple, maker of the iPhone; AT&T, the iPhone’s broadband provider; and Google Voice, a VoIP service (among other things) that seeks to carry the calls of iPhone users.

The iPhone and its close competitors, like the Palm Pre, have two ways to access broadband: a “3G” channel provided by the carrier and paid for as part of the subscriber’s data plan; and Wi-Fi, much like that in a laptop, which of course works only at Wi-Fi-equipped locations. Apple has long allowed VoIP on the iPhone's Wi-Fi link, but never on the 3G channel. This matters to users, because relatively few of the locations where a person might want to place or receive a call have Wi-Fi service. AT&T, in responding to an FCC inquiry, was blunt about why it (and Apple) block VoIP from 3G: VoIP is a much cheaper substitute for minutes of voice service. Its use thus cuts into carrier revenues, including the revenues needed to recover the subsidy that lets Apple price the iPhone at far below its actual cost. Read more here.

But now AT&T has abruptly reversed course.

It will allow VoIP on the iPhone 3G channel after all. If you hear loud cheers from the general direction of Mountain View, CA, that’s the Google folks breaking out the Red Bull. Apple still has not formally approved the Google Voice app, but a big obstacle is now out of the way.

The coincidence? Exactly one day before AT&T’s about face, the FCC announced the date, two weeks from now, on which it will formally propose its network neutrality rules. One of the key factors that precipitated the current surge of interest in network neutrality was a 2007 request from Skype, a VoIP company, asking the FCC to prohibit wireless companies (like AT&T) from blocking VoIP service. So the rules that might eventually be adopted, a year or two from now, may require action along the lines that AT&T took today.

Down here in the bunker we are a little surprised at the news. The wireless carriers have been erecting a protective wall of press releases that say network neutrality rules will bring about the end of technical innovation, social progress, and cheap cell phones. And AT&T’s decision may fundamentally change the economics of wireless phone service. We can expect vigorous marketing of VoIP services to iPhone users. That will probably cause a significant drop in paid-for voice minutes. Will AT&T start charging more for its data plan? Will Apple abandon the subsidy on the iPhone and start charging customers what the phone actually costs? AT&T may have brought us a little closer to a system in which customers have free choice and pay only for what they choose.

Sometimes the FCC can get the results it wants without actually regulating. Sometimes just announcing the date on which it plans to begin to consider regulating is enough.

Apple to FCC: "No Answer" Doesn't Mean "No"

Apple, AT&T answer FCC inquiry about rejection of Google Voice

We reported here on the FCC’s requests to Apple and AT&T, the iPhone maker and service provider, asking why Apple had rejected an iPhone App called Google Voice. This provides access to a range of advanced voice features free of charge, in some instances bypassing services that AT&T charges for. The FCC also wanted to hear Google’s side of the story.

The answers came in several days ago, and we have been mulling them over ever since. (Okay, we did some of our mulling at the beach.)

Apple has not actually rejected Google Voice, it says. But neither has it accepted Google Voice. Rather, Apple continues to study the application.

Over 95% of applications are approved within 14 days of submission, so this one must fall in the other five percent. Most non-approvals occur because the program crashes or fails to function properly, according to Apple, but somehow we doubt Google submitted buggy code. Other submissions are rejected for sexual or violent content, also not a factor here. Apple’s problem with Google Voice, rather, is that the application “appears to alter the iPhone’s distinctive user experience” by, for example, handling voice mail and contact lists differently.

While it makes up its mind, Apple generously invites Google to put the application on other, non-iPhone platforms “and let consumers make their choices.” Apple apparently misses the irony. If it truly favored consumer freedom, it would let customers include Google Voice in their choice of user experiences on the iPhone.

AT&T, for its part, claims no involvement in Apple’s decision (or failure to make one) regarding Google Voice. But AT&T is equally irony-challenged. Much of its response (a) touts the benefits of wireless competition, while (b) defending AT&T’s arguably anticompetitive policy of blocking VoIP services on its broadband network. The response is surprisingly frank about the rationale. VoIP users run up fewer minutes of voice service. AT&T needs the revenues from voice minutes to pay back the subsidy that lets consumers buy the iPhone at an artificially low price, which in turn has attracted many new customers to AT&T’s network (and billings for voice minutes).

Here’s an idea: a wireless network that offers its users maximum choice, and charges only for services actually selected and delivered. No limitations on handset applications; no handset “subsidies” recovered through excessive monthly charges. The wired phone system once had carrier-imposed equipment subsidies and service restrictions. Their removal by the FCC triggered the current telecommunications revolution and helped to produce the Internet. Maybe it’s time to try the same approach for wireless services as well.

Google’s response to the FCC on Google Voice might be interesting and helpful, but we will never know. Except for a glowing account of the advantages of Google Voice and Android, a Google-supported operating system for wireless phones, public copies of the response are heavily redacted, especially as to communications between Google and Apple about getting Google Voice approved. Again, the irony is hard to miss. Google has the legal right to redact information that it thinks might unfairly help its competitors. But as a company that has long championed openness on the Internet, it might have been more open with information that affects not only Google and Apple, but all of us interested in making the best use of communications resources.

FCC Examines Exclusion of Google Voice from iPhones

Letters sent to Apple, AT&T in expansion of “network neutrality” inquiry

The FCC recently expanded its “network neutrality” inquiries into an ongoing contretemps among three giants of consumer technology: Google, Apple, and AT&T. The dispute follows Apple’s disallowing Google Voice service on its iPhone handsets, possibly at the request of AT&T, the carrier having exclusive rights to the iPhone.

Network neutrality is the idea that communications customers, such as Internet and cell phone subscribers, should be able to use all lawful services and hardware without interference from the provider. It sounds simple enough, but in practice the issues get a little complicated. See here and here and here. Back in 2005, the FCC enunciated four “principles” of network neutrality, but has not adopted actual rules on the subject.

Wireless phone providers have traditionally favored the opposite of neutrality: a “closed” model in which the same company supplies over-the-air service, sells the handsets, and picks the services users can access. If you obtain cell phone service through one of the major carriers – Sprint, AT&T, Verizon, or T-Mobile – you probably bought your phone from them, too. And if you use the phone for on-line banking and certain other lucrative services, chances are the company you’re dealing with pays the carrier for the privilege of having your business.

The FCC has two proceedings underway that could eventually challenge this kind of arrangement.

One started with a petition from Skype, which provides free or inexpensive phone service over the Internet.  Most wireless carriers do not allow access to Skype over their handsets, because the customer could call via Skype instead of running up expensive minutes. The other proceeding began with a group of small rural cell companies asking the FCC to ban exclusive arrangements for handsets. Because such deals limit the most desirable handsets to the majors, the small carriers lose business to customers who want the latest in hardware. So far, though, the FCC has only invited public comment on these requests, with no hint as to whether it might act.

The newest wrinkle comes out of Apple’s decision against Google Voice.

Broadly speaking, Google Voice brings phone service into the Internet Age. A subscriber receives a new phone number, local in any region of the subscriber’s choosing. Calling that number rings all the customer’s phones, wherever they are: office, home, cell, etc. Different callers can be automatically routed to different phones, or forwarded selectively to still other phones, or fed different voice mail greetings, or given different rings, or blocked altogether. All the voice mails from all the phones end up in one place, where they can be read in printed form, like emails, or listened to online from anywhere. There are provisions for setting up conference calls, and for recording phone conversations for online storage. Parallel features cover SMS messaging.

And calling anywhere in the United States is free.

Apple rejected Google’s application to sell Google Voice through the App Store, the only legal source of iPhone software. And Apple revoked previous App Store approvals for third-party software intended to work with Google Voice. Early speculation supposed that Apple had acted at the request of AT&T, whose network uses the iPhone, but press reports say that AT&T has denied any involvement. Apple’s motivation for stirring up its customers remains unknown.

Now the FCC has sent letters to all three companies: Google, Apple, and AT&T, asking Apple and AT&T which one of them made the decision to bar Google Voice, and why, and whether Apple and AT&T offer competing applications. The letter to Google asks for details on how Google Voice works, and for a summary of the discussions with Apple and AT&T.

What the FCC will do with this information is not clear. Also not clear is whether it will even get the information. Or whether it has the authority to ask. Back in the 1976 Computer II proceeding, the FCC relinquished jurisdiction over information flowing through communications systems. It would regulate the lines, it then decided, but not the bits and bytes moving over them. (In the broadband environment, it has since deregulated even the lines.) With only limited exceptions for certain forms of VoIP , the FCC has indeed kept its hands off Internet applications. Apple and AT&T have to concede the FCC’s authority over wireless voice service, and may even acknowledge some control over handsets, but may well argue that Computer II put optional software applications beyond Commission reach.

For those of us who enjoy corporate conflict as a spectator sport – over-muscled, over-equipped gladiators struggling in the arena – the Google-Apple-AT&T spat is a welcome addition to the long-running Google-Microsoft and Apple-Microsoft events. “The enemy of my enemy is my friend,” the saying goes. But now the two biggest enemies of Microsoft have become enemies themselves.

Pass the popcorn, and keep your scorecard ready.