Long tailed migration and coexistence, no rip and replace - work with what enterprises have today
Well defined, documented scenarios that persist across releases to protect customer investments
From Planning through Spec, Dev, Test, Doc and Sustained Engineering
Industry Alliances and Workgroups – UCI Forum, OVCC, ATIS, IETF, ETSI, and 802.11
Protocol documentation (all client-server protocols) – Office Protocol Docs
Scale programs – UC Open Interoperability Program technet.microsoft.com/UCOIP
Phones, Endpoints, Handsets, Wireless clients
Video Teleconferencing (VTCs), Multipoint Control Units (MCUs), Gateways
Network, PBX, Gateways, Branch Survivability, Session Border Controllers
SIP Trunking, E911 Routing
Products qualified with Lync Online D
Ensuring that customers have seamless experiences with
setup, support, and use of qualified products & services
snom 821 UC Edition
HP 4110
snom 370 UC Edition Polycom KIRK DECT Wireless
Polycom CX500
HP 4120
snom 300 UC Edition
$100+
USB
Audio &
Video
Devices
Polycom CX600
Aastra 6721 iP
$150-200
Aastra 6725 iP
$200-300
Polycom CX3000
$850+
Packet on one side, different packet on the other
Gateways with Lync software for survivability in case of WAN outage
https://blogs.technet.com/b/lync/archive/2013/05/23/lync-skype-connectivity-available-today.aspx
Home Server
Mediation Server
Lync Server 2013
Lync 2013
Lync 2013
Supported
Lync Server 2013 –
Lync Server 2010
Lync 2013
Lync 2010
Supported
Lync 2010
Lync 2013
Supported
Lync Server 2013 –
OCS 2007 R2
Lync 2013
OCS 2007 R2
Supported
OCS 2007 R2
Lync 2013
Not Supported
Lync 2010 Pool
Lync 2013 Preview
Pool
Lync 2010 SBA
Supported
Supported *
Lync 2013 SBA
Not Supported
Supported
Mediation Server
Next Hop Server
Home Server
Lync Server 2013
Lync 2013
Lync 2013
Lync 2013
Supported
Lync Server 2013 –
Lync Server 2010
Lync 2013
Lync 2013
Lync 2010
Supported
Lync 2010
Lync 2010
Lync 2013
Supported
Lync Server 2013 –
OCS 2007 R2
Lync 2013
Lync 2013
OCS 2007 R2
Supported
OCS 2007 R2
OCS 2007 R2
Lync 2013
Supported
* Contents from 2010 SBA will write monitoring and archiving contents to Lync 2010 store
** Assumed certified Gateways for the release of MS shown in the tables above
OIP
qualified
IP-PBX
capable of
bypass
Lync pool
with
MS role
PBX end-points
Lync end-points
Media
Signaling
PBX, IP-PBX, SBA or GW that supports bypass
All qualified SBA support bypass
GW qualified at Lync level support bypass
Unfortunately, few PBX or IP-PBX support bypass today (use SBC, GW if not)
Need a centralized media processing point
No bypass direct to endpoint (phone) is supported
Requires a media aggregation point, e.g. Cisco’s Media Termination Point (MTP)
Not the simplest of topics…
Skills on 2 systems; routing optimization; resiliency scenarios…
For complex topologies, recommend an experienced partner
CUCM + MTP1
Lync
Lync
8000
Lync
8500
WAN
MTP 2
Cisco
8501
Cisco
8001
Mediation
HQ Site
Branch
CUCM
Codec based
on CAC or RTT
Lync
G.711
Lync
client
Lync
client
WAN
ISR (MTP)
Cisco
phone
Cisco
Endpoint
Mediation
HQ Site
Branch
CUCM
Lync
Endpoint
Lync
Lync
Endpoint
WAN
G.711
ISR (MTP)
Cisco
phone
Cisco
Endpoint
Mediation
HQ Site
Branch
CUCM
Lync
Endpoint
Lync
Lync
Endpoint
WAN
G.711
ISR (MTP)
Cisco
phone
Cisco
Endpoint
Call stays up
Mediation
HQ Site
Atlanta Branch
Centralized IP-PBX, gateways in branches
IP-PBX in HQ
Handles signaling and call control centrally for all users
Local media resources in branch sites
Resources that support media connection but don’t provide autonomous call
control or external signaling
Often called “media gateways”
Ex: Cisco ISR with MTP – hardware or software
Lync supports media bypass in multiple sites
Bypass media to local media resource where client is located
Mediation always exchanges signaling with centralized instance
Possibly multiple regions with this topology
No need to define the gateways in advance
Define regions and sites in network topology
(same as CAC)
Define (virtual) media gateways in topology
builder
Associate representative IP address for site to each media gateway
Depending on specific IP-PBX requirements, different listening ports
Establish appropriate routing on both systems
Many, many ways to route…
PBX unaware of Lync client’s dynamic location, hence better outcome by routing
all calls from PBX to Lync to closest trunk
Lync 2010 Mobile
No Voice/Video over IP experience
Windows 8/RT Modern UI
Point-to-point video
Multi-party video (Gallery View)
Leveraging H.264 SVC
H.264 encoding within ARM chipsets
Lync 2013 Mobile
Point-to-point video
Multi-party video (single active speaker)
Leveraging H.264 SVC
H.264 encoding within ARM chipsets
Signaling
Peer-to-Peer Scenarios
Media
RTV
Option 1
Option 2
H.264
SVC
H.264
AVC
RTV
Option 1
Option 2
H.264 SVC / AVC
H.264
AVC
Signaling
Multiparty Scenarios
Media
H.264 SVC + RTV
RTV Client Joins
2013 Clients add
RTV Stream
Media
Transcoding
Media Relay
RTV
RTV
H.264 SVC
+ RTV
H.264 SVC
H.264 AVC
http://channel9.msdn.com/Events/TechEd
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn