Skip to main content

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. Load Balancers
  7. Reverse Proxy
  8. Virtual Desktop Infrastructure


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
AastraMX-ONE5.0 SP3 HF2IP-PBXQualified with SRTP and TLS+S
Aastra 470R3.1IP-PBXQualified with SRTP and TLS+S
AudiocodesMediant 5006.60A.236.002Basic GatewayQualified with SRTP and TLS+S
Mediant 8006.60A.236.002Basic GatewayQualified with SRTP and TLS+S
Mediant 10006.60A.022.003Enhanced GatewayQualified with SRTP and TLS+S; with IPv6
Mediant 20006.60A.236.002Enhanced GatewayQualified with SRTP and TLS+S 
Mediant 30006.60A.236.002Enhanced GatewayQualified with SRTP and TLS+S 
BressnerUCFeatureBox UCFB-xxxr1.8-422960MBasic GatewayQualified
CiscoISR 384515.1.4M6Basic GatewayQualified with SRTP and TLS

Documentation: Integrating Lync 2013 and ISR 3845 Configuration Guide v1.0

Configuration Notes:

  1. Disable REFER and RTCP support on both Lync Mediation Server and Cisco GW.
  2. While a specific ISR model was tested, any model in this series running the qualified firmware is 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.
  2. No ringback is heard when call is forwarded from a Lync Endpoint to a PSTN Endpoint. This can be corrected by allowing 183 without SDP on the outbound dial-peers to Lync, but this will result in no ring back on regular inbound calls.
ISR 392515.3(3)M1Basic GatewayQualified with SRTP and TLS

Configuration Notes:

  1. Disable REFER and RTCP support on both Lync Mediation Server and Cisco GW.
  2. While a specific ISR model was tested, any model in this series running the qualified firmware is supported.

Known Limitations:

  1. Call Park on Lync Client fails. Lync Client drops the call as the Gateway responds with "a=sendrecv" to an INVITE from Lync to place the call on hold. This issue is documented under case number CSCuo44538 with Cisco Support.
  2. As the Gateway overrides the progress indicator from Lync Sever, PSTN calling party does not hear IVR when the Lync called party is set to simultaneous ring an IVR number with Early Media.
  3. Call Hold and transfer on Analog Endpoints fails with the recommended dial peer configuration on the ISR.
Ericsson-LG EnterpriseIPECS IP-PBX; SW Version: 5.5Bd5.5BdIP-PBXQualified with SRTP and TLS+S

Configuration Notes:

  1. Disable REFER support on Lync Mediation Server

Known Limitations:

  1. DNS Load Balancing and IPv6 are not supported
Ferrari electronic AGOfficeMaster Gate4.0-1Enhanced GatewayQualified with SRTP and TLS+S; with IPv6
HPFlexBranch Multi-Service Router (MSR) SeriesComware, version 5.2, Release 2317Enhanced GatewayQualified with SRTP and TLS+S
Itibia TechnologiesOfficeTen IPPBX 28001.3.1.1IP-PBXQualified with SRTP and TLS+S
Patton ElectronicsSmartNode SN46716.TBasic GatewayQualified with SRTP and TLS
SamsungSamsung Communication Manager4.1.0Direct SIPQualified with SRTP and TLS

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.

Known Limitations:

  1. DNS Load Balancing using the same FQDN for two IP addresses is not supported by the Samsung PBX.
Sangoma TechnologiesNetborder Express Gateway4.4Basic GatewayQualified with SRTP and TLS
Vega 400gR100S044Basic GatewayQualified with SRTP and TLS
Vega 200gR100S044Basic GatewayQualified with SRTP and TLS
Vega 100gR100S044Basic GatewayQualified with SRTP and TLS
SonusSBC 1000/20002.2.1, V 3.1.1v285Enhanced GatewayQualified with SRTP and TLS+S
VX 1200V 4.9v55Enhanced GatewayQualified with SRTP and TLS+S


Qualified for Lync 2010

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

VendorQualified ProductSoftware Version TestedSupported Configuration
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.
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 
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 ElectronicsSmartNode SN4671R6.T 2012-04-23Basic GatewayQualified
SangomaNetBorder Express6.0.42.4Basic GatewayQualified with SRTP and TLS+S 
SonusSBC 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

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.

Supported with Lync 2013

IP-PBX VendorTested ProductSupported ConfigurationSoftware Version Tested
AvayaAura Session Manager 6.1Direct SIP6.1.2.0.612004 (Service Pack 2)
 

Documentation: Lync 2013 and Avaya Aura 6.1 Integration Guide v1.3

