1. Microsoft® Lync™ Server 2010 The Voice Story Module 03
Microsoft Corporation
Slide Objective:
Notes:
Thank the Attendees, for the feedback and support
Topic of presentation
diving deeper into the voice
covering infrastructure investments in Lync Server 2010 to enable various voice scenarios

2. Session Objectives
Provide an overview of Microsoft® Lync™ Server 2010 voice investments
Understand Lync Server 2010 architectural components
Understand how Lync Server 2010 investments help lower Total Cost of Ownership (TCO)
Understand core routing changes and media bypass
Understand PBX interoperability options
Slide Objective: Introduce the objectives of this module
Notes:
Overview of all investments made in Lync Server 2010
Touch on architecture concepts
Changes in core infrastructure prospective (routing, number manipulation, media bypass)
Few screenshots to show simplicity in configuring complex concepts
Lowering TCO :
not by cost of acquisitions
by lower cost of operations
simplifying manageability of solution
abstracting complex scenarios to admins
Few slides to our commitment to interoperability, we don’t assume that you drop all you have today and adopt Lync Server 2010
Investment made to be able to be interoperable with existing systems

3. Agenda Voice Investments overview Voice Architecture overview
Media Bypass
Routing changes
Caller ID controls
Route translations
Analog Devices, Private line
Malicious Call Trace, Enhanced (E9-1-1)
Interoperability
Summary
Slide Objective: Discuss the agenda of this module
Notes:
Historical Big Picture.

4. Voice Investments Lync Server “OCS 2007 R2” “OCS 2007”
Branch Resiliency (SBA)
Datacenter Resiliency
Call Admission Control
Call park, Unassigned #
Topology changes
Media bypass
Enhanced for North America (NA)
Routing changes
Analog devices
Common area phones
Private line
Malicious Call Trace (MCT)
Larger device portfolio
“OCS 2007”
Single Number reach
Attendant Console
Delegation/TeamCall
Response Groups
Session Initiation Protocol (SIP) Trunking
Dial-in audio conferencing
Higher definition video
UC Workflow activities
“Anywhere Access”
IM and Rich Presence
Common voice features
Unified messaging
Audio and video conferencing
Desktop integration
Slide Objective: Discuss the new Voice Investments ad compare to past versions of OCS
Notes:
OCS 2007
Oct we released OCS 2007
Last Bill Gates software announcement
Quote” “In the next decade, sweeping technology innovations driven by the power of software will transform communications.” Bill Gates, October 16, 2007
OCS 2007 R2
Added: delegation, team call, response groups, dial in conferencing
Lync Server 2010
Big steps to address core infrastructure requirements
E9-1-1 – Note Location infrastructure can be used for various scenarios
Branch Resiliency
Datacenter resiliency
Voice has to always be available
Large investment – resilient for WAN and infrastructure failures
Call Control Features
Call Park
Unassigned numbers – reroute, announcement
Private Line for Executive scenarios for inbound calls
Bottom numbers
Percentage of features in Voice RFP scenarios covered by each products
In Lync Server 2010 small percentage number, but most difficult and required a significant investment
71%
17%
12%

5. Voice Investments Lync Server Topology changes Media bypass
Enhanced for North America (NA)
Routing changes
Analog devices
Common area phones
Private line
Malicious Call Trace (MCT)
This
Session
Slide Objective: Introduce the voice investments to be discussed in this module
Notes:
Describe what will be covered (on the screen)

6. Voice Topology: OCS 2007 R2 PSTN Circuit Packet UC Endpoints PIC XMPP
Archiving
Monitoring
PIC XMPP
MSN
Perimeter Network
UC Endpoints
AOL
Yahoo
Remote
Users
UC Pool
AD DNS
Front End
Back End
Federated
Businesses
Edge
Services
SIP Trunking
ExUM
Mediation Servers
PSTN
Media gateway
On-premise
Slide Objective: Discuss the Voice Topology of OCS 2007 R2
Notes:
Familiar 2007 Infrastructure
Point large number of Mediation servers requiring dedicated hardware
Describe Scenarios (Direct SIP, gateway, Direct SIP)
1:1 relationship
IP-PBX
Direct SIP
Circuit
Packet

