Skip to main content
Sign in
Home Online 2013 2010 Interop Programs Library Forums Gallery Lync Blogs

Infrastructure qualified for Microsoft Lync

Find out more about the Microsoft Unified Communications Open Interoperability Program (UCOIP) 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. For information on Office Communications Server 2007 and Office Communications Server 2007 R2, please see Unified Communications Open Interoperability Program for Office Communications Server.

  1. Qualified IP-PBXs & Gateways
  2. Supported IP-PBXs
  3. Survivable Branch Appliances
  4. Session Border Controllers
  5. Networking
  6. Hardware Load Balancers
  7. Software Load Balancers
  8. Additional resources

Qualified IP-PBXs & Gateways

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 for Lync 2013

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

VendorQualified ProductSoftware Version TestedSupported Configuration
AudiocodesMediant 10006.60A.022.003Enhanced GatewayQualified with SRTP and TLS+S; with IPv6
Ferrari electronic AGOfficeMaster Gate4.0-1Enhanced GatewayQualified with SRTP and TLS+S; with IPv6
SonusSBC 1000/20002.2.1Enhanced GatewayQualified with SRTP and TLS+S; with IPv6


Qualified for Lync 2010

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

VendorQualified ProductSoftware Version TestedSupported 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 
GenbandA28.0 SP1IP-PBXQualified with SRTP and TLS 
C20CVM14IP-PBXQualified with SRTP and TLS 

Configuration Notes:

  1. Disable REFER, TLS and SRTP on Mediation Server. They are not supported by Genband.

Known Limitations:

  1. Media Bypass is not supported.
  2. DNS load balancing is not supported by the Genband C20, but load-balancing to multiple provisioned IP addresses is supported.
HuaweiAR1220V200R001C01IP-PBX Qualified

Configuration Notes:

  1. Disable REFER, TLS and SRTP on Medaition Server. They are not supported by Huawei.

Known Limitations:

  1. DNS load balancing is not supported by Huawei.
  2. Mediation Server Failover is not suppored by Huawei.
eSpace U1910, U1930, U1980V100R001IP-PBX Qualified with SRTP and TLS+S 

Configuration Notes:

  1. Disable REFER on Mediation Server. It is not supported by Huawei.
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 
Media5Mediatrix 30002.0.1v116Enhanced GatewayQualified+S
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.
Patton ElectronicsSmartNodeR6.T 2012-04-23Basic GatewayQualified
SangomaNetBorder Express6.0.42.4Basic GatewayQualified with SRTP and TLS+S 
SonusGSX90007.3.7s300Enhanced GatewayQualified with SRTP and TLS+S
SBC 10002.0.1v118Enhanced GatewayQualified with SRTP and TLS+S
SBC 20001.0.2v221Enhanced GatewayQualified with SRTP and TLS+S
Tenor DXP108-09-18Basic GatewayQualified
UX10002.0.1v118Enhanced GatewayQualified with SRTP and TLS+S 
UX20001.0.2v221 patch 1
2.0.1v118		Enhanced GatewayQualified with SRTP and TLS+S 
VX900
VX1200
VX1800		4.7.2v69Enhanced 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 Manager
Cisco Unified Session Manager*		Direct SIPUCM 8.5.1.12900-7

Configuration Notes:

  1. On the Cisco IP-PBX, configure MTP to enabled and PRACK to enabled.
  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.

* Note on Cisco Unified Session Manager: Cisco states that Unified Session Manager is based on the same SIP capability as Unified Communications Manager. As such, it is supported with the same capabilities as the qualified version of Unified Communications Manager.

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

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.

Qualified for Microsoft Lync Server 2013

VendorQualified DeviceQualified Firmware
AudiocodesMediant 800/1000/2000 SBASBA 1.1.11.40 / GW 6.60A.022.003
Ferrari electronicOfficeMaster SBASBA 2.0.4 / GW 4.0-1
SonusSBC10002.2.0b181
SBC20002.2.0b181


