Skip to main content
Sign in
HomeOnline2010LibraryPartnersForumsLync Blogs
Network Infrastructure
Load Balancer Partners
Open Interoperability Program
Video Solutions
Phones and Devices

Unified Communications Open Interoperability Program – Lync Server

Find out more about the Microsoft Unified Communications Open Interoperability Program for enterprise telephony services and infrastructure, including finding qualified SIP Trunking Services, E911 Service Providers, Survivable Branch Appliances, SIP-PSTN Gateways, Session Border Controllers (SBCs) and IP-PBXs.

This page details infrastructure and services qualified with Lync Server 2010. For information on Office Communications Server 2007 and Office Communications Server 2007 R2, please see Unified Communications Open Interoperability Program for Office Communications Server.

Overview

This qualification program for enterprise telephony services and infrastructure ensures that customers have seamless experiences with setup, support, and use of qualified telephony infrastructure and services with Microsoft's unified communications software including Lync Server and Exchange Server.

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 Lync Server & Exchange Server Voice Mail
  • Testing requirements for qualifying interoperability with Lync 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 Lync Server utilizes a Survivable Branch Appliance, SIP/PSTN Gateway, IP-PBX or SIP Trunking Service for communication with the PSTN or E-911 Service provider for communication with emergency services.

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

Additional Resources

Interested in Joining?

Qualified Services and Infrastructure

The qualification program for enterprise telephony services and infrastructure ensures that customers have seamless experiences with setup, support, and use of qualified telephony infrastructure and services with Microsoft's unified communications software.

Direct SIP
Supported IP-PBXs
Survivable Branch Appliances
SIP Trunking
Session Border Controllers
E911

Direct SIP: PSTN Gateways and IP-PBXs Qualified for Lync Server

Listed below are the PSTN gateways and IP-PBX products along with the necessary firmware combinations that have been independently qualified with Lync Server. It is recommended that you visit the vendor's Web site for the latest information regarding protocol, capacity, country support and documentation including a Quick Start Guide, release notes and any known issues.

Qualified= "Qualified"     Qualified with SRTP and TLS+S = "Qualified with SRTP & TLS"

VendorQualified ProductSoftware Version
Tested		Supported Configuration
AudiocodesMediant 800 MSBG6.00AL.019.007Enhanced GatewayQualified with SRTP and TLS+S 
Mediant 10006.00A.033.005Enhanced GatewayQualified with SRTP and TLS+S 
Mediant 20006.00A.033.005Enhanced GatewayQualified with SRTP and TLS+S 
Mediant 30006.00A.033.005Enhanced GatewayQualified with SRTP and TLS+S 
AastraMX-One4.1 SP3IP-PBXQualified with SRTP and TLS+S 

Configuration Notes:

  1. On Lync Mediation Server, Enable Media Bypass and RTCP, but Disable REFER. Testing determined that REFER does not function.
  2. MX-One does not support sending DTMF as a part of early media.
CiscoISR 29xx / 39xx15.1(3)TBasic GatewayQualified
ISR 281112.4(24)TBasic GatewayQualified
ISR 384512.4(15)T3Basic GatewayQualified

Configuration Notes:

  1. Disable REFER on both Lync Mediation Server and Cisco GW.
  2. On Lync Mediation Server, disable TLS and SRTP. Secure connectivity is not supported. 

Known Limitations:

  1. Analog devices connected to FXS ports do not support hold/resume. To support hold/resume, the FXS port needs to be controlled by a Cisco PBX.
DialogicDMG10006.0 SU7Enhanced GatewayQualified with SRTP and TLS+S 
DMG20006.0 SU7Enhanced GatewayQualified with SRTP and TLS+S 
DMG4000SU4, SIPcontrol 2.5, DIVA System Release 9.5 WinBasic GatewayQualified with SRTP and TLS+S 
Ferrari Electronic AGOfficeMaster Gate3, 3.3Enhanced GatewayQualified with SRTP and TLS+S 
InnovaphoneIP3010v.9.00 [90773]IP-PBX Qualified with SRTP and TLS+S  

