In a 13-page letter to the Federal Communications Commission Wednesday, the carrier again said that Google should play by the same rules as its telecom competitors. AT&T also took issue with the search giant’s claim that Google Voice restricts calls to certain rural areas to avoid the so-called traffic pumpers that route calls there to drive up charges.

“Contrary to the public pronouncements of Google and its allies, Google’s rural call blocking regime is not limited to Google simply blocking calls to ‘adult sex chat lines’ and ‘free’ conference calling services to avoid high access charges,” wrote AT&T’s senior vice president, Bob Quinn, in the letter to the FCC’s wireline bureau. “In fact, Google is blocking calls to, among others, an ambulance service, church, bank, law firm, automobile dealer, day spa, orchard, health clinic, tax preparation service, community center, eye doctor, tribal community college, school, residential consumers, a convent of Benedictine nuns, and the campaign office of a Member of the U.S. House of Representatives.”

My God. Google, the company whose business philosophy proudly proclaims “you can make money without doing evil,” blocking calls to small businesses? To Benedictine nuns? Don’t be evil?

Don’t be evil, my ass.

“We can now see the power of Internet-based applications providers to act as gatekeepers who can threaten the ‘free and open’ Internet,” Quinn continues. “Google’s double standard for ‘openness’–where Google does what it wants while other providers are subject to Commission regulations–is plainly inconsistent with the goal of preserving a ‘free and open’ Internet ecosystem.”

That established, Quinn goes in for the kill, arguing that the FCC should regulate the search giant not just on the wires, but on the Web as well.

“Google’s call blocking begs an even more important question that the Commission must consider as it evaluates whether to adopt rules regarding Internet openness,” he writes. “If the Commission is going to be a ’smart cop on the beat preserving a free and open Internet,’ then shouldn’t its ‘beat’ necessarily cover the entire Internet neighborhood, including Google? Indeed, if the Commission cannot stop Google from blocking disfavored telephone calls as Google contends, then how could the Commission ever stop Google from also blocking disfavored websites from appearing in the results of its search engine; or prohibit Google from blocking access to applications that compete with its own email, text messaging, cloud computing and other services; or otherwise prevent Google from abusing the gatekeeper control it wields over the Internet?”

An interesting question. And one for which Google (GOOG) is presumably already preparing a long-winded answer. This is far from over yet, and we’ll continue to go round and round until the FCC puts a stop to it.

Interesting, given the recent flap over Google Voice for iPhone, which Apple (AAPL) hasn’t yet allowed into its iTunes App Store because it “appears to alter the iPhone’s distinctive user experience by replacing the iPhone’s core mobile telephone functionality and Apple user interface with its own user interface for telephone calls, text messaging and voice mail.”

How is Vonage’s (VG) app different? Its features and functionality are certainly very similar to those of Google Voice.

Apple won’t say, but the company did tell the Associated Press that Vonage’s app falls under the same category as other VoIP applications that have already been approved for the iPhone.

Asked by the Federal Communications Commission in August if it had rejected Google’s Voice app from its iTunes App Store, Apple (AAPL) claimed it had not and that the app was still under review.

“Contrary to published reports, Apple has not rejected the Google Voice application, and continues to study it,” Apple explained to the FCC. “The application has not been approved because, as submitted for review, it appears to alter the iPhone’s distinctive user experience by replacing the iPhone’s core mobile telephone functionality and Apple user interface with its own user interface for telephone calls, text messaging and voicemail.”

The FCC put the same question to Google (GOOG) and received a very different answer, which was revealed this morning when Google allowed an unredacted version of the document it submitted to the commission to be made public. Here’s how Google responded to the FCC’s question:

Apple’s representative informed Google that the Google Voice application was rejected because Apple believed the application duplicated the core dialer functionality of the iPhone. The Apple representative indicated that the company did not want applications that could potentially replace such functionality.

… In a series of in-person meetings, phone calls and emails between July 5 and July 28, 2009, Apple and Google representative discussed the approval status of the Google Voice application that was submitted on June 2, 2009. The primary points of contact between the two companies were Alan Eustace, Google Senior Vice President of Engineering and Research and Phil Schiller, Apple Senior Vice President of Worldwide Product Marketing. On July 7, Mr. Eustace and Mr. Schiller spoke over the phone. It was during this call that Mr. Schiller informed Mr. Eustace that Apple was rejecting the Google Voice application for the reasons described above.

Ah, I see. So by “delayed,” Apple apparently meant “rejected.” Interesting. The full document, below.

UPDATE: As I report in a later post on this unfolding story, Apple has denied Google’s assertion to the FCC that it rejected the Google Voice app.

9182009_Google_Filing_iPhone –

Evidently, AT&T has finished “finalizing” those very important “internal system upgrades” that prevented the company from supporting the feature at the outset like virtually every other carrier, a delay that made it the laughing stock of Macworld earlier this year.

AT&T (T) had repeatedly insisted that MMS capability would be available by the end of summer. By debuting the service on Sept. 25, it’s launching it three days into fall. But, whatever. At least, AT&T is launching it.

MMS will be available at no extra charge to iPhone users who already have a text-messaging subscription from AT&T and own a 3G or 3GS iPhone. It will be enabled by a software update on Sept. 25.

The official release, below:

An Update on iPhone MMS for our Mobility Customers
We know many of our iPhone customers are eager for an update on our rollout schedule for Multimedia Messaging Service (MMS). We’ve been working for the past several months to prepare our systems and network to ensure the best possible experience with MMS when it launches–and that launch date is: September 25 for iPhone 3G and 3GS customers. MMS will be enabled through a software update on that day.
We know that iPhone users will embrace MMS. The unique capabilities and high usage of the iPhone’s multimedia capabilities required us to work on our network MMS architecture to carry the expected record volumes of MMS traffic and ensure an excellent experience from Day One. We appreciate your patience as we work toward that end.
We’re riding the leading edge of smartphone growth that’s resulted in an explosion of traffic over the AT&T network. Wireless use on our network has grown an average of 350 percent year-over-year for the past two years, and is projected to continue at a rapid pace in 2009 and beyond. The volume of smartphone data traffic the AT&T network is handling is unmatched in the wireless industry. We want you to know that we’re working relentlessly to innovate and invest in our network to anticipate this growth in usage and to stay ahead of the anticipated growth in data demand, new devices and applications for years to come.
We thank you for your business and look forward to keeping you updated on our initiatives.

“AT&T does not manage or approve applications for the App Store,” the company said in a statement. “We have received the letter and will, of course, respond to it.”

A flat denial, and one that would seem to throw Apple (AAPL) under the bus for denying iPhone owners access to Google Voice. Though just why Cupertino would take issue with an an iPhone application that offers free text messaging and allows users to make calls, routed via the Internet, for free in the United States and for a small fee internationally is unclear. After all, it’s not Apple’s domestic and international calling business the app is potentially encroaching on.

And AT&T (T) is being somewhat disingenuous here since it acknowledged this past May that it had SlingPlayer for iPhone black-holed from the App Store because of concerns over bandwidth.

So while AT&T may not directly “manage or approve applications,” the carrier is clearly capable of influencing management and approval of them.

Could it be that Apple is contractually bound to reject apps that might compete with AT&T’s service? An agreement like that would certainly make it easy for AT&T to adopt the hey-don’t-look-at-me stance it has taken with the FCC.

That said, it’s entirely possible that the Apple’s rejection of Google Voice apps had nothing to do with AT&T and everything to do with its increasingly complicated relationship with Google (GOOG).

As Daring Fireball’s John Gruber notes, “Google Voice is a mobile phone service provided by the maker of one of the biggest competitors to the iPhone OS. What if Google Voice were instead Microsoft Voice? And what if Windows Mobile were as modern and competitive as Android? Would you be as surprised then that Apple is discouraging iPhone owners from using the service?”

The flaw was first demonstrated Thursday. “This is serious. The only thing you can do to prevent it is turn off your phone,” security researcher Charlie Miller said of it earlier this week. “Someone could pretty quickly take over every iPhone in the world with this.”

Well, not anymore, as Apple (AAPL) was quick to note. “This morning, less than 24 hours after a demonstration of this exploit, we’ve issued a free software update that eliminates the vulnerability from the iPhone,” said an Apple spokesperson. “Contrary to what’s been reported, no one has been able to take control of the iPhone to gain access to personal information using this exploit.”

Tragically, that’s not the case.

The Metrolink engineer responsible for the worst U.S. train crash in the last decade sent and received 45 text messages while helming his train the day of the deadly collision in California last month–including one just moments before running a red signal and crashing head-on into a freight train. According to the National Transportation Safety Board, the last message the engineer received was at 4:21:03, more than a minute before the accident. The last one he sent was at 4:22:01, just 22 seconds before the trains, traveling at some 40 miles an hour, collided.

Rail experts were aghast at the news. “For me, it just gives me heart palpitations thinking about it,” said Tim Smith, California chairman of the Brotherhood of Locomotive Engineers and Trainmen. “The last thing you want to be doing is something that takes your eyes off the road.”

iPhone version 2.1 contains many bug fixes and improvements, including the following:

• decrease in call set-up failures and call drops
• significantly improved battery life for most users
• dramatically reduced time to back up to iTunes
• improved email reliability, notably fetching email from POP and Exchange accounts
• faster installation of third-party applications
• fixed bugs causing hangs and crashes if you have lots of third-party applications
• improved performance in text messaging
• faster loading and searching of contacts
• improved accuracy of the 3G signal strength display
• repeat alert up to two additional times for incoming text messages
• option to wipe data after 10 passcode attempts
• Genius playlist creation