7. Voice Topology: Lync Server 2010
Archiving
Monitoring
PIC XMPP
MSN
Perimeter Network
UC Endpoints
AOL
Yahoo
Remote
Users
UC Pool
AD DNS
Front End (incl. Mediation)
Back End
AV Conf.
Federated
Businesses
Edge
Services
SIP Trunking
Direct SIP
ExUM
Mediation Server
PSTN
IP-PBX
On-premise or online
Analog Devices
Slide Objective: Discuss the voice topology of Lync Server 2010
Notes:
New features from the top
Common Area Phone was missing in R2, New Phones (Aries)
More roles on Front End, more focus on deploying service than server roles
In Lync Server 2010 Mediation Service allows N:1 scenario note: next slide has more details , sip trucking we still require single Mediation server
Media Bypass – allows co-location with Front End
A-V Conferencing pool, potential for future deployments, can be shared amongst multiple FE pools, can be co-located on FE
SBA (new appliance)
Analog Devices, was possible in 2007 but we go one step further so we can manage them
Exchange On-Line (BPOS)
Private Line (Secondary DID for excess), Call Park and Outgoing DID Manipulation.
Media gateway / SBA
Circuit
Packet

8. Mediation Service Collocation
Multiple Gateways per Mediation Service
Lync Server 2010 allows for Gateways to be connected to the same Mediation Service (N:1)
Voice Routes point to a Gateway
Topology document used to find an appropriate Mediation Service, inserted into the routing path
Mediation Service uses the gateway fully qualified domain name (FQDN) in the Request-Uniform Resource Identifier (URI) to route to appropriate Gateway
Multiple Mediation servers in a pool
Allows a certified Internet Protocol Public Switched Telephone Network (IP-PSTN) gateway to load balance across a pool of Mediation Servers
OCS 2007 R2
Route
gateway
Route_US
LAX_GW
Route_EUR
DE_GW1
DE_GW2
Route_APAC
SYD_GW
Lync Server 2010
Route
gateway
Route_US
LAX_GW
Route_EUR
DE_GW1
DE_GW2
Route_APAC
SYD_GW
Slide Objective: Explain One of TCO examples
Notes:
In R2
Required One Mediation per Gateway/Trunk
Mediation server may be able to scale much better than a gateway or Trunk, you still need 1:1
In Lync Server 2010
Mediation server is a service
We did core routing changes to allow routes to multiple gateways trough single Mediation server (N:1)
Example Med SW can handle 500 calls, but gateway can do only 50, you don’t need 10 Med servers
In route you put gateway as destination
From Topology, Lync Server 2010 determines route to gateway through proper Med SW
Since it is a service, with Media bypass you can co-locate Mediation role with FE, or put Multiple Mediation Servers in the separate Mediation Server Pool
Lower TCO and better quality, few scenarios

9. Media Bypass
Lync Server 2010 introduces media bypass of the Mediation Server:
In Lync Server 2010, whenever possible, media will flow directly to gateway without traversing Mediation Server
Signaling continues to traverse Mediation Server role
Key scenarios:
Bypass to a media gateway
Bypass to select IP-PBX (may require Media Termination Point)
Slide Objective: Explain difference in Media bypass between Lync Server 2010 and OCS 2007 R2
Notes:
OCS 2007 R2
In OCS 2007 and R2, when signaling goes through Mediation Server, media has to also flow through Mediation Server
Topology complexity and cost, MS scalability limitations, Quality of Experience (QoE) impact
Another box in media flow
Lync Server 2010
Allows direct media in the same site
More direct path
We have more intelligence and we even pull Location Infrastructure and Topology builder helps us to figure out whether caller is local
Requires intelligence on the gateway also
Mediation server is still require for other features and all signaling (SIP)
Previous slide (less processing on Mediation server)
Lync Server 2010 introduces media bypass of the Mediation Server:
In Lync Server 2010, whenever possible, media will flow directly to gateway without traversing Mediation Server
Applies where media can stay local to a capable next hop (within a site or branch)
Does not apply where media is not local
Signaling continues to traverse Mediation Server role
Could be on FE, in an SBA, or standalone
Low CPU intensity enables running MS role on FE
Media Bypass Key Scenarios:
Bypass to a media gateway - Lync Server 2010 Open Interoperability Program (OIP) qualified gateway – G.711 over SRTP direct from Lync 2010 to gateway
Bypass to select IP-PBX (may require Media Termination Point) - Specific versions TBD – ex: G.711 direct from Lync 2010 to Cisco Unified Communications Manager (CUCM) Media Termination Point (MTP) to Cisco IP phone