Configuration Notes:

  1. Media Bypass, TLS and SRTP are supported.
  2. Disable REFER on Lync Mediation Server. Attended Transfer functions correctly only when REFER is disabled.
  3. Disable RTCP on Lync Mediation Server for active calls and calls on hold. The session timer should be enabled.

Known Limitations:

  1. While the IP-PBX supports Comfort Noise negotiation, it does not generate CN packets itself.
Interactive IntelligenceCustomer Interaction Center4.0 SU1IP-PBXQualified 
Mitel33004.2.1.6IP-PBXQualified 

Configuration Notes:

  1. On Lync Mediation Server, Enable Media Bypass and Disable REFER and RTCP. Testing determined that Mitel does not support REFER and RTCP.

Known Limitations:

  1. When a Mitel user calls a Lync user, there is no ring back tone provided for the Mitel user. Mitel is investigating adding RFC 3960 support in the future.
  2. Mitel does not support comfort noise. As a result, comfort noise is not played on Microsoft Lync.
NETVX900
VX1200
VX1800		4.7.2v69Enhanced GatewayQualified with SRTP and TLS+S 
UX10002.0.1v118Enhanced GatewayQualified with SRTP and TLS+S 
UX20001.0.2v221 patch 1
2.0.1v118		Enhanced GatewayQualified with SRTP and TLS+S 
NET/QuintumTenor DXP108-09-18Basic Gateway 
SangomaNetBorder Express6.0.42.4Basic GatewayQualified with SRTP and TLS+S 
SonusGSX90007.3.7s300Enhanced GatewayQualified with SRTP and TLS+S

For more information on Direct SIP configurations with Lync Server, please see PSTN Connectivity Components from the Lync TechNet library.

Supported IP-PBXs for Microsoft Lync Server 2010

The following IP-PBXs are supported by Microsoft but have not gone through the formal UCOIP 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 VendorTested ProductSupported ConfigurationSoftware Version Tested
Alcatel-LucentOmniPCX Enterprise OXEDirect SIPR9.1

Configuration Notes:

  1. On Lync Mediation Server, Media Bypass, RTCP and REFER are set to disabled. Testing found Media Bypass does not work for inbound calls, REFER is not supported and Alcatel does not send RTCP messages.

Known Limitations:

  1. When Lync user initiates a call to PBX or PSTN endpoint and subsequently places the call on hold, they will receive the error "call could not be put on hold" with the Lync client muted. Afterwards, the Lync client cannot be unmuted.
  2. When a Lync user performs a Blind transfer of a PBX or PSTN call to another PBX, PSTN or Lync number, if the transfer target doesn't answer, the call cannot be recovered to the original call. If the transfer completes, the local PBX phone will still show connected to the first Lync user
  3. When an call is ringing to a Lync user, the caller (either on an Alcatel station or a PSTN line routed through the PBX) will not get a ring-back tone.
  4. Comfort noise generation is not supported. As a result, comfort noise is not played on Microsoft Lync.
  5. When a Lync user declines a PSTN call routed from some PSTN trunk configurations, the PSTN caller does not get disconnected, and instead will start to hear Ring-Back.
  6. Because Alcatel sends a 502 message for a T1 line out of service or disconnected instead of a 503, failover to an alternate route will not function.
AvayaAura Session ManagerDirect SIP6.0.1

Configuration Notes:

  1. On Lync Mediation Server, Media Bypass and REFER are set to disabled. Testing found Media Bypass does not work for inbound calls and REFER is not supported.
  2. TLS and SRTP are not supported by Avaya and as a result need to be set to disabled on Mediation Server.

Known Limitations:

  1. Avaya does not support using an FQDN in the connection field.
  2. Comfort noise generation is not supported. As a result, comfort noise is not played on Lync.
  3. Testing found when calls routed to Avaya Audix voice mail may hear partial audio followed by disconnection.
Communications Manager SIP Enablement ServicesDirect SIP4.0
5.1
5.2.1

Documentation: Integrating Microsoft Lync Server 2010 and Avaya Communications Manager S8300

