1. Interoperability with Lync
Microsoft Lync
11/12/2017
Interoperability with Lync
October 2013
Microsoft Corporation
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Voice Interoperability

3. Connecting to the PSTN Typical starting point at many Enterprises
PBX presence
PSTN Termination at the PBX
Existing numbering plan
Typical dialing habits that originate from the PBX
Class of Service that define the destinations users can call to to
Numbering Plan
Existing PBX
Class of Service
No premium
Local, National
International
No premium
Local, National
Existing Phone Handsets
4 digit Internal extensions
9 for an outside line
3 digits + extension for other locations
…..
Dialing Habits

4. Flexible deployment Remplacer Améliorer Ajouter
Remplacer le PBX avec une solution UC complète, comme Sprint, Colombian National Police & Lionbridge
Lync 2010 répond aux besoin de téléphonie des entreprises
Se connecter au réseau de téléphonie via un SIP Trunk ou une passerelle, et se connecter à n’importe quel PBX pendant la phase de transition
Remplacer
Améliorer le PBX avec UC, comme AT Kearney & Royal Dutch Shell
Le téléphone du PBX reste en place pendant la transistion, souvent avec de la sonnerie simultanée afin que le téléphone et Communicator sonnent en même temps.
Le Click-to-call est une option pour que les utilisateurs puissent initier ou recevoir des appels depuis un téléphone PBX (RCC) avec une perte de fonctionnalté, notamment en mobilité.
Améliorer
Ajouter la conférence, la messagerine instantanée et la présence au PBX, comme Intel
Audio, video, et les conférences web avec Lync ou audio et conférences depuis le téléphone PBX.  Nouvelle fonctionnalité “Joindre depuis” : appelle automatiquemetn le téléphone PBX.
Donne aux organisations l’option de facilement rajouter la voix dans le futur, mais ne fournit pas une solution UC complète avec les fonctionnalités telles que la voix en mobilité.
Ajouter
Deployment Scenario: Replace
This customer wants to be on top of the communication scene. In this case, you can recommend replacing the PBX for some or all employees with Lync Server The customer will get a complete UC solution that also meets enterprise telephony requirements. Lync Server 2010 can connect directly to the PSTN through a gateway or SIP trunking, and it can connect directly to any PBX during the transition phase. Employees can have their phone numbers moved to Lync Server 2010, or they can receive new ones.
Advantages:
Highly cost-effective to purchase and manage
Full and seamless UC experience
Disadvantages:
Purchase of new devices
Cultural change represented by the elimination of the PBX and the addition of new communication methods
Most Useful For:
Fastest ROI at locations with no or depreciated legacy infrastructure
All information workers, particularly mobile, collaborative, and new
Issues Resolved:
Replacing this organization’s PBX with full UC allows employees to:
Have remote access via the Internet
Click to join scheduled conferences
Click to join ad hoc conferences
Use PC audio and video
Click to call
Supplemental Materials (Case Studies):
Colombian National Police
Sprint
Lionbridge 
Winning in Voice: How Communications Server 14 Enables you to Replace, Enhance, or Add to Legacy Communication
Deployment Scenario: Enhance
“Our organization is not quite ready to transition to a fully unified communication plan. The problem is that since many of our workers are rarely in the office, they miss many of the calls that go directly to their desks. In our business, missed calls are missed opportunities.” In this instance, the customer would benefit from enhancing the current PBX system while leaving it in place. Reassure your customer that Lync Server 2010 will provide full UC in parallel to the existing PBX. Each employee can be given Lync, and Lync can be configured to ring whenever the PBX rings—letting the user receive calls on the road or in the home office.
Allows employees to use PC or phone for voice calls
Ongoing cost for PBX operations and maintenance
Presence of phone may slow user adoption of UC
Customers with non-depreciated equipment who also want to provide a best-of-breed UC solution
The customer can now begin to transition to a fully unified communication plan, while keeping the recently purchased PBX system in place. The parallel ringing of a PBX phone and Lync can result in fewer missed opportunities, and employees can stay better connected with each other and their customers. Similar to replacing a PBX system, enhancing a PBX system gives users:
Remote access via the Internet
PC audio and video
Supplemental Materials (Case Studies):
Royal Dutch Shell
AT Kearney
Deployment Scenario: Add
“In our organization of 12,000 national employees, we really like our PBX. We are, however, interested in adding presence, instant messaging, and conferencing to our system. We tend to do a lot of conferencing, but our conferencing costs are quite expensive. There has to be a way to use our PBX for voice and have a greater presence with each other and our customers.” Lync Server 2010 also provides options for this customer. When your customer wants to only add instant messaging and conferencing to the current PBX system, this is the best scenario. With Lync Server 2010, the customer can take advantage of audio, video, and Web conferencing with Lync, in addition to the features of the PBX offerings.
Provides an option to use the PC for the full audio, video, and Web conferencing experience
Eliminates costs for conferencing services
Provides rich roster controls
Architecture investments allow transition to Lync Server voice in the future
Ongoing costs for PBX operations and maintenance
No video conferencing while using phone
No remote phone capabilities
Limited ad hoc conferencing using Lync
Customers not ready to use Lync Server for voice, but who want to take advantage of Lync Server conferencing to lower costs and improve capabilities
Your customer can keep the existing PBX system, while adding Lync Server 2010 to save on conferencing costs. By adding Lync Server, the customer can:
Intel

5. Open Interoperability Program
Testing and qualification of third party solutions for interoperability with Microsoft UC
Independent testing by third party labs based on standards based open documentation
Rich scope of program
SIP-PSTN gateways
Direct SIP with IP-PBX
SIP trunking with carriers
Enhanced gateways:
Audio quality certification
REFER support
TLS/SRTP

6. Connecting to the PSTN via gateway
Use supported gateways (UCOIP)
A gateway is a physical device that connects two networks
A gateway translates signaling and media between Lync and the PSTN
Allows gateway to act as transcoding resource for calls between Lync Server 2013 and the PSTN
TDM Trunking benefits
More broadly understood
No WAN dependency
Local carrier choice
Branch resiliency

7. Connecting to the PBX Direct SIP
Only for supported PBX systems (UCOIP)
Interop between IP-PBX and Lync Server 2013
Provides voice capabilities between endpoints on either call control server
Allows endpoints on both sides to utilize features on the other call control server
Simplest method of interoperability, relying on standard SIP protocols
Via a Gateway
Use supported gateways (UCOIP)
Use gateway as intermediary in scenarios such as SIP to TDM/H323, or to nonqualified third-party call control
Allows gateway to act as transcoding resource for calls between Lync Server 2013 and third party

8. Lync Voice Interoperability : Sim-ring to Lync
PSTN
Tel : ;
ext =
1234
Sip
jassha @
microsoft .
com *
725 +
Lync Server
2013
Environment
Cisco Unified Call
Manager
Gateway

9. Site Topology Site A : Green Field Site B : Existing PBX
Telephony Lync
All features : IM/P/Audio/Video/Web/ Telephony
Site B : Existing PBX
User Profile 1 – Lync Telephony
Upstream Gateway
Sim/ring IP Phone & Lync
User Profile 2 – No Lync Telephony
Exisitng Office 365 Features : IM/P/Audio/Video/Web
Site C : Conference
Existing telephony
Existing Office 365 Features : IM/P/Audio/Video/Web
Site D : Legacy
No Office 365 or Lync needs
Migration to C, B or A
Lync On-prem user : IM/P/A/V/Web/Telephony
Lync Office 365 user : IM/P/A/V/Web
Phone (Aastra, Siemens, ….)

10. Video Interoperability

11. Video Interoperability Direction
H.264 Video Codec
Provides another codec for traditional VTC and Telepresence to connect
Partners will support H.264 and RTVideo in Lync 2013
RTVideo is required for Lync 2010
Video enhancements in signaling
To take advantage, partners need additions in signaling
Changes documented in Microsoft Office Protocols Documents
Unified Communications Interop Forum (UCIF)
Continue work in UCIF for interoperability
Partners will support same UCIF adopted UC mode 0 and UC mode 1

