Microsoft IT Unified Communications Deployment Overview
Explore how Microsoft IT architected and deployed unified communications to enhance productivity, ensure security, and manage a vast IT environment globally. The deployment includes Single Instance SAP, incident management, remote access, and regional pool topology.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
How Microsoft IT Architected and Deployed Unified Communications Jonathan R. Lewis Sr. IT Manager, Australia Microsoft Corporation
Microsoft IT Purpose Be Microsoft s first and best customer Ensure security of Microsoft s digital assets Drive productivity of our customers, clients, and partners Run a world class information technology (IT) environment November 2006 3
Single Instance SAP (1.5Tb Db) Apps Single Instance SAP 1,371LOB apps Microsoft IT Data 120,000 e-mail server accounts 300,000+ PCs and devices Devices 300K PCs 10K data centre servers 10K network devices Incident Mgmt 90K help desk calls/month 7K infrastructure Service Requests/month 6K changes/month Dublin Redmond Silicon Valley Monthly Remote Access 45K RAS 49K OWA 18K RPC over http Singapore 92,000 end users 89 countries MSIT supports over 400 sites globally; 25% Internet connected only 3M+ e-mail messages per day internally, 10M externally; 8M filtered out 99.99% availability 7,000,000 remote connections/month
Central Resource Forest Design Intranet Border Redmond Corporate Central Resource Forest Applications Server Network Load Balancer Standard Edition Pre-Production Server SAN Clustered SQL Server Database Server 5 Pooled Enterprise Edition Front-end Servers 2 Internal Director Servers Archiving Agent & Database Server Intranet Users 3/17/2025
Remote User and Federated Access Enhanced Federation Public IM Connection Remote Access (no VPN) Communicator Web Access 3/17/2025
Regional Pool Topology Microsoft Confidential
MS IT OCS Topology LCS Corp deployment was a single EE Pool for all global users. Chose Regional model for OCS (Redmond, Dublin, Singapore) Improved performance for regional users Especially for Audio and Video Web Components and Conferencing Remote Access Provisioning Still Automated Also lays foundation for global business continuance and disaster recovery strategy Microsoft Confidential
Business and IT Benefits Information worker within Microsoft saves approx 68min (3%) per week thru use of OCS/Communicator High availability and low operating cost with Enterprise Edition pool-based regionally managed system >99.9 3 dedicated FTE to support Low user/ticket ratio Single Identity management system using AD Secure IM Single client for all IM contacts via PIC and Federation Intelligent IM Filter provides simple protection Against malware, links, attachments Insure Intellectual Property stays internal November 2006 12
MS IT Deployment Overview Regional Deployments Exchange UM for voicemail EE, CE and SE Topologies Parallel OCS and LCS deployment Not Just the Corp deployment Converting our MMS LCS Customers to OCS New MMS customers will be hosted on OCS Microsoft Confidential
UC Planning Considerations Regional site PBX requirements Local dial plan interrogation Gateway requirements User Communication Exchange UM Integration UC Routing (Location Profiles) Network traffic planning Mediation Server placement
Site Selection Considerations Deploy to countries where regulatory and homologation hurdles are cleared for gateway and VoIP deployments. Site has adequate bandwidth for added UC users (Peer to Peer), and Client to Mediation Server. Device availability (Catalina or Tanjay) PBX has spare QSIG T1/E1 ports for gateway connectivity Users Basic phone users with PSTN phone number Microsoft Confidential
UC Telephony Scenarios Tanjay Best for deskbound workers Catalina/Softphone Best for deskbound remote or mobile workers HIGH phone usage Headset compatible Device controls calls Telephone independent of PC LOW phone usage Headset compatible Communicator controls calls Must be logged in to use your telephone or forwarded to another number, or using a simultaneous ring 16 3/17/2025
Gateway + Mediation Servers SIP Gateway Translate SIP/RTP to/from circuit switched telephony protocols Mediation Server Interfaces with a SIP gateway Intermediates SIP signaling interactions TLS/SRTP SIP/RTP Transcoding of codec RT Audio G.711 Media flows between OCS 2007 network and the SIP gateway Deploy Gateway and Mediation Server at a 1:1 ratio Install Reskit / Admin tools Useful to have Netmon installed on server for troubleshooting Microsoft Confidential
Mediation Server Deployment Datacenter vs Branch Office Data Center a good choice when High bandwidth w/ QoS between DC and Branch Office Low Latency between DC and Branch office No server hardware support at Branch office Branch Office good choice when 120 Kbps per call network bandwidth not available High number of users on system Microsoft Confidential
Helpful UC Tools OCSUMUtil.exe RouteHelper.exe (ResKit) Creates UC/UM Integration UC Routing Tool Provides Telecom Manager friendly interface for configuring UC routing Bridges many of the UC routing objects into one easy interface. Reduces routing complexity by abstracting telecom manger from RegEx code. Provides test interface for all sites in the forest. Manage gateways Reads ExUM Info Dial plan name Phone Number Creates an AD Contact UC enables contact Sets phone number Sets ExUM integration attributes in contact
Per user calculation Media Type Bandwidth Needed Audio 45 Kbps Video 250 Kbps Data ~45 Kbps Signaling 10 Kbps Total Type of usage is important when planning Consider the whole path end to end 350 Kbps per direction
Other Network Considerations Delay Engineer to less than a mean of 150 ms Loss up to 10% can be handled without significant problems Connectivity The clients can connect through pretty well all common networks
Troubleshooting Serverside Post Install Server Validation Wizard OCS MOM Packs for Operations Manager 2005 and 2007 OCS Logging Tool Replacement for Flatfile logging Best Practice Analyzer Perfmon for trending and quick health checks Microsoft Confidential
Troubleshooting Clientside Install Client with Logging enabled where possible, especially during pilot Very useful to understanding client issues Some Privacy and Compliance concerns Microsoft Confidential
Voice Troubleshooting Steps to Isolate Voice Quality Issue: Get a clear definition of the issue. Is it reproducible consistently. Did anything change recently new devices, new environment Anything at all Which end is the problem Network parameters to consider Jitter, Packet loss, Delay, Bandwidth Touch points for Media Device (Hard phone/Soft phone) Computer/Laptop Mediation Server Media Gateway PSTN network/Mobile Operator Install Ethereal or Netmon on Mediation servers
Lessons Learned Important to drive synergies between all teams (Networking, Telephony, Messaging and UC) early. Lack of telephone number standardization caused delays in enabling users. Wireless can be problematic. Live Meeting without wired power can cause issues. Using voice from other enterprise locations causes RTP to go over TCP, firewalls typically only allow 443 or 80 which causes audio to go over 443 via TCP. Legacy network hubs / switches can cause poor audio. Slower laptop CPU s can be problematic with UC audio and RoundTable, especially when Recording. Microsoft Confidential
Gateway Lessons Learned Choose good partners Provide site deployment plans early and often to Gateway Vendor so that delays in homologation don t hinder deployments. Bring up T1/E1 2 weeks prior to deployment Standardize on tie line interfaces between the PBX and UC (i.e. QSIG) Microsoft Confidential
Deployment Challenges Dial Plans are located in UC, PBX, Gateways and Exchange UM Not all Telco carriers are created equal Each country is different for T1/E1 configuration Variable length phone numbers Outbound Caller ID variants Inconsistent, inbound Caller ID can impersonate internal users if it matches the length and range of an internal extension. Users that require advanced PBX features are impacted. Microsoft Confidential
Best Practices Infrastructure Standardize gateway hardware Deploy in phases Ensure a crisp and well thought out enablement process End User Create strong communications package Standardize user devices Introduce users to the softphone concept End user training/preparation Helpdesk preparation 28 September 07
