The Voice On The Web public chat has continued to be lively through the week. Not only has Skype’s Senior Product Manager responsible for Skype for SIP, Chris Moore, participated but a couple of other guests have joined the discussion to clarify some issues.

First to summarize Chris’ comments:

• He is sorting through the overwhelming number of beta program applications with the intent to make accepted accounts live early next week
• G.711 codec support is in the late stages of development and may be available as early as next week; this will be accompanied by a list of countries where G.711 is supported.
• Chris has been taking input from participants with respect to SIP header information that would make Skype for SIP more broadly applicable. This, of course, leads into a discussion of going outside the “box” of SIP header standards. (SIP headers basically provide information that is transferred across a SIP connection.) More information from Jason Goecke at Adhearsion; Dan York at Voxeo has made an initial suggestion over at Github.

However, more significant have the the responses from Digium about their perspective on where Skype for Asterisk is positioned and the participation of David Tang, Vice President, Global Marketing at VoSKY in the Public Chat discussion.

Steve Sokol at Digium put up a post, “The Rumors Of Our Death” where he outlines key differentiators of Skype for Asterisk from Skype for SIP (slightly revised by Steve after feedback from Skype and chat participants):

• SFA can handle incoming Skype calls directly from any user on the Skype network.  SFS can receive incoming calls from Skype users names that are statically mapped to a Skype name to a SIP account.
• SFA can place calls to any user on the Skype network.  SFS cannot place calls to Skype users.
• SFA includes support for Skype presence information.  SFS has no support for presence.
• SFA includes buddy list management.  SFS has no buddy list management features.
• SFA calls are encrypted from end-to-end while SFS calls are delivered to the SFS endpoint devices (PBX) as unencrypted RTP streams.
• SFA supports multiple media codecs including G.711 aLaw and uLaw as well as G.729.  Wide-band audio will be available in a near-term revision.  SFS supports only compressed telephony-grade G.729 media streams.

Ultimately, the key differentiator is that SFA is designed to allow developers to build rich applications that are deeply integrated with the Skype network, while the SFS offering is a trunking solution for legacy IP-PBX systems that support SIP. Both have their place and neither is specifically competitive with the other. Both Digium and Skype are dedicated to Skype For Asterisk and both are working hard to make sure that when released it exceeds expectations.

Steve then goes on to discuss the current status of Skype for Asterisk, why it is taking so long to come out of beta and makes this important point about changes in the Skype Business Control Panel:

Enter the Skype Business Control Panel (BCP).  Skype’s Skype For Business division has launched an all-out effort to make business customers a corporate priority. Currently the BCP is simply a way to aggregate and share Skype credit.  As business services like SFA and SFS are rolled out it will take on a much more prominent role as the administrative interface for commercial customers.

The next update to the BCP will allow business customers to create master accounts that are owned and managed by companies rather than individuals.  With the BCP, Bob’s account would have belonged to AGI rather than to Bob, much like his AGI email account and company credit card.  If Bob went in search of greener pastures the system administrator could simply redirect his calls to another sales guy.

Jason Goecke has then put up his second post on Skype for SIP, Skype for Asterisk DOA; long live Skype for Asterisk, clarifying his positioning of the two offerings and concludes with:

The point is not to declare SFA dead, but to highlight these points in the hopes that the opportunities for deeper integration and the associated benefits are clear. For SFA to overshadow the SFS announcement, I contend these features are needed:

• Two-way chat via the Manager API
• Extended presence support
• SILK-codec support, which would require end-points (ie – SIP soft phones/hardware phones) embedding SILK

I understand that Digium and Skype need to get SFA to market, but a clear roadmap of what comes next and the timing would be immensely useful as developers look to place their bets. I applaud the work that Skype and Digium have been doing and the opening of the Skype network on multiple fronts. I just hope this is an opportunity to open the Skype network that little bit more.

David Tang at VoSKY has also contributed to the discussion; his main point:

We have our fair share of scars from being an early pioneer working with Skype.  Digium is just beginning to experience it.

From the tone of a few comments re VoSKY in the chat and considering their long experience with Skype implementations in businesses, a large reseller network and their creative ingenuity, we can expect that VoSKY will figure out a way to  go beyond simply continuing to be a “Skype trunking” solution for legacy PBX’s lacking SIP support (non-SIP PBX’s).