12. Lync 2013 Interoperability Use Cases
Qualified Systems
H.264 SVC UCConfig Mode 1 and RTV Support
Centralized Conferencing Control Protocol Support
Multiparty Gallery view and Face Detection with Smart Framing
Compatible Systems
Require updates to support changes in Lync signaling and transport protocol
RTV is required as H.263 codec support dropped
H.264 AVC or SVC interop possible
Standard Systems
No native Microsoft protocol or codec support
Need new gateway to provide signaling interop and H.264 and RTV video

13. Compatible Systems & Clients
TechReady 17
11/12/2017
Lync Server 2013 Interop
Signaling
Media
Peer-to-Peer Scenarios
Lync Clients
Lync Server
Qualified Gateway
Qualified Systems
Compatible Systems
Option 1
Option 2
Standard Systems
Option 1
Option 2
Qualified Systems
Compatible Systems & Clients
Standard Systems
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Polycom Interoperability - Lync 2013
Expanding Broadest Voice Solutions Qualified for Lync
Completing Lync 2013 Qualification across voice solutions
Advanced Lync voice capabilities on VVX platform with UC Software release
Lync 2013 Video Compatibility and Native Interoperability
RealPresence Video solutions compatibility
HDX, Group Series, RMX, DMA, and CSS
CX Device Family
CX5000 and CX7000 compatibility
New CX5100 and CX5500 for products
A Polycom Lync Room System for optimized collaboration experience

15. User Experience - Conference Room Integration
Native Integration
Enhanced Presence
Custom Status
Directory Search
Contact List Integration
Click-to-Call Video
Federation Support
Drag-and-Drop Conferencing
Wideband Audio
High Resolution Video
Unique Panoramic Video
Content Sharing

16. User Experience - Multiparty Conferencing
Lync AVMCU
Integrated video conferencing supporting up to 5 concurrent desktop video streams
Supports video across Lync clients and Polycom endpoints
Polycom Collaboration Server
Simultaneous integration capabilities with multiple protocols (H.323, SIP, ISDN) and products
Numerous layout options providing Continuous Presence
Supports CIF through HD resolutions with video up-scaling providing the highest resolution per endpoint
Wide-scale resiliency and load-balancing options
Supports video participants across standards-based H.323, SIP, and ISDN as well as Lync & Cisco TIP endpoints

17. Simple and Native Lync User Experience
From Lync side receiving or sending content to Video Rooms
Without CSS Solution
With CSS Solution

18. Architecture Contoso Microsoft Lync 2013 Environment
Polycom Room Systems and MCU integrated natively to Lync 2013
Webcam
MCU (RMX)
(MS-SIP;
MS-RTV, H264SVC)
VTC (HDX, GS rooms)
(MS-SIP;
MS-RTV, H264SVC)
Active Directory
Lync Pool
Front End Server
CSS
Lync Edge Server
GateKeeper (DMA)
Contoso
Other Third Party Room Systems none integrated natively to Lync 2013,
like H323 endpoints, can join the same conference directly via Polycom
Webcam
External VTC
External
HDX or GS Rooms
(H323, SIP; H264)
External
Remote Lync User
Signalling
Media
Authentication
Provisionning

19. Cisco Interoperability
Announced at Lync Conference
Make rich video more pervasive and accessible
Interoperability between Lync and Cisco VTCs
Video Interoperability Server forthcoming

20. Lync 2010 and Cisco VCS
A company is using a Lync system into their network to provide Microsoft Lync Clients on everyone’s desk to supply messaging, presence, audio video conferencing capabilities for all staff. Integrating this with their existing Video Network, which handles their video conferencing, provides the ability for video endpoints to make calls to and receive calls from Lync, and for Lync to see the presence of the video endpoints.

21. Lync 2013 and Cisco

22. 11/12/2017
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.