Unified Communications Open Interoperability Program – Office Communications Server

Vendor Process

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

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	IP-PBX	CS 1000, 5.50.12	+S
Avaya	IP-PBX	CS 1000, 6.00R / 6.00.18	+S
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
Cisco	IP-PBX	Unified Communication Manager 8.0.1
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
Genband	IP-PBX	CS2000/C20, CVM14
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
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
Patton	Basic Gateway	SmartNode 4600 Series Gateways, R5.6 and newer
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.

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 365 Dedicated
AT&T	AT&T IP Flexible Reach Service
BT Global Services	BT Onevoice
Etherspeak	LyncTrunk
Global Crossing	SIP Trunking Services
IntelePeer	IntelePeer SIP Trunking
Interoute	InterouteOne
IP Directions	OCS Telephony Services
Jajah	JAJAH SIP Trunking
Level 3	Level 3 Communications SIP Trunking
Orange Business Services	SIP Trunking
Paetec	Paetec SIP Trunking Services
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.00W Signaling Server 5.00.31 Multimedia 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:

• http://support.microsoft.com/?kbid=943083
• http://support.microsoft.com/?kbid=943085 
• http://support.microsoft.com/?kbid=943086 
• http://support.microsoft.com/?kbid=944285

Qualified Gateways for Exchange Server Voice Mail

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

Qualified PBXs for Exchange Server Voice Mail

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