10. Media Bypass – Main Benefits
Consolidation of most Microsoft resources on Front End and/or at Data Center:
Topology simplification:
TCO: greatly reduces total number of servers
Simplify interop with Internet Protocol private branch exchange (IP-PBX):
Keep in-branch media between IP-PBX and Lync 2010 local without deploying Mediation Server on site
Optimize media flow and Quality of Experience (QoE):
Eliminate unnecessary hops and potential points of failure
Save bandwidth across wide-area network (WAN) by not hair-pinning
Improve voice quality
Slide Objective: Discuss the benefits of Media bypass in Lync Server 2010
Notes:
Benefits
Mediation server is not required in a branch with gateway deployed
Media is not flowing through WAN in centralized Mediation server deployments
Consolidation of most MS resources on FE and/or at Data Center:
Topology simplification:
Together with SBA, removes need for MS in most local sites (major competitive talking point)
TCO: greatly reduces total number of servers
Microsoft Information Technology Group (MSIT) expects more than 50% reduction
Simplify interop with IP-PBX:
Keep in-branch media between IP-PBX and Lync 2010 local without deploying Mediation Server on site
Optimize media flow and QoE:
Eliminate unnecessary hops and potential points of failure
Save bandwidth across wide-area network (WAN) by not hair-pinning
Improve voice quality:
No needless transcoding and use of codec with optimal theoretical Mean Opinion Score (MOS)
Reduction in latency and in probability of network quality issues
Note:
SIP Trunk from Third Party Vendors still requires single Mediation Server
If gateway does not support Media Bypass you need single mediation server

11. Media Bypass Example Topologies
PSTN Call from Main site via Gateway with bypass
PSTN Call from Branch via existing IP-PBX with bypass
PSTN Call from Branch via Gateway
PSTN Call from Main Site & Branch Office using Centralized SIP Trunking
PSTN Call with CAC rerouting through Branch PSTN Connection
Main site call with Lync Server 2010 endpoint & PBX endpoint via Main PBX
Branch call between Lync Server 2010 endpoint & PBX endpoint via Branch PBX
Branch call between Lync Server 2010 endpoint & PBX endpoint via Main PBX
Slide Objective: Introduce example topologies
Notes:
Next slides described

12. Media Bypass Example Topologies
Mediation shown here standalone for clarity Can also be collocated in the pool
Lync Server
WAN
IP-PBX
Lync 2010
Endpoint
Lync 2010
Endpoint
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
Gateway
GW / SBA
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Same as OCS 2007
Central Data Center
Branch (use to contain Mediation sever next to gateway)
We had deployments with Mediation Server at Data Center
Same deployment in Lync Server 2010 (Note Mediation role separated for clarity and can be collocated)
Branch Site

13. Media Bypass PSTN Call from Main Site via Gateway
Lync Server
WAN
IP-PBX
Lync 2010
Endpoint
Lync 2010
Endpoint
PBX
Endpoint
G.711
IP-PBX
PSTN
PBX
Endpoint
Mediation
Gateway
GW / SBA
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Signaling is through Mediation but Media is direct
Branch Site

