The crux of AT&T's recent complaint to the FCC regarding Google Voice was that Google -- not being subject to the common carrier rules that help facilitate fair, open telephone networks -- was blocking customers from accessing numbers managed by rural carriers that charged higher connection fees, thereby giving it a leg up on its Old Guard competition by saving cash in ways AT&T and others are legally barred from doing. Google's hitting back today, not by agreeing to submit to common carrier rules (come on now, don't be ridiculous) but by saying in a statement to the FCC that it's now blocking calls to "fewer than 100" numbers in total now that it has finished implementing new back-end capabilities that allow it to single out specific numbers rather than entire exchanges. Google complains that calls to the top ten exchanges accounted for 26 percent of its entire connection fee outlay -- but yeah, that's pretty much what telcos have been dealing with since time immemorial, so the bellyaching's likely to fall on a lot of deaf ears. For what it's worth, the company is still asking the FCC to make sweeping changes to connection fee policy, but whether this ends up getting them out of AT&T's more immediate concerns remains to be seen.

[Via Phone Scoop]

AT&T filed a scathing letter with the FCC earlier today complaining that Google's exhibiting a blatant double standard with Google Voice by blocking customers' access to numbers hosted by carriers that charge higher interconnect fees -- something that's specifically forbidden for traditional telephone carriers under so-called common carrier laws. The argument essentially revolves around the fact that Google's move helps it compete unfairly against AT&T and others by arbitrarily blocking calls to numbers that'd cost it too much to connect, which AT&T says puts Google in an "intellectual contradiction" given its "noisome trumpeting" (ouch!) of support for net neutrality.

It is pretty interesting that Google wants a free, open internet with the left hand while it's blocking certain telephone calls with the other, but Mountain View wasted no time in responding to the communication, posting an quick blog piece where it says there are "many significant differences" that should exempt it from common carrier legislation (some sound reasonable, though the argument that "Google Voice is currently invitation-only, serving a limited number of users" makes us think they're digging pretty deep to come up with reasons they shouldn't have to pony up the cash to get these calls connected).

If there's a bright side to the bickering, it's that both AT&T and Google can agree on one thing: rural carriers' continued ability to charge high connection fees hurts everyone -- it's a "badly flawed" system, in Google's words, and it'd be great if the FCC would do something about it. Whether this whole spat ultimately influenced the outcome of the Google Voice iPhone app debacle is unclear, but it's obvious that AT&T's been stewing about this for a while -- so let it all out, guys, mommy FCC's here for you, and one way or another we suspect GV's going to have to end up going legit if it wants to grow its user base by any significant measure. Check out the gallery for AT&T's letter and follow the read link for Google's shorter, slightly less aggressive response.

It was always curious that Google's response to the FCC inquiry about Google Voice and the App Store had been redacted, but now we're starting to see why -- El Goog and the FCC have just released the full text of the letter, and it flatly contradicts Apple's take on the matter. If you'll remember, Apple claimed that while Google Voice hadn't been approved, it also hadn't been rejected, and that its status was in limbo while the folks in Cupertino "studied" the matter. Not so, says El Goog: according to its letter, Phil Schiller himself told Google that GV had been rejected on July 7 for duplication of functionality, following a similar conversation on April 10th during which Schiller rejected Google Latitude in part because it might "offer new features not present on the preloaded maps application." Yeah, that's a huge discrepancy, and it makes Apple's version seem even more divorced from reality that it already is. Things are starting to heat up -- we'll see what the FCC makes of all this.

Update: And here we go -- Apple just pinged us to say the following: "We do not agree with all of the statements made by Google in their FCC letter. Apple has not rejected the Google Voice application and we continue to discuss it with Google."

Update 2: So we've been thinking about it, and here's our question -- if Apple didn't reject GV, and is still studying it, what exactly did Phil Schiller say to Google to make them think it had been rejected? The difference between "rejected" and "on hold pending further discussion" isn't a subtle one, and Google clearly thought GV had been explicitly rejected. For whatever it's worth, reports of GV's "rejection" are how this whole mess got started, so either this is all one huge misunderstanding, or someone here isn't telling the entire truth.

Read - Google unredacted FCC filing [Warning: PDF]
Read - Google Public Policy Blog explaining decision to release letter

Well, we can't say we didn't see this one coming. At today's meeting, the FCC has said that it will be launching a formal inquiry into the wireless industry and specifically into certain business practices of the big four: AT&T, Sprint, T-Mobile USA , and Verizon Wireless. The commission hasn't yet detailed exactly how they're going to go about this, but you can bet they'll be looking into exclusivity deals between handset manufacturers and carriers. And who knows? They might be interested in the whole iPhone / AT&T / Google Voice conundrum, especially if it turns out that AT&T had a hand in dissing the app. According to Reuters, the agency is looking into "how competition affects consumers," with an eye towards further investigations into other areas, including cable and broadband.

[Via Phone Scoop]

Whoa -- we were just sent AT&T response to the FCC's investigation into the rejection of Google Voice apps from the iPhone app store, and Ma Bell isn't pulling any punches: according to the letter, AT&T "had no role in any decision by Apple to not accept the Google Voice application." That puts the ball pretty firmly in Apple's court, but it doesn't close the door on AT&T's involvement in App store approval shenanigans entirely, since the letter also says "AT&T has had discussions with Apple regarding only a handful of applications that have been submitted to Apple for review where, as described below, there were concerns that the application might create significant network congestion." Not only did that result in CBS and MobiTV killing the Final Four app's ability to stream video over 3G, it also explains what happened to SlingPlayer Mobile -- we'll see what the FCC says about that.

Update: And here come Apple and Google's responses as well! We're digesting everything as fast as we can, we're going to do this semi-liveblog style after the break, so grab a frosty and dive in.

Update 2: Okay, so we've read through all three filings and broken them down after the break. Our main takeaway? Apple's being pretty hypocritical by claiming on the one hand that the iPhone is at the forefront of a mobile revolution and then saying iPhone users can't figure out how Google Voice is different than the iPhone's built-in functionality on the other. Either your customers are paradigm-busting visionaries or they're not very smart at all, Apple -- you have to pick one. As for AT&T, well, it just seems like it's worried about its network above all else, and while we think it's ridiculous that it enforces the VoIP and SlingPlayer ban on the iPhone and not, say, Windows Mobile devices, we can see why the carrier would push those contract provisions hard. In the end, we're just hoping the FCC forces everyone involved to be more open and transparent about what they're doing and the deals they're making -- Apple's not necessarily exaggerating when it says these are entirely new problems, and whatever happens next will set a precedent for a long time to come.

Yeah, we're pretty much all peeved by Apple suddenly ejecting all traces of Google Voice from the app store, but now it looks to have drawn the ire of the Federal Communications Commission, as well. According to a report from The Wall Street Journal, the agency has sent out three letters, one each to Apple, AT&T, and Google. To the latter company, it asked for a description of the Google Voice app and whether previous Google apps have been approved for the store (it has, but that's another interesting story). To Cupertino, it's asking the phone manufacturer to explain itself over the sudden exorcism and what involvement, if any, AT&T had in this decision. The report doesn't make a direct indication of what the letter to the carrier said, but we can imagine it's similar to what Apple got, plus some doodles at the end of a stick figure letting out an exasperated sigh. In a statement today, FCC Chairman Julius Genachowski said it "has a mission to foster a competitive wireless marketplace, protect and empower consumers, and promote innovation and investment." Hey Julius, while you're at it, can you see about Skype and Slingbox for us, too? Thanks.

