Microsoft Communications Server “14” Interoperability: Voice, Video, Conferencing, IM, and PresenceFrançois DorémieuxPrincipal Program ManagerMicrosoft Corporation

SESSION CODE: UNC321

Complete an evaluation on CommNet and enter to win!

Session objectivesUnderstand Microsoft’s strategy and investments on UC interoperability

Assessing the importance of interoperabilitySharing our guiding principles and activitiesDescribing current achievements and highlighting new capabilities

Not a detailed technical session – focused more on strategy and capabilities (what you can do) than implementation (how). For detailed implementation discussion:

UNC08-INT - Microsoft Communications Server "14" Interoperability Q&AToday at 13:15, room 352

In the old world, your PBX's proprietary functions were what added the value […]. You weren't free to change out or mix-and-match systems because lack of interoperability resulted in vendor lock-in.

Today, the opportunity for value-add is in making an enterprise communications system the best and most effective broker among devices, networks and systems[…]. A vendor whose platform can't do this brokering […] — that vendor is the enemy of enterprises […].

— Eric Krapf, Enterprise Connect (formerly VoiceCon), Editor, No-Jitter, May 10, 2010

If you want to go fast, go alone. If you want to go far, go together.

– African proverb

Interoperability in the time of Software-based UCThe end of the mainframe era

Microsoft UC InteroperabilityAgenda

The challenges of interoperability Microsoft UC: interoperability by design

Principles and processesEngagements and programsAnnouncing: Unified Communications Interoperability Forum

Microsoft Communications Server: interoperability in actionRich and reachPresence and instant messagingAudio-VideoTelephony and conferencing

Conclusion and Q&A

Microsoft UC InteroperabilityAgenda

The challenges of interoperability Microsoft UC: interoperability by design

Principles and processesEngagements and programsAnnouncing: Unified Communications Interoperability Forum

Microsoft Communications Server: interoperability in actionRich and reachPresence and instant messagingAudio-VideoTelephony and conferencing

Conclusion and Q&A

Ex-post interop with in-place assets: a hard battle Closed by design

Vertical (mainframe) lock-inUndocumented proprietary protocols and API

Installed base – hard to teach the old dog new tricksProactively building interop in future products: technological and process challenges

Lots of “standards”, even more interpretations; same vendors who like proprietary lock-in use standards as an excuse to stay locked-inNo strong multilateral process toward interoperability, dispersed industry efforts

Still customers and industry need interopEnabler for migration to new capabilities and economicsMarket requirements and ethical grounds should drive vendorsOpportunities for industry leadership

The Challenge of InteroperabilityInterop is the right thing to do – but it’s not easy

My arbitrary taxonomyInteroperable: 1+1 = 1.5

Distinct solutions that work together with basic capabilities“Lowest common ground”, mostly ex-postEx: traditional PBX interop with QSIG or SIP

Integrated: 1+1 = 3Solutions deeply weaved to enhance each otherTypically built to be integrated (by design), using common platformEx: contact center and CRM integration

Unified, Converged: 1 platform for most/all of your needsPlatform that can support “all” you need in a deeply integrated mannerFully extensible for further integration, still able to interop

The Challenge of InteroperabilityWhat does “Interop” mean anyway?

Microsoft UC InteroperabilityAgenda

The challenges of interoperability Microsoft UC: interoperability by design

Principles and processesEngagements and programsAnnouncing: Unified Communications Interoperability Forum

Microsoft Communications Server: interoperability in actionRich and reachPresence and instant messagingAudio-VideoTelephony and conferencing

Conclusion and Q&A

Listen to customersIdentify and prioritize key interoperability scenarios based on customer needs and feedback

Make interoperability an explicit part of the development processPrioritize interoperability scenarios as core product features – define ship criteria and align test plansDeliver comprehensive, natural integration of all Microsoft UC modalities within business processesDeliver capabilities across multiple client platforms – rich and reach

Engage the industryParticipate in initiatives that detail how to apply standards to specific technical scenariosEncourage development of solutions that are interoperable by design

Harbor a healthy partner ecosystemProvide protocol documentationEnable platform extensibility via APIsEnable, support and encourage partners

Microsoft UC: Interoperability by DesignPrinciples and processes

Normative reference for every protocol used to send packets over the wire between Communicator and other Microsoft Products, in conformance with the Interoperability PrinciplesPublished on MSDN, e.g.

http://msdn.microsoft.com/en-us/library/cc307432.aspx

