Minnesota Microsoft Unified Communications User Group Welcome! March 26, 2009
Today s presenters Rob Hanson rhanson@avtex.com Business Development for UC Colleen Reynolds creynolds@avtex.comcom Ops Manager for UC Mark Granquist mgranquist@avtex.com Project Engineer
AGENDA Welcome Feature comparison OCS 2007 vs. R2 OCS Core Servers & Roles OCS Advanced Servers & Roles OCS Architecture OCS Resources Wrap up
OCS 2007 and R2 Comparison Feature OCS 2007 OCS 2007 R2 Enterprise Instant Messaging Enhanced presence Peer to peer voice and video File transfer Multi party Web conferencing Application sharing Software powered VoIP Call management Dial in audioconferencing Desktop sharing Persistent Group Chat Attendant console and delegation Session Initiation Protocol trunking Mobility and single number reach
OCS Core Servers & Roles
REQUIREMENTS Operating System and Processor Support OCS R2 is available only in a 64 bit edition, which requires 64 bit hardware and the 64 bit edition of Windows Server. Operating Systems The 64 bit edition of Windows Server 2008 Standard operating system, or the 64 bit edition of Windows Server 2008 Enterprise operating system The Windows Server 2003 R2 Standard x64 Edition operating system with Service Pack 2 (SP2), or the Windows Server 2003 R2 Enterprise x64 Edition operating system with SP2 The Windows Server 2003 Standard x64 Edition operating system with SP2, or the Windows Server 2003 Enterprise x64 Edition operating system with SP2 Client computers are not required to have 64 bit hardware or software.
Standard or Enterprise Edition Standard Edition Enterprise Edition (Consolidated) One or more Standard Edition servers can be deployed alone or in combination with one or more Enterprise pools Maximum of 5,000 users Single server for core functionality Front End Server, Back End Database, A/V Conferencing Server, Web Conferencing Server, Web Components Server, Application Sharing Server including Response Group Service, Conferencing Attendant, Conferencing Announcement Service, and Outside Voice Control applications Recommendation if you have remote sites with more than 100 users connected by a WAN to your central site or data center we recommend that you have a local OCS core server deployed Maximum of 100,000 users (fully enabled) Eight FE servers running all server roles Back End Database server (can be clustered in a two node activepassive configuration) High Availability High Scalability Active Directory must conform to the supported domain and configuration requirements
OCS Advanced Servers & Roles
Consolidated Edge Deployed in a perimeter network to support access by external users. External users include remote, federated, and anonymous users. Server supports connectivity with one or more of the following public IM service providers: AOL, MSN, and Yahoo!. Supports Communicator Mobile (COMO) An Edge Server automatically runs these three services Access Edge service, provides the core functionality for collaboration between your internal users and external users. The Access Edge service providesa single, trusted connection point for both outbound and inbound Session Initiation Protocol (SIP) traffic., Audio/Video Edge service, proivdes audio and video with external users. Web Conferencing Edge service, which enables external users to joinon onpremises meetings. This service enables your users to invite external users to meetings; these external users can include your organization s remote users, federated users, and any other external users who are sent invitations to specific meetings..
Consolidated Edge continued Capacity Access Edge service supports 5,000 client connections Web Conferencing Edge supports service 1,000 client connections A/V Edge service supports 500 concurrent audio/video (A/V) sessions HTTP reverse proxies are also recommended in the perimeter network. Required to enable external users to download meeting content, Address Book files, and distribution group expansion. Can reuse existing if deployed in perimeter network Collocation of an Edge Server with a reverse proxy or with an internal or external firewall is not supported.
Communicator Web Access (CWA) Provide Office Communications Server services such as instant messaging (IM), presence, audio conferencing, and desktop sharing You can configure Communicator Web Access to handle service requests from three different types of users: internal users (users located behind your organization s firewall) external users (users on the Internet) anonymous users (users who do not have an account in your Active Directory or the Active Directory of a federated partner) Communicator Web Access requires that Office Communications Server 2007 R2 is installed somewhere within your Active Directory forest.
Communicator Web Access (CWA) continued This includes users who: Do not run Microsoft Windows. (Macintosh and Linux using a supported Web browser) Log on from outside the organization s firewall. You do not need a virtual private network (VPN) connection in order to use Communicator Web Access. Have locked down computers. No software other than a supported Web browser is required to access features such as instant messaging and rich presence. Capacity CWA supports 5,000 users 120concurrent desktop sharing users Communicator Web Access requires that Office Communications Server 2007 R2 is installed somewhere within your Active Directory forest.
Enterprise Voice Enablement Communications Server Stand Alone Sole telephony solution for part or all of an organization Communications Server PBX Coexistence Native IP PBX integration IP PBX that natively supports SIP and IP media in a format that is interoperable with Office Communications Server. TDM PBX integration through a media gateway A PBX combined with a media gateway that connects the PBX to the Office Communications Server infrastructure.
Enterprise Voice Components Mediation server Intermediates signaling and media between your internal OCS infrastructure and your media gateway or Session Initiation Protocol (SIP) trunk. Media Gateways Physical connection and conversion for TDM, Voice over IP (VoIP) or public switched telephone network (PSTN) to mediation server. Gateway types Basic consist of a basic media gateway and a separate Mediation Server. Basic Hybrid consists of the basic gateway and Mediation Server collocated on a single computer. Advanced media gateway, the Mediation Server logic is incorporated within the gateway software itself. A media gateway is not required for a SIP trunk connection.
Enterprise Voice Deployment Options PBXcoexistence Requirements Basic, basic hybrid, or advanced media gateway configured to connect to PBX. Mediation Server configured with the IP address of the PBX and the fully qualified domain name (FQDN) of the A/V Edge Server. Users enabled for Enterprise Voice and PBX integration. Voice mail configured on PBX or Exchange UM. Recommended A/V Edge Server for media relay across network address translations (NATs) and firewalls. Telephony device
Enterprise Voice Deployment Options continued Communications Server Stand Alone Requirements Basic, basic hybrid, or advanced media gateway configured to connect to PSTN. Mediation server configured with IP address of basic or basic hybrid media gateway (not required for advanced gateway). Users enabled for Enterprise Voice. Exchange Unified Messaging deployed and configured to provide voice mail. Recommended A/V Edge Server for media relay across network address translations (NATs) and firewalls. Telephony end point
Application Sharing Server Component (UCAS) UCAS is installed on each Enterprise Edition Front End Server and Standard Edition server. Support applications: Conferencing Attendant Enables enterprise users to use a public switched telephone network (PSTN) phone to dial in to a conference. Conferencing Announcement Service Enables tones to be sounded to announce when users join or leave a conference, and notifications to users when they are muted or unmuted. Response Group Service Enables users to create response groups for the purpose of routing and queuing incoming phone calls to one or more designated agents. Outside Voice Control Provides enterprise voice functionality and call control to mobile phones that are not otherwiseenabled enabled for enterprisevoice voice. Application Server runs only applications shipped with Office Communications Server it does not run third-party applications.
Group Chat Server Provides persistent, ongoing IM conversations. along with all files, Web links, and other associated data. This persistence makes it possible to maintain complete records of each session. Group chat requires you to deploy three components: Office Communications Server 2007 R2 Group Chat Server, which gives users access to Group Chat functionality. The Office Communications Server 2007 R2 Group Chat Administration i ti Tool, which h allows an Office Communications Server 2007 R2 administrator or delegate to manage chat rooms and users. Office Communications Server 2007 R2 Group Chat, a desktop client application that makes chat room conversations and features available to end users. It also enables users to send and receive IM, either in a chat room or singly with another user outside the chat room. If you want to make chat rooms available, you must install this component in addition to Office Communicator. If archival of chat room content is required for compliance reasons, you can also install the optional Group Chat Compliance service.
Group Chat continued Capacity: Note: Chat rooms can support more than 30 participants, and the Group Chat client is capable of supporting more than 30 chat rooms. However, large numbers of participants in a chat room may impact server performance. The maximum tested configuration for chat rooms is 1,000 participants. p Use of chat rooms with large numbers of participants p should be limited to no more than 10% of all chat rooms created.
Archiving Server Optional server role for both Office Communications Server Standard Edition and Office Communications Server Enterprise Edition. Archives for compliance purposes the content of instant messaging (IM) sent in Office Communications Server, including federated contacts. Consists of the Archiving service and a SQL Server database, which is called the Archiving database. One Archiving Server Supports 300,000 users The Archiving agents are installed and activated automatically.the agents capture messages for archiving and send them to the destination queue on the Archiving Server. No messages are actually captured unless an Archiving i Server is deployed. d The Archiving Server reads the messages from the archiving agents in the Front End Servers and then writes them to the Archiving Back End database. The Archiving Server Back End database runs on SQL Server and stores the archived messages.
Archiving Server topologies
Monitoring Server Dtb Database storage of call records and quality of experience Optional Server role Key Features Single server for all monitoring Immediate access to CDR and QoE data Usage reporting/roi analysis Export into billing and other systems One server supports 200,000 users New QoE metrics captured Audio and video quality PSTN connections Network connectivity Response Group service IT administrators can maintain logs of calls for compliance reasons and monitor quality attributes (ex: MOS scores of voice & video)
Quality of Experience management Monitoring server captures MOS data for voice and video calls to enable network hot spot identification and remediation Traditional QoS Diffserv marking supported, but not required No Call Admission Control (CAC) support for LAN Considering options for future WAN link management
Monitoring Server topologies
OCS Architecture
OCS Resources
COLLOCATION Many Office Communications Server 2007 R2 components can be collocated on the same computer. Anycombination that is not identified hasnot been tested and is not supported http://technet.microsoft.com/en us/library/dd425201(office.13).aspx
PBX Integration See http://technet.microsoft.com/ucoip for certified gateways and IP PBXes qualified for Direct SIP connection Updated regularly
Network Design Right size the network All network traffic is crucial: voice and applications Design for expected load to guarantee throughput h t and low latency
Microsoft technical resources Microsoft Office Communications Server http://www.microsoft.com/communicationsserver Open Interoperability Program http://technet.microsoft.com/ucoip Quality of Experience Whitepaper http://download.microsoft.com/download/3/a/3/3a367b0d d /d l d/3/ /3/3 367b0d 4fff 44c5 9125 3ac5c037f195/OCS_QoE.doc Additional Technical Resources http://www.microsoft.com/uc/tech.mspx / /t h
Final thoughts Check out the website http://www.msucug.org Invite your colleagues! Future ideas? Email mnmsucug@live.com Next meeting April 23 rd Video Conferencing on OCS Platform