Back to the Business Control Panel (“BCP”) and its role. To date it has simply been a means for an administrator to manage Skype accounts in terms of handling Skype credits and implementing Skype on PC’s within an enterprise. Going forward Chris Moore has made the following comment:

I think I’ve chatted about the BCP in some interviews, yes the BCP will take a larger role in administration for small business of existing and new services. It will be the central portal for an SMB to use Skype.

Seems that there are many of the Voice On The Web Public Chat who are ready to start experimenting and developing with Skype for SIP; I look forward to monitoring the feedback as they finally get their hands-on experiences. Bottom line: from these developers, Digium, VoSKY and others, Skype has launched a significant opportunity to see innovation at work solving real business communications issues.

Overall Skype is starting to execute on their Business strategy through the new Business marketing group. The Business Control Panel is central to this strategy. We now have seen three activities in that direction: Skype for SIP, Skype for Asterisk and the Lotus Live support.

Update: Chris Moore has confirmed that the first beta account acceptances have gone out today; login details and passwords will be issued Monday/Tuesday next week.

Related articles by Zemanta

• Skype Now Means Business, Friends The SIP World (gigaom.com)
• Skype opens up to corporate SIP communications (Chaim/About Skype) (techmeme.com)
• Skype Opens Up To SIP, Finally Eyes Enterprise Customers The Way It Should (techcrunch.com)
• OpenSky Opens Skype, But Does It Work? (phoneboy.com)

Yesterday’s announcement of the Skype for SIP beta created lots of commentary in the blogosphere; it remained the leading topic on Techmeme for several hours.

• Phil Wolff over at Skype Journal, in “Skype For SIP: Big Money, Skypeless, Brand Destroyer”, outlines some of the positioning with respect to Skype for Asterisk, channel schism issues and worries that it abandons Skype’s central tenants and could undermine the brand.
• Alec Saunders, in “Skype embraces SIP; announces beta service for business users”, talks about the impact on businesses using legacy PBX’s, the increased pressure on international long distance markets and a reminder that about 1/3 of all current Skype traffic is business related.
• Jason Goecke at Ahearsion, a Skype for Asterisk beta developer, worries about the impact on the market for Skype for Asterisk in “Skype for SIP = Skype for Asterisk DOA?”

But most interesting was the Voice On The Web Public Chat session that ensued. Being on a vacation I was away from my laptop for about seven hours (yes, it was a great day to be golfing) but when I returned I found a session that not only provided the flavor of the vibrant debate going on but also many answers. The key – Chris Moore, Skype’s Senior Product Manager responsible for Skype for SIP joined into the discussion to make several points:

• Most importantly – this is Skype for SIP beta; his team is looking for feedback from a range of beta testers, not only third party developers but also the IP PBX vendors themselves. To quote Chris:
  

  Yep, whole idea is to get feedback, see what people want/don’t want to help prioritize development of new features. Our group, Skype For Business, is getting a lot of focus and its a key strategic focal point for Skype now. We’ll never get it completely right at the start, but a start is still a start

• To qualify as a beta tester you need to have some experience with configuring IP PBX’s that are currently in the market. For instance, “you must have, and be able to configure, your own SIP Enabled PBX that supports G.729 codec.”
• Beta testers will need to create a temporary Skype name to use in the beta program; the issue of a separate SkypeID and how it was handled was hotly debated.
  One point to clarify:

  Skype for SIP actually can allow multiple Skype IDs to be mapped through to a single SIP identity. However, during the beta period, we are only supporting a 1 to 1 mapping due to the fact that Skype’s advanced Business Control Panel (BCP) configuration portal is not yet available at this time. If a company wishes to configure multiple Skype ID’s mapped to a SIP identity, we can accommodate this for a subset of the beta trial participants.

• The key connections made by Skype for SIP are:
  

  - PBX –> SkypeOut (PSTN)
  - SkypeIn/Online numbers (PSTN) –> PBX
  - Skype Clients –> PBX

• The business model, including pricing, has yet to be worked out. It will require Skype to determine a means to separate out business users from “consumer” users on both Skype for SIP and Skype for Asterisk. The principle here is that business benefits from the various features of these offerings; where such significant value-add exists there is a market for the services. But any pricing for either offering is yet to be determined, keeping in mind that both offerings’ desire to make significant market penetration will be a key moderator on pricing. Again quoting Chris:
  

  no new road is easy and enhancing our focus so Skype can support business users as a distinct group differently from consumers takes some work