Configuration Notes:

  1. REFER can be set to enabled and RTCP set to Disabled.
  2. TLS and SRTP were not tested.
  3. Disable "ForwardCallHistory" on the trunk Call forwarding on Lync client fails at PRI when History-Info is turned on.

Known Limitations:

  1. Due to a the issue documented in KB 2904439, call hold fails with media bypass enabled.
  2. Comfort noise generation is not supported. As a result, comfort noise is not played on Lync.
Aura Session Manager 6.3Direct SIP6.3.2.0.632023
 

Configuration Notes:

  1. Media Bypass, RTCP, and History-Info were set to Enabled.
  2. REFER and Session Timer were set to Disabled.

Known Limitations:

  1. With Media bypass enabled in Lync, for an incoming call to Lync client that has simultaneous ring to a number with early media enabled, caller will hear ring back instead of the early media.
  2. Avaya Aura communication manager does not send disconnect to PSTN via ISDN trunk while receiving SIP 603 response from Mediation server for incoming call to Lync client. Caller will hear overflow tone and call will not disconnect until caller drops the call.
CiscoCisco Unified Communications ManagerDirect SIPUCM 8.6.2.20000-2
 

Configuration Notes:

  1. On the Cisco IP-PBX, configure MTP to enabled and PRACK to disabled (the default for PRACK).
  2. In order to manage call hold appropriately in bypass scenarios, the following update is needed for the Lync client.
  3. On Lync Mediation Server, Media Bypass, REFER and Session Timer are set to enabled. RTCP is set to disabled.

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.
  3. Cisco UCM does not originate or pass through ‘History-Info’ and ‘Referred-by’ nor convert it to ‘Diversion’ header. As a result, calls being forwarded or transferred to a PSTN user or calls that simultaneously ring a PSTN user, may fail with Service Providers that expect history information (transferring party info). Service Providers not looking for the transferring party details in history or diversion headers may pass the call through, however this may cause billing challenges for these kinds of calls.
Cisco Unified Communications ManagerDirect SIPUCM 7.0.1.11000-2
 

Configuration Notes:

  1. On the Cisco IP-PBX, configure MTP to enabled and PRACK to disabled (the default for PRACK).
  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 without a Referred-By header.

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.
  4. CUCM will not send OPTIONS, impacting failover scenarios as the IP-PBX cannot determine Lync's state until a call is offered.


Supported with Lync 2010

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
HPHP MSR Small Survivable Branch Communication MIM Module powered by Microsoft Lync (JG587A)
HP MSR Medium Survivable Branch Communication MIM Module powered by Microsoft Lync (JG588A)
HP MSR Large Survivable Branch Communication FIC Module powered by Microsoft Lync (JG589A)
HP MSR OAP SBA Version 1.0.2217.0
Ferrari electronicOfficeMaster SBASBA 2.0.4 / GW 4.0-1
SonusSBC10002.2.0b181
SBC20003.1.1 build 285


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
HPHP MSR Small Survivable Branch Communication MIM Module powered by Microsoft Lync (JG587A)
HP MSR Medium Survivable Branch Communication MIM Module powered by Microsoft Lync (JG588A)
HP MSR Large Survivable Branch Communication FIC Module powered by Microsoft Lync (JG589A)
HP MSR OAP SBA Version 1.0.2217.0
Survivable 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 2600 SBC6.60A.024.008
Mediant 3000 SBC6.60A.024.008
Mediant 4000 E-SBC6.60A.024.008
Mediant 9000 SW Edition SBCV 6.80A.216.004
Ferrari electronic AGOfficeMaster Gate (Virtual Edition) SBC4.0-5
ItaltelNetmatch-S SBC2.0
Nable Communications, Inc.nXer SBCv2.0
OracleOracle e-SBCACME Net-Net OSVM, with firmware ECZ6.4.0 MR-2
AP1100 Session Border ControllerECZ720p1.64.bz
Sangoma TechnologiesVega Enterprise SBC2.0
NetBorder Carrier SBC2.0
SonusSBC 10002.2.1, 3.1
SBC 20002.2.1, 3.1
SBC 51004.0
SBC 51104.0
SBC 52004.0
SBC 52104.0, 4.1.0
SBC 70004.1.1
SBC VX 12004.9v55
SWe SBC4.1.1
TE-SYSTEMSANYNODE1.1.122


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 2600 E-SBC6.60A.020.007
Mediant 3000 E-SBC6.20A.037.007
Mediant 4000 E-SBC6.60A.020.007
GenbandQUANTiX SBC8.2.1.3
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 DeviceController UsedFirmware Version Tested
Aruba Networks, Inc.Aruba Mobility Controller and Aruba AP 204/205, AP 214/215, AP 224/225, AP 274/275 802.11ac Access Points3600AOS 6.4.2.0
Aruba Mobility Controller and Dual-Radio 802.11n Aruba Access Points AOS 6.1.3.2
Virtual controller for Aruba Instant. IAP 224/225, IAP 274/275 802.11ac Instant Access Points. Dual-Radio 802.11n Instant Access Points 4.0.0.7
Cisco SystemsCisco Wireless LAN Controllers, Cisco Aironet 802.11n Access PointsAIR-CT5508-K9SW 7.6
Dell, Inc.PowerConnect W-Series Mobility Controllers and W-AP104/105/134/135 Access Points AOS 6.1.3.2
Extreme NetworksIdentiFi Wireless Appliances and IdentiFi 802.11n Access PointsIdentiFi V2110 Virtual Controller on Vmware9.01.01.0228
WS-AP3825e, WS-AP3825i, WS-AP3865 802.11ac Access PointsIdentiFi V2110 Virtual Controller on Vmware09.12.01.0067
HPMSM720/MSM760/MSM765 zl/MSM775 zl Wireless LAN Controllers
and
MSM430/MSM460/MSM466/MSM466-R and HP 425 Access Points
MSM7206.0.1.1
HP 560, HP 425, MSM430/MSM460/MSM466/MSM466-RHP 830 8G3507P26
H3C   
Juniper NetworksWireless LAN Controllers, WLA532 Wireless LAN APsWLC880RMSS 8.0
Meru NetworksAP-322, AP-832, AP-822 802.11ac Access Points and MC-4200 ControllerMC-42006.1.2
Motorola SolutionsMotorola Wireless LAN Controllers and 802.11n Access PointsNX9510WiNG 5.5.0.0
RuckusZoneFlex R500, R600, T300Zone Director 1200, 3000, 50009.9.0/0 build 118
Ruckus WirelessRuckus Wireless LAN Controllers and 802.11n Access PointsSCG-200SCG 2.5