35 documents, 1800+ pages of documentationFirst published April 4, 2008; latest release April 30, 2010 (incl. CS “14” specific material)

Forums and other support processes in place

Microsoft UC: Interoperability by DesignProtocol documentation

Active participation in and support of multiple forumsSIPForum, SIPit, IETF Martini workgroup, etc

Working towards industry interoperability specificationsEx: SIPconnect 1.1 (SIP trunking)

Workgroup established 2008[T]he industry support for SIPconnect 1.1 is impressive […]. Avaya, Broadsoft, CableLabs, Cbeyond, Microsoft and Siemens all submitted content. SIPconnect 1.1 will feature a variety of enhancements, but a few items you can expect to be addressed are improved security practices, clarity around user identity, TCP vs UDP SIP, and media standards. – Chris Gatch, CTO, Cbeyond

Microsoft UC: Interoperability by DesignIndustry engagements

Testing and qualification of third party solutions for interoperability with Microsoft UCIndependent testing by third party labs based on standards based open documentationRich scope of program

SIP-PSTN gatewaysDirect SIP with IP-PBXSIP trunking with carriers

Microsoft UC: Interoperability by DesignOpen Interoperability Program – http://technet.microsoft.com/ucoip

With the Open Interoperability Program, you have a extremely broad choice of voice interoperability solutions

47 SIP-PSTN gateways qualified or supported for OCS 2007 or OCS 2007 R2Aculab, Audiocodes, Avaya, Cisco, Dialogic, Ferrari Electronic, Media5, NEC, NET, Nuera Communications, Quintum, Tango Networks, Teldat, Vegastream

18 IP-PBX qualified or supported for OCS 2007 or OCS 2007 R2Aastra, Altigen, Avaya, Cisco, Huawei, Innovaphone, Mitel, Nortel, Seltatel, Siemens

14 Service providers’ SIP trunking service qualified for OCS 2007 R2AT&T, BT, Global Crossing, IntelePeer, Interoute, IP Directions, Jajah (Telefónica), Orange Business Services, Sotel, Sprint, Swisscom, Telenor, ThinkTel, Verizon

Even more coming soon!Using existing OIP solutions with CS “14”

Will work; supported at level qualifiedWe intend to re-qualify most solutions for CS “14”; may require firmware updates

Microsoft UC: Interoperability by DesignOpen Interoperability Program – http://technet.microsoft.com/ucoip

Ensures optimal quality of experience for users, empowers a competitive horizontal business modelMore than 50 devices “optimized for Communicator” from 12 vendors

Audio USB peripherals:Headsets, handsets, speakerphonesWired or wirelessDesktop or nomadicWide price range

USB webcamsIncl. High Definition

Standalone IP phonesPCs

Microsoft UC: Interoperability by DesignOptimized devices – http://technet.microsoft.com/en-us/bb970310.aspx

Interoperability beyond the RFCsA new industry effort is needed to make sense of increasing complexity

UC products need to support multiple protocols today

XMPP, SIMPLE for IM/P and H.323, SIP, XMPP/Jingle for Voice & Video“Stovepipe” organizations focused on a single protocol leave much of UC uncovered

UC interoperability requires a robust testing and certification program

UC complexity makes test suites difficult (and expensive) to develop“Self-certification” and voluntary programs provide limited value to vendors and customers

Unified Communications Interoperability Forum (UCIF)

ANNOUNCING

Announcing the newly formed UCIFNon-profit vendor alliance Open to all UC hardware, software vendors, service providers and network operators (NOT an exclusive club)Founders:

HP, Juniper Networks, LifeSize/Logitech, Microsoft and PolycomContributors:

Acme Packet, Aspect, AudioCodes, Broadcom, Brocade, Broadsoft, ClearOne, Jabra, Plantronics, RADVISION, Siemens Enterprise Communications and Teliris

Formed in April 2010

Announcing the newly formed UCIFMicrosoft is one of the founding members

UCIF’s mission: enable interoperability of UC scenarios based on existing standardsNOT another standards bodyInteroperability and investment protection for customers is the ultimate goalUCIF is platform agnostic UCIF will define test plans, advance testing protocols and facilitate verification testing for member’s UC solutions and scenarios

Certification markUnique to the UCIF, a certification mark will be developed for use by member vendors, as a signal to customers that a scenario or solution meets the UCIF interoperability requirements

Announcing the newly formed UCIFAimed at interoperability of UC scenarios