• Differentiation from Skype for Asterisk will be an ongoing challenge. Initially Skype for Asterisk, which will be an Asterisk channel, includes handling SIP—>Skype calls, Skype-to-Skype calls and will incorporate presence information. (My comments on an ignored aspect differentiating these are below.)
• While SFS may incorporate some “Skype trunking” capability, SFS also offers the handling of inbound calling from Skype Online numbers.
• As for the current status of SFS, Chris says the focus at the moment is on getting voice connections right as this is the feature most demanded in the market:
  

  and this is baby steps for Skype, there are many more UC services to come, voice for SIP is the biggest ask from customers. Video/presence etc only make  sense when codecs are common between skype clients and SIP endpoints.Some work left there!

• Codecs are an issue. The initially supported G.729 codec requires licensing. The Skype for Business team is working on incorporation of G.711 within a few weeks but eventually hopes to assist with the adoption of the SILK codec across the industry by supporting SILK. But this also requires SILK support at the end points. Bottom line: codecs have both a technology and business issues to be resolved.
• Security is an issue that will probably provide one of the major challenges as Skype opens up access to its cloud from both Skype for Business offerings.

My own observations, not having been around for the discussion:

• Skype for SIP and Skype for Asterisk: the discussion yesterday centered on technical issues but totally ignored the market channel issues.
• Skype for SIP requires working with the various IP PBX vendors who have their own distribution channels; Skype for Asterisk is a partnering project with Digium who has its own unique distribution channels. These channels are both looking for innovation that keeps them in business. Yes, the common issue is that SFS and SFA both threaten the long distance market, but the VAR’s and System Integrators in these channels will need new offerings that meet this challenge.
• A significant challenge for both SFA and SFS will be the User Interface. How much will either of these products make the installation,  configuration and operational aspects so user friendly that outside support requirements are minimized or eliminated. This is a huge challenge in the SMB market as many small business owners will simply not want to be involved with such issues; they have their own business specialty to focus on. The value-add of VAR’s and SI’s serving any business market comes in making business communications low cost, seamless to the business operation and five 9’s uptime for their customers.
• There is not one solution that will meet the complete world of business needs. Currently in this SMB space we have several vendors: Cisco, Microsoft Response Point, Avaya, Siemens, etc. The world would be up in arms if there were only one offering for providing the disruptive innovation for which Skype can provide support to these channels.
• The issue of addressing consumer users vs business issues recalls the PC market twenty years ago when PC hardware vendors, initially Compaq, finally figured out how to differentiate and address these markets. This was a major issue I had to deal with in setting up a PC reseller network at the time. Today we see Dell addressing these various markets as soon as you launch into their website.

The Skype-enabled world is only healthy if there are alternative offerings and channels. Recall the theme of Skype President Josh Silverman’s reminder to the analysts last week: “Skype is a software company but we plan to be everywhere”. The Skype for Business group is focusing on making the software required to support these offerings; this software will leverage the IP PBX vendors and Digium distribution channels to drive adoption through into the various regional business market channels worldwide.

Update: While Om’s post, Skype Now Means Business, Friends the SIP World, demonstrates that he has not been following very closely the strategy being laid out by Skype’s new executive team over the past few months, the comment stream it triggered  is well worth reading. For instance, check out SFA developer Tim Panton’s comment about the opportunity for innovation he has found in SFA:

That aside, I’m a huge fan of S4A and our experience to date has been positive. We leverage the improved identity management (vs PSTN or SIP) and low costs of Skype to do some very cool integration with business processes and web applications by routing Skype calls through the extensible and scriptable platform of Asterisk. [author’s bold]

Next Post: Why Skype needs to get Skype Public Chat back into the latest release of Skype for Windows 4.0. The discussion referenced above demonstrates that this is the major failing of this version.

Update: Andy Abramson at VoIP Watch: Skype and SIP Equals A Takeaway of Toll Free

Related articles by Zemanta

• Skype Taps ShoreTel for Enterprise Play (gigaom.com)

Skype announces launch of a beta version of Skype for SIP, connecting IP-PBX’s to the Skype cloud.

Dan York, while a keen supporter of Skype, has been campaigning for a Skype to SIP interconnect on his Disruptive Telephony blog. In a post last fall, “Skype and SIP – the two sides of the issue raised by Michael Robertson”, he says:

We need to build the interconnect.

Yeah, there are a TON of issues out there that we still need to address to build that interconnect. There’s a whole host of security issues… there are billing issues… there are trust issues… there are network plumbing issues. Yes, there are all those issues. But if we are to succeed in ultimately bringing about the rich communication experience we want, we need to make this happen.