Wired

VendorQualification
Aruba NetworksS1500, S2500, and S3500 Mobility Access Switches
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

Listed below are hardware load balancers that have been tested by the vendor and reviewed by Microsoft to meet Lync Server 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 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

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

VendorQualified ProductSoftware Version TestedVendor's Lync Page
A10NetworksAX Series 1000, 2200, 32002.4.3 AX Series for Lync 2010 Overview and Deployment Guide
64-bit AX Series 2500, 2600, 3000, 5100, 5200
Array NetworksAPV SeriesArrayOS TM 8.x or later Deployment Guide for Array Networks APV Application Delivery Controllers and Microsoft Lync Server 2010
AVANUWebmux 481SD, 591SGQ, 690PGV8.x and up WebMux and Microsoft Lync 2010
BarracudaNetworksBarracuda Load Balancer ADC 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
CitrixSystemsNetscaler8.1, 9.x, 10.5 Netscaler Developer Network
F5BIG-IP Local Traffic Manager11.x F5 Lync Server Solutions
HAProxy TechnologiesALOHA Load Balancer5.5 Aloha Deployment Guide for Lync 2010
jetNEXUSAccelerating Load Balancer (ALB)ALB 2.0 Advanced Load Balancing for Microsoft Lync 2010
Accelerating Load Balancer Extreme (ALB-X)3.42.1 (Build 1475)
KEMP TechnologiesLoadMaster7.1-18b LoadMaster Deployment Guide
Loadbalancer.orgEnterprise, Enterprise MAX, Enterprise 10Gv6.18, v7.4.1 Microsoft Lync 2010 Deployment Guide
RadwareAppDirectorv.2.14.03 Radware AppDirector optimizing the delivery of Microsoft Lync 2010
Alteonv.28.1.0 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 msucoip@microsoft.com.

 

Software load balancers for Lync Server

Listed below are software load balancers that have been tested by the vendor and reviewed by Microsoft to meet Lync Server 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

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
HAProxy TechnologiesALOHA Load-Balancer Virtual Appliance5.5 Deployment guide
jetNEXUSAccelerating Load Balancer (ALB)ALB 2.0 Advanced Load Balancing for Microsoft Lync 2010
Accelerating Load Balancer Extreme (ALB-X)3.42.1 (Build 1475)
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 msucoip@microsoft.com.

 

Reverse proxies

This section lists the server reverse proxy products that have completed solution testing with Lync Server. While any reverse proxy is expected to work with Lync Server, the reverse proxies listed below have completed extensive testing and are posted with detailed deployment white papers to assist in configuration.