14. Media Bypass PSTN Call from Branch via existing IP-PBX
Lync Server
WAN
Lync 2010
Endpoint
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
Gateway
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Here signaling goes through WAN but media is sill direct. In R2, media would traverse WAN in this scenario.
IP-PBX:
must support media bypass for this scenario to work
there is a list of the vendors who support it
Branch Site

15. Media Bypass PSTN Call from Branch via Gateway
Lync Server
WAN
Lync 2010
Endpoint
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
Gateway
GW / SBA
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Same applies for gateway (ref previous slide)
Branch Site

16. Main Site (with Data Center)
Media Bypass PSTN Call from Main Site & Branch Office using Centralized SIP Trunking
Lync Server
RT Audio Narrowband
Lync 2010
Endpoint
WAN
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
G.711
GW / SBA
SIP Trunking
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Scenario: Two active end-points:
Local client –G.711 remote RTAudio
Branch Site

17. Main Site (with Data Center)
Media Bypass PSTN Call with CAC Rerouting through Branch PSTN Connection
Lync Server
Lync 2010
Endpoint
WAN
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
GW / SBA
SIP Trunking
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
For example, if Wan is congested we can re-route call via PSTN
Branch call to Voice Mail is the same scenario
CAC = Call Admission Control
Branch Site

18. Main Site (with Data Center)
Media Bypass Main site call with Lync Server endpoint & PBX endpoint via Main PBX
Lync Server
WAN
Lync 2010
Endpoint
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
Gateway
GW / SBA
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Media between client and PBX (one less hop)
IP-PBX:
must support media bypass for this scenario to work
there is a list of the vendors who support it
Branch Site

19. Main Site (with Data Center)
Media Bypass Branch call between Lync Server endpoint & PBX endpoint via Branch PBX
Lync Server
Lync 2010
Endpoint
WAN
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
Gateway
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
Branch Site

20. Main Site (with Data Center)
Media Bypass Branch call between Lync Server endpoint & PBX endpoint via Main PBX
Lync Server
RT Audio Narrowband
Lync 2010
Endpoint
WAN
IP-PBX
Lync 2010
Endpoint
G.711
IP-PBX
PBX
Endpoint
PBX
Endpoint
PSTN
Mediation
Gateway
Main Site (with Data Center)
Slide Objective: Explain Scenario
Notes:
RTA-N to Mediation – G.711 to IP-PBX – no bypass because simple site.
Branch Site

21. Caller ID Presentation Controls
Admins can natively control what Caller ID is presented to receiving party (PSTN/PBX):
Per user/group controls to suppress/alter calling party number
Granular controls based on caller and destination number:
Alice calls an external PSTN number, caller ID is presented as
Alice calls an internal PBX number, caller ID is presented as
Override for “simultaneous ringing”: Bob calls Alice, who has simultaneous ringing configured to her mobile number; Bob’s caller ID is presented
Calling Name Display feature allows display name to flow to/from OCS (also in OCS 2007 R2 CU)
Slide Objective: Introduce Caller ID controls
Notes:
Few DCR’s requested
Does not meet all scenarios but covers majority
You can change Caller ID for user or group of users based on destination number
We provide override on SIM ring, when call is forwarded on Lync 2010, you want to see originator not your office number (where possible due to geography/laws)

22. Configuring Caller ID
Slide Objective: Example of Caller ID Configuration
Notes:
Simple configuration, ultimately landed as a part of voice route
Screenshot from Administrator UI (Control Panel)

23. Voice Routing Enhancements
Centrally manage number formatting prior to routing to PBX/PSTN
Alice calls ; based on route translation pattern, called number formatted to when using gateway in Redmond
Alice calls ; based on route translation pattern, called number formatted to when using gateway in London
Slide Objective: Discuss new voice routing enhancements
Notes:
Outbound number normalization was not possible on 2007/R2 (+ only could be removed)
In previous release all other number manipulation was done on gateway
Done at certificate services (CS) now
No limit on number of rules issue with some of gateway manufactures
Simplifies administration
Explain rules from the screen (details in next two slides)