Qualified for Microsoft Lync Server 2010

VendorQualified DeviceQualified Firmware
AudiocodesMediant 800 SBASBA: 1.1.8.21,
Gateway: 6.00A.033.005
Mediant 1000 SBASBA: 1.1.8.21,
Gateway: 6.00A.033.005
Mediant 1000B SBASBA: 1.1.10.23,
Gateway: 6.40A.034.005
Mediant 2000 SBASBA: 1.1.8.21,
Gateway: 6.00A.033.005
CiscoCisco 3925 ISR G2SRE-900
For more information on this configuration, please see Deploying the Survivable Branch Appliance in Lync Server 2010 for Cisco Integrated Services Router / Service Ready Engine.
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
SonusSBC1000SBA: 4.0.7577.0,
Gateway: 2.0.1v118, 2.0.2v132
SBC2000SBA: 4.0.7577.0,
Gateway: 1.0.1.194, 2.0.1v118, 2.0.2v132

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

Session border controllers qualified for Lync Server

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.

Qualified for Microsoft Lync Server 2013

VendorQualified ProductSoftware Version Tested
Acme PacketNet-Net 3820/4500 SBCEC6.4.0
AudiocodesMediant 800/850 E-SBC6.60A.024.008
Mediant 1000B E-SBC6.60A.024.008
Mediant 4000 E-SBC6.60A.024.008
ItaltelNetmatch-S SBC2.0
SonusSBC 1000/20002.2.1


Qualified for Microsoft Lync Server 2010

VendorQualified ProductSoftware Version Tested
Acme PacketNet-Net 3820 / 4500C6.2m6p1, C6.3m2p3
Net-Net Enterprise Session Director, VM Edition (Net-Net ESD-VME)E3.6
AudiocodesMediant 1000 E-SBC6.20A.037.007
Mediant 3000 E-SBC6.20A.037.007
Mediant 4000 E-SBC6.60A.020.007
IngateSIParator/Firewall4.10.2
SonusSBC 10002.0.1v118
SBC 20001.0.2v221
SBC 5200V03.00.00-R000
SBC 5100V03.00.00-R000
UX10002.0.1v116
UX20001.3.2v83
TE SystemsAnynode SBC1.0.35

Networking for Lync Server 2010 and 2013

Listed below are the network infrastructure solutions that have been tested by these partners and reviewed by Microsoft to meet Lync Server 2010 requirements. It is recommended that you visit the partner’s web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the listed partner for more information on these products.

Additional information on networking with Microsoft Lync Server 2010, including Planning, QoS, Call Admission Control and Security can be found on the Lync Server Network Infrastructure Roadmap.

For more information on optimizing Wi-Fi networks with Microsoft Lync, please see the white paper Delivering Lync Real-Time Communications over Wi-Fi.

Wi-Fi

VendorQualified DeviceFirmware Version Tested
Aruba Networks, Inc.Mobility Controllers and AP-104/105/134/135 Access PointsAOS 6.1.3.2 and higher
Dell, Inc.PowerConnect W-Series Mobility Controllers and W-AP104/105/134/135 Access PointsAOS 6.1.3.2 and higher


Wired

VendorQualification
BrocadeBrocade MLX, SX, ICX, VDX, 5120
Extreme NetworksExtremeXOS 15.3.14
HPHP 2610, 2910al, 3500yl, 5400zl, 8200zl
Juniper NetworksJuniper 10.2R2.11

Hardware load balancers for Lync Server 2010

Listed below are hardware load balancers that have been tested by the vendor and reviewed by Microsoft to meet Lync Server 2010 requirements. It is recommended that you visit the vendor's web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the vendor for more information on these products.

Usage