Configuration Notes:

  1. On the Avaya IP-PBX, the 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.
  2. On Lync Mediation Server, Media Bypass and REFER are set to disabled. Testing found Media Bypass does not work for inbound calls and REFER is not supported.

Known Limitations:

  1. When a Lync user transfers a PBX call to another PBX user, the local PBX phone will still show connected to the first Lync user.
  2. When a call is ringing to a Lync user, the caller (either on an Avaya station or a PSTN line routed through the PBX) will not get a ring-back tone. This issue has been resolved by Avaya with the 5.2.1 SP1 software release.
  3. Monitoring reports will not contain information regarding jitter and packet loss.
  4. Comfort noise generation is not supported. As a result, comfort noise is not played on Lync.
  5. ISDN Failover is not supported from a Lync perspective. If the Avaya PBX is being used for PSTN connectivity and multiple T1s are being utilized, a Lync client will not retry a call based on a T1 being unavailable. It may be possible to configure the PBX to not assign outbound calls from Lync to an unavailable T1, but this configuration was not tested.
CiscoDocumentation: Integrating Microsoft Lync Server 2010 and Cisco Unified Communications Manager
Cisco Unified Communications ManagerDirect SIPUCM 8.5.1.12900-7

Configuration Notes:

  1. On the Cisco IP-PBX, configure MTP to enabled and PRACK to disabled (the default for PRACK). The PRACK message sent by CUCM is malformed by missing the MAXFORWARDS header.
  2. On Lync Mediation Server, Media Bypass is set to enabled. RTCP is set to disabled, as Cisco doesn't send RTCP messages. REFER should be set to enabled, as REFER is supported by this IP-PBX.

Known Limitations:

  1. Comfort noise generation is not supported. As a result, comfort noise is not played on Microsoft Lync. When a Lync user configures call forward or simul-ring to a PSTN IVR number, the calling party will not hear early media played from the IVR.
Cisco Unified Communications ManagerDirect SIPUCM 8.0.3.21900-8

Configuration Notes:

  1. On the Cisco IP-PBX, configure MTP to enabled and PRACK to disabled (the default for PRACK). The PRACK message sent by CUCM 4 is malformed by missing the MAXFORWARDS header.
  2. On Lync Mediation Server, Media Bypass is set to enabled. RTCP and REFER are set to disabled, as Cisco doesn't send RTCP messages and REFER is not supported by this IP-PBX.

Known Limitations:

  1. Comfort noise generation is not supported. As a result, comfort noise is not played on Microsoft Lync.
  2. When a Lync user configures call forward or simul-ring to a PSTN IVR number, the calling party will not hear early media played from the IVR.
Cisco Unified Communications ManagerDirect SIPUCM 4.2 2000-4-4a
UCM 6.1.3.2000-1
UCM 7.1.3.10000-11

Configuration Notes:

  1. On the Cisco IP-PBX, configure MTP to enabled and PRACK to disabled (the default for PRACK). The PRACK message sent by CUCM 4 is malformed by missing the MAXFORWARDS header.
  2. On Lync Mediation Server, Media Bypass is set to enabled. RTCP and REFER are set to disabled, as Cisco doesn't send RTCP messages and REFER is not supported by this IP-PBX.

Known Limitations:

  1. When a Lync user transfers a PBX call to another PBX user, the local PBX phone will still show connected to the first Lync user.
  2. Comfort noise generation is not supported. As a result, comfort noise is not played on Microsoft Lync.
  3. When a Lync user configures call forward or simul-ring to a PSTN IVR number, the calling party will not hear early media played from the IVR.

For more information on Direct SIP Configurations with Lync Server, please see: PSTN Connectivity Components.

Survivable Branch Appliances Qualified for Microsoft Lync Server 2010

Listed below are the Survivable Branch Appliances (SBAs) along with the relevant firmware that have been independently qualified with Lync Server. It is recommended that you visit the vendor's Web site for the latest information regarding protocol, capacity, country support and documentation including a Quick Start Guide, release notes and any known issues.

