Microsoft Unified Communications Open Interoperability ProgramFind out more about the Microsoft Unified Communications Open Interoperability Program for enterprise telephony infrastructure, including finding qualified SIP-PSTN gateways, IP-PBXs and SIP Trunking services. Vendor ProcessIf you are interested in joining the Microsoft Unified Communications Open Interoperability Program, please go to the Vendor Process for Microsoft Unified Communications Open Interoperability Program page and follow instructions to join and participate in the program. OverviewThe qualification program for SIP/PSTN Gateways, IP-PBXs and SIP Trunking Services ensures that customers have seamless experiences with setup, support, and use of qualified telephony infrastructure and services with Microsoft's unified communications software. Only products that meet rigorous and extensive testing requirements and conform to the specifications and test plans will receive qualification. While the specifications are based on industry standards, this program also defines: - Specific requirements for interoperability with Office Communications Server & Exchange Server 2007 Unified Messaging
- Testing requirements for qualifying interoperability with Office Communications Server & Exchange Server 2007 Unified Messaging
- Installation, set-up and configuration requirements via a Quick Start Guide
- Release Notes with any known issues
- Documented support process between Microsoft and the vendor
- Enterprise-class standards for audio quality, reliability, and scalability
The scope of the qualification is for environments where either Office Communications Server 2007 or Exchange Server 2007 utilizes a SIP/PSTN Gateway, IP-PBX or SIP Trunking Service for communication with the PSTN. The testing focus of the program is designed to ensure that vendors providing interoperability with Microsoft unified communications solutions do so in a consistent and supportable manner, including SIP and signaling support used with the Mediation Server role of Office Communications Server 2007 and the Unified Messaging role of Exchange Server 2007. Supported Configurations Available for Qualification with Office Communications Server 2007 R2The program currently supports three primary telephony integration components: SIP-PSTN Gateways, IP-PBXs and SIP Trunking Services. Please read the white paper "Integrating Telephony with Office Communications Server 2007" for an overview of the different supported configurations. Their components integrate with Office Communications Server 2007 and Office Communications Server 2007 R2, with four deployment scenarios available for qualification. Direct SIP - For SIP/PSTN Gateways: SIP/PSTN Gateways are typically designed to be dedicated to a function, a network node equipped to manage translation of different protocols. In this scenario, Gateways will facilitate connectivity between one or multiple Mediation Servers via SIP connectivity on one end and a TDM circuit connected with a PBX or the PSTN on the other end. Gateways are available in two configurations, basic and basic hybrid. Basic Gateways require a separate mediation server for connecting to the Office Communications Server, while Basic Hybrid gateways are bundled with Mediation Server on the same physical platform.
- For IP-PBXs: IP-PBXs that support native SIP connectivity (Direct SIP) may also provide and manage other call functionality independently of their role with Mediation Server, however numbers that are to be used by Office Communications Server 2007 are not managed by the IP-PBX in this configuration.
NOTE: Products qualified for Direct SIP Interoperability with Office Communications Server 2007 may also be capable of supporting Microsoft Exchange Server 2007 Unified Messaging with Exchange Server 2007 Service Pack 1. For example, in certain configurations, Exchange Server 2007 Unified Messaging is configured within the Office Communications Server 2007 deployment. Within this program we refer to this as “Exchange Unified Messaging via Office Communications Server 2007”. Please see the Planning Guide for more information.
SIP Trunking Service - A SIP Trunk is the use of SIP and RTP to pass telephony traffic from the enterprise network edge to a network service provider over an IP connection without traversing TDM or circuit networks. SIP Trunking is supported by Microsoft Office Communications Server 2007 R2 to a service provider offering PSTN origination, termination, and emergency services by making use of the SIP protocol.
Supported Configurations Available for Qualification with Exchange Server 2007 The program currently supports two primary telephony integration components: SIP-PSTN Gateways, and IP-PBXs. Please read the white paper "Exchange Server 2007 Unified Messaging " for an overview of the different supported configurations for IP-PBXs and Gateways. These components integrate with Exchange Server 2007, with two deployment scenarios available for qualification. - Direct SIP Connectivity via Gateway: In this scenario, Gateways will facilitate connectivity between one or multiple UM Servers via SIP connectivity on one end and a TDM circuit connected with a IP-PBX on the other end.
- Direct SIP Connectivity via IP-PBX: IP-PBXs that support native SIP connectivity (Direct SIP).
Direct SIP: Gateways and IP-PBXs Qualified for Office Communications ServerListed below are gateway and IP-PBX products and necessary firmware combinations that have been independently qualified. It is recommended that you visit the vendor's Web site listed in the table below for the latest information regarding PBX, protocol, capacity, country support and documentation including a Quick Start Guide, release notes and known issues. Other supported products are also listed by request of the Vendor as the same firmware runs across these products. While these have not been specifically tested, the Vendor does fully support this configuration for the listed Qualification Level. Please contact the Vendor for more information on these products. The Microsoft Partner Program recognizes the expertise and impact of partners in the technology marketplace. Find out more on the Microsoft Partner Program site. ** See partner’s site for known issues and support notes Dual Forking Qualified for Microsoft Office Communications ServerListed below are IP-PBX and firmware combinations that have been independently qualified. Please contact the vendor for more information on these products. Other supported products may also be listed by request of the vendor as the same firmware is used in these products. | IP-PBX Vendor | Tested Product | Qualification Level | Software Version Tested | Vendor's Web site | Other Supported Products | Office Communications Server 2007 R2 | Office Communications Server 2007 | Nortel
.jpg) | CS 1000 | Dual Forking*** Dual Forking with RCC*** | Call Server X2105.00W Signaling Server 5.00.31 Multimedia Communications Manager 3.0.1.77 | Nortel | CS 1000 Series | | .jpg) |
The Microsoft Partner Program recognizes the expertise and impact of partners in the technology marketplace. Find out more on the Microsoft Partner Program site. *** If you are deploying Dual Forking, you must also install the following updates for Microsoft Office Communications Server 2007: SIP Trunking Services Qualified for Microsoft Office Communications Server 2007 R2SIP Trunking enables an enterprise to connect their on-premise voice network implemented by Microsoft Office Communications Server 2007 R2 to the Public Switched Telephony Network (PSTN) directly over SIP. SIP Trunking services are offerings from IP Telephony Service Provider partners that offer PSTN origination, termination, and emergency services using the SIP protocol. Listed below are SIP Trunking Services that have been independently qualified to meet the UCOIP requirements. | Carrier | Service Name | Vendor's Web site | Global Crossing | SIP Trunking Services | Global Crossing | Interoute
.jpg) | InterouteOne | Interoute | Jajah
| JAJAH SIP Trunking | Jajah | Sprint
.jpg) | Sprint Global MPLS, SIP Trunking | Sprint | ThinkTel
| OCS Connect | ThinkTel |
The Microsoft Partner Program recognizes the expertise and impact of partners in the technology marketplace. Find out more on the Microsoft Partner Program site. Supported IP-PBXs for Microsoft Office Communications ServerThe following IP-PBXs are supported by Microsoft but have not gone through the formal OIP qualification process nor was the testing requested by the vendor. Sufficient internal testing has been performed by Microsoft such that specific configurations are supported by Microsoft (where applicable with known limitations). These configurations utilize the commercially available production SIP trunk interface of the IP-PBX vendor but may not be supported by the IP-PBX vendor. In addition, IP-PBX vendor-provided complete documentation for installation and set-up, release notes, or documented support processes may not be available. Wherever possible, Microsoft will endeavor to provide documentation for installation and set-up. Qualified Gateways for Exchange Server 2007The current list of supported gateways is maintained here. Gateway vendors interested in being listed on this page please follow the vendor process for Microsoft Unified Communications Open Interoperability Program mentioned below. Qualified PBXs for Exchange Server 2007The current list of supported IP-PBXs is maintained here. IP-PBX vendors interested in being listed on this page please follow the vendor process for Microsoft Unified Communications Open Interoperability Program mentioned below. Additional Resources for Office Communications Server |