For qualification, Lync Server 2010 requires integrating hardware load balancers in three deployment configurations. Hardware load balancers load balance traffic across several servers.

  • Enterprise pool with multiple front-end servers: In this scenario, the hardware load balancer will be the connectivity point to multiple front-end servers in an Enterprise pool in consolidated and expanded configuration. In the expanded configuration, the hardware load balancer also load balances traffic to the Web Components servers of the Enterprise pool.
  • Array of Directors: In this scenario, the hardware load balancer serves as the connectivity point to multiple Directors in an array.
  • Array of Edge Servers: In this scenario, if the hardware load balancer supports multiple virtual IP addresses (VIP), it will serve as the connectivity point to both the internal and external NICs for multiple Edge Servers in an array. If the hardware load balancer only supports a single VIP, then two hardware load balancers are required to load balance Edge Servers, one for the internal NICs and one for the external NICs of the Edge Server.

Hardware load balancers for Lync Server 2010

Note: These devices are backward compatible with Office Communications Server 2007 R2.

VendorQualified ProductSoftware Version TestedVendor’s Lync PageOther Supported Products
A10NetworksAX Series 1000, 2200, 3200

64-bit AX Series 2500, 2600, 3000, 5100, 5200		2.4.3 AX Series for Lync 2010 Overview and Deployment Guide 
Array NetworksAPV SeriesArrayOS TM 8.x or later Deployment Guide for Array Networks APV Application Delivery Controllers and Microsoft Lync Server 2010
  • Exchange 2010
  • SharePoint 2010
  • Array AG Series – Secure Access Gateway
AVANUWebmux 481SD, 591SGQ, 690PGV8.x and up WebMux and Microsoft Lync 2010
  • Office Communications Server 2007 R2
  • SharePoint 2010
  • Exchange Server 2010
BarracudaNetworksBarracuda Load Balancer Model 340, 440 or 6403.3.1.005, 3.5.0.008 Barracuda Load Balancer Deployment Guide 
BrocadeServerIron XL,4G,GTC,GTE,350,450 & 850SI V10.0.0a  Brocade Communications' Microsoft Unified Communications Solutions 
ServerIron ADX 1000, 4000, 10000V12.1, V12.2 Brocade Communications' Microsoft Unified Communications Solutions 
CitrixSystemsNetscaler8.1, 9.x Netscaler Developer Network 
ExcelianceALOHA Load Balancer5.5 Aloha Deployment Guide for Lync 2010 
F5BIG-IP Local Traffic Manager10.x, 11.x F5 Lync Server Solutions
  • Exchange 2003-2013
  • SharePoint 2007-2013
  • Microsoft Private Cloud 
jetNEXUSAccelerating Load Balancer (ALB)

Accelerating Load Balancer Extreme (ALB-X)		ALB 2.0

Software Version:3.42.1 (Build 1475)		 Advanced Load Balancing for Microsoft Lync 2010
  • Exchange 2010
  • SharePoint 2010
  • Terminal Services/Remote Desktop Services
  • ADFS
KempLoadMaster 2200, 2600, 3600, 5500V5.1 LoadMaster Deployment Guide for Microsoft Lync 2010
  • Exchange 2010
  • Windows 2008 RDS
  • SharePoint 2010
Loadbalancer.orgEnterprise, Enterprise MAX, Enterprise 10Gv6.18, v7.4.1 Microsoft Lync 2010 Deployment Guide
  • Exchange 2010
  • SharePoint 2010
  • Terminal Services/Remote Desktop Services
Radware

AppDirector

 

Alteon

v.2.14.03

 

v.28.1.0

Radware AppDirector optimizing the delivery of Microsoft Lync 2010

Alteon Application Switch (AAS) optimizing the delivery of Microsoft Lync 2010

 

Load balancer vendors interested in qualification of their load balancer solutions with Office Communications Server should contact uclb@microsoft.com.

Software load balancers for Lync Server 2010

Listed below are software load balancers that have been tested by the vendor and reviewed by Microsoft to meet Lync Server 2010 requirements. It is recommended that you visit the vendor's web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the vendor for more information on these products.

