Microsoft Unified Communications Open Interoperability Program

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.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 and Microsoft Office Communications Online (BPOS-Dedicated).

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 Voice Mail
  • Specific requirements for interoperability with Office Communications Online Services for SIP Trunking Service Providers
  • Testing requirements for qualifying interoperability with Office Communications Server & Exchange Server Voice Mail
  • 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 or Exchange Server Voice Mail utilizes a SIP/PSTN Gateway, IP-PBX or SIP Trunking Service for communication with the PSTN. Additionally, qualification is available for Microsoft Office Communications Online Service environments utilizing Office Communications Server with Exchange Online Unified Messaging.

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 and the Voice Mail role of Exchange Server.

Direct SIP: Gateways and IP-PBXs Qualified for Office Communications Server

Listed 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 for the latest information regarding PSTN/PBX, protocol, capacity, country support and documentation including a Quick Start Guide, release notes and known issues.

— “Qualified” +S —”Qualified with SRTP & TLS”

Vendor Configuration Tested Product Communications Server Version
2007 R2 2007
Aastra IP-PBX MX-ONE V.4.0 +S  
Aculab Basic Hybrid ApplianX Gateway for Office Communications Server 2007, V1.0.0       
Altigen IP-PBX MAXCS, 6.5.0.1000    
AudioCodes Basic Gateway Mediant 1000, 5.60A.013.005 +S  
AudioCodes Basic Gateway Mediant 1000, 5.20A.043    
AudioCodes Basic Gateway Mediant 2000, 5.60A.013.005 +S  
AudioCodes Basic Gateway Mediant 2000, 5.20A.043    
AudioCodes Basic Hybrid Mediant 1000 Hybrid, 5.60A.013.005 +S  
AudioCodes Basic Hybrid Mediant 1000 Hybrid, 5.20A.043    
AudioCodes Basic Hybrid Mediant 2000 Hybrid, 5.60A.013.005 +S  
AudioCodes Basic Hybrid Mediant 2000 Hybrid, 5.20A.043    
Avaya IP-PBX Avaya Aura Session Manager 5.2 with Avaya Aura Communication Manager 5.2.1 SP1    
Avaya Basic Hybrid Secure Router 4134, 10.2.1    
Avaya Basic Hybrid Secure Router 4134, 10.1.0    
Avaya Basic Gateway Secure Router 2330, 10.2.1    
Cisco Basic Gateway**    2851 Integrated Services Router, IOS 12.4(15)T    
Cisco Basic Gateway** 2851 Integrated Services Router, IOS 12.4(24)T    
Cisco Basic Gateway** 3845 Integrated Services Router, IOS 12.4(15)T    
Cisco Basic Gateway** 3845 Integrated Services Router, IOS 12.4(24)T    
Cisco IP-PBX Unified Communication Manager 7.1.3    
Dialogic Basic Gateway DMG2000, 6.0.128 +S  
Dialogic Basic Gateway DMG2000, 5.1.142    
Dialogic Basic Hybrid DMG4000, 1.5.102    
Dialogic Basic Hybrid DMG4000, Dialogic Diva SIPcontrol 2.1.0.33 +S  
Ferrari electronic AG Basic Gateway OfficeMaster Gate, 3.1    
Ferrari electronic AG Basic Gateway OfficeMaster Gate, 3.2 +S  
Ferrari electronic AG Basic Hybrid OfficeMaster Hybrid Gate, 3.2 +S  
Huawei Technologies IP-PBX SoftCo, V100R002    
Innovaphone IP-PBX IP6000, V7.00 ocs-certified 09-7034301    
Media5 Basic Gateway Mediatrix 3000 Series, DGW 2.0    
Mitel IP-PBX 3300, 9.0.0.41    
NEC Basic Gateway SV70 OCS-GW-A, MG-16SIPC    
NET Basic Gateway VX1200, 4.7v88 +S  
NET Basic Gateway VX1200, 4.4.2.v31    
Nortel IP-PBX CS 1000, 5.50.12 +S  
Nuera Communications    Basic Gateway GX-1K, 5.60A.013.005 +S  
Nuera Communications Basic Gateway GX-1K, 5.20A.043    
Nuera Communications Basic Gateway GX-2K, 5.60A.013.005 +S  
Nuera Communications Basic Gateway GX-2K, 5.20A.043    
Quintum Basic Gateway Tenor DX, P107-06-00-OCSR2-03    
Quintum Basic Gateway Tenor DX, P105-19-10-MS-01    
Quintum Basic Hybrid Tenor Hybrid Gateway 60, P107-06-00-OCSR2-03    
Seltatel IP-PBX SAMoffice 4, 2.8.0    
Tango Networks Basic Gateway Abrazo (qualified with Audiocodes Mediant 2000 5.20A.043), 3.3    
Teldat Basic Gateway Vyda-2M 10.7.55 +S  
VegaStream Basic Gateway Vega400, 8.282S029    

** See partner’s site for known issues and support notes

Other Supported Products

Other supported products are listed by request of the Vendor as the same qualified firmware may be supported across several different 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.

Gateways or IP-PBXs Other Supported Products
AudioCodes Mediant 1000 MediaPack 11x, Mediant
Cisco 2851 Integrated Services Router    2800 Series  
Cisco 3851 Integrated Services Router 3800 Series  
Dialogic DMG2000 DMG1000 and DMG2000 Series  
Dialogic DMG4000 Dialogic 4000 Media Gateway Series and Dialogic Diva SIPcontrol  
Mediatrix 3000 Series Mediatrix 4100 Series, Mediatrix 4400 Series  
NET VX1200 VX Series, VX900, VX1800  
Quintum Tenor DX Tenor AS, AF, AX, BX, DX and CMS Series  
Teldat Vyda-2M Vyda Series and Atlas Series  
VegaStream Vega400 Vega50 Europa Vega 5000  