24. Voice Routing Enhancements
Centrally manage number formatting prior to routing to PBX/PSTN
Alice calls ; based on route translation pattern, called number formatted to when using gateway in Redmond
Alice calls ; based on route translation pattern, called number formatted to when using gateway in London
Slide Objective: Discuss new voice routing enhancements
Notes:
Continuation form the previous slide, shows creation process of translation rule (helper wizard integrated with normalization rules)
Shows simplicity
In this policy everything that starts with + is replaced with 9011

25. Voice Routing Enhancements
Centrally manage number formatting prior to routing to PBX/PSTN
Alice calls ; based on route translation pattern, called number formatted to when using gateway in Redmond
Alice calls ; based on route translation pattern, called number formatted to when using gateway in London
Slide Objective: Discuss new voice routing enhancements
Notes:
Continuation from the previous slide, shows new policy at the bottom

26. Enhanced Voice Policies
Provide admins flexibility to control user voice entitlements
Useful to address Common Area Device requirements
Slide Objective: Discuss new voice routing policies
Notes:
In R2 we could only enable/disable SimRing on per user basis
In Lync Server 2010 more control to admins and features flexibility
Admin’s can enable/disable per User/Group
Example:
call fraud on common area phone where you can block call forward on common area phone long distance calls from a lobby phone
Call park enables users to park calls and then pick up the call from a different phone or client. Disabled by default.
Call forwarding enables users to forward calls to other phones and client devices. Enabled by default.

27. Analog Phone Device Management
Physical connectivity of Analog devices provided by gateway partners
All routing and policy enforcement for Analog devices centralized in Lync Server 2010 – eliminates the need to manage gateways as “mini-PBX”
Certificate Services (CS) Call Detail Record (CDR) infrastructure used to track usage
PSTN
Analog Device
Lync Server
Gateway
Signaling
ATA
Media
Analog Device
Slide Objective: Explain the benefits of Analog Phone Device Management
Notes:
Analog Devices are contacts
Connected via gateway
All routing is via certificate services (CS)
Benefit:
Central place for policies
Removes need to manage gateways
Analog device presented almost as CS Endpoint
Graph describes media flow

28. Analog Fax Device Management
Physical connectivity of FAX devices provided by gateway partners
All routing and policy enforcement for FAX devices centralized in Lync Server 2010 – eliminates the need to manage gateways as “mini-PBX”
Certificate Services (CS) Call Detail Record (CDR) infrastructure used to track usage
Optimized routing to allow Fax calls routing through Lync Server 2010 without terminating Media
PSTN
Fax
Lync Server
Gateway
Signaling
ATA
Media
Slide Objective: Explain the benefits of Analog Fax Device Management
Notes:
We don’t terminate media.
The gateway must present fax calls to Lync Server as G.711 audio calls; if presented as image calls, they will be rejected.
T.38 is not supported protocol for signaling only
Media is between gateway and Fax
Fax calls are not supported through a SIP trunk.
Graph describes media flow
Fax

29. Private Line Lync Server 2010 introduces support for private line
Single SIP URI, single Exchange mailbox, single presence source
Receipt of inbound calls on private Direct Inward Dialing (DID) to same Session Initiation Protocol (SIP) URI
Private telephone lines are available for on-premises deployments only
Private lines carry many of the same features
Call pickup & park work as expected
Simultaneous ringing & call deflection on primary line carry to private line
Private lines are different:
Available for inbound calls only
Overrides delegation, call forwarding, do-not-disturb and other routing options – private calls are always going to go through
Calls to a private line have a distinctive ring & “toast” pop-up
Slide Objective: Introduce private line support
Notes:
Feature not heavy used , but high exposure to executives.
A user can have only one private telephone line
Allow us to receive call on private line, distinguished ring
Not able to send call on private line
Leftover form One identity on Lync Server 2010, will be explored in future release to allow outbound calls from private line