Software load balancers for Lync Server 2010

VendorQualified ProductSoftware Version TestedVendor's Lync Page
A10Networks64-bit AX Series: SoftAX2.6 AX Series for Lync 2010 Overview and Deployment Guide
Citrix SystemsNetscaler VPX9.1.102.8 Netscaler Developer Network
F5BIG-IP Local Traffic Manager Virtual Edition10.x, 11.x F5 Lync Server Solutions
jetNEXUSAccelerating Load Balancer (ALB)

Accelerating Load Balancer Extreme (ALB-X)		ALB 2.0

Software Version:3.42.1 (Build 1475)		 Advanced Load Balancing for Microsoft Lync 2010
KEMPLoadMaster VLM-100, VLM-1000V5.1 LoadMaster Deployment Guide for Microsoft Lync 2010
Loadbalancer.orgEnterprise VAv6.18, v7.4.1 Microsoft Lync 2010 Deployment Guide
Riverbed TechnologyStingray Traffic Manager8.x and up Riverbed Stingray and Microsft Lync 2010: Deployment Guide

Load balancer vendors interested in qualification of their load balancer solutions with Office Communications Server should contact uclb@microsoft.com.

Reverse proxies

This page describes which server reverse proxy partners have completed solution testing with Lync Server 2013 and contains pointers to accompanying deployment white papers hosted by the partner.

Qualified for Lync 2013

Listed below are reverse proxies that have been tested by the vendor and reviewed by Microsoft to meet Lync Server 2013 requirements. It is recommended that you visit the vendor's web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the vendor for more information on these products.

VendorQualified ProductSoftware Version TestedVendor's Lync Page
F5BIG-IP LTM and Virtual Editionv11, 11.0.1, 11.1, 11.2, 11.3F5 Deployment Guide for Microsoft Lync


Overview

The qualification program for reverse proxies is designed to ensure that customers have seamless experiences with setup, support, and use of qualified reverse proxies with Microsoft's Lync Server 2013. Only products that meet Lync Server 2013 requirements will be listed.

The qualification program for our reverse proxy partners is defined as follows:

  • Specific requirements for interoperability with Lync Server 2013
  • Testing scenario requirements for qualifying interoperability with Lync Server 2013
  • Quick Start Guide for installation and configuration requirements
  • Vendor Release Notes documenting any known issues
  • Enterprise-class standards for reliability and scalability

The program is designed to ensure that interoperability is tested by the vendor to meet Lync Server 2013 requirements in a consistent and supportable manner.

Note: The qualification program described here is not a Microsoft certification or logo program. Microsoft makes no warranties or representations with regard to the third-party solutions included in the program, including without limitation the supportability of such third-party solutions. Support for the specific implementation of third-party products within a Lync solution is provided by the third-party vendor under the terms agreed between you and the vendor. You are solely responsible for selecting, evaluating, and determining whether any third-party offering listed on this site is appropriate for your use.

Reverse Proxy vendors interested in qualification

Reverse Proxy vendors interested in participating in interoperability testing of their solutions with Lync Server 2013 should contact lyncrp@microsoft.com

Featured resources

Downloads

more

Note: The qualification program described here is not a Microsoft certification or logo program. Microsoft makes no warranties or representations with regard to the third-party solutions included in the program, including without limitation the supportability of such third-party solutions. Support for the specific implementation of third-party products within a Lync solution is provided by the third-party vendor under the terms agreed between you and the vendor. You are solely responsible for selecting, evaluating, and determining whether any third-party offering listed on this site is appropriate for your use.

Reverse Proxy vendors interested in qualification

Reverse Proxy vendors interested in participating in interoperability testing of their solutions with Lync Server 2013 should contact lyncrp@microsoft.com

Additional resources

Lync 2013

Server Resources

Client Resources

Connect

TechCenters

Information for

Join us: Follow us on Facebook Facebook  Follow us on Twitter Twitter

© 2013 Microsoft