BroadSoft announces XO Communications is leveraging the Enterprise Trunking feature set of the BroadWorks VoIP application platform to deliver a new XO Enterprise SIP offering. Introduced today XO Enterprise SIP is an enhanced SIP trunking service offering for large enterprises, that enables them to transform their distributed PBX/PSTN interconnection to a more centralized and cost-effective VoIP solution. Enterprises can deploy a centralized IP-PBX in one or several primary locations and deliver VoIP services to other sites across their network. Businesses can also configure trunk capacity across their network, providing each site with on-demand access to unused call capacity. This will greatly reduce capital expenses and operating costs of managing voice services and equipment at each location.

Today's announcement builds upon BroadSoft's existing relationship with XO Communications, which dates back to early 2005. XO Communications currently uses BroadWorks to support its flagship XO IP Flex and XO SIP integrated access service offerings targeted at the small and mid-sized business market.

Large enterprises with multi-site locations such as banks, international financial institutions, retail stores and professional services firms, have unique requirements when it comes to SIP trunking deployments. It is often the case where a single, large IP PBX provides for an entire 50,000 person organization; therefore, loss of PSTN connectivity can have a major impact on business operations.

Based on the latest release of BroadWorks, XO Enterprise SIP uses BroadSoft's Enterprise Trunking feature set to simplify management of VoIP services and ensure business continuity across an enterprise's network by providing:

• Support for multiple, redundant SIP trunk groups per PBX/IP PBX
• Sophisticated routing and traffic distribution policies
• Enterprise-level call capacity and "bursting" in support of multi-site enterprise environments
• New caller ID screening features for enterprise least-cost-routing and improved interoperability with non-SIPconnect compliant IP PBXs