30. Malicious Call Trace
Lync Server 2010 provides the end-user the capability of tagging the prior call as a malicious call
Supported in Lync 2010, Lync 2010 Phone Edition & Attendant Console
Tagging is reflected in the backend CDR database, enabling the Lync Server 2010 administrator to take action on the call
Slide Objective: Introduce Malicious Call Trace
Notes:
Important feature for certain group of customers
Monitoring Server must be deployed for malicious call tracing.
Used for Bomb/Harassment threat
You can flag it
Puts flag on CDR database
Admin can talk to Exchange(PBX) carrier to figure out the source

31. Enhanced 9-1-1 Design requirements and goals for Lync Server 2010
4/19/ :51 AM
Enhanced Design requirements and goals for Lync Server 2010
Base requirement – provide location with emergency calls
The dispatchers must know the civic/street address of the caller
Locations may need to be to specific building, floor, wing, office, etc.
Support the roaming nature of Lync Server 2010 users
Inside the network – automatic or manual
Outside the network – first manual then automatic for frequent locations
Connecting to the appropriate authorities without having a PSTN gateway for each emergency network location
Slide Objective: Briefly introduce Enhanced 911
Notes:
Separate session, do not go into too many details
Fundamental: Provide location where the call comes from
Our implementation is different than the rest of the market. Lync 2010 endpoint can be very mobile.
Our expectation is that you could be anywhere, in the boardroom with your laptop instead of being at your desk or external user outside of the corporation
Fundamental requirement is Location Information
We leverage location information for other services, like CAC
© 2007 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.

32. Enhanced 9-1-1 Location Infrastructure Partner Components
Enablement location provides flexible deployment
“Network Sites” – definition of where E9-1-1 services are available
Users – E9-1-1 enablement available through user policy
Location Information Server (LIS) added to Lync Server 2010 Web components
Locations can be based on subnet, switch, port, Wi-Fi access point, and are updated on each client registration or network change
Partner Components
Emergency signaling and location conveyed from client via SIP trunks to 3rd party partner for Public Safety Answering Point (PSAP) routing
Connexion and Intrado have announced routing services
Based on National Emergency Number Association i2 architecture
Slide Objective: Briefly introduce Enhanced 911
Notes:
There is a separate E9-1-1 session, do not go into too many details
You define in network topology where E9-1-1 services will be available
If user roams in to the site where E9-1-1 is available, they will be able to take advantage
Location Information Server (LIS) is a service, not a separate server
In the backend it is a database which links civic address with location
Granularity allows compliancy with different state/country laws
LIS added to Lync Server 2010 web components
Contains records of civic addresses associated with network identifiers
No additional server roles to purchase or manage
Renders locations to UC clients
Locations can be used independent of E9-1-1
Second component
Partners terminate call coming for Lync Server 2010
Signaling comes from Lync Server 2010 as a SIP trunk and terminates at SBC for a Routing Provider
National Emergency Number Association i2 - NENA i2
NENA i2 architecture – defines everything from Enterprise Telephony to Cable and Wireless, we focus in Enterprise telephony
3rd party – Connexion and Intrado; they are 911 providers for cell networks, cable Internet
We send information as XML file to SBE
Traditional PBX sends Proper Automatic Number Identification (ANI or PANI) to carrier, and carrier and looks into the PSAP database

33. PBX Interoperability For Customers Not Ready to Replace PBX
VOICE
Lync 2010 user
PBX user
VOICE
Lync Server 2010 voice networks with any PBX
Direct SIP for signaling
G.711 and other standard codecs
CONFERENCING
Lync Server 2010 conferencing connects to any PBX
PRESENCE
Lync Server 2010 presence is available to any PBX
SIP verbs to get and set presence
Lync
PBX
Direct SIP
CONFERENCING
PBX user with Lync conf
Lync
PBX
Direct SIP
PRESENCE
PBX user with Lync IM/P
Lync
SIP
get and set
Slide Objective: Discuss Interoperability with PBX
Notes:
We have to work in interop
We improved interop
3 major segments
Voice
For voice, Any PBX with direct SIP (Interop list)
Option IP-PBX gateway (Interop list)
Conferencing in Lync Server
improved (next slide, again Interop)
Presence
Ability for PBX to use standard subscribe to gave GET and SET helps showing in a call
PBX