VendorQualified DeviceQualified Firmware
AudiocodesMediant 800 SBASBA: 1.1.8.21,
Gateway: 6.00A.033.005
AudiocodesMediant 1000 SBASBA: 1.1.8.21,
Gateway: 6.00A.033.005
AudiocodesMediant 2000 SBASBA: 1.1.8.21,
Gateway: 6.00A.033.005
DialogicDMG4000 SBASU4, SIPControl 2.5,
Diva System Release 9.5 WIN
Ferrari electronic AGOfficeMaster SBA3.3
HPSurvivable Branch Communication zl ModuleSBA: 1.0.5,
Gateway: 3.0.3
NETUX1000SBA: 4.0.7577.0,
Gateway: 2.0.1v118
NETUX2000SBA: 4.0.7577.0,
Gateway: 1.0.1.194
NETUX2000SBA: 4.0.7577.0,
Gateway: 2.0.1v118

For more information on Survivable Branch Appliance configurations with Lync Server, please see Planning for Branch-Site Voice Resiliency; from the Lync Technet Library.

SIP Trunking Services qualified for Lync Server 2010

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 Lync Server.

Listed below are SIP Trunking Services that have been independently qualified to meet the UCOIP requirements.

CarrierService NameOffice 365 DedicatedQualified with
TLS & SRTP
AT&TAT&T IP Flexible Reach Service 
BT Global ServicesBT Onevoice 
ColtColt VoIP Access  
ElisaSIP Trunking  
Global CrossingSIP Trunking Services 
GlobalConnectGlobalConnect SIP Trunking  
HafslundHafslund SIP Connect  
IntelePeerIntelePeer SIP Trunking  
InterouteInterouteOne  
KordiaOnkor Voice  
Level 3Level 3 Communications SIP Trunking 
MyNetFoneMyNetFone SIP Trunking  
OneXSOneConnect SIP Trunk  
OptimusSIP Trunk  
Orange Business ServicesSIP Trunking  
Pure IPOneLync SIP Trunks 
QSC AGIPfonie®extended link  
SpeakUpspeakup trunk  
SwisscomSwisscom VoIP Gate  
TDCTDC Business Trunk 
TelenetTelenet SIP Trunking  
TelenorTelenor Samordnet kommunikasjon (Unified Communication)  
TeliaSonera Finland OyjSonera Business Voice Access  
ThinkTelOCS Connect  
Verizon BusinessIP Trunking Services 

For more information on SIP Trunking configurations with Lync Server, please see SIP Trunking from the Lync Technet Library

Session Border Controllers qualified for Lync Server 2010

Listed below are the Session Border Controllers (SBCs) along with the necessary firmware combinations that have been independently qualified with Lync Server. It is recommended that you visit the vendor's Web site for the latest information regarding protocol, capacity, country support and documentation including a Quick Start Guide, release notes and any known issues.

VendorQualified ProductSoftware Version Tested
Acme PacketNet-Net 3820 / 4500C6.2m6p1
AudiocodesMediant 1000 E-SBC6.20A.037.007
NETUX10002.0.1v116
NETUX20001.3.2v83

E-911 Service Providers and ELIN Gateways qualified for Lync Server 2010

Microsoft Lync supports two methods of placing E-911 calls: Using a qualified service delivered via a SIP Trunk, and using a qualified gateway that provides ELIN capabilities. Both provide routing of emergency calls from Lync to the correct emergency dispatch center responsible for deploying emergency responders for the given client location. Enterprises can use E-911 Services or ELIN Gateways to provide location-aware emergency dialing support for both hard phones and soft phones.

E-911 Service Providers

CompanyService Name
911 EnableEmergency Routing Service
Level 3Level 3 SIP Trunking for Lync

Learn more about E911 Services here: Emergency Services (E9-1-1).

E-911 ELIN Gateways

CompanyQualified Product
AudiocodesMediant Gateway & SBA version 6.4
911 EnableEmergency Gateway (EGW)


To find out more about how Microsoft recognizes the expertise and impact of partners in the technology marketplace, visit the Microsoft Partner Program site.



© 2012 Microsoft