SIP Trunking Services Qualified for Microsoft Office Communications Server 2007 R2

SIP Trunking enables connectivity 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. An enterprise can use SIP Trunking to connect their on-premise voice network implemented by Microsoft Office Communications Server 2007 R2 or to provision PSTN termination capability for Office Communications Online (BPOS-Dedicated).

Listed below are SIP Trunking Services that have been independently qualified to meet the UCOIP requirements along with those services who meet the additive requirements for Office Communications Online (BPOS-Dedicated).

Carrier Service Name Office Communications Online (BPOS-D) Ver 10.1
AT&T AT&T IP Flexible Reach Service  
BT Global Services BT Onevoice  
Global Crossing SIP Trunking Services  
IntelePeer IntelePeer SIP Trunking  
Interoute InterouteOne  
IP Directions OCS Telephony Services  
Jajah JAJAH SIP Trunking  
Orange Business Services SIP Trunking  
Sotel SoTel IP Services  
Sprint Sprint Global MPLS, SIP Trunking     
Swisscom Swisscom VoIP Gate  
Telenor Telenor Samordnet kommunikasjon
(Unified Communication)
 
ThinkTel OCS Connect  
Verizon Business IP Trunking Services  

Supported IP-PBXs for Microsoft Office Communications Server

The 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.

IP-PBX Vendor Tested Product Supported Configuration Software Versions Tested 2007 R2 2007
Avaya Communications Manager SIP Enablement Services Direct SIP 4.0    
Known Limitations:

  • Configuration requires setting “Alternate Route Timer(sec)” value from default of 10 sec to 30 sec. The configuration should show “Alternate Route Timer(sec): 30” in the corresponding SIP signaling group.
  • When an call is ringing to the Office Communicator user, the caller (either on an Avaya station or a PSTN line routed through the PBX) will not get ring back tone. This issue has been resolved by Avaya with the 5.x software releases.
  • Quality of Experience reports will not contain information regarding jitter and packet loss.
  • Comfort noise generation is not supported. As a result, comfort noise is not played on Office Communicator.
  • ISDN Failover is not supported from an OCS perspective. If the Avaya PBX is being used for PSTN connectivity and multiple T1’s are being utilized, an OC client will not retry a call based on a T1 being unavailable. It may be possible to configure the Avaya to not assign outbound calls from OCS to an unavailable T1, but this configuration was not tested.
Cisco Cisco Unified Communications Manager Direct SIP 4.2(3)_SR3a    
4.2(3)_SR4b    
5.1(1b)    
5.1(3e)    
6.1(1b)    
6.1(3a)    
Known Limitations:

  • The PRACK message sent by CUCM 4.2(3) is malformed by missing the MAXFORWARDS header.  As a result, this configuration requires PRACK to be disabled.  By default, PRACK is disabled in CUCM 4.2(3)
  • For Office Communications Server 2007, this support requires update package for Communications Server 2007 Mediation Server: August 2008.
  • OCS 2007 may not appropriately normalize the PAI in the 200 OK or UPDATE, resulting in OC displaying a non RFC3966 formatted global number and in failed RNL on OC. When calling from OC 2007 to a Cisco phone number, after the caller gets connected, the name of the person on the Cisco phone may not be shown on Communicator, and instead OC may display the E.164 number (without a “+”) for the person on the Cisco phone. This is resolved in OCS 2007 R2
  • When calling from OC 2007 to a Cisco phone number, where the Cisco extension is disconnected or out of service, the Cisco IP-PBX may not notify OC 2007 in a timely manner. This has been remediated in OCS 2007 R2.
Siemens
Enterprise
Communications
OpenScape Direct SIP 3.1R3    
Known Limitations:

  • Inbound early media/PRACK is not supported on the Siemens PBX. As a result, in some situations the initial audio of a call may be clipped as the call signaling is being set up.
  • Certain Siemens IP phones may not render audio for inbound calls. If this occurs, a phone configuration change to support both symmetric and asymmetric RTP will be needed.
  • For Hold/Un-hold to function properly, OpenScape needs the RTP config parameter Srx/Sip/ZeroIpOnHold set to false.
  • For full SDP versioning support, OpenScape needs the RTP config parameter Srx/Sip/CompareSdpBody set to true.
  • Quality of Experience reports will not contain information regarding jitter and packet loss for PSTN calls coming through the Siemens IP PBX.

Dual Forking Qualified for Microsoft Office Communications Server

Listed below are IP-PBX and firmware combinations that have been independently qualified. Please contact the vendor for more information on these products.

IP-PBX Vendor    Tested Product    Qualification Level    Software Version Tested Other Supported Products    2007
Nortel CS 1000 Dual Forking***Dual Forking
with RCC***
Call Server X2105.00WSignaling Server 5.00.31Multimedia Communications Manager 3.0.1.77    CS 1000 Series  
         

*** If you are deploying Dual Forking, you must also install the following updates for Microsoft Office Communications Server 2007:

 Source:  http://technet.microsoft.com/en-us/office/ocs/bb735838.aspx

2017-07-27T00:01:11+00:00 June 9th, 2010|Uncategorized|

About the Author:

Clint is cool as a cucumber, but has been aged in habanero brine.