Microsoft UC InteroperabilityAgenda

The challenges of interoperability Microsoft UC: interoperability by design

Principles and processesEngagements and programsAnnouncing: Unified Communications Interoperability Forum

Microsoft Communications Server: interoperability in actionRich and reachPresence and instant messagingAudio-VideoTelephony and conferencing

Conclusion and Q&A

Infrastructure:64 bits OS, Windows Server 2008, SQL Server 2008CDR, monitoring, archiving improvementsSimplified topologies, more roles but less serversImprovement of edge rolesCWA: deskshare, call-me-back

Collaboration:PSTN audio conferencing bridge with PIN (incl. strong authentication)HD and VGA videoPersistent group chatP2P and multiparty RDP desk sharingPresence federation with Cisco, IBMXMPP gatewayVideo interop (HP, Polycom, Tandberg…)

Voice/telephony:Team calls, hunt groups, basic ACD with MoH and IVRBoss-Admin scenarios, call delegation, admin and attendant consoleImproved voice quality:

Faster call setup, improved media stack, lower latency, standard CNGG.711 to Mediation Server on LANMedia resiliency on signaling loss

More connectivity options:Direct SIP to IP-PBXSIP trunking to carriers

Mobility:Fixed mobile convergence: single number, single voice mailPerformance improvementsSupport for variety of device platforms

Platform:First platform w/ Signaling, Media and SpeechCode Gallery: webservice built on top of the managed API.Workflow integration

Main investments in OCS 2007 R2With main interop investments in yellow

Capabilities across desktop platformsRich clients for Windows and MacOS

Office for Mac 2011 will continue to support OCS/CS “14”Silverlight/browser based reach clients (browsers and platforms supported by Silverlight)Third party clients for Linux (Pidgin plugin, HW phones…)

Communicator Mobile on a variety of device platformsWindows MobileNokia S40, S60 (released May 2010)

http://www.prnewswire.com/news-releases/microsoft-communicator-mobile-for-nokia-debuts-92841594.html

Motorola RAZR v3xxThird party clients for RIM, iPhone (e.g. Modality’s iDialog)

Communications Server: Interoperability in ActionRich and reach

Collaborate, even with people who don’t have communicator

If you can view a web page, you can join a meetingMac and Linux users can organize and/or present meetingsEasily go from a phone call to rich interaction online

Communications Server: Interoperability in ActionRich and reach – new for CS “14”

Public IM connectivityEnables IM and Presence interoperability (federation) with public IM cloudsIntroduced and offered by Microsoft since LCS 2005 SP1Currently available for federation of Communications Server with AOL, Windows Live Messenger, Yahoo

AOL and Windows Live Messenger federation: customers with Standard CAL in place qualify for federation with AOL and WLM without additional licensing requirementsYahoo federation requires the Office Communications Server Public IM Connectivity (PIC) per user subscription license; PIC license is sold separately on a per-user, per-month basis as a Microsoft service

For ordering and provisioninghttp://www.microsoft.com/communicationsserver/en/us/public-im-connectivity.aspx

Communications Server: Interoperability in ActionPresence and IM

Interdomain presence federation with third-party solutions:Cisco Unified Presence Server 7.x (released 3Q08)

http://www.cisco.com/en/US/docs/voice_ip_comm/cups/7_0/english/integration_notes/federation/Overview_chapter.pdf

IBM Sametime 8.0.2 GW with HF3 (released 4Q09)http://www-01.ibm.com/support/docview.wss?uid=swg21393043

Microsoft OCS XMPP gateway (initial release for OCS 2007 R2 in 4Q09)Available at no additional licensing costProvides Presence and IM with XMPP networks: Jabber 5.4, GoogleTalkhttp://communicationsserverteam.com/archive/2009/10/02/620.aspxhttp://communicationsserverteam.com/archive/2009/10/01/588.aspxRole supported in CS “14”, additional features and capabilities under consideration

Communications Server: Interoperability in ActionPresence and IM

New capabilities for presence interoperability in CS “14”

ANNOUNCING

Communications Server: Interoperability in ActionPresence – new for CS “14” (available after RTM)

CS “14” introduces easier management of presence by third parties – GET and SETEnables PBX and third party infrastructure to publish presence states to CS “14” (as well as to retrieve presence from CS “14”)Facilitates an integrated presence experienceUses standard SIP verbs like SUBSCRIBE and PUBLISH, and PIDF (RFC 3863) formatSuperior to CSTA:

More presence states than “in-a-call”No feature trade-offSimple topologiesMultiple contributors and/or subscribers

IP-PBX CS14

Mobile Operator

GET-presence&

SET-Presence

Video room interoperabilityCommitted roadmap with HP, PolycomHad close interop partnership with Tandberg; future interop dependent on Cisco Three phases

Now: basic registration from gateway or endpoint with “lowest common denominator” P2P interopSoon: richer capabilities, enabling firewall traversal and secure callsW14 roadmap: seamless interop with video room endpoints acting as fully capable, high quality CS endpoints

Microsoft licensed technology to partners, provided all documentation and supportVideoconferencing Interoperability White Paper

http://technet.microsoft.com/en-us/office/ocs/cc836454.aspx

Communications Server: Interoperability in ActionAudio-Video

Basic P2P calls between OC and partner solution:

SIP registrationPresence publishingH.263 interopNTLM authenticationWideband audioSecure signaling (TLS)

Communications Server: Video InteroperabilityRoadmap

Now Secure calls across firewalls between OC and partner solution:

Firewall transversal (ICE v19)Secure calls (SRTP)

SoonRich, high quality multiparty calls between OC and partner solution:

RTVideo – CIF, VGA, HDCCCP for AVMCU support

W14

Registrar

OCS R2 Pool (s)

MCUs

FederatedCompany

Edge Servers

ISDN and H.323

Traditional Video Conference Endpoints

SIP Video Conference Endpoints

Gateway

[MS-SIP]

TLSICE v19

CCCP

RTVideo

UC Video endpoints

Meeting Console R2 Communicator

H.263 Video

SRTP

Registrar

Communications Server: Video InteroperabilityInterop architecture

Registrar

OCS R2 Pool (s)

MCUs

FederatedCompany

Edge Servers

ISDN and H.323

HDX

RMX

UC Video endpoints

Meeting Console R2 Communicator

Registrar

Virtual Rooms

Legacy + telepresence

Communications Server: Video InteroperabilityInterop architecture – Polycom

Communications Server: Video InteroperabilityInterop support – Polycom

HDX RMXICE/SRTP Mid 2010 Mid 2010RTV End 2010 End 2010CCCP NA NA

Polycom Unified Communications for Microsoft Office Communications Server 2007 R2 Software Download: http://www.polycom.com/forms/solutions_sw_dl_thankyou.html

Committed roadmap

Registrar

OCS R2 Pool (s)

MCUs

FederatedCompany

Edge Servers

ISDN and H.323

MXP, Codian. telepresence

E20

UC Video endpoints

Meeting Console R2 Communicator

Registrar

VCSor VGW

Communications Server: Video InteroperabilityInterop architecture – TANDBERG

Media interoperability between Communications Server and Windows Live Messenger

ANNOUNCING

Media federation between CS “14” and nextgen WLM (W4)

P2P wideband audio and HD videoCustomers with Standard CAL in place qualify for media federation with WLM without additional licensing requirementsNotes:

Requires Communicator “14” and WLM W4 (next gen)P2P only, no encryption or data collaboration at this time

Communications Server: Interoperability in ActionAudio-Video interoperability between CS and WLM

Media by-pass of Mediation Server with select IP-PBXCan greatly simplify interop topologies

New capabilities for “CS” 14 gatewaysBasic gateways

Media by-pass of Mediation Server (i.e. direct media Communicator to GW)SRTP, media quality requirementsTypically software upgrade for R2 qualified gateways

Survivable Branch AppliancesIncl. support for SIP trunking

New number formatting capabilitiesRemoves the need for post-formatting through a GW or IP-PBXSimplifies interop with IP-PBX (less/no new rules needed) and PSTN access providers

Communications Server: Interoperability in ActionVoice/telephony – new for CS “14”

PBX end-points

OCS Pool

OCS end-points

MediationServer

MediaSignaling

Communications Server: PBX InteroperabilityInterop via gateway in R2

PBX TDM

OIPMedia

Gateway

PBX end-points

CS14 Poolwith MS

role

CS14 end-points

MediaSignaling

Communications Server: PBX InteroperabilityInterop via gateway in CS “14” with media bypass

PBX TDM

W14 OIPMedia

Gateway

OIPqualifiedIP-PBX

PBX end-points

OCS Pool

OCS end-points

MediationServer

MediaSignaling

