Microsoft Unified Communications Open Interoperability Program
Find out more about the Microsoft Unified Communications Open Interoperability Program for enterprise telephony infrastructure, including finding qualified SIP-PSTN gateways and IP-PBXs and the process for telephony infrastructure vendors to join and participate in the program.
Overview
The qualification program for gateways and IP PBXs ensures that customers have seamless experiences with setup, support, and use of qualified telephony gateways and IP-PBXs 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 2007 & Exchange Server 2007 Unified Messaging
- Testing requirements for qualifying interoperability with Office Communications Server 2007 & 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 gateway or IP-PBX 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.
* "Interoperability Between Office Communications Server 2007 and PBX Systems: Dual Forking" and "Telephony Partner Product Interoperability - Interfaces for Connection to Mediation Server/OCS 2007 and to Exchange Server 2007 Unified Messaging"
IP-PBX and Gateway Supported Configurations with Office Communications Server 2007 Available for Qualification
The program currently supports two primary telephony integration components: SIP-PSTN Gateways, and IP-PBXs. Please read the white paper "Integrating Telephony with Office Communications Server 2007" for an overview of the different supported configurations for IP-PBXs and Gateways (Basic and Basic Hybrid).
There components integrate with Office Communications Server 2007, with four deployment scenarios available for qualification.
- Direct SIP Connectivity via Gateway: 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.
- Direct SIP Connectivity: 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. - Dual Forking: IP-PBXs can also support Dual Forking, which enables sharing of a common number with Office Communications Server 2007 to provide a richer user experience. In this example, the PBX could also support Direct SIP for certain numbers (managed by Office Communications Server), or manage the numbers themselves (for users not enabled for voice via Office Communications Server 2007).
- Dual Forking with Remote Call Control: Finally, IP-PBXs can support Dual Forking when used in combination with Remote Call Control. Remote Call Control provides information to Office Communications Server 2007 about the state of PBX-connected lines. This allows, for example, presence updates when the user is on the PBX-connected station set.
PBX vendors may offer Remote Call Control (RCC) as a standalone configuration option. While Microsoft will only qualify this feature when tested with Dual Forking, this is a supported configuration and customers interested in this should talk to their PBX vendor directly for supported products.
IP-PBX and Gateway Supported Configurations with Exchange Server 2007 Available for Qualification
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 PBX on the other end.
- Direct SIP Connectivity: IP-PBXs that support native SIP connectivity (Direct SIP).
System Integrators: Unified Communication
These are systems integrators who have received technical training on Microsoft’s Unified Communications platform. To ensure a smooth transition, Microsoft recommends that all customers engage the assistance of system integrators with Unified Communications specialization. For contact information, visit the Microsoft Unified Communications Partners overview page.
Qualified Gateways for Office Communications Server 2007
Listed below are gateway and firmware combinations that have been independently qualified via tekVizion labs or at Microsoft to meet qualification requirements. It is recommended that you visit the vendor's Web site 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.
Gateway Vendor | Tested Product | Qualification Level | Software Version Tested | Gateway Configuration | Vendor’s Website | Other Supported Products |
Aculab
.jpg "Microsoft Gold Certified Partner")
| ApplianX Gateway for Office Communications Server 2007 | Direct SIP Connectivity via Gateway | V1.0.0 | Basic Hybrid | Aculab | |
AudioCodes
| Mediant 1000 | Direct SIP Connectivity via Gateway | 5.20A.043 | Basic Gateway | AudioCodes | MediaPack 11x |
Mediant 2000 | Direct SIP Connectivity via Gateway | 5.20A.043 | Basic Gateway | AudioCodes | MediaPack 11x, Mediant |
Mediant 2000 Hybrid | Direct SIP Connectivity via Gateway | 5.20A.043 | Basic Hybrid | AudioCodes | MediaPack 11x, Mediant |
Cisco | 2851 Integrated Services Router | Direct SIP Connectivity via Gateway** | IOS 12.4(11)XJ | Basic Gateway | Cisco Cisco Interoperability Documents | 2800 Series |
3845 Integrated Services Router | Direct SIP Connectivity via Gateway** | IOS 12.4(11)XJ | Basic Gateway | Cisco Cisco Interoperability Documents | 3800 Series |
Dialogic
| 2000 | Direct SIP Connectivity via Gateway | 5.1.142 | Basic Gateway | Dialogic | DMG1000 and DMG2000 Series |
4000 | Direct SIP Connectivity via Gateway | 1.5.102 | Basic Hybrid | Dialogic | DMG4000 Series |
Ferrari electronic AG
| OfficeMaster Gate | Direct SIP Connectivity via Gateway | 3.1 | Basic Gateway | Ferrari | |
NEC
| SV70 OCS-GW-A | Direct SIP Connectivity via Gateway | MG-16SIPC | Basic Gateway | NEC | |
NET
| VX1200 | Direct SIP Connectivity via Gateway | 4.4.2.v31 | Basic Gateway | NET | VX Series |
Nortel
| Secure Router 4134 | Direct SIP Connectivity via Gateway | 10.1.0 | Basic Hybrid | Nortel | |
| Nuera Communications | GX-1K | Direct SIP Connectivity via Gateway | 5.20A.043 | Basic Gateway | Nuera | |
GX-2K | Direct SIP Connectivity via Gateway | 5.20A.043 | Basic Gateway | Nuera | |
Tango Networks
| Abrazo (qualified with Audiocodes Mediant 2000 5.20A.043) | Direct SIP Connectivity via Gateway | 3.3 | Basic Gateway | Tango | |
Quintum
| Tenor DX | Direct SIP Connectivity via Gateway | P105-19-10-MS-01 | Basic Gateway | Quintum | Tenor AS, AF, AX, BX, DX and CMS Series |
Tenor Hybrid Gateway 60 | Direct SIP Connectivity via Gateway | S. 106-06-02 | Basic Hybrid | Quintum | |
VegaStream
| Vega400 | Direct SIP Connectivity via Gateway | 8.282S029 | Basic Gateway | VegaStream | Vega50 Europa Vega 5000 |
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
Qualified IP-PBXs for Microsoft Office Communicator 2007
Listed below are IP-PBX and firmware combinations that have been independently qualified via tekVizion labs or at Microsoft to meet qualification requirements. 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 |
Cisco
| Cisco Unified Communications Manager | Direct SIP | 6.1.1.3000-2
(requires update package for Communications Server 2007 Mediation Server: August 2008) | Cisco | |
Nortel
| 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 |
Seltatel
| SAMoffice 4 | Direct SIP | 2.8.0 | Seltatel | |
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:
Qualified Gateways for Exchange Server 2007
The 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 IP-PBXs for Exchange Server 2007
The 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.
Vendor Process for Microsoft Unified Communications Open Interoperability Program
Gateway or IP-PBX vendors interested in qualifying their product for Office Communications Server 2007 must meet both technical and marketing requirements. Participation in the program is solely at Microsoft’s discretion. Upon successful completion, the product and firmware combination tested will be listed on this site.
Summary of Requirements
- Be an IP-PBX or Gateway vendor (this program is not open to System Integrators utilizing 3rd party hardware)
- For Direct SIP, comply to the specification “Telephony Partner Product Interoperability – Interfaces for Connection to Mediation Server/OCS 2007 and to Exchange Server 2007 Unified Messaging”
- For Dual Forking, comply to the specification “Interoperability Between Microsoft Office Communications Server 2007 and PBX Systems: Dual Forking” and test plan
- For RCC, comply to the specification “PBX Telephony Features (CSTA/RCC) Specification for Microsoft Office Communications Server 2007” and test plan
- Successfully meet technical Qualification Program requirements at tekVizion labs for the respective qualification level
- Become member of TSANet
- Provide Quick Start Guide for configuration steps for Office Communications Server 2007
- Provide dedicated website for Office Communications Server 2007 supported products, including support, ordering, and technical documentation
- Join Microsoft Partner Program
To begin the process, vendors should:
- Read the Integrating Telephony with Office Communications Server 2007 document, and download the trial versions of the product.
- Register to join the Microsoft Unified Communications Open Interoperability Program by visiting Microsoft Connect, logging in with their Passport account, click Invitations on the left navigation, and use this Invitation code: oip-YJ3X-7FK4.
- Fill out the survey and click Submit. To be approved, you must provide your corporate email address from a Gateway or IP-PBX vendor.
- Upon approval into the program (please allow 1-2 weeks), Microsoft will provide access to the technical specifications, documentation on the program requirements and information on how to engage with tekVizion.
Additional Resources for Office Communications Server 2007