Here We Go Again: Getting Ready for the Next Google Voice Train Wreck


Self-inflicted wounds are nothing new in the technology business, but Google spent much of last week working hard to take top honors for what is clearly one of the most selfish and short-sighted moves ever in the telecommunications marketplace. Less than a week after extolling the values of open source technology during Google I/O 20131, Google wasted little time performing a complete 180 by deep sixing further support of the open source XMPP protocol for messaging and VoIP communications. With one brief announcement, Google basically killed off years of Google Voice development and announced the upcoming demise of Google Voice, XMPP, and Jabber messaging as we know it. Never mind that literally millions of users have come to rely upon Google Voice and XMPP messaging as their primary sources of communications. Google now has declared XMPP too confining for their view of what the telecommunications world really needs. Instead, we get yet another proprietary communications protocol. So much for the Do No Evil ethos. With classic pot calling the kettle black ire, one of Microsoft’s leading cheerleaders wasted little time condemning the move.

So why the sudden change of heart at Google? Well, it had nothing to do with the needs of Google customers obviously. In the old days, Google at least labeled projects as beta (for years) to warn you that something might happen down the road, good or bad. That era is over. Now the carnage happens almost randomly. Remember Google knols? It was perhaps the greatest collection of medical and technical literature of all time. Poof! All gone. We won’t go through the entire litany. Suffice it to say, this is nothing new for Google. Every company is entitled to its New Coke moment. Google has had more than its fair share, and it should serve as a wakeup call to organizations and individuals that reliance upon Google infrastructure is a really bad idea.

The current train wreck turns out to be yet another turf war motivated by retribution against Microsoft’s recent decision to support XMPP in its Outlook.com unified messaging product, something most companies would have greeted with jubilation. Instead, Google is miffed that Microsoft was now supporting its messaging protocol while continuing to keep its own protocol proprietary. That meant Microsoft cellphones could chat with Android phones but not the other way around. The moral of the story for consumers is pretty simple. Don’t for a minute assume that any technology company has your best interests at heart. None of them do. It’s all about money and industry domination. Google viewed this as a brazen attempt by Microsoft to create a messaging platform that could speak Android while continuing to restrict access to the Microsoft messaging installed base. And Google chose to pick up its marbles and go home rather than hand Microsoft easy access to hundreds of millions of Android cellphone users. So we’re back to handing the Bell Sisters the unified messaging monopoly with SMS and MMS as the lowest common denominator. Welcome to Big Business!

What does all of this have to do with Google Voice? Well, it rides along on the same messaging platform as Google Talk, Microsoft Lync, and XMPP/Jabber-based solutions including Asterisk, FreeSwitch, Yate, Cisco Jabber, Openfire, and Avaya in addition to all of the Google Voice-compatible softphones and OBiHai devices. So expect a train wreck!

We’re all about VoIP communications so we’ll leave the cellphone messaging for others to sort out. The important question for those of us that depend upon Google Voice for VoIP communications is what can you do to insulate yourself from the upcoming disaster. You can bury your head in the sand and pretend this isn’t going to happen, and you’d be dead wrong for the reasons we’ve outlined above. And, remember, Google has served clear notice that XMPP is over as far as they are concerned unless Microsoft, Apple, and now Facebook blink. Of course, Google could always redeploy SIP for Google Voice calling. If you think any of that is likely to happen, you also might want to buy a lottery ticket which affords you about the same chance of seeing any of your dreams come true.

