Программа совместимости телефонных станций и медиа-шлюзов с сервером Lync
Open Interoperability Program - это совместная с производителями программа тестирования голосовых шлюзов и PBX при работе с Lync Server. Тут все просто, ниже приведен список протестированного оборудования с комментариями.
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" +S —"Qualified with SRTP & TLS"
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 Vendor |
Tested Product |
Supported Configuration |
Software Version Tested |
| Alcatel-Lucent |
OmniPCX Enterprise OXE |
Direct SIP |
R9.1 |
|
Configuration Notes:
- 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:
- 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.
- 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
- 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.
- Comfort noise generation is not supported. As a result, comfort noise is not played on Microsoft Lync.
- 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.
- 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.
|
| Avaya |
Communications Manager SIP Enablement Services |
Direct SIP |
4.0
5.1 |
|
Documentation: Integrating Microsoft Lync Server 2010 and Avaya Communications Manager S8300
Configuration Notes:
- 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.
- 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:
- 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.
- 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 software release.
- Monitoring 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 Lync.
- 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.
|
| Cisco |
Cisco Unified Communications Manager |
Direct SIP |
UCM 4.2 2000-4-4a
UCM 6.1.3.2000-1
UCM 7.1.3.10000-11 |
|
Configuration Notes:
- 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.
- 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:
- 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.
- 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.
|
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.
| Vendor |
Qualified Device |
Qualified Firmware |
| Audiocodes |
Mediant 1000 SBA |
SBA 1.1.8.21, GW 6.00A.033.005 |
| Audiocodes |
Mediant 2000 SBA |
SBA 1.1.8.21, GW 6.00A.033.005 |
| Dialogic |
DMG4000 SBA |
SU4, SIPControl 2.5,
Diva System Release 9.5 WIN |
| Ferrari electronic AG |
OfficeMaster SBA |
3.3 |
| HP |
Survivable Branch Communication zl Module |
SBA 1.0.5, GW: 3.0.3 |
| NET |
UX2000 |
SBA Version: 4.0.7577.0,
Gateway Version: 1.0.1.194 |
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.
For more information on SIP Trunking configurations with Lync Server, please see SIP Trunking from the Lync Technet Library
E-911 Service Providers qualified for Lync Server 2010
E911 Service Providers provide routing of emergency calls from Lync to the correct emergency dispatch center responsible for deploying emergency responders for the given client location, directly over SIP. An enterprise can use E-911 Services to provide location-aware emergency dialing support for both hard phones and soft phones.
Learn more about E911 Services here: Emergency Services (E9-1-1).
Оригинальная информация лежит тут
Tags: Lync Server | совместимость
|