Communications Server: PBX InteroperabilityInterop via Direct SIP to IP-PBX in R2

OIPqualified

IP-PBXcapable of

bypass

PBX end-points

CS14 Poolwith

MS role

CS14 end-points

MediaSignaling

Communications Server: PBX InteroperabilityInterop via Direct SIP to IP-PBX in CS “14” with media bypass

Use CS “14” to replace any or all PBX and create a complete UC solution

Example customers: Sprint, Lionbridge, Royal Dutch ShellWhat: all users migrated from PBX to Communications Server (typically with DID), PBX retiredWhy: greenfields, replacement of depreciated/old PBX, strategic transformation to UCHow: interoperability with existing PBX/IP-PBX during migration and coexistence: OIP Direct SIP, GWPros: simplicity; economicsCons: less proven solution

Communications Server: Interoperability in ActionVoice deployments: CS “14” gives you choices (1/3)

Bob Alice Bob Alice

PSTN

Use CS “14” to enhance (complement/overlay) the PBX

Example customer: AT KearneyWhat: deploy Enterprise Voice in addition to continuing to use PBXWhy: customer not ready to take PBX phones away but wants to enjoy benefits of UCHow: option to forward PBX line to Communicator or (less commonly) simultaneous ringing; OIP interoperability; SET-presencePros: less drastic change; may facilitate user experience transitionCons: less simple; added DID; potentially less economic advantage

Communications Server: Interoperability in ActionVoice deployments: CS “14” gives you choices (2/3)

Bob’s deskDID1

Bob anywhereDID2

PSTN

DID1 forwardedto DID2

Use CS “14” to add IM, presence and conferencing to the PBX

Example customer: IntelWhat: deploy CS for everything but Enterprise Voice; voice = PBXWhy: customer not ready for VoIP or wants to stay on current solution only but wants to save with CS "14" audio- and web- conferencingHow: new “Join from” feature automatically rings PBX phone; OIP interoperability; SET-presencePros: start saving with audio-conferencing, have option to easily add Enterprise Voice in futureCons: does not provide full UC capabilities such as remote usage

Communications Server: Interoperability in ActionVoice deployments: CS “14” gives you choices (3/3)

Microsoft UC InteroperabilityAgenda

The challenges of interoperability Microsoft UC: interoperability by design

Principles and processesEngagements and programsAnnouncing: Unified Communications Interoperability Forum

Microsoft Communications Server: interoperability in actionRich and reachPresence and instant messagingAudio-VideoTelephony and conferencing

Conclusion and Q&A

Summary / ConclusionMicrosoft’s strategy and investments on UC interoperability

Interoperability is core to Microsoft’s approachInterop by designUCIF

We interop today to fulfill (virtually) all your needsPresence and IM; Audio-video; Telephony

CS “14” makes interop easierReach scenarios; more video interop; easier IP-PBX interop topologies…

For detailed implementation discussions, white board, Q&A:

UNC08-INT - Microsoft Communications Server "14" Interoperability Q&AToday at 13:15, room 352

Related SessionsNo such thing as too much UC!

Wednesday11:45 UNC321 CS “14”: Interoperability: Voice, Video, Conferencing, IM, & Presence

13:15 UNC08-INT Microsoft Communications Server "14" Interoperability Q&A

Thursday13:15 UNC401

Advanced SIP-Based Solutions Built on the Microsoft Unified Communications Managed API 3.0 and Microsoft Communications Server “14”

15:00 UNC10-INT

Microsoft Unified Communications Managed API 3.0: Sample Demo Fest

You are here

Unified Communications Track Call to Action!Learn More!

View Related Unified Communications (UNC) Content at TechEd/after at TechEd Online

Visit microsoft.com/communicationsserver for more Communications Server “14” product information

Find additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on Twitter

Check out Microsoft TechNet resources for Communications Server and Exchange Server

Visit additional Exchange 2010 IT Professional-focused content:Partner Link or Customer Link (Name: ExPro Pword: EHLO!world)

Try It Out!Exchange 2010 SP1 Beta download is now available from the download center!

Complete an evaluation on CommNet and enter to win!

Resources

www.microsoft.com/teched

Sessions On-Demand & Community Microsoft Certification & Training Resources

Resources for IT Professionals Resources for Developers

www.microsoft.com/learning

http://microsoft.com/technet http://microsoft.com/msdn

Learning

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

JUNE 7-10, 2010 | NEW ORLEANS, LA