NameTitle
Microsoft
Voice SolutionArchitecture Design Session
Architecture Design Session
Solution
Overview
Technology
Overview
Point out technologie
s for relevant
capabilitiesDiscuss
technologies
Architecture
Discussion
Discuss Architecture
Decision Points
POC Plannin
g
Develop scope and
specifications for POC
VPC-based demo
View the capabilities
in action
Show various
possibilities
Vision scope input
from solution briefing
Solution
Briefing Summa
ry
Architecture Design Session
Vision scope input
from solution briefing
Solution
Briefing Summa
ry
• Employees working from home and on the road
• Greater use of shared work spaces (“hot desking”)
• More teams distributed• PBX maintenance costs• PBX obsolescence
Challenges
• Employee retention AND productivity
• Lower real estate costs• Improve collaboration• Reduce costs now and in
the future
Business Drivers
Summary of Pains and Drivers
Technical Requirements • Provide a solution that provides access to voice and all other
communications wherever the employee is working• Integrate with existing telecom infrastructure to allow migration
of users at the right pace• Use Active Directory rather than separate directory systems
Architecture Design Session
Solution
Overview
VPC-based demo
View the capabilities
in action
Show various
possibilities
Vision scope input
from solution briefing
Solution
Briefing Summa
ry
Authentication
Administration
Storage
Compliance
Unified Inbox & Presence
AudioConferencing
E-mail andCalendaring
WebConferencing Telephony
VideoConferencing Voice Mail
InstantMessaging (IM)
Authentication
Administration
Storage
User ExperienceAuthentication
Administration
Storage
UserExperience
Authentication
Administration
Storage
User Experience
Authentication
Administration
Storage
UserExperience
Authentication
Administration
Storage
User Experience
Authentication
Administration
Storage
UserExperience
Authentication
Administration
Storage
User Experience
Telephony and
Voice Mail
InstantMessaging
E-mail andCalendaring
Unified Conferencing: Audio, Video,
Web
On-Premises Hybrid In the Cloud
Communications TodayFuture of Communications
Microsoft Unified CommunicationsIncreased productivity through communications convergence
Streamline Communications
Amplify Protection and Control
Provide a Unified and Extensible
Platform
Across Devices PC, Mobile, Web
Increase Efficiency and
Flexibility
>>
>>
>>
>>
Maximize IT Resources with S+S
Authentication
Administration
Storage
Compliance
Unified Identity, Presence, and Inbox
On-Premises, Hybrid, or in the Cloud
Sce
nari
os
Pro
duct
s
On Premise Hosted by Microsoft
Deliv
ery
IM and Presence
Unified Messaging
E-Mail and Calendaring
VoIP
Mobility
Security and Compliance
E-mail Security, Compliance, and
Continuity
Hosted by Microsoft or by Partners Hosted by Partners
Conferencing
Microsoft Unified Communications Products and Services
Conferencing
UC Journey Through Infrastructure Optimization
Basic
BasicStandard ized
StandardizedDynam ic
DynamicRationalized
Rationalized
identify where
you are
identify where you
want to be
Basic e-mail, file shares, mostly phone based
communication
Standard platform for
secure e-mail and IM
Ad hoc teaming around functions & projects based on IT standards
Increasing unification of
communication channels
Fully managed collaboration platform and
pervasive access
Seamless collaboration across the firewall
Federation of communication information and
policy
IT is astrategic asset
IT is abusiness enabler
IT is an Efficient cost
center
IT is a cost center
Identifying Target Maturity Level IM
&
Pre
sen
ceBasic
BasicStandardized
StandardizedDynamic
DynamicRationalized
Rationalized
Vo
ice
Co
nfe
ren
cin
gM
essa
gin
g
Legacy TDM PBX, traditional phones
Limited voice mail and call routing
Highly available hybrid telephony infrastructure
Online & offline access to voice mail
Managed call routing
Encrypted voice infrastructure with unified inbox accessible from PCs, phones, & web browsers
Managed storage
Presence-based call routing
Integrated voice platform for IM/presence; conferencing with LOB applications
Auto-remediation, proactive monitoring of call quality
Federated identity and presence-based call routing
Rich mailbox & calendaring
Secure, remote, online & offline access
Basic AV/AS/AP protection and disaster recovery
Solution supports encryption
Business continuity with AS/AP and multi-layer AV protection
Support advanced policy-driven message controls
Provisioning for user inboxes
Basic email with no remote access and with limited security
Minimal or decentralized IT support
User inboxes are fully managed by IT
Seamless business continuity with multiple AV/AS protection
Advanced policy control to mobile devices & applications
Integration with LOB applications
Federation of calendar
Public IM/online presence, ad-hoc use for daily business
Secure access from inside & outside the firewall
Supports peer-to-peer voice & video communications
Presence enabled email client
Secure IM/online presence accessible from a variety of devices and integrated into enterprise productivity & collaboration platform
Persistence group chat
Supports federation and integration with LOB applications
Sporadic use of audio & web conferencing
Limited video conferencing capabilities
Integrated & secure conferencing platform
Supports high-quality audio & video
Remotely accessible collaboration features
Secure web conferencing accessible from remote locations and devices
IT-managed video conferencing with limited remote access
Contextual unified conferencing solution tightly integrated with collaboration infrastructure and LOB applications
Voice
Architecture Design Session
Solution
Overview
Technology
Overview
Point out technologie
s for relevant
capabilitiesDiscuss
technologies
VPC-based demo
View the capabilities
in action
Show various
possibilities
Vision scope input
from solution briefing
Solution
Briefing Summa
ry
15
Client Experience
Make a call from anywhere
Share video in calls and conferences
Take phone calls where you want them
Manage communications for someone else
Manage your own communications
Make emergency calls that include location
UX Value Propositions A dial pad that looks and acts like you’d expectHave confidence in call quality before dialingGet actionable feedback when call quality declinesReceive calls on a private line
New FeaturesSeparate phone environmentFamiliar DTMF dial padClick to Call from contactsMake a test callIn-call quality notificationsPrivate line
Make a Phone Call from AnywhereA phone you can trust, with a familiar interface
16
UX Value Propositions Easy, intuitive controlsSee the whole roomWatch full-screen video in high definition (HD)
New FeaturesVGA video supportAlpha-blended video controlsPanoramic video supportSeparate video window
Share Video in Calls and ConferencesHigh-quality video brings nuance to your communications
17
UX Value Propositions Quickly configure and test USB peripheralsMove your calls from one device to anotherEasily enable call routing so that calls reach youTake your calls with you wherever you are
New FeaturesTop-level device selectionImproved device tuning user experienceIn-call device “hot-swapping”Endpoint transfer to mobile phone
Phone Calls Where You Want ThemEasy control of calls and devices
18
UX Value Propositions Know that you have missed calls and messages waiting at a glancePlay voice mail directly from Lync 2010Easily reply to voice mail messages using other modalities
New FeaturesMessage Waiting IndicatorInline voice mail playbackContext across modalities
Manage Your CommunicationsStay on top of your day-to-day communications
19
UX Value Propositions Emergency responders need to know your location
New FeaturesAutomatic location supportCustom location setting
Making Emergency Calls That Include LocationA phone you can trust in emergencies
20
PBX phone automatically called upon meeting join
PBX InteroperabilityStreamlining Unified Conferencing for PBX Phone Users
21
Voice Key Features and CapabilitiesSurvivable Branch ApplianceMediation Server CollocationMediation Server BypassPBX InteroperabilitySIP TrunkingEmergency Dialing (E9-1-1)Analog Device ManagementSingle Number ReachCall Admission Control FunctionalityPrivate LineMalicious Call TracingVoice MailMonitoringCall ParkResponse Groups
Survivable Branch Appliance (SBA)An appliance optimized to provide resilient multi-modal communication for maximizing branch office user productivity
23
PSTN
WAN
Data Center
LyncPool
EdgeServe
r
SBA
Branch Office
Components Functionality Go-To Market
Windows Server® 2008 R2Mediation ServerRegistrar PSTN Gateway
Normal/Failover mode SIP Registrar SIP Proxy and Routing engine PSTN connectivity Voicemail routing PSTN re-routingCentrally provisionedUp to 1000 user support
OEM (Embedded channel) 5 partners• Audiocodes• HP• Dialogic• NET• Ferrari
Mediation Service ColocationEnabled through two enhancements that lower TCO and optimize quality
Multiple Gateways per Mediation Service
Lync Server 2010 allows for Gateways to be connected to the same Mediation ServiceRoutes point to a GatewayTopology document used to find anappropriate Mediation Service is inserted into the routing pathMediation Service uses the GW-FQDN in the Request-Uniform Resource Identifier (URI) to route to appropriate Gateway
Multiple Mediation servers in a poolAllows a certified IP-PSTN gateway to load balance across a pool of Mediation Servers
OCS 2007 R2
Lync Server 2010Route GW
Route_US LAX_GW
Route_EURDE_GW1
DE_GW2
Route_APAC SYD_GW
Route GW
Route_US LAX_GW
Route_EURDE_GW1
DE_GW2
Route_APAC SYD_GW
Mediation Service ColocationEnabled through two enhancements that lower TCO and optimize quality
Media Bypass of Mediation ServerWhenever possible, media for calls egressing to the PSTN will flow directly to upstream device without traversing Mediation ServerApplies where media can stay local to a capable next hop - a site or branch
Does not apply where media is not localSignaling continues to traverse Mediation Server role
Consolidation of most Mediation resources at the Data Center.
Mediation could be on a Front End, in a SBA, or standaloneLow CPU intensity enables running Mediation role on FE & Appliance
Media BypassBenefits of direct routing of media
Topology simplificationTogether with Survivable Branch Appliances, removes need for standalone Mediation Server in most local sites.Greatly reduces total number of servers for lower Total Cost of Ownership.
Optimize media flow and Quality of ExperienceEliminate unnecessary hops and potential points of failure.Save bandwidth across wide-area network (WAN) by not hair-pinning.Improve voice quality:
Use of codec with optimal theoretical Mean Opinion Score (MOS).No needless transcoding.Reduction in latency and in probability of network quality issues.
Media BypassKey Scenarios
Bypass to a media gatewayGateways qualified for Lync Server 2010 will be supported for bypass.G.711 over SRTP direct from Microsoft Lync 2010 to Gateway.
Bypass to select IP-PBXs (Specific versions TBD)
Keep in-branch media between IP-PBX and Lync 2010 local without deploying Mediation Server on site.May require Media Termination Point or similar – testing underway.G.711 direct from Lync 2010 to Cisco Unified Communications Manager (CUCM) Media Termination Point (MTP) to Cisco IP phone.
SIP TrunkingSupport TBD – Carrier SBCs generally don’t accept connections from any client.
Media BypassExample Topologies
1. PSTN Call from Main site via Gateway with bypass2. PSTN Call from Branch via existing IP-PBX with bypass3. PSTN Call from Branch via Gateway4. PSTN Call from Main Site & Branch Office using Centralized
SIP Trunking5. PSTN Call with CAC Rerouting through Branch PSTN
Connection6. Main site call with Lync Server 2010 endpoint & PBX
endpoint via Main PBX7. Branch call between Lync Server 2010 endpoint & PBX
endpoint via Branch PBX8. Branch call between Lync Server 2010 endpoint & PBX
endpoint via Main PBX
PBX InteroperabilityFor Customers Not Ready to Replace PBX
VOICELync Server 2010 voice networks with any PBXDirect SIP for signaling G.711 and other standard codecs
CONFERENCINGLync Server 2010 conferencing connects to any PBXDirect SIP for signaling G.711 and other standard codecs
PRESENCELync Server 2010 presence is available to any PBXSIP verbs to get and set presence
29
Direct SIPLync PBX
CONFERENCING
Direct SIPLync PBX
VOICE
SIP get and set
PRESENCE
Lync user PBX user
PBX user with Lync conf
Lync PBX
PBX user with Lync IM/P
PBX Deployment ScenariosReplace, Enhance, Add
Replace the PBX with a complete UC solutionLync Server 2010 meets enterprise telephony requirements. Connect to the PSTN via a SIP Trunk or gateway, and connect to any PBX during transition phase.
Enhance the PBX with Full UCPBX phone left in place for transition, often with Simultaneous ringing used to have both Lync 2010 and PBX phone ring. Click-to-call an option for some users to initiate or answer calls using PBX phone (RCC) with feature loss including Mobile access.
Add conferencing, presence & IM to the PBXAudio, video, and web conferencing using Lync 2010, or audio and web conferencing using their existing PBX phone. New “Join From” feature rings the user’s PBX phone automatically. Gives organization the option to easily enable the voice capability in the future, but does not provide full UC capabilities such as mobile voice.
Key Features Direct SIP connectivity
between Mediation Server and ITSP
Session Border Controller not required on customer premises
Microsoft participating in SIPConnect working group
MediationServer
SIP
Lync 2010
Lync Server 2010
IM, Presence, AudioVideo, Conferencing
ITSP: Access to PSTN and
Mobile Phone Networks
Organizations can reduce costs and simplify management by directly connecting to the PSTN over SIP without on-premise gateways
SIP TrunkingDirect connectivity to the PSTN using SIP
Enhanced 911Design Requirements and Goals for Lync Server 2010
Base requirement - provide location with emergency calls
The dispatchers must know the civic/street address of the callerLocations may need to be to specific building, floor, wing, office, etc.
Support the roaming nature of Microsoft Lync 2010 users
Inside the network - automatic or manualOutside the network - first manual then automatic for frequent locationsConnecting to the appropriate authorities without having a PSTN gateway for each emergency network location
Enhanced 911Provides location information for emergency calls
Lync client can be enabled to provide location information for emergency callsAcquires location informationRoutes the call along with location and callback information to an Emergency Services Service Provider
Enhanced 911Location Infrastructure
Enablement location provides flexible deployment“Network Sites” – definition of where E911 services are availableUsers – E911 enablement available through user policy
Location Information Server (LIS) added to Lync Server 2010 Web components
Contains records of civic addresses associated with network identifiersNo additional server roles to purchase or manageRenders locations to UC clientsLocations can be used independent of E911
Locations can be based on subnet, switch, port, Wi-Fi access point, and are updated on each client registration or network change
Analog Device ManagementAnalog devices can be managed using Lync Server
Analog devices use Lync Server to make and receive callsAnalog devices are associated to AD contact objectsSupported devices: analog phone and analog fax machinesPhysical connectivity of Analog devices (FXS) provided by GW partnersAll routing and policy
enforcement for Analog devices centralized in Lync Server 2010CDR tracks the usage
Fax
Lync Server 2010
PSTN
Signaling
MediaATA
Analog Device
Gateway
Single Number Reach Outside Voice Control
Employees can use single telephone number on their business cardOutbound calls will use work number identitySingle voice mailboxLync Call back will enable cost saving in calling-party-pays markets
Feature Description
Click-to-CallCall SIP URIs and telephone numbers from contact list and smart search results.
SNR - IncomingReceive calls dialed to their single number on their Communicator Mobile device.
SNR – OutgoingMake calls from their Communicator Mobile device. The caller-ID received reflects their single number.
Deflection services for voice mail
Incoming calls may be deflected to other targets – for example, voice mail.
A way for enterprise users to hand out a single identity and be reached wherever and on
whichever device
Alex select “Work Call” (signal goes trough the cellular network data channel)
Alex and Ben both receive call back from Lync (signal goes through cellular network voice channel+ PSTN)
BenAlex
PSTN
Internet
Mobile Operator
Lync Server 2010
Single Number Reach ExampleScenario: Alex calling Ben
Least Cost RoutingLowest termination cost
Leverages existing multiple VoIP gateways deployed in the organizationTerminates calls to PSTN in the location that will allow for lowest termination costExample: A call placed from a supported mobile client to a long-distance PSTN number can be routed over the enterprise IP network to the PSTN gateway that is nearest to the location of the destination number.
Call Admission controlBandwidth Management
Rich capabilitiesReroutes or fail sessionFully configurableDynamically enforced by link and media type
Cost effectiveSimple – no additional physical servers requiredNo requirement for specific network hardware or integration
Unified Communications modality supportAudioVideo
Customizable Customizable to meet customer needs
Private LineFor the executive in your organization who has everything…Lync Server 2010 introduces support for private line
Single SIP URI, single Exchange mailbox, single presence sourceReceipt of inbound calls on private DID to same SIP URI
Private lines carry many of the same featuresCall pickup & park work as expectedSimultaneous ringing & call deflection on primary line carry to private line
Private lines are different:Available for inbound calls onlyOverrides delegation, call forwarding, do-not-disturb and other routing options – private calls are always going to go throughCalls to a private line have a distinctive ring & “toast” pop-up
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.
Voicemail – Exchange 2010 UM Integration
Voicemail integrationSupport for recording high-fidelity voice mailsOutlook Voice AccessMissed call notificationsAssign subjects and prioritiesInbound Call can be forwarded to another number or to an Exchange UM Auto AttendantDirect Voicemail calling
IT administrators can maintain call records and monitor quality attributes (ex: MOS scores of voice & video)
Monitoring ServerDatabase storage of call records and quality of experience
A/V Quality metrics reportsQuality reports collected at the end of each callFrom Lync 2010, IP Phone, A/V Conferencing Server, Mediation Server, Attendant ConsoleReports aggregated and stored into DB
Instrumentation and AlertingStatistical based performance counters for Network factorsGrouped by Location, A/V Conferencing Server, and Mediation Server. A Location is one or more subnetsInstrumentation is consumed by SCOM Pack for alerting
Out of Box Reports
Call Park
Put a call on hold and then retrieve the call from same or another computerPut a call on hold to transfer it to a department or general areaPut a call on hold and keep the original answering phone free for other callsRetrieve parked calls by dialing the orbit number or clicking the orbit link or button in the Conversation window
Administrators easily create hunt groups for departmental teams, and allow management by the people that use them
Response GroupsCall queuing and routing for workgroup environments
FeaturesCall queuingAnonymous CallsAttendant routing methodSerial, parallel, round-robin, longest-idle, and attendant routing methodMusic on holdFormal and informal agentsInteractive voice response with built-in text-to-speech and speech recognitionPre-defined workflow templates for easy setupTimeout and overflow handling
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 numberGranular controls based on caller and destination number:
Alice calls an external PSTN number, caller ID is presented as +1 425 555 0100Alice calls an internal PBX number, caller ID is presented as +1 425 555 2302
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 through Lync Server 2010
Also Available for OCS 2007 R2 through KB
Caller ID Presentation Controls
Voice Routing Enhancements
Centrally manage number formatting prior to routing to PBX/PSTN
Alice calls +44221234567; based on route translation pattern, called number formatted to 01144221234567 when using GW in Redmond
Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using GW in London
Voice Policy Enhancements
Provide admins flexibility to control user voice entitlements
Call ForwardingDelegationCall TransferCall ParkSimultaneous RingingTeam CallPSTN ReroutingBW Policy OverrideMalicious Call Tracing
Useful to address Common Area Device requirements
UC Session Bandwidth Costs
Bandwidth numbers include overhead for framing, encryption, and IP routing information in addition to actual encoded media and based on 20 milliseconds (ms) audio p-timesTypical bandwidth values bit rate are measurements of typical activity level values under good network conditions (i.e. no FEC for audio sessions)Typical bandwidth number can be used for capacity planning to assess if a network should be considered “right provisioned”Upper Limit numbers can be used to set initial control points on sessions in network weak spots
Monitor actual Bandwidth usage of UC sessions and then refine
Codec RTAudio - 8Khz
RTAudio - 16 Khz
Siren G.711 G.722 RTVideo -CIF 15fps
RTVideo -VGA 30fps
RTVideo -HD
30fps
RDP – App
Sharing
Typical Bandwidth – No FEC
27.8 kbps 45 kbps 32 kbps 80 kbps 80 kbps 203 kbps 492 kbps 1230 kbps70 kbps – 2 Mbps
Upper Limit – No FEC
39.8 kbps 57 kbps 47.6 kbps 92 kbps 99.6 kbps 250 kbps 600 kbps 1500 kbps ~10Mbps
Upper Limit - FEC
51.6 kbps 86 kbps 63.6 kbps 156 kbps163.6 kbps
n/a n/a n/a n/a
Unified Communications Open Interoperability Program
The UC Open Interoperability Program for SIP/PSTN Gateways, IP-PBXs and SIP Trunking Services ensures that customers have seamless experiences with setup, support, and use of qualified telephony infrastructure and services with Microsoft's unified communications software. Only products that meet rigorous and extensive testing requirements and conform to the specifications and test plans will receive qualification.
http://technet.microsoft.com/ucoip
Architecture Design Session
Solution
Overview
Technology
Overview
Point out technologie
s for relevant
capabilitiesDiscuss
technologies
Architecture
Discussion
Discuss Architecture
Decision Points
VPC-based demo
View the capabilities
in action
Show various
possibilities
Vision scope input
from solution briefing
Solution
Briefing Summa
ry
Voice Topology: Lync Server 2010
PICXMPP
MSNAOL
Yahoo
RemoteUsers
FederatedBusinesse
s
EdgeServices
Front End (incl. Mediation)
Back End
ExUM
UC Endpoin
ts
ArchivingMonitoring
AD DNS
`
Media GW / SBA
On-premise or online
UC Pool
PSTNIP-PBX
SIP Trunkin
gDirect SIP
AV Conf.
Analog Devices
Mediation Server
CircuitPacket
53
Perimeter Network
Lync
UM Topology Architecture
VoIP protocols (SIP, RTP, T.38) between UM and IP-PBX or IP GatewaysOther protocols between server rolesSupports variety of PBXs and IP-PBXsWell suited for site consolidationScalable and reliable
Security Enhancements for Voice Edge Server and NAT
Internal Edge InterfaceNo NAT supported
External InterfaceSingle Edge Server
Routable IPs or 1:1 NAT
Hardware Load BalancedRoutable IPs
DNS Load Balanced1:1 NAT
Ports 50,000-59,999Required for federated media trafficFederation with OCS 2007
Open UDP and TCP in- and out-bound
Federation with OCS 2007 R2/Lync Server 2010Open TCP outbound
•AD, Exchange, security•LAN and WAN networks•Current PBX network, PSTN trunking, DIDs
Current Infrastructure
•Voice needs and goals•Lync Voice users now and in the future
Future Infrastructure
•WAN and LAN utilization and impact•Telephony integration
Network and Telephony
•Scope and nature of applications•Development expertise on staffRemote Access
Architecture Decision Points
Active Directory Forest topology?Single Forest / Multi Forest, Single DomainSpecify forest and domain functional levelSpecial Security Requirements
PKI / certificate infrastructure?Existing infrastructure, plans to implement to support remote access
Messaging infrastructure?Exchange deployment and versionExchange or other voice mail
Architecture Discussion PointsCurrent Infrastructure
Company sites, populations, network interconnections
LAN and WANTelephony tie linesLinks already over or near capacity
Existing PBX network, PSTN connectivity, DID ranges
Particularly those serving users who will move to LyncVoice mail / UM connectivityDial plans and call routingUsage patterns
Architecture Discussion PointsCurrent Infrastructure
Which groups of users in which locations will move to Lync voice initially?
Locations, requirements, current calling patternsHow much will they use audio, video, web conferencing, and application sharing in addition to voice?
Which groups of users in which locations are likely to move next?Will you provide remote (VPN-less) access to voice and other communications?Use Planning Tool as necessary
Lync Server 2010 Planning Tool
Architecture Decision PointsFuture Infrastructure
Given the expected usage of Lync users, what is the impact on current WAN, LAN, and Internet connections?
Plan for approximately 45Kbps for each Peer-to peer audio connection (86 Kbps maximum)Plan for approximately 28Kbps for each UC-PSTN audio connection (52 Kbps maximum)Plan for approximately 610Kbps for each video (VGA) connection
Are upgrades or policy decisions required?
Architecture Decision PointsNetwork Utilization
Given the users migrating now and in the future:Which PBXes (if any) should Lync network with, and via which approach (Direct SIP or a gateway)? How much capacity is needed?Which PSTN trunks should terminate on Gateways connected to Lync instead of on a PBX?
Do dial plans or routing need to be updated?
Architecture Decision PointsTelephony Integration
What are the Service Availability requirements for Edge?What certificate types will be required? How will they be deployed?Are there multiple Internet connections?Will you enable Federation with partners?Do your security policies demand high security of your internal server from the external network?
Architecture Decision Points Remote Access
Additional Project Considerations
Project PlanningDedicated Project Office – Project Manager, Project Plans.Risk Management
End-User Change ManagementUser TrainingDevice distribution and removal
Migration PlanningTransition existing telephony to Lync Server 2010Transition existing OCS 2007 / R2 deployments to Lync Server 2010
Architecture Design Session
Solution
Overview
Technology
Overview
Point out technologie
s for relevant
capabilitiesDiscuss
technologies
Architecture
Discussion
Discuss Architecture
Decision Points
POC Plannin
g
Develop scope and
specifications for POC
VPC-based demo
View the capabilities
in action
Show various
possibilities
Vision scope input
from solution briefing
Solution
Briefing Summa
ry
POC Planning
Sponsor NameProject Timing Goals and ObjectivesScope Milestones Risks & Dependencies
Next Steps
Proof of Concept• Assemble resources from the
business side and from the IT group• Understand business processes
that are being addressed• Gain knowledge about technology
infrastructure• Verify the technology roadmap• Review the POC scope and
assumptions
Proof of Concept
Architecture Design Session
Solution Briefing
Solution Development
© 2007 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
Appendix Slides