Disruptive Telephony

After already publishing my last post about mashups, I came across Jim Courtney's Skype Journal post about the Skype mashup competition, which in turn led me to Thomas Howe's excellent "API of the week" post (got all that?) which had these wonderfully-written words (so much so that I feel compelled to excerpt them here, something I seldom do to this extent):

If you were to ask me, I would say the twenty year old software engineer has a distinct advantage over the older telephone guys (such as me) in the realm of innovation.  Since the barriers to entry to deploying a service provider have fallen through the floor, the larger challenge is not in complex engineering, but is instead in innovation.   The younger engineers are free of the legacy of the PSTN, and many things would occur to an experienced engineer won't to them, and it's not a bad thing. 

<snip>

What does this have to do with telephony? Nothing. What does this have to do with next generation applications? Everything.  Applications that use the Internet as the platform use APIs from a large number of sources, and by and large, these APIs are not telephony. However, nearly every time a telephony API is used, an API such as GoogleMaps, Amazon SQS or DBPedia will be used right alongside it.  As a developer in this market, it makes a lot of sense for you to get to know your neighbors for two reasons. First, the more you can make your API play well with others, the faster the adoption of it will be. Secondly, the more you can understand your customers, their problems and how they need your part for their solution, the better you can make your API for them.   I'm supposing this means that you need to get familiar with APIs like this.

Which leads me back to my original statement.  The twenty-something-don't-know-or-care-about-SS7 engineer will sit down and design their version of the hot-or-not site one day, and use a whole bunch of crazy APIs to put together the application.  Then, they will go have a beer, come back, and say "You know, it would be really cool if you could just call the person you want to hook up with.  Is there an API for that?"  They won't even consider for a minute the words "termination", "LATA" or "CALEA".  They're just writing an application.  They need an API for some function, and it will take a few minutes to integrate it into their application.  And, there are many, many more of these guys than all the telecom engineers that have ever, and will ever, exist.

<snip>

Well, said, Thomas! (Read his original post for the full text.) And to copy a former US President:  "It's the API's, stupid!"

It's very cool to see that one of the leading web sites about "mashups", ProgrammableWeb.com, has announced the launch of a new section focused on "Mobile/Telephony" mashups.  They actually call it a "Market", and there are two others launched today: Mapping and Shopping. 

The obvious focus for this blog, though, is the "Mobile/Telephony" market. The announcement notes that there are currently over 25 different APIs under "Telephony" or "Messaging" and in the actual lists of mashups, 104 are tagged "mobile" and 113 tagged "messaging".  The announcement also notes that Thomas Howe will be assisting with the content of this new section. (Congrats to Thomas!)

The list of telephony APIs (only 11, the other 14+ must be "messaging) is available and several names are probably quite familiar.  Thomas Howe also wrote a piece to explain the different types of APIs and provide a bit of background:  "Telephony & Mobile APIs and Mashups, the Big Picture".

I did find it a bit puzzling that the list of telephony APIs didn't include Skype, given that Skype has a whole developer website set up to support its APIs.  Likewise no mention of Asterisk even though the entire thing is really one big set of APIs.  But hey, the section is only a day old, so we'll have to give them a bit to see how it develops.

The fun thing about the state of VoIP/IP telephony right now is that it really is becoming all about APIs and mashups...  voice is truly just another form of data on the network... and once it is just a bunch of packets you can do really fun stuff with it!  Kudos to the ProgrammeableWeb team and Thomas Howe for helping point the way to some of the interesting stuff people are doing in this area.

Definitely do check out their telephony mashup site.

Back at our Mitel Forum event in late June, analyst Blair Pleasant from Unified Communications Strategies recorded a couple of podcasts[1] with Mitel executives and I've been meaning to write about them here. (Full Disclosure: While Mitel has no direct connection to this blog, I do work for Mitel.)

First up, Blair interviewed Mitel CEO Don Smith.  They discussed Mitel's view of unified communications, business process improvement, the use of SIP and XML interfaces and much more. Don discussed the importance of presence and availability, the need for "in the moment" communication and the importance of "presence everywhere". He also offers his view of the greatest challenges facing Mitel and the industry in the time ahead and his view of where Mitel is heading.

Second, Blair interviewed Stephen Beamish, Mitel VP of Business Development and Strategic Alliances about the partnerships Mitel has with Microsoft, HP and Sun. Given the announcement before Mitel Forum of the partnership with Sun, this interview gives one of the first views into the Mitel-Sun relationship.  Blair and Stephen also, of course, discuss Mitel's relationship with Microsoft, especially in light of the Microsoft-Nortel relationship as well as Microsoft's other partners.  Stephen also talks about the HP relationship and Mitel's participation in HP Procurve's upcoming "Taking It To The Edge" Seminar Series. Finally, he discusses some of the environmental benefits of using Mitel products in terms of power savings.

For those interested in where Mitel is heading and Mitel's views of unified communications, both podcasts are highly recommended. Each podcast runs around 16 minutes.

[1] And yes, as a podcaster I had serious geek envy of the Sony PCM-D1 recorder that Blair was using  courtesy of her colleague Jim Burton.  Very nice piece of hardware! (And also just a wee bit outside of my personal price range!)

If any of you reading this will be attending VoiceCon out in San Francisco, August 20-23, please do drop me a note. I'll be there from August 20-22 and am looking forward to connecting with a range of people from around the industry.

FYI, if you are a Facebook user and are attending, there is a Facebook event for VoiceCon to which you can add yourself to facilitate networking with other FB users at the show.

Is "the coming VoIP war" to be fought out between Microsoft and Cisco?  So asks a column "The Coming VoIP War" by Larry Hooper in today's issue of CRN.  On one level, the debate isn't as interesting to me as the venue... "CRN" is "Computer Reseller News" and has been around the industry for many years.[1]  At various times I've personally had a subscription to the print version or at least had it around the office to read.[2] Supported by advertising and theoretically sent to a targeted profile of subscribers, I've always seen it as one of the more "established' newsmagazines of the information technology space... and one obviously targeted at resellers of such technology. So to me it is interesting that the question is being discussed within CRN's print and web pages.

As to the larger question of whether "the coming VoIP war" will be between Microsoft and Cisco, one can't ignore that these two companies are giants in the overall IT industry with extremely significant resources and yes, the point is valid that as the interests of the two companies have converged in this merger of communication that many call "unified communications", they are now definitely going to be competing head-to-head.  All I can say is that the time ahead in this industry shall very definitely be quite an interesting one!

P.S. In full disclosure, my employer, Mitel, has had a partnership with Microsoft for several years now. A lot of Mitel equipment also gets deployed on a Cisco infrastructure and I communicate with a number of Cisco folks on standards issues.

[1] I would love to find out when CRN started, but the CRN.com site seems to have no info about its history and there's no Wikipedia article on it yet.
[2] At the current time, I do have a subscription to CRN.  Sometimes my subscription has lapsed when I've forgotten to annually fill out their subscription form.

Just out yesterday, TMC.Net published an interview with me titled, "Security and Disaster Recovery for IP Telephony Systems", by Mae Kowalke, where I talk about general VoIP security issues and then get into specifics about Mitel solutions.  Given that the author nicely gave me the chance to review the text and offer feedback before she published it, I have to say I'm pleased with how it came out. :-)

(And yes, I normally blog about VoIP security over on the Voice of VOIPSA weblog, but I just field weird about posting something like this over on that site.)

Late last week  there was quite the buzz in the VoIP part of the blogosphere about "Ooma" a new company with $27 million in funding that claims to "transform telecom services" and let you "make local and long-distance calls anywhere in the US for free" (provided, of course, that you live in the US).  I saw all the coverage and thought about writing something here, but I just couldn't get overly excited to do so.  My first reaction was, well, "how is this different from PhoneGnome or other similar systems?"  (And I enjoyed the fact that PhoneGnome promptly came out with a "Build Your Own Ooma" Challenge!)

My second reaction was that with their peer-to-peer architecture (letting others share your phoneline) there are bound to be security concerns (opinions here and here) and that it looks like it involves changing out your existing firewall/router and that simply isn't something I see people wanting to do. 

Anyway, there's been a whole lot of words written on this issue and so I thought I'd point to some of the pieces out there.  First, some nice summaries:

• ComputerWorld's IT Blog Watch: "Ooma selling free phone service"
• Jon Arnold: "Ooma - a Triumph of Technology or PR?"

And here are a range of the other articles out there:

• Om Malik's original post which has now attracted 130 comments: "Ooma wants voice to be free"
• Aswath Rao critiques it:  "Ooma? No Ma"
• Ken Camp gives it a thumbs-down: "Oompa Loompa Oooma"
• Stuart Henshall rips it apart: "Ooma - Will Blow $27 Million"
• Alec Saunders provides some good details and analysis: "Ooma revisited"
• Mark Evans is excited about free local calls: "The Dawn of the Free Local Call"
• Markus Göbel outlines security concerns: "Why Ooma is a security risk"

More details direct from ooma through the ooma FAQ.  Kudos for them for calling their beta program the "White Rabbit" program - it's cute for those who understand the reference.

In the end, it will be interesting to see what, if anything, comes of it all.  I have a really hard time believing that a huge number of people will shell out $399 for a box like this.  We'll see.

P.S. I noticed that the FAQ says this about international calling:

If you want to call overseas, you can use ooma by pre-purchasing international minutes at ooma.com for rates as low as five cents per minute.

In the era of Skype, Yahoo!Voice, Microsoft's Windows!Live, AIM and countless others that are essentially driving the cost of international calling down toward $0, it seems hard to believe that they will get people to pay "rates as low as five cents per minute".

Here's a great side benefit of having an IP phone in teleworker mode hanging off of a system somewhere out there on the Internet - you have a close-to-instant warning system about Internet connectivity issues. 

Take this morning... I walk into my home office and see that one of my phones has come out of its sleep status and the backlight is on and showing "CONNECTION PENDING..." with these black square boxes next to it.  I glance at another IP phone:  "PLEASE WAIT"

Oh, %#$#?!.  It's going to be that kind of Monday morning!

Yes, indeed, as I woke up the PCs, I did indeed have no connectivity.  Couldn't get to any websites and all the IM clients were cycling waiting to get connected.  After doing the usual power-cycling of the cable modem and verifying that I could get an address but couldn't ping beyond the next hop router, a relatively-quick call to Comcast brought the word that there was a "partial outage" in my area and that connectivity might be going up and down for the next two hours.

Great.  Wonderful way for a home office worker to start a Monday.

But it did remind me of one great benefit of having these IP teleworker phones[1] - they are a great way to know almost instantly whether my connection is up.  If I'm in the middle of doing something on my PC and it seems like connectivity is down, I just turn my head to look at the phones and can see very quickly if they are up.  Likewise, if I'm downstairs using my wife's PC and it seems like Internet access is down, I just go up the stairs and pop my head in the office... first glance is to see if the phones are up. 

It's a great side benefit of having the phones, although admittedly it wasn't anything on my mind when we were rolling out the Mitel Teleworker solution back in January 2003.  (Full disclosure: I was the product manager for the product when it was released.)

Now, this works in my case because the phones are using Mitel's own MiNET protocol and always have an encrypted MiNET connection established back to the Teleworker server sitting on the edge of the corporate network.  If the connection is broken, the phone flags that by displaying the aforementioned warning messages.  It's not *instant*, but typically within 30-60 seconds of the connection being down the messages appear.  If the phones were, say, in SIP mode connected to a SIP server out there, I wouldn't get the same fast notice because in SIP mode they are essentially stand-alone endpoints - think of them as mini-computers with a phone handset.  The first time I'd really notice was when I went to make a connection (or if the phone went to make some regularly scheduled connection and couldn't and put up an error message). 

This "side benefit" is, of course, not at all unique to Mitel implementations.  Basically any other IP phones that have "always-on" connections back to a central server will have the potential to do the same thing.

It works the other way, too, in letting you know when the connection is back online... while I was on the phone talking to the pleasant customer service rep at Comcast, how did I know that my Internet service was restored  (at least for the moment) without looking at my PC?  Simple...

... all my IP phones were back in operation.

[1] And yes, I have several teleworker phones- three to be exact, but hey, I'm working on emerging technology stuff so I have to be able to experiment and work with these phones.  They are also on different switches and trial systems.

Last week I wrote some first impressions of iSkoot, a new Skype client for Blackberry, and while I still think it's a very cool idea, I don't see myself using it all that much.  Why not?  Very simply...

Battery life!

Or the lack thereof.  Yes, indeed, it all does seem to come down to batteries, and iSkoot seems to certainly consume its share of power.  Now granted, my Blackberry 7290 is an older model and for all I know could probably use a new battery, but in "normal" operation, I can charge it up and then have it run for a good 3 or 4 days before it needs a recharge.  However, start up iSkoot and I found I suddenly needed a recharge by the end of the day!

In fairness, iSkoot is not alone in this... the other Blackberry IM clients I've used, both the Windows Messenger client and also most recently the IM+ client for Skype also have this same problem.  I'm assuming it has something to do with the need to regularly use the data connection for updates to status and to update chat messages.

I can see this actually being most useful to me when I'm traveling and need to quickly reach someone from within an airport or something like that. Of course, that's also when I want the longest battery life, too!  I think I'll keep it installed on my BB, but I don't think I'll have it running except for those times when I'm somewhere and I want a quick way to do IM via Skype.

Too bad, really, because one of the fun aspects of it was that I had a very easy way to read Twitter updates and Facebook updates on my BB (since I have both Twitter and Facebook status streams piped into a Skype chat).

Ah, the joy of batteries...

NOTE: Please see the updates at the bottom of this post.

Back on Monday, Jim Courtney over at Skype Journal IM'd me (on Skype naturally) asking if he could do a test call to me on "another Skype client for the Blackberry". Naturally, I said yes and in a moment or so we were speaking.  It turned out that he was using a new beta application from iSkoot.  From the news release:

The new iSkoot v1.1 delivers a comprehensive mobile Skype experience on BlackBerry: With the click of a button, users can instantly chat with their Skype contacts, make and receive Skype calls, and use SkypeOut™ to inexpensively call regular phone numbers nearly anywhere in the world. iSkoot v1.1 also displays complete Skype contact status information, so BlackBerry users can see which friends, family members and business colleagues are available, as well as manage their own online presence. This latest release features a next generation, easy-to-use interface especially designed for BlackBerry users and will offer additional features soon. iSkoot works without any need for PCs, special hardware, custom phones or Wi-Fi hot spots, and utilizes the existing mobile network infrastructure to route Skype calls through the voice channel.

It sounded interesting and so, of course, I had to try it out as well and finally had a spare moment to do so today.  Now, both Jim and I had commented a month ago about the IM+ Skype client from ShapeServices (my posts first here and then here with a link to Jim's coverage) so that previous experience somewhat colors my own view of the iSkoot application.

The installation was fairly straightforward. I filled out a form on iSkoot's site and was then SMS'd instructions for the download.  I simply opened the link in my Blackberry's browser and proceeded with the install in the normal "over the air" process.  One minor detail was that my Blackberry 7290 was not in the list of supported handsets, but I took a guess that the 7100 binary might work and so I used that (and it seems to work).

Here are some initial positive impressions:

• Nice user interface - Very nice interface.  Tabs that you can use Alt+wheel to move between for your contacts, online contacts, SkypeOut contacts and chats.
  
• Presence worked - I could see the presence of the other Skype users on my contact list.  I didn't try to see what happens when a user changes to see what kind of time delay there may or may not be.
  
• Outbound calls worked, although with an annoying step in the process - Move to a Skype contact and push your thumbwheel twice to call.  (Or push it once to see your options.) The call then starts by initiating a regular mobile call from your Blackberry to a phone number in Massachusetts (for me).  It then seems to call the other person on Skype and connect you through the gateway at iSkoot.  The annoying step was that when I first initiate a call, my Blackberry throws up a menu saying that an application is requesting to make a call and do I want to allow it, with the default being No. I therefore have to scroll up and press my thumbwheel again.  It's a pain and I couldn't find a way to remove that request.  I don't remember having to do that step in the IM+ client (and my trial has expired).  In any event, once the calls were connected, the audio quality sounded fine on both ends.
  
• Chats worked, and alerted you to new chats - Easy to initiate chats. Nice list of current chats.  If a new chat is opened up with you, you get a notification and can open it up.  If there are new messages in existing chats, you get notified of those as well.
  
• No conference call appearance - Unlike the IM+ client, your call just appears as a regular Skype call.  In fact, there was really no way for me to know Jim was not calling me from his regular Skype client.  With the IM+ client, you wound up getting put into a conf call with the other recipient which just seemed a bit strange.

Realizing it is still in beta (like, it seems, most everything on the net these days), here are some negative impressions:

• No support for groupchats - Using the Skype 3.2/3.5beta clients, I'm accustomed to having several public groupchat windows open.  Unfortunately, groupchats are not supported per the FAQ, and my public groupchats did not appear.  This does work in the IM+ client, so score 1 for IM+.
  
• Very slow updates to chats - In our experiment today, Jim Courtney and I both had Skype running on our PCs and so we could see our chat messages in a chat window there as well.  There were times when it took 5-10 minutes for messages typed in the PC chat window to appear in the iSkoot window!  Given that this is supposedly instant messaging, such a delay was hard to fathom.  Now there is a "Refresh Now" choice in the menu which could force a refresh, but the normal process seemed to have some kind of refresh interval.  Not all the time.  Sometimes messages appeared right away... but other times there was as much as a 10-minute delay before seeing the other message.  Hopefully this is just a scaling issue as iSkoot deals with their release!
  
• Slow call initiation process - Forgetting about my annoying Blackberry question I had to answer, the whole process of initiating the call seemed to take longer than the IM+ client did.  I'd have to purchase IM+ to actually test the timing, but the iSkoot process just seemed slower.
  
• Status did not have DND/Busy - Curiously, you can change your status in the iSkoot client, but you only have the choices of: Online, Away, Not Available and Invisible.  One of the ones I use often is "Do Not Disturb", so that I'm not disturbed.  That choice isn't here.  Perhaps the assumption is that you'll just exit the application.
  
• You can't receive Skype calls if you have Skype Voicemail enabled - Per the FAQ.  Not entirely sure why but this seems to be a bit of a headache if you this is not your only Skype client.  I also have Skype on my PC and if I am not there, I'd prefer to have the call go to voicemail.  Since I'm mostly looking to use this for Skype chats and Skype outbound calls, I don't expect it to be a big deal for me (I'll leave voicemail on) but I could see it being a pain if I did want to receive calls.
  
• You still have to give over your Skype password - As with IM+, you have to provide iSkoot with your Skype username and password and then they log in as you from their server/gateway.  As a commenter pointed out, there is a basic problem here that with your Skype account being connected to your PayPal account which in turn is connected to your bank account, you are potentially letting someone you don't know have access ultimately to your bank account.  Do you trust iSkoot (or anyone else) enough?  On the other hand, I'm not sure how any of these services can really work if you do not provide that information.  (See update below.)

All in all, it's an interesting entry into the idea of taking Skype onto a mobile phone.  As I have time I'll keep experimenting with it over the next few weeks... I could see it be especially useful if you were travelling (which, for better or worse, I'm not doing).

As I'll write up in another post, the one interesting use for me was that I could see Twitter and Facebook updates appearing in a Skype chat window and could post Twitter updates (without using the SMS interface)... which was an interesting experience.

In the meantime, if you are a Blackberry and Skype user and want to experiment, you can head over to iSkoot.com and try it out.

UPDATE #1 - 11 Jul 07: Jim Courtney IM'd me with the following comment on the Skype<->PayPal linkage:

btw, I investigated re the PayPal access issue. To do anything meaningful you need to log into PayPal as well. Also PayPal would not allow a process that was open to abuse. All you can buy automatically are voice mail, SkypeIn, SkypeOut and even there you can put on a daily limit as low as $50. And my PayPal password is definitely not my Skype pwd.

UPDATE #2 - 3 Aug 07: Jacqueline Van Meter with iSkoot Product Management has responded in a comment to my later post about iSkoot, addressing a number of the concerns I raised here.