We recommend 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.

Qualified for Lync 2013

VendorQualified ProductSoftware Version TestedVendor's Lync Page
A10 NetworksThunder and AX Series2.7.1 Deployment Guides
F5 NetworksBig-IP LTM11.0 - 11.4.1 Configuring Reverse Proxy Access to Microsoft Lync Using a Big-IP LTM V.11
CitrixNetScaler10.5 Microsoft and Citrix NetScaler
KEMP TechnologiesLoadMaster7.1-18b LoadMaster Deployment Guide
MicrosoftInternet Information Services Application Request Routing  (IIS ARR)v2.5 Using IIS ARR as a Reverse Proxy for Lync Server 2013
MicrosoftForefront Threat Management Gateway (TMG) **2010 Setting up Reverse Proxy Servers with TMG
MicrosoftWeb Application ProxyWindows Server 2012 R2 Configuring the Windows Server 2012 Web Application Proxy as a Reverse Proxy for Lync Server

** In November, 2012, Microsoft ceased license sales of Forefront Threat Management Gateway 2010, or TMG. TMG is still a fully supported product, and is still available for sale on appliances sold by third parties.

 

Qualified for Lync 2010

VendorQualified ProductSoftware Version TestedVendor's Lync Page
MicrosoftInternet Information Services Application Request Routing  (IIS ARR)v2.5 Using IIS ARR as a Reverse Proxy for Lync Server 2013
MicrosoftForefront Threat Management Gateway (TMG) **2010 Setting up Reverse Proxy Servers with TMG

** In November, 2012, Microsoft ceased license sales of Forefront Threat Management Gateway 2010, or TMG. TMG is still a fully supported product, and is still available for sale on appliances sold by third parties.


Virtual Desktop Infrastructure for Lync Server 2013

Listed below are the VDI Partner platforms and client hardware platforms which are supported with Lync Server 2013. In order for a given configuration to be supported, both the VDI partner platform and the client hardware platform need to be supported.

About VDI

With the release of Lync Server 2013, Microsoft has worked closely with multiple partners to bring enterprise-grade audio and video communication support using Lync to thin clients running in a Virtual Desktop Infrastructure (VDI) environment. This is done through a combination of the Lync rich client running in the datacenter along with a Lync VDI plug-in running in the local client hardware. The solution is extensible and designed to work on both VDI Partner platforms such as VMware and client hardware platforms such as Dell Wyse and HP.

See also:

VDI environments

The following table lists the VDI partners and their products which have been tested with the Lync 2013 VDI plug-in. 

VendorTested ProductLocal ClientRemote ServerProtocol
CitrixXenDesktopCitrix Receiver 4.1.02XenDesktop Virtual Delivery Agent 7.1ICA

http://www.citrix.com/products/xendesktop/overview.html

Note: Citrix VDI solution for Lync Plugin is currently approved for use with Win7 client OS. Testing on Win8 and 8.1 is in progress. For the best experience, Microsoft recommends updating to the latest available Lync cumulative update.

MicrosoftMicrosoft Remote Desktop ServicesRemote Desktop Client*Remote Desktop ServerRDP

http://technet.microsoft.com/en-us/windowsserver/ee236407.aspx

* mstsc.exe only.  The Windows 8 App "Remote Desktop" is not supported

VMwareHorizon View 5.2Horizon View Client 5.2Horizon view AgentPCOIP

http://www.vmware.com/solutions/desktop/business-process-desktop/partners.html

 

Client hardware platforms

The Lync 2013 VDI Plug-in is required to be installed on the local machine in combination with the VDI Partner's local client. The Plug-in will use the local machine's processing, memory and network resources to provide an optimal media experience for the end-user. 

The Lync 2013 VDI Plug-in is available in 32-bit and 64-bit versions and is supported on clients meeting following requirements:

Supported operating systems:

  • Windows 7 Service Pack 1
  • Windows 8
  • Windows Embedded Standard 7

Minimum system requirements:

  • CPU: 1.5 GHz processor
  • Memory: 2 gigabyte (GB) of RAM
  • Space required: 32 bit: ~700 MB, 64 bit: ~900 MB

Clients which do not meet the requirements above are not supported by Microsoft.

Following are the specific VDI client terminals tested by the VDI client manufacturers and validated by Microsoft. 

VendorTested terminals
Dell WyseR90L7
X90m7
Z90D7
HPt510
t5740e
t610

 

For additional information about specific thin clients, please contact the client hardware manufacturer.