The big story this week (so far), Skype for Asterisk (SFA) comes to its end. The official notification reads:
Skype for Asterisk will not be available for sale or activation after July 26, 2011.
Skype for Asterisk was developed by Digium in cooperation with Skype. It includes proprietary software from Skype that allows Asterisk to join the Skype network as a native client. Skype has decided not to renew the agreement that permits us to package this proprietary software. Therefore Skype for Asterisk sales and activations will cease on July 26, 2011.
This news arrived two weeks after Microsoft’s announcement to acquire Skype for $8.5 billion. This caused many to conclude that SFA’s demise is part of Microsoft’s dastardly plot to destroy all goodness in the world. Some of these theories can are seen here:
Now a good debunking requires a common frame of reference, so a short background on SFA. The Digium Alliance partnership was announced in 2008, and SFA was in beta in 2009. It was a pretty ingenious concept, connect Skype to a PBX. Prior attempts at this were all miserable – take a look at VoSKY. But what was really cool about SFA was it was more than basic voice. SFA provided bi-directional integration with Skype that included presence and SkypeName dialing. No other solution had or has done this with Skype.
It was a coup for Asterisk, and it was really big for Skype as it had conquered the individual user, but still sought corporate adoption. Going out on a limb here, perhaps Skype’s limited corporate success can be partially attributed to its fickle strategies. SFA was first, then came Skype for SIP, then the program changed to Skype for Business, and its current effort to conquer the enterprise is called Skype Connect.
All of these subsequent attempts, were/are effectively SIP trunks. Dumb SIP trunks. No presence, no outbound dialing to SkypeIDs. The service is primarily implemented for cheap long distance – not unified communications.
SFA was off to a great start. It got a lot of positive attention and licenses were selling. But the product had some unusual limitations – was Skype committed to it? In a post, Tim Panton, believes Skype wasn’t – that Skype hobbled the product. He points to an incredibly slow development/beta period, public friction, and odd license restrictions.
While SFA was still in beta, Skype launched Skype for SIP. Evidently, Skype liked the idea of connecting to a PBX – at least its voice services. Skype for SIP, looked to the PBX like a SIP voice trunk, the lowest common denominator of VoIP - simple and cheap to implement. The service initially launched on ShoreTel systems. Support for several additional systems and gateways including Avaya, Cisco, and SIPFoundry followed – but never for Asterisk.
It is easy to say that SFA was better than Skype for SIP, it was. But the advantages required education, commitment, budget, and administrators willing to set it up. It addressed a need that people didn’t understand. It required training and vision. Conversely, people understood long distance savings. Plus, everyone knows how to dial a phone. SFA faltered before it got out of the gate. Digium tried to spin damage control (http://blogs.digium.com/2009/03/26/the-rumors-of-our-death/), but Skype For SIP just had a more attractive cost/benefit/risk proposition.
SFA is big news this week, but it didn’t come up much in 2010 or 2011 before this week. It has been dying on the vine waiting to be put out of its misery.
I do love a good conspiracy, and it would be great to pin this on Microsoft.
Speaking of conspiracies, don’t even try to convince me that Darth Vadar had nothing to do with the destruction of the Death Star – he willed it. Come on, he just happened to be safely aboard a TIE fighter when it was destroyed?
But MS shutting down SFA is weak.
For starters, I might just subtly point out that Digium is the one that killed SFA – not Skype. UPDATE: This is wrong. Skype killed SFA, not Digium. Now it is possible Digium is a covert MS controlled front. Consider this, its CEO presents how to run a business on open source – and then publicly blogs about how his company was forced to shut down while it cleaned up its mess.
Another factor to consider is the Microsoft-Skype deal is agreed, but not done. Microsoft is not running Skype yet, and it is pretty unlikely the boys in Redmond are so worried about SFA that it needed to use back door nods and winks to kill it months before taking over the company. I heard a rumor that the whole deal actually nearly fell apart when Ballmer learned about SFA.
I think I will also take this opportunity to dispel another related yet separate topic that comes up. I keep hearing that MS will ruin Skype because Microsoft is a proprietary company. Microsoft may indeed ruin Skype and Microsoft may indeed be a proprietary company. But let’s be fair, few companies are more proprietary than Skype.
Skype uses its own clients, its own codecs, its own signaling, and its own firmware licensed to hardware partners. It does not interface with any other networks or equipment other than basic voice services. How its network actually functions, its resilience, reliability, encryption and security is a guarded secret.The logic that MS will ruin it because Skype is open and MS is not is hypocritical jabberwockey. If anything, Skype might teach MS a thing or two about being proprietary.
So that leaves the question: why did Skype kill off SFA this week and not next or the week before? To that, I have no frick’n idea. Maybe because they had an obligation to support it until now? Maybe because the Skype MS news earlier this month reminded them it still existed (I forgot), maybe because aliens that control Skype insisted. There could be several reasons, and it’s a reasonable question. Why Microsoft killed SFA, isn’t. (updated paragraph).