Update: TechCrunch has published the three letters sent out, all very interesting reads. The FCC asks Apple specifically if any approved VoIP apps are allowed to be used over AT&T's 3G network, and more generally what are the "standards for considering and approving iPhone applications" and more details into the approval process. It also asks for the contact information of all developers of rejected Google Voice apps, presumably for further investigation. In the Google letter, it seems to be asking if Voice will be able to be utilized in any capacity over the web, without inclusion in the iTunes store. Unsurprisingly, a number of questions to Apple and AT&T concern the carrier's involvement in which apps or types of apps get rejected. All companies have until August 21st to respond and can request confidentiality on all or portions of their response.

Google Voice might have just been unceremoniously thrown out of the iPhone App Store, but that doesn't mean development isn't racing forward on other platforms -- say hello to dkGoogleVoice, an unofficial client for the Palm Pre. Yeah, it's buggy and has a bare-bones feature set, but hey -- it exists, and it's only going to get better. Can't say that about your little phone, can you Steve?

[Via PreCentral]

So well-mannered, straight-laced iPhone users got a pretty big slap in the face yesterday by way of Apple's (and AT&T's, no doubt) total Google Voice rejection. Looks like jailbreakers are picking up the pieces, as GV Mobile developer Sean Kovacs -- whose app was in the iTunes store for some time before being yanked yesterday -- has ported the Voice client over to Cydia free of charge, although donations are gladly accepted. Even more interesting, but less concrete, Kovacs said he was already working on a web app version, possibly for submission to Palm's app catalog. No word on the fate of GVdialer, an app that was also unceremoniously pulled, but we wouldn't be surprised if it followed in similar footsteps.

Read - GV Mobile now on Cydia
Read - Sean Kovacs on Twitter

Perhaps the big G spoke too soon when it said its new Google Voice service was coming to iPhone. First, GV Mobile developer Sean Kovacs relays a phone call he had with Apple where he was notified of his app being removed from the iTunes store for duplicating built-in iPhone features -- an app that was originally and purportedly approved by Phil Schiller himself. Next out the door was GVdialer, and if you thought that was all bad, now comes word that Google's official Voice app was flat-out rejected by Cupertino. Now it's hard to say with certainty who's to blame for these app rejections, but a good many fingers are pointing to the cellular carriers -- and given AT&T's previous statements about the SlingPlayer app, it's hard to argue with that. For its part, the company hinted at finding a workaround via web apps, much like they did when Apple gave Latitude a cold shoulder -- but doesn't that feel just a little 2007?

[Via Apple Insider]

Read - Official Google Voice App Blocked from App Store
Read - GV Mobile is getting pulled from App Store
Read - Sean Kovac's Twitter status on Schiller

There have been pretty decent unofficial hacks to get Google Voice fully functional on a variety of mobile devices for a while now, but Google's finally taking the next logical step in its world domination strategy by releasing totally 100-percent legit first-party apps for a couple key platforms today -- BlackBerry and, of course, its own Android. As you might expect, the app lets you make calls and send texts through your Google Voice number (great for taking advantage of its mega-low international rates) and integrates with the service's excellent visual voicemail and voice transcription service. iPhone is on the way, but for now, the BlackBerry build should be hitting a pretty wide, interested demographic -- now about those Google Voice invites, eh?

With home screen widgets, an on-screen keyboard, great notification management, and hands-down the best Gmail experience of any platform, Android 1.5 finally makes it easy (or easier, anyway) to love Google's foray into the mobile world. Of course, if you're coming from an iPhone -- as some users inevitably will be -- there are a few features that'll be sorely missed as you make the transition. For us, a biggie was visual voicemail, and after a little trial and error, we found a cool way to add it into our device without even leaving the Google ecosystem -- and even better, it's totally free. Follow the break for the full story!