Skype selected Net-Net OS-Enterprise (OS-E) session border controllers from Acme Packet for its Skype for SIP beta offering. Acme Packet provides session border control (SBC) solutions and is the sole SBC partner for the Skype-for-SIP beta program.Skype's deployment of Acme Packet's SBC simplifies the interoperability and feature compatibility of the Skype for SIP beta offering with enterprise IP-PBX equipment and unified communications (UC) platforms which utilize the SIP standard. Skype-for-SIP allows enterprises with an on-premise IP PBX to take advantage of an IP-enabled communications tool and to benefit from end-to-end interoperability.
Skype and Acme Packet state that the Skype-for-SIP benefits are:
* Reduced costs by making outbound calls to landlines and mobiles worldwide at low Skype rates from devices connected to existing SIP-enabled PBX systems.
* Organizations can receive inbound voice calls to their PBX from the more than 400 million registered Skype users around the world via a global click-to-call button on their Web site.
* Customers that buy and associate local online numbers with their PBX can receive inbound calls to the PBX from landline and mobile phones via Skype.
* Skype integrates with existing IP PBX and UC platforms
I think that Skype's adoption of Acme Packet's SBCs may reduce the concern of security (You Said Not To Worry) for enterprises considering Skype-for-SIP, but I don't think it secures Skype. Skype has a sizeable presence, so attracting Skype users to companies could be a good thing. Down and dirty, Skype is cheap and easy to deploy--just click and agree. For the SMB/Es, this could potentially be an easy solution to deploy since the investment is very low and the Skype rates are competitive. I'm still not sold on using Skype, for all the past concerns I've already noted, and I'm thinking that this deal strengthens Skype but.... Reading Irwin's post on Skype-->Gizmo-->Jabber-->Cisco?? I still remain cautious. Will you deploy the beta Skype-for-SIP in your organization?