34. PBX Interoperability Streamlining Unified Conferencing for PBX phone users
PBX phone automatically called upon meeting join
Slide Objective: Discuss Interoperability with PBX
Notes:
Improvements
Where to join the conference from, example of headset on desk phone

35. PBX Interoperability Options for Customers
1. Full Unified Communications (UC) with legacy phone elimination
Lync Server 2010 connects to PSTN or PBX via SIP Trunking, Direct SIP or gateway. User’s DID homed on Lync Server 2010, user provided with optimized device
2. Full UC with legacy phone left in place for transition period
Same as above, but with the PBX phone left in place for transition, often with Simultaneous ringing used to have both Lync Server 2010 and PBX phone ring
3. Legacy phone with OCS unified conferencing
Lync Server connects to existing PBX systems via Direct SIP or SIP/PSTN gateway. Lync allows user to “Join From” their PBX phone when in audio conferences
4. “Click-to-Call” with legacy phone via Lync Server 2010
Lync Server 2010 integrates with existing PBX systems using Click-to-Call capability. Conferencing join through dial-in or “click-to-join” with multipoint control unit (MCU) dial-out
5. PBX manufacturer plug-in to Lync Server 2010
Software built on Microsoft’s UC development platform provided by PBX manufacturer is deployed on all user desktops alongside Lync 2010
Slide Objective: Discuss Interoperability with PBX
Notes:
Most to least preferred.
Rip and replace forward DIDs to Lync 2010 phones
Leave PBX but get separate DID’s and set simultaneous ring (almost co-existence)
Sub-option of previous one, leave legacy PBX for voice but leverage richness of other functions like conferencing
Would like to initiate call and PBX phone goes of hook, + conferencing
Leverage rich capabilities of Lync 2010 without voice
Dual Forking is not available in Lync Server 2010

36. Summary: Key Voice Changes
4/19/ :51 AM
Summary: Key Voice Changes
Resilient and always available
Caller ID presentation controls
Selectively exposing Calling Party Number
Passing Calling Party Name (in/outbound)
Routing enhancements
Centrally managing called party number formatting without relying on gateway
Mediation server 1:N to gateway
Enriched voice policies
Centralized management of analog lines
Mediation server Media bypass
Remove most/all dedicated Mediation Server boxes from topology
Keep media local to the site, avoid/limit tromboning
Locally exchange media with IP-PBX without any incremental hardware on site
Slide Objective: Go over the summary for key voice changes
Notes:
Resiliency: Always available voice
Call number manipulation: Richness
Routing : Richer and easier to manage
Media Bypass
Cutting number of servers by collocating roles
© 2007 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.

37. Summary: Key Benefits 4/19/2017 11:51 AM
PBX feature parity/completeness
Analog lines
Calling ID management
Management simplification/centralization
Routing enhancements from local gateway management to centralized management
Facilitating full scale deployments
Topology simplification (media bypass)
Centralized management of Analog devices
TCO reduction
Less physical boxes
Centralized management
Better user facing capabilities with respect to QoE
Interoperability
Improved interoperability options
Slide Objective: Go over the summary for Key Benefits
Notes:
More advanced call control
More advanced number Mgmt
More Advanced routing Mgmt
TCO
Interop
© 2007 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.

38. Q&A Slide Objective: Answer questions relating to… Notes:
Do you have any questions about…

39. 4/19/ :51 AM
© 2011 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.  This document may contain information related to pre-release software, which may be substantially modified before its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED  OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Unless otherwise noted, the example companies, organizations, products, domain names, addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, address, logo, person, place or event is intended or should be inferred.
© 2011 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.  This document may contain information related to pre-release software, which may be substantially modified before its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED  OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Unless otherwise noted, the example companies, organizations, products, domain names, addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, address, logo, person, place or event is intended or should be inferred.
© 2009 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.