Transcript Hybrid Lync 2013 Preview About this Presentation Capabilities are subject to change Packaging and licensing have not yet been determined Any screen captures or.

Hybrid
00
Lync 2013 Preview
About this Presentation
Capabilities are subject to change
Packaging and licensing have not yet been determined
Any screen captures or concepts shown are pre-release and for illustration purposes only
Disclaimer
This presentation contains preliminary information that may be changed substantially prior to final commercial release of the software described herein.
The information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of the 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 presented after the date of the presentation. This presentation is for informational purposes only.
MICROSOFT MAKES NO WARRANTIES, EXPRESSED, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this presentation. Except as expressly
provided in any written license agreement from Microsoft, the furnishing of this information does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.
OIP page
OIP page
Client-Side & Server-Side Integration
Lync user
RCC Integration
CSTA Gateway
PABX phone
user
Lync
PABX
Gateway Integration
PABX phone
user
Lync user
Lync
Gateway
Legacy
SIP
Protocol
Client Side Integration
PABX
Lync User
Lync
Lync user
Lync
3rd Party Plug-in
PABX
Client API
Direct SIP Integration
PABX phone user
Direct SIP
PABX
Client Side Integration
Lync User
Lync
3rd Party Plug-in
PABX
Client API
Lync user
Lync
Direct SIP Integration
PABX phone
user
Direct SIP
PABX
Gateway Integration
PABX phone
user
Lync user
Lync
Gateway
Legacy
SIP
Protocol
PABX
Lync user
RCC Integration
CSTA Gateway
Lync
PABX phone
user
PABX
What You Get
What’s Missing
► Escalate to Lync multi-party
audioconf (Multi party just on
your phone is still possible)
► Receive calls at home, on the
road(voice always on
Deskphone)
► Synchronize Do Not Disturb
► Escalate inbound call to
desktop sharing
► No delegation
Direct SIP to IP-PABX with media bypass
OIP
qualified
IP-PABX
capable of
bypass
Lync pool
with
MS role
PABX end-points
Media
Signaling
Lync end-points
What it is and benefits
New Lync 2013 features with Interop implications:
Using Pool FQDN instead of individual machine FQDN for cert & connection checking.
Failover Routing and four second socket connection timer from Mediation.
DNS Load Balancing Support outbound from Mediation to SIP peer.
Dual Stack IPv4/IPv6
Unsupported: Bypass on v6 & Standalone v6 on Mediation egress
Passing Referred-By and History-Info from Mediation to Peer (dropped the other way)
Resiliency enhancements for trunking – bidirectional OPTIONS, peer routing to backup
pools
Gateway /
SBA
SBC
Pool FQDN for Cert
Yes
N/A
Fail-over Routing
Yes
N/A
DNS LB Support
Yes
N/A
IPv4/IPv6 Support
Optional Optional
SIP Header Support
Yes
Yes
M:N Routing
Yes
Yes
IP-PBX
Optional
Optional
Optional
Optional
Yes
Yes
SIP
E911 SP
Trunk
Optional
N/A
Yes
Yes
Optional
N/A
Optional Optional
Yes
Optional
Yes
Yes
Supported: Lync 2010 Mediation with Lync 2013 pool
Functional at 2010 level of capability
Great for customers upgrading to Lync Server 2013 with minimal
impact
2013 Mediation needs to interoperate with 2013 qualified
infrastructure
Timing: When will X be qualified with Lync
2013?
Interop testing starts when the product is completed
RCC interconnects with a legacy PBX
Provides click-to-call using PABX handset & informs binary phone presence in Lync
Does NOT work with Enterprise Voice – client can be either RCC or EV
Interop with the PABX uses ECMA standard TR/87 for CSTA over SIP
RCC is still supported in Lync 2010 and Lync 2013
P2P video calling for RCC-enabled users supported as of March 2012 update
Split Audio / Video continues to remain deprecated for future
There is no interop program for RCC (and there never has been….)
The protocol is stable with little to no investment on either PABX or Lync side
Generally available from major PABX manufacturers through their presence engines
RCC is a legacy feature that ties the customer to disadvantageous PABX economics
SBCs recent addition to UCOIP qualification
ACME Packet, AudioCodes, NET/Sonus
Equivalent testing to Gateways & IP-PABXs
Useful when customers are:
Already is using an Enterprise SBC (typically ACME) for multivendor protocol interoperability
SIP Trunking deployments to support bypass.
Not qualified for firewall traversal / edge
Lync edge offers support for greater range of modalities
Exchange 2013 Preview
Lync 2013 Preview