To keep things simple, let’s divide VoIP communications into four categories: inbound calling, outbound calling, messaging, and faxing. We’ll leave video for another day only because it remains a niche product. With the demise of Google Voice, we recommend not putting all of your eggs in one basket (again). Inbound calling is the most critical. That’s your phone number, and it’s how folks get in touch with you. If there are numbers (DIDs) that you don’t want to lose, now is the time to move them away from Google Voice before it’s too late. If Google elects to shut down Google Voice, your ability to port your numbers elsewhere is OVER! So don’t procrastinate on this one. Luckily, Vitelity (one of the primary supporters of Nerd Vittles and the PBX in a Flash projects) has provided an incredible deal to our fan club for many, many years. For $3.95 a month you get a DID with unlimited inbound calls. It’s not free, but it’s not expensive either. And the call quality and service reliability are as good or better than anyone else in the business. You can read all about the offer at the end of this article. Google charges $3 to port your number out of Google Voice to a new provider. The step-by-step tutorial is available in the PIAF Forum. Do it while you still can!

For outbound calling (terminations), the thought process is different. Unlike traditional analog telephony, there is no reason not to have multiple providers especially if you’re using Asterisk, PBX in a Flash, or Incredible PBX as your communications server. If one outbound path fails, your server can automatically send the calls out through another call path. So continue to cling to your Google Voice dream for outbound calling if you’re a Believer. But do a little advance planning while there’s no crisis. There are numerous termination providers and generally you get what you’re willing to pay for. If cheap is your primary objective and call quality is secondary, then Anveo Direct and VoIP.ms can’t be beat. Both allow you to spoof your CallerID to match a DID that you own so they work well with a service such as Vitelity that is being used to handle your inbound calls. We’ve written about both of them, and we use both of them with excellent results. There are many, many others. Visit the PIAF Forum for lots of additional recommendations.

SMS messaging is an evolving technology in the VoIP marketplace. Expect to see some terrific new services before the summer is over. If you’re in a hurry, the easiest current solution to implement is through Anveo Direct. Our recent article will walk you through the setup process to send and receive SMS messages with Asterisk.

Faxing remains a crap shoot using VoIP technology. If you want commercial quality, then choose one of Vitelity’s dedicated fax circuits. If you want analog faxing that usually works, then Anveo Direct and VoIP.ms are about as good as you can do. All versions of Incredible PBX for PBX in a Flash include a free faxing solution using the HylaFax/ AvantFax platform. A similar solution is provided on the Raspberry Pi platform. As we said, it’s not perfect but it usually works.

Continue reading Part II: Google Puts the Final Nail in the Google Voice Coffin

Originally published: Monday, June 3, 2013




Need help with Asterisk? Visit the PBX in a Flash Forum.
Or Try the New, Free PBX in a Flash Conference Bridge.


whos.amung.us If you’re wondering what your fellow man is reading on Nerd Vittles these days, wonder no more. Visit our new whos.amung.us statistical web site and check out what’s happening. It’s a terrific resource for all of us.


 
New Vitelity Special. Vitelity has generously offered a new discount for PBX in a Flash users. You now can get an almost half-price DID from our special Vitelity sign-up link. If you’re seeking the best flexibility in choosing an area code and phone number plus the lowest entry level pricing plus high quality calls, then Vitelity is the hands-down winner. Vitelity provides Tier A DID inbound service in over 3,000 rate centers throughout the US and Canada. And, when you use our special link to sign up, the Nerd Vittles and PBX in a Flash projects get a few shekels down the road while you get an incredible signup deal as well. The going rate for Vitelity’s DID service is $7.95 a month which includes up to 4,000 incoming minutes on two simultaneous channels with terminations priced at 1.45¢ per minute. Not any more! For PBX in a Flash users, here’s a deal you can’t (and shouldn’t) refuse! Sign up now, and you can purchase a Tier A DID with unlimited incoming calls for just $3.99 a month. To check availability of local numbers and tiers of service from Vitelity, click here. Do not use this link to order your DIDs, or you won’t get the special pricing! Vitelity’s rate is just 1.44¢ per minute for outbound calls in the U.S. There is a $35 prepay when you sign up. This covers future usage and any balance is fully refundable if you decide to discontinue service with Vitelity. 


Some Recent Nerd Vittles Articles of Interest…

Be Sociable, Share!

  1. Larry Page reportedly commented as follows: “I’ve personally been quite sad at the industry’s behavior around all these things. If you take something as simple as IM, we’ve had an open offer to interoperate forever. Just this week Microsoft took advantage of that by interoperating with us but not doing the reverse. Which is really sad and not the way to make progress. You can’t have people milking off of just one company for their own benefit…” []

4 Responses to “Here We Go Again: Getting Ready for the Next Google Voice Train Wreck”

  1. Cam says:

    Ward, I am sorry to see that you have joined the “Amen chorus” for those who seem to think that Google will simply pull the plug on Google Voice without warning. I disagree, for reasons mentioned in some of my posts in the thread at http://pbxinaflash.com/community/index.php?threads/replacement-for-google-voice.12625/

    We’re actually talking two separate issues here, which is whether Google Voice will discontinue XMPP access to Google Voice, which they might but I still doubt it will happen anytime soon, and whether they will discontinue Google Voice altogether, which I very much doubt. So in my opinion, there is no need to run out and port a number away from Google Voice, since you will very likely be able to at least forward your Google Voice calls to another number, though at some point you may no longer be able to send your Google Voice calls to a Google Talk destination. But when that day arrives, you will have the ability to forward your calls to a regular phone number while you consider what other options you wish to take. Remember that Google has already said that Google Voice would be free through 2013, so that rather implies they aren’t planning on shutting it down.

    If Google does drop the ability to use XMPP then it may still be possible to place and receive Google Voice calls by reverting back to an older method, as discussed in the thread at http://pbxinaflash.com/community/index.php?threads/old-fashioned-google-voice-calls.12620/

    I’m sorry to disagree with you, Ward, but I just think that now is not the time to panic. If I were a gambler I’d bet the farm on the fact that Google Voice will be around at least until the end of this year, and that if Google ever does decide to discontinue it they will give users at least a couple months’ notice. The XMPP thing I am not quite so confident about, but if that should happen I have a fallback method ready to go.

    I also think Google may live to regret pulling the plug on XMPP – it sort of blows apart “Don’t be evil”, doesn’t it? For a company that wants to be big in all things technology, they seem to be trying their best to burn through all the goodwill they have generated over the years. The wi-fi snooping thing, where Google Street View cars were capturing bits of people’s wi-fi connections as they drove by, was my first indication that Google’s moral compass may have gone a bit askew. So it’s not that I think them incapable of pulling the plug on Google Voice someday, but I just don’t believe that will happen until at least the end of the year.

  2. Whatever the case, this certainly underscores the fact that a free service like Google Voice cannot be relied upon to the be the foundation of any valid business telecom strategy. This has been my feeling all along. If there’s no deterministic way to get timely support then it cannot be anything more than a sandbox of sorts.

    Free doesn’t mean its wholly without cost.

  3. Bob Koure says:

    Hi Ward,
    As best as I can tell (from reading other boards) what Google is discontinuing is XMPP federation – which doesn’t seem a major issue for what we’re doing. It’s not clear whether this is a first step in discontinuing support for it altogether or not.
    That said, yeah, this might be a good time to at least start preparing to move away from it. It was never a good idea for a business to depend on it, but I’m sure there are plenty of individuals (like me: started using GrandCentral so I could use two mobile phones and not make callers track multiple numbers) who depend on it to at least some degree.
    So, if you’re right, there’s going to be a large number of folks looking for a replacement. Yes, PIAF is potentially an excellent one, but there are some pieces missing – and it’s not the easiest thing to learn.
    Maybe I’ll bring this up on the PIAF forum – unless someone else does first. Hope it doesn’t turn acrimonious like last time.

  4. Jason says:

    So, has google pulled the proverbial plug on xmpp yet?

    I’m confused as to what this literally means for someone using Google Voice and incredible pbx as a home phone.

    Can I still send and receive calls? That is all I want it for.

    If it has gone away, what is the next solution?

    [WM: Still working so far as long as you don’t switch your account over to Google Hangouts.]

Ringbinder theme by Themocracy