And for that, Skype’s walls need to come down…. at least a bit.

What we need is that Interconnect from Skype’s cloud out to the emerging IP infrastructure. Think about it… Skype right now has a two-way interconnect between Skype’s cloud and the cloud we know as the PSTN. It’s called “SkypeOut” and “SkypeIn” (or whatever marketing names they are being called now). If you dial my SkypeIn number, you can reach me on Skype wherever I am. From my Skype client, I can call anyone on the PSTN. The two-way interconnect is already there.

This morning Skype announced the launch of a beta version of Skype for SIP as a major initiative for further penetration into the business market. Basically Skype for SIP allows SIP PBX owners to access the Skype cloud as additional inbound lines , via Skype Online numbers, and outbound extensions to their existing PBX, via SkypeOut. From the press release:

Key Features

The beta version of Skype For SIP will enable business users to:

• Receive and manage inbound calls from Skype users worldwide on SIP-enabled PBX systems; connecting the company Web site to the PBX system via click-to-call
• Place calls with Skype to landlines and mobile phones worldwide from any connected SIP-enabled PBX; reducing costs with Skype’s low-cost global rates
• Purchase Skype’s online numbers, to receive calls to the corporate PBX from landlines or mobile phones
• Manage Skype calls using their existing hardware and system applications such as call routing, conferencing, phone menus and voicemail; no additional downloads or training are required.

In an interview with Skype Senior Product Manager Chris Moore, I learned:

• Skype’s’ goal will be to have a totally user friendly interface such that Skype for SIP is a seamless service
• Administration will be done through an extended Skype Business Control Panel interface which, amongst other activities will establish Skype for SIP account mapping, manage online numbers and perform appropriate configuration for the various PBX’s.
• Skype will be looking to work with the various SIP PBX and Unified Communications vendors, such as Cisco, Avaya, Nortel and Siemens. When I asked about Microsoft Response Point, which had been demonstrated to me the previous day, Chris confirmed, yes, they were another prospective vendor to be approached.
• during the beta, Skype will be used on a pay-as-you-go basis; pricing for the service once it is launched has yet to be determined
• Skype will be including security issues as one major consideration (I expect Dan York to have more to say on this issue)
• The service will be configured to take advantage of Skype’s royalty free SILK codec; if both endpoints of a call support SILK, then the SILK support will carry across the Skype for SIP interface.

This has to be a landmark announcement for the IP-based communications space. It effectively allows businesses to integrate the Skype cloud into existing infrastructure to handle all long distance and international calling. Some other initial observations:

• Does Skype for SIP impact the space currently served by Vosky’s PBX services?  It definitely leaves open for Vosky the analog PBX market; one question will be how does Vosky figure out a way to work Skype for SIP into their business activities and offerings during the six- to twelve-month beta?
• It’s currently a beta; applicants for beta participation can apply at www.skypeforsip.com. From the press release: “Applicants will need to be businesses, have an installed SIP based IP-PBX system, as well as a level of technical competency to configure their own SIP-enabled PBX. The initial beta is available to a limited number of participants.”
• Skype also expects to determine an appropriate distribution channel. While ease-of-use is a key goal, there will still be small business owners who will want third party expertise to manage their communications activities. So expect Skype to look to a VAR or Systems Integrator channel to support implementation.
• Skype for SIP broadens Skype’s penetration into the small-to-medium business market. Where Skype for Asterisk introduces a Skype feature-rich Asterisk channel to Asterisk PBX’s, Skype for SIP simply brings Skype cloud connectivity to a major subset of existing small business PBX installations.
• Along another feature axis we see hosted services vs on-premise implementations. Will widely geographically distributed small businesses favor a hosted service, such as OnState’s Virtual PBX, or one of these on-premise PBX offerings.

One sure call: the market for business long distance, especially international calling, is about to be radically disrupted as these services come into play. It brings about new business opportunities and, most significantly, makes any business a global business, if the will is there. With probably over one million IP PBX’s out there (Skype’s press release says over 438,000 were sold in 2008 along), Skype for SIP brings the slow but sure death of legacy international calling, one PBX at a time.

And, of course, Dan York brings his deep perspective, not only on how Skype for SIP works, but also on the security and codec issues surronding Skype for SIP: Skype tears down more walls